|
So I guess management missed the it’s a cluster memo the
whole idea is to leave stuff up while you bounce the box? If you upgrade the driver I won’t tell anyone <g>. From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Medeiros, Jose Hi
Brian, Thank
you for the reply. Unfortunately, these are production database clusters and I
do not have the luxury of disabling and re-enabling the Nic interface on the
servers. Also the standard Support Pak that we use is 7.2, and I am not allowed
to install the latest and greatest drivers, and or patch’s on existing
servers (However our new builds are now using HP Support Pak 7.4). It seems
that some one at Microsoft’s marketing and Sales department told the
managers here at Intel that the servers can stay up for over a year with out
requiring a reboot ( We are only allowed to power down the servers once a year
during new years eve during our site power shutdown ). The
management here also seems to think that it’s okay to push out MOM server
monitoring agents & other patch’s with out a reboot, or having them
affect the existing applications such as Oracle and other third party applications
installed. (
These systems are replacing our VAX and VMS systems and are expected to have
the same uptime ) I
have been working with NT server since NT 3.51 and have always found that it
best to reboot a server every few weeks to clear hung DLL’s and Memory
leaks that may be occurring. But
thank you so much for your suggestion, I could not agree with you more. Jose
J From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brian Desmond Have you tried disabling and reenabling the interface? You could also upgrade to the 7.4 support pak and see what
happens? I’m running 7.3 and 7.4 heavily in production… From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Medeiros, Jose Greetings fellow AD
Guru’s, I have been trying to
trouble shoot some intermittent network connectivity issues with our Active Directory
domain controllers and our SQL database clusters, our network group doing the
network packet capture, believe that our HP Proliant
Dl-380 G3 servers using HP support pak 7.2 on 2003 server
have a bad network driver. Is there a way to clear
the Netstat -p tcp -s statistics with out rebooting a Windows 2003 server? Jose Medeiros MCP+I, MCSE, NT4 MCT 408-765-0437 Direct 408-449-6621 Cell |
RE: [ActiveDir] Is there a way to clear the Netstat -p tcp -s statistics with out rebooting Windows?
Title: Is there a way to clear the Netstat -p tcp -s statistics with out
rebooting Windows?
- [ActiveDir] Is there a way to clear the Netstat -p tcp -s s... Medeiros, Jose
- RE: [ActiveDir] Is there a way to clear the Netstat -p... Brian Desmond
- RE: [ActiveDir] Is there a way to clear the Netstat -p... Medeiros, Jose
- RE: [ActiveDir] Is there a way to clear the Netsta... Brian Desmond
- Re: [ActiveDir] Is there a way to clear the Netsta... Al Mulnick
- RE: [ActiveDir] Is there a way to clear the Netstat -p... Jonathan Meyer
- RE: [ActiveDir] Is there a way to clear the Netstat -p... Hutchins, Mike
- RE: [ActiveDir] Is there a way to clear the Netstat -p... Medeiros, Jose
- RE: [ActiveDir] Is there a way to clear the Netstat -p... Medeiros, Jose
- RE: [ActiveDir] Is there a way to clear the Netsta... Brian Desmond
- RE: [ActiveDir] Is there a way to clear the Netstat -p... Medeiros, Jose
- RE: [ActiveDir] Is there a way to clear the Netstat -p... Medeiros, Jose
