Posted by: Roger Crawford
HP NIC Teaming, HP Servers, Windows Updates
There are days you just wish you had not got up early. Wednesday morning I had a site that needed updated with Windows updates so I was around about 2:30 and started updating all the servers. This was the only time of day we could do this so I got them all done by 5:30 or so and I checked OWA and the TS Gateway and the different programs and it all looked good. So I thought anyway about 8 we got the call that users could not access their email or user files. I popped in and looked around and it looked good from the server perspective anyways.
So they sent someone on-site and they couldn’t find anything so they started a Server down call with MS and worked on this much of the day and into the night. I got a email from the tech on-site about 9 wondering if I could relieve him at midnight if nothing had changed. I checked and nothing had changed so I headed on-site and got their a little after midnight and the MS guy was dwelling on the networking of the server and I watched for while and I could see one of the NICs was showing as failed which when I looked more it was actually the Network Team that was broken. We got the HP updates and updated the server with the latest and greatest updates and then rebooted the server still no go so I suggested removing the team which the MS guy thought would be a good deal. We removed this and then set the right IP on one of the adapters and disabled the other rebooted the server and life was good. We got the virtual servers back online and everything working. Moral to the story is make sure you ahve your HP Server updated with the newest updates as some of the MS Updates are not compatible with older drivers and firmware and such.
Til later just Roger