Timeline for Cisco Nexus vPC LACP bonding with server issue
Current License: CC BY-SA 4.0
20 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 17, 2020 at 8:51 | history | edited | CommunityBot |
Commonmark migration
|
|
| Mar 6, 2020 at 9:07 | comment | added | Yogesh Bangar | Please share the VPC configuration of 3K and 9K | |
| Jan 11, 2019 at 11:35 | comment | added | Marc 'netztier' Luethi |
You may also want to check if lacp suspend-individual is active on port-channel interfaces by default on that switch. I found it to be active by default on N3K-3164Q-40GE with 7.0(3)I4(6). This gave the server guys a hard time bootstrapping their server, because the bonding driver isn't running during all phases of the setup (or boot) phase, and the port remained suspended. I had to turn it off for all port-channel objects (no lacp suspend-individual) to allow the ports to come up. Note that this might be a bad idea for inter switch links, but for edge ports to servers it is acceptable.
|
|
| Jan 11, 2019 at 11:20 | answer | added | screenie | timeline score: 0 | |
| Nov 10, 2018 at 18:00 | history | tweeted | twitter.com/StackNetworkEng/status/1061317692169297921 | ||
| Nov 9, 2018 at 16:57 | vote | accept | Satish | ||
| Nov 6, 2018 at 22:00 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Oct 7, 2018 at 21:00 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Sep 7, 2018 at 20:00 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Aug 8, 2018 at 19:00 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jul 9, 2018 at 18:47 | answer | added | Satish | timeline score: 2 | |
| Jul 9, 2018 at 17:42 | comment | added | Satish | frustrated now, look like its not VLAN issue, i did same thing on other server and it didn't work :( still digging | |
| Jul 9, 2018 at 17:06 | comment | added | Satish |
I found issue, on switch side i have configured switchport trunk allowed vlan 10,20,30 but on server side i only configured VLAN 10,20 it was the issue, look like LACP negotiating VLAN also, How to stop VLAN negotiation on LACP, reason we set multiple VLAN on trunk so it will allow us to setup server dynamically and we don't need to go to every switch and adjust VLAN, Anyone know how to make it work?
|
|
| Jul 9, 2018 at 15:41 | comment | added | Satish |
@Zac67 I have updated output of linux side boding its saying Dynamic link aggregation so does that means auto right? as soon as i set channel-group 1 mode on it brought up vpc but server not pinging
|
|
| Jul 9, 2018 at 15:39 | history | edited | Satish | CC BY-SA 4.0 |
added 712 characters in body
|
| Jul 9, 2018 at 15:28 | comment | added | Zac67♦ | Make sure you've got active LACP configured on at least one side - a passive-passive LACP trunk won't come up (but should as a single interface). | |
| Jul 9, 2018 at 14:48 | history | edited | Satish | CC BY-SA 4.0 |
added 1609 characters in body
|
| Jul 9, 2018 at 12:25 | comment | added | Satish |
In logs i am not seeing anything interesting, all standard logs IF up IF down, should i need to increase logging, if you then do you know what logging level i need to set?, i will try to remove bpduguard and try will update you result soon
|
|
| Jul 9, 2018 at 6:26 | comment | added | Zac67♦ |
What does the log show when the vPC is first brought up/the server is booted? My guess is there's a BPDU from the server and the bpduguard option shuts the bond.
|
|
| Jul 9, 2018 at 5:05 | history | asked | Satish | CC BY-SA 4.0 |