- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Re: Network Teaming adapter fails to initialize
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
тАО08-07-2006 10:05 PM
тАО08-07-2006 10:05 PM
Network Teaming adapter fails to initialize
We use NFT with preference order teaming on Proliant DL385 servers. When the server is restarted with only one LAN port physically connected to the switch, the Teaming adapter fails to initialize (it tries to acquire an IP address via DHCP instead of using it's configured fixed IP address!?).
The OS is Windows Server 2003 R2 and the network configuration utility version is 8.37 (also tried 8.35).
Switches are Cisco 2960 and 3750, speed/duplex settings fixed to 1000/full on both switch and network adapted.
pls advise
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-09-2006 08:02 AM
тАО08-09-2006 08:02 AM
Re: Network Teaming adapter fails to initialize
Did you set the static IP on the Local Area Connection for the virtual NIC that was created after you setup the team? It's called "HP Network Team #xxx" under "Device Name" in "Network Connections".
If you set a static IP on the physical NIC itself, that static setting is NOT used by the team. That static setting is only used if that physical NIC is removed from the team.
Best Regards,
OB1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-09-2006 10:55 AM
тАО08-09-2006 10:55 AM
Re: Network Teaming adapter fails to initialize
Anyway back to the original issue --- How did you team your NICs? What is the topology? I assume PSP is installed?
I guess if NIC teaming is based on the MAC address, and you only unplug the 2nd NIC within a minute for testing just before the reboot, then the Cisco switch would have an entry on its MAC table and may prevent the 1st NIC to re-advertise the logical MAC address in order to reclaim itself as the source. If that is the case, try clear mac-address-table on your switch.
There has been discussion recently and may be ideal to have a look
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1036761
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1014438&admit=-682735245+1155162179288+28353475
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-09-2006 03:34 PM
тАО08-09-2006 03:34 PM
Re: Network Teaming adapter fails to initialize
About the MAC/CAM address table...
I'm not sure how an erroneous/stale CAM table entry would cause a NIC in a server to switch from a static IP configuration to using DHCP. I could see a stale CAM entry causing DHCP to timeout and then the NIC would fall back to Microsoft's auto IP, but not the other way around.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-09-2006 07:25 PM
тАО08-09-2006 07:25 PM
Re: Network Teaming adapter fails to initialize
Just to clarify things a bit more:
We use PSP 5.51.
The Teaming adapter (fault tolerance with preference order) is configured with a fixed IP address. The protocol bindings on the physical adapters are indeed grayed out (like it should).
No change in behaviour when enabling/disabling portfast on the Cisco switch.
We can reproduce this error on all our servers: just remove one network cable and restart the server and the teaming adapter seams to switch to DHCP mode (although it doesn't get/ask an IP address... the status remains on 'acquiring IP address' forever).
When manually disabling/enabling the teaming adapter (using Windows), it all works fine again (until the next reboot).
Another thing I discovered. It only happens when disconnecting the least preferred NIC!