Not really but since the network is going to be down for a few minutes anyway, why not reboot the
servers (clean up memory, etc).  Our servers boot pretty quick.  I have the upgrade/reboot down to only a 2 minute network outage for the reslife network and wireless.  We run in Virtual Gateway mode.

John



John Truelove
Network Engineer - CCNP
Indiana State University
210 N 7th Street
Office of Information Technology
Rankin Hall Rm 054
Terre Haute, IN 47809
812-237-4921
>>> [log in to unmask] 10/27/05 9:31 AM >>>
I've seen no reason yet to reboot these boxes.  They've been up since 
the start of school.  BTW: Is there any reason to reboot when you do an 
upgrade?  We've moved from 3.5.0, 3.5.2, 3.5.3, 3.5.3.1, 3.5.5 all 
without a reboot (just service perfigo stop, upgrade, service perfigo start)

# uptime
 10:20am  up 92 days, 19:06,  2 users,  load average: 1.20, 1.53, 1.58

Erik Ball - CCNA GSEC
-----------------------------------
Xavier University ISS Dept.
Network Engineer
(513) 745-1970 || Fax: 745-4329



John Stauffacher wrote:

> Aaron Havens wrote:
>
>> The question came up because we were having problems with one of our 
>> VLANs. Users on that VLAN can pull a DHCP address but can't go 
>> anywhere else on the network. (We use DHCP relay) The Agent has the 
>> Login option grayed out. If the users computer is moved to another 
>> CCA managed vlan it works fine.
>>
>> The networking group said they haven't changed anything and we 
>> haven't changed anything on our end with the server so I was hoping 
>> maybe the problem could be resolved by rebooting.
>>
>> We currently have had 92 days of uptime with no problems. However 
>> when I went to reboot the fail over servers I found that one of them 
>> did not have a link on the switch. So now we are troubleshooting that.
>>
> #>uptime
> 9:08am  up 49 days, 19:03,  1 user,  load average: 0.11, 0.10, 0.08
> #>cat /perfigo/build
> VERSION=3.5.5
> NAME=Clean Access Manager
> DATE=2005/08/31
>
> Last reboot was install of 3.5.5
>