ProCurve / ProVision-Based
cancel
Showing results for 
Search instead for 
Did you mean: 

VLAN's over LACP

Dave Baddorf
Occasional Advisor

VLAN's over LACP

I am clearly missing something.  And I hope that someone can point it out to me... :-)

 

I can't get my VLAN 10 traffic to pass between switches.

I have two ProCurve 3500 (J8693A) switches.  Both have port 1-4 connected as an LACP trunk and tagged VLAN 10 traffic is configured on Trk1.  When both my primary Cisco Wireless Controller (ports 41 + 42)  and primary Cisco ASA (port 43) are on on the same switch they can pass wireless traffic (VLAN 10).  However when the Cisco ASA fails over to the secondary ASA unit, which is on the 2nd HP Switch (port 43), the VLAN 10 wireless traffic no longer passes between the Wireless Controller and the ASA.  Can anyone please point me in the right direction to fix this?  Or even on what to try next?  I'll be glad to provide further info if it would be helpful...

much thanks!  dave

 

Partial Switch Configurations:

trunk 1-4 Trk1 LACP
vlan 1
  name "DEFAULT_VLAN"
  untagged 5-48
  ip address 172.25.24.69 255.255.0.0
  no untagged Trk1
exit
vlan 10
  name "Warehouse"
  tagged 41-43,Trk1
  no ip address
exit

 

Show Trunk:

Port | Name Type | Group Type
---- + -------------------------------- --------- + ----- -----
1 | core-trunk 100/1000T | Trk1 LACP
2 | core-trunk 100/1000T | Trk1 LACP
3 | core-trunk 100/1000T | Trk1 LACP
4 | core-trunk 100/1000T | Trk1 LACP

 

Show LACP:

PORT LACP TRUNK PORT LACP LACP
NUMB ENABLED GROUP STATUS PARTNER STATUS
---- ------- ------- ------- ------- -------
1 Active Trk1 Up Yes Success
2 Active Trk1 Up Yes Success
3 Active Trk1 Up Yes Success
4 Active Trk1 Up Yes Success

 

Show VLAN 10:

Status and Counters - VLAN Information - Ports - VLAN 10

VLAN ID : 10
Name : Warehouse
Status : Port-based
Voice : No
Jumbo : No

Port Information Mode Unknown VLAN Status
---------------- -------- ------------ ----------
41 Tagged Learn Up
42 Tagged Learn Up
43 Tagged Learn Up
Trk1 Tagged Learn Up

 

Full Switch Config:

Running configuration:

; J8693A Configuration Editor; Created on release #K.12.57

hostname "ProCurve 3500 Swtch #2"
snmp-server contact "xxxxx"
snmp-server location "Data Center"
module 1 type J86yyA
module 2 type J86xxA
interface 25
flow-control
exit
interface 26
flow-control
exit
interface 27
flow-control
exit
interface 28
flow-control
exit
interface 29
flow-control
exit
interface 30
flow-control
exit
interface 31
flow-control
exit
interface 32
flow-control
exit
interface 33
flow-control
exit
interface 34
flow-control
exit
interface 35
flow-control
exit
interface 36
flow-control
exit
interface 37
flow-control
exit
interface 38
flow-control
exit
interface 39
flow-control
exit
interface 40
flow-control
exit
interface 41
flow-control
exit
interface 42
flow-control
exit
interface 43
flow-control
exit
interface 44
flow-control
exit
interface 45
flow-control
exit
interface 46
flow-control
lacp Passive
exit
interface 47
name "Fiber"
flow-control
exit
interface 48
flow-control
exit
interface 1
name "core-trunk"
exit
interface 2
name "core-trunk"
exit
interface 3
name "core-trunk"
exit
interface 4
name "core-trunk"
exit
interface 5
lacp Active
exit
interface 6
lacp Active
exit
interface 7
lacp Active
exit
interface 8
lacp Active
exit
interface 9
lacp Active
exit
interface 10
lacp Active
exit
interface 11
lacp Active
exit
interface 12
lacp Active
exit

 


trunk 1-4 Trk1 LACP
ip default-gateway x.x.x.x
snmp-server community "public" Unrestricted
vlan 1
name "DEFAULT_VLAN"
untagged 5-48
ip address x.x.x.x 255.255.0.0
no untagged Trk1
exit
vlan 10
name "Warehouse"
tagged 41-43,Trk1
no ip address
exit
jumbo ip-mtu 9000
jumbo max-frame-size 9018
spanning-tree
spanning-tree Trk1 priority 4

2 REPLIES
Dave Baddorf
Occasional Advisor

Re: VLAN's over LACP

   I tried some more experimenting.  I connected two laptops running linux and configured them to use VLAN 10.  When both laptops are connected to the same switch they can ping each other.  But if they are on separate switches, then they can't ping each other.  It appears like VLAN 10 traffic just isn't crossing the two HP Switches.  But I thought that I have the configuration allowing VLAN traffic to pass through?

   I wonder whether I just stumbled upon something.  While these are the "core" switches there are other "access" switches, doing a "show spanning-tree" seems to indicate that these two switches aren't passing traffic through this LACP trunk (one says Trk1 blocking).  Since I am not trunking VLAN 10 traffic anywhere else but between these two "core" switches I think my problem is with spanning-tree.  I'll need to dig into this further when I'm back next week.  

Richard Brodie_1
Honored Contributor

Re: VLAN's over LACP

Since I am not trunking VLAN 10 traffic anywhere else but between these two "core" switches I think my problem is with spanning-tree.

 

Your problem may be that you assume that spanning-tree cares about VLANs, and that you can make a loop as long as you can't traverse it on one VLAN. That's more or less true for PVST but not for RSTP or MSTP.