Snap 410 Dropping off Network w/ Reserved IPs

[teastman]

I am having a repeated issue with network behavior for my Snap Server. It “falls” off the network periodically and we can’t see it.

Historical info;

Snap Server 410 with Guardian OS 4.4.049
1 Gig of Adaptec Ram.
1 terabyte model
Networked to a Windows SBS 2003 network.

It HAD been okay from about March until the July 4th weekend storms. It needed to be completely reconfigured and have it’s system settings restored from a “disaster recovery” image. Before the July 4th crash the IP addresses reserved for the SNAP (from Server1) were 192.168.1.200 & 192.168.1.201 (it has two NICs). But now the Server1 DHCP console shows them as Reserved but “Inactive”.

The SNAP server has those IPs configured as “Static” such that it doesn’t have to lease IPs from the Server1 pool (that’s an Adaptec recommendation). And this is my confusion. If the Snap Server has those as Static and the Server1 has those as reserved – why would the SNAP be dropping off the Network?

I will be calling Snap’s illustrious tech support here in a couple hours but I wanted to ping this off you guys first. If the syswrapper will be helpful to you guys I might be able to figure out how to upload it.

I have to get this nailed down.

Thanks!
tje

[blue68f100]

Having an IP reserved and the server set as Static could cause some problems. I use reserved exclusively. If I have to use a static I assign it outside of the DHCP range. So use either or but not both. But I have seen both used with no problems, too. But if your DHCP is having a problem and users can access the snap directly a static will maintain access if it's not a hardware problem. Set one as static and the other as DHCP then see which one is and/or dropping.

Snap's tech will probably tell you to re-install the OS. My experience if it's corrupted you really need to do a clean install. Which will wipe all data off of the HD's.

[teastman]

Hmmm Okay. Some of that makes sense. This actually was a clean install done over the phone with Adaptec Tech support.

I am wondering if you are on to something with reservations. I am running a Windows SBS 2003 server as my company's DHCP server. Most "reserved" IP addresses actually are within the range of the DHCP leasing pool.

The "Default" setting off the shelf for the 410 is to have both of these NICs set as DHCP - not static. Which is why I'm wondering why the phone support said to do that.

Then do you think it would it make sense to "reserve" those IPs at the Win SBS 2003 DHCP server but then set the Snap 410 to DHCP vs static?

I really don't mean to be obtuse here but I don't do this for a living - I'm just a CAD grunt.

[blue68f100]

I would set 1 as static but outside of the DHCP range. Then set the other using the reserved DHCP (within the DHCP server). Then when/if it goes down test (ping) from both IP's. This may help you locate where the problems is.

I personlly like the reserved IP, mainly because I can move it to another subnet and and not have to change anything.

If another piece of hardware decides to use the same IP address as your servers, it will knock it off line. I had a person deside to make up his own IP address and took down a security server. He did receive a chewing, and did not take long to trace where ihe was coming from on a site with 2000+ pc's. The advantage of managed switches and having a complete map of the site.

ps, I don't do this for a living either. (home users)