- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Networking
- >
- NC7131 team drops data when set to 2GB
Networking
1751763
Members
5389
Online
108781
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
тАО11-04-2005 02:16 AM
тАО11-04-2005 02:16 AM
NC7131 team drops data when set to 2GB
After updating to ver 8.10.0.0 of the teaming software teaming was set to auto config. Although the team runs at 2gb this appears to cause data timeouts and the server dropping from the network. I have provisionally forced the teaming to fault tolerance only so that only one NIC is running.
The NICs are connected to seperate cisco 4006 switches. My dilemma now is, is it the new teaming software at fault or a problem the cisco ios in that it won't support this type of teaming.
The NICs are connected to seperate cisco 4006 switches. My dilemma now is, is it the new teaming software at fault or a problem the cisco ios in that it won't support this type of teaming.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-05-2005 04:18 AM
тАО11-05-2005 04:18 AM
Re: NC7131 team drops data when set to 2GB
Kim:
Did you also update the driver(s) to 8.6.11.0:
http://h18023.www1.hp.com/support/files/networking/us/download/22806.html
(I am assuming you're running Windows Server 2003).
Make a great day!
Roger
Did you also update the driver(s) to 8.6.11.0:
http://h18023.www1.hp.com/support/files/networking/us/download/22806.html
(I am assuming you're running Windows Server 2003).
Make a great day!
Roger
Make a great day!
Roger
Roger
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-05-2005 07:33 AM
тАО11-05-2005 07:33 AM
Re: NC7131 team drops data when set to 2GB
Kim,
Automatic mode first tries 802.3ad port trunking using LACP. If the switches don't suppport it or the configuration doesn't support it (like being connected to two different switches), then Automatic mode will fall back to Transmit Load Balancing (TLB).
In some environments where NIC Teams are connected to dual switches and one of them is configured for Layer 3 switching (routing), then the routing engines ARP cache can end up being different than the switching engine's ARP cache - even though they are both on the same switch.
This behavior can be seen by pinging something on the same subnet (uses switching engine) and something on a different subnet (uses routing engine). If the device on the different subnet has problems but the device on the same subnet doesn't, then you are most likely experiencing this problem.
If you have this problem, you have two choices:
1. Use NFT (like you are doing)
2. Plug both NICs in the Team to the same switch (downside is you lose switch redundancy).
We are working on a resolution to this issue but it won't be out anytime soon.
If all the information above was useless because you aren't experiencing that problem, repost and we can continue troubleshooting. :-)
Oh, if you continue to have problems, I recommend running a DOS utility we install with teaming called HPNETSVY.EXE. This utility provides all the configuration information about your HP NICs and Teams. It's in your windows directory so you can run it from any directory path. Run the utility (with the configuration GUI NOT running) and send the output to a text file (hpnetsvy >output.txt). Attach the text file to your post if you need to request additional assistance.
Best regards,
-sean
Automatic mode first tries 802.3ad port trunking using LACP. If the switches don't suppport it or the configuration doesn't support it (like being connected to two different switches), then Automatic mode will fall back to Transmit Load Balancing (TLB).
In some environments where NIC Teams are connected to dual switches and one of them is configured for Layer 3 switching (routing), then the routing engines ARP cache can end up being different than the switching engine's ARP cache - even though they are both on the same switch.
This behavior can be seen by pinging something on the same subnet (uses switching engine) and something on a different subnet (uses routing engine). If the device on the different subnet has problems but the device on the same subnet doesn't, then you are most likely experiencing this problem.
If you have this problem, you have two choices:
1. Use NFT (like you are doing)
2. Plug both NICs in the Team to the same switch (downside is you lose switch redundancy).
We are working on a resolution to this issue but it won't be out anytime soon.
If all the information above was useless because you aren't experiencing that problem, repost and we can continue troubleshooting. :-)
Oh, if you continue to have problems, I recommend running a DOS utility we install with teaming called HPNETSVY.EXE. This utility provides all the configuration information about your HP NICs and Teams. It's in your windows directory so you can run it from any directory path. Run the utility (with the configuration GUI NOT running) and send the output to a text file (hpnetsvy >output.txt). Attach the text file to your post if you need to request additional assistance.
Best regards,
-sean
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