Installing GuardOS 3.1 to 4200 issue

[snapwall]

G'day folks.

Am a newbie to this forum and to SNAP server and any assistance is most appreciated.

I just bought a new snap server 4200 from auction and despite being listed as "new" it was semi used and only came with a user guide CD which just happen to have the GuardianOS 3.1 .gsu file, SNAP MGR program, and some documentation files.

I booted up the snap 4200 server and it halts with the following message:

"Uncompressing Linux.....OK, Booting Kernel"

My limited knowledge tells me I am screwed here... The question I have are:

1) Is there a way to upload the .gsu so that I can get the SNAP server up and running? What Linux platform do I have to lay to get it kick started? If I can jump start that car, I mean snap server and load the .gsu, I am hoping it should work..

2) Do I need to get a separate Snap server Assistant program to load the .gsu file?


Please note, I am not requesting for a free copy of any software. I am willing to purchase from Snap reseller if there is no solution and if that is the last resort.....

Thanks in advance!

Best Rgds

Snap-hit-a-wall

[blue68f100]

Well, If it is booting you are not screwed. The older units stored the OS in flashram. So if you installed drives, it should come up. The model you have may not be compatable with the SnapOS. The Guardian OS had more automated function. You may be able to download what you need from SanpAppliance = Adaptec. I can send you assist but I don't know if it will work with guardian. The Snap Manager should be the same as assist.

Most servers are set with a static IP. Clearing the network settings should reset it to DHCP.

Check the manual and see what the reset procedure is for resetting the network and password or all. What you need should be on the CD. The old snaps when reset would only use DHCP in a NetBuae system, the reason for assist. The newer models supports more protcall, and may show up without assist. Look at your router log and see. If you are mac filtering you should either add the 4200 or drop it off till you get it setup.

The older units use a modified FreeBSD Unix for the base. The manager program can also be used for upgrading the os of needed.

[snapwall]

THanks blue68f100! You are a champ!

Got my SNAP 4200 working again. Just so that others can benefit from your advise, I have summarised what I have done to get it working:

Problem:
When my 4200 was started, it started booting and seemed like it hanged with the following message:

"Uncompressing Linux.....OK, Booting Kernel"

Resolution:
Seems like this is the correct display for 2.5.xx version GuardianOS...in fact when I upgraded to 3.1, there is new display that specific states that "This device cannot be managed by keyboard/video/mouse..." and to use the web interface to manage SNAP server.

Anyway, here are steps I took to get it back up again.


1. Issue most likely related to unidentified/unconfigured IP Address. I have setup my DHCP server to reserve the MAC address of the SNAP Server 4200 specifically to an IP Address.

[Note: From the manual, Snap Servers are preset to acquire an IP address from a DHCP server. If no DHCP server is found on the network, the Snap Server defaults to an IP address of 10.10.10.10, and you may not be able to see the server on your network. You can discover a Snap Server using either the default server name or the Snap Server Manager (SSM) utility. Use the server name method if you are installing one Snap Server on the network. Use SSM if you are installing two or more Snap Servers, or if your network does not have a DHCP server.]

2. I rebooted the SNAP Server by pressing t

5. From the SNAP MGr, I launched the Web Admin. Selected Maint->Update and chose the GuardianImage.gsu file to upgrade to 3.1 version.

So it seems like everything working just fine.

Thanks again blue68f100, for making my 1st experience with Snap real smooth experiene!

regards
snapwall.