mipetrin Wed, 02/01/2012 - 00:34
User Badges:
  • Cisco Employee,

Hi Rajtilak,


There isn't enough information to determine if that would be the case. Ideally a NIC failure wouldn't cause a server reboot.


What server are you using?

What version of firmware are the servers running?

What type of NIC are you using?

What makes you think that the NIC failed?

Do you have any logs or screenshots of the errors?


Take this as a starting point and we can see where we go from here.


Thanks,

Michael

Rajtilak Sivaluri Wed, 02/01/2012 - 22:32
User Badges:



os : Windows 2003 SE.


Adapter Type: HP NC326m PCIe Dual Port Adapter


Version : 3.28.0


Please do let me know if you need any more information

mipetrin Thu, 02/02/2012 - 00:34
User Badges:
  • Cisco Employee,

Hi Rajtilak,


Seeing that this is an issue with a HP NIC, have you contacted HP support or posted on their forums for assistance? I couldn't tell if you were using a Cisco UCS server or not.


Basically you should check the NIC card, network cables and the upstream devices.


Further to this, a quick google search has many results with people experiencing this issue and what can be done to correct this.


http://www.google.com/search?q=nic+agent+connectivity+has+been+lost+for+the+nic+in+slot


If using a HP server, this following post may be of particular interest to you:


http://h30499.www3.hp.com/t5/Windows-2000/NIC-Agents-Error/td-p/3968293


Hope this helps you moving forward.


Thanks,

Michael

Actions

This Discussion