- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Networking
- >
- NIC Teaming to 4000M
Networking
1753746
Members
5079
Online
108799
Solutions
Forums
Categories
Company
Local Language
юдл
back
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
юдл
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО04-06-2006 01:44 AM
тАО04-06-2006 01:44 AM
NIC Teaming to 4000M
I have an issue with teaming to a ProCurve 4000M switch. The server is a ML350 G4 with a NC7760 and a NC7770 connected to a Procurve 4000M. The switch has firmware C.09.09. Both Nic's have the 8.39.1.0 driver. The server runs Windows 2000 SP4. The switch has two ports set to FE and the NIC's are teamed and IP addresses are assigned. Everything looks fine, however, when I connect the second NIC to the switch, the system goes to a crawl. I don't have an analyzer but it looks like the network might be getting flooded. In failover mode it works fine.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-06-2006 12:57 PM
тАО04-06-2006 12:57 PM
Re: NIC Teaming to 4000M
Bob:
NIC Teaming seems to be a frequent problem for a lot of admins and if you end up abandoning it, except for failover, don't feel so bad. For WinOSes it seems to be more problematic.
That being said you can try a few ideas to see if this will get Teaming to work properly.
1) You already mentioned it but yes, those using static IP addresses have more success with teaming. Stick with that strategy at least until the problem is solved.
2) Another tip that has worked well for me is to use a static speed for the server NICs. Do not use Auto Negotiate. It's a time waster. Set both NICs to 100 Mb/s Full Duplex. I'm not familiar with the 4000M but if you can login to it and check port speed do so. Make sure it is at 100Mb/s & full-duplex.
3) Teaming is very sensitive regarding DNS data. Two adapters must use the same DNS data. If out of sync Teaming can experience problems. To sync the adaptors
i) Disable teaming. Disable the second adaptor.
ii) At the command prompt
ipconfig 0 /registerdns
iii) Now enable the second adaptor and at the cmd prompt
ipconfig 1 /registerdns
iv) Re-enable teaming. See if this helps.
Using /registerdns will initiates manual dynamic registration for the DNS names and IP addresses that are configured at a computer.
see http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/ipconfig.mspx?mfr=true
You mentioned you are using Win2K. In the Start menu under Administrative Tools you should find Microsoft Network Monitor. Here you can see what packets are flying around your LAN.
Hope this helps.
Rob
NIC Teaming seems to be a frequent problem for a lot of admins and if you end up abandoning it, except for failover, don't feel so bad. For WinOSes it seems to be more problematic.
That being said you can try a few ideas to see if this will get Teaming to work properly.
1) You already mentioned it but yes, those using static IP addresses have more success with teaming. Stick with that strategy at least until the problem is solved.
2) Another tip that has worked well for me is to use a static speed for the server NICs. Do not use Auto Negotiate. It's a time waster. Set both NICs to 100 Mb/s Full Duplex. I'm not familiar with the 4000M but if you can login to it and check port speed do so. Make sure it is at 100Mb/s & full-duplex.
3) Teaming is very sensitive regarding DNS data. Two adapters must use the same DNS data. If out of sync Teaming can experience problems. To sync the adaptors
i) Disable teaming. Disable the second adaptor.
ii) At the command prompt
ipconfig 0 /registerdns
iii) Now enable the second adaptor and at the cmd prompt
ipconfig 1 /registerdns
iv) Re-enable teaming. See if this helps.
Using /registerdns will initiates manual dynamic registration for the DNS names and IP addresses that are configured at a computer.
see http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/ipconfig.mspx?mfr=true
You mentioned you are using Win2K. In the Start menu under Administrative Tools you should find Microsoft Network Monitor. Here you can see what packets are flying around your LAN.
Hope this helps.
Rob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-07-2006 02:39 AM
тАО04-07-2006 02:39 AM
Re: NIC Teaming to 4000M
Thanks. Give me something to do this weekend while everyone is off the system. I will see if it helps.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP