- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- ProLiant DL380G2 ./. Link Aggregation issue
ProLiant Servers (ML,DL,SL)
1753519
Members
3906
Online
108795
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
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
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
08-06-2010 06:48 AM
08-06-2010 06:48 AM
ProLiant DL380G2 ./. Link Aggregation issue
Hello community,
we have re-installed a ProLiant DL380G3 with Windows Server 2003 R2 SP2.
The server is connected to a Juniper EX4200 Switch via both onboard NICs NC3163.
Driver version is 8.0.43.
We are running the NIC teaming software to have both NICs connected to the Switch via 802.3ad Link Aggregation.
On the switch, the LACP is set to "active".
The IP address for the virtual NIC of the teaming software is set fixed, no DHCP.
This setup works fine with 4 other identical servers which were set up 2 years ago but not with this one:
Our problem:
When we reboot the server, the virtual NIC is searching for a IP address - which shouldn't be the case as it is set static.
When this happens the NIC teaming tool shows the LAG to be fine/operational.
Same on the switch, LAG diagnostic shows all to be fine.
When this happens we see a message in the eventlog telling:
Team ID: 0
Aggregation ID: 0
Team Member ID: 0
PROBLEM: 802.3ad link aggregation (LACP) has failed. ACTION: Ensure all ports are connected to LACP-aware devices.
Before reinstalling the server worked fine with the settings on the switch which were not changed in any way.
We suspect the NIC teaming software version to be the problem but unfortunately I wasn't able to find out which version is installed on the older, fine working servers.
Any help would be appreciated.
thanks and kind regards
Mike
we have re-installed a ProLiant DL380G3 with Windows Server 2003 R2 SP2.
The server is connected to a Juniper EX4200 Switch via both onboard NICs NC3163.
Driver version is 8.0.43.
We are running the NIC teaming software to have both NICs connected to the Switch via 802.3ad Link Aggregation.
On the switch, the LACP is set to "active".
The IP address for the virtual NIC of the teaming software is set fixed, no DHCP.
This setup works fine with 4 other identical servers which were set up 2 years ago but not with this one:
Our problem:
When we reboot the server, the virtual NIC is searching for a IP address - which shouldn't be the case as it is set static.
When this happens the NIC teaming tool shows the LAG to be fine/operational.
Same on the switch, LAG diagnostic shows all to be fine.
When this happens we see a message in the eventlog telling:
Team ID: 0
Aggregation ID: 0
Team Member ID: 0
PROBLEM: 802.3ad link aggregation (LACP) has failed. ACTION: Ensure all ports are connected to LACP-aware devices.
Before reinstalling the server worked fine with the settings on the switch which were not changed in any way.
We suspect the NIC teaming software version to be the problem but unfortunately I wasn't able to find out which version is installed on the older, fine working servers.
Any help would be appreciated.
thanks and kind regards
Mike
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