- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- NIC team oddity !
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-06-2006 09:00 PM
тАО11-06-2006 09:00 PM
I have a BL20pG2 that's in an enhanced
enclosure that, for some months, has quite
happily run with 3 NIC's in a Fail on Fault
team.
All of a sudden the server cannot be contacted
and after an iLO logon was found to have the
team (in network connections)to be disabled,
but all 3 NICs in an OK and operating state.
There's nothing in any of the logs (either
Microsoft or HP) to suggest where to start.
Anyone with any ideas ?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-07-2006 03:55 AM
тАО11-07-2006 03:55 AM
Re: NIC team oddity !
NIC Driver ?
NCU Release ?
Reseat NIC ?
Dissolve Team Test one Port at time
Update SW if needed
http://h18023.www1.hp.com/support/files/server/us/index.html
swap card from another server for test
you have two NIC on the Mezzanine and one on the board
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-07-2006 08:45 PM
тАО11-07-2006 08:45 PM
Re: NIC team oddity !
issue. You can't reseat NIC's in a BL.
All the nic connections, according to
windows were OK. It was just the team
connection that was disabled. The NCU is
8.37.00.
NCU will let me look at the team but the
actual connection is disabled so the server
is off the network !!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-08-2006 05:03 AM
тАО11-08-2006 05:03 AM
SolutionGet the latest drivers for the Nic(9.52 at the time) , latest NCU(8.40 at the time) , and the firmware for the NIC.
1. Go to the network connections, into the network control panel(where you see you ipx, ip and other protocols) uninstall Network Config Util for Both Nics.
2. Go to Device Manager and remove both nics.
3. Reboot the server (Exit any automatic install on boot up)
4. Execute the latest Drivers File.
5. Execute the latest NCU setup.
6. Run the latest F/W upgrade if necessary
7. Configure the cards.
It's important to do the steps above in order, or additional networking issues may be seen
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-08-2006 07:00 PM
тАО11-08-2006 07:00 PM
Re: NIC team oddity !
It turned out to be nothing to do with
drivers or firmware !
Root cause is still unknown, but the fix,
as jaragon pointed out, is to remove the
teaming from the nic properties, various
reboots and then a reinstall of the team
under NIC properties :-)
Still haven't found what caused the Team
connection to become disabled but ..... at
least my mail bridge head is now back on the
air - hurray