I am PoC'ing Aruba 2540s as a cheaper replacement for our L2 devices (currently a majority Catalyst 2960s). The CLI has been similar to what I'm used to in Cisco, but am having what I believe may be a spanning tree issue.
The issue: The Aruba (port 48) is directly plugged into my core (Catalyst 9300 port 24), but fails to come online as a trunk. I believe my understanding is correct in that Aruba's "trunk" equivalent is "tagged". However, the only way I can get connectivity up is if I switch the Aruba port from "tagged" to "untagged". As soon as I do that, I'm up and running.
This is what the link on the Cisco side looks like: interface GigabitEthernet1/0/24 description to HP Aruba 2540 switchport trunk native vlan 2 switchport mode trunk
And on the Aruba side: vlan 2 name "Management" tagged 47-52 untagged 2,44 ip address 192.16.1.14 255.255.255.0
Again, if I remove the range of tagged and add 48 to untagged, it works just fine.
If I try to bring the link up while while 48 is tagged on the Aruba, I see this pop up in the Aruba log: I 11/21/20 07:57:52 03816 stp: VLAN 2 - Root changed from 4096: 9cafca-14ff80 to 32768: (this device) W 11/21/20 07:57:52 03813 stp: VLAN 2 - Starved for a BPDU on port 48 from Designated Bridge 32768:5ca62d-acfb80
What's interesting is that I see no corresponding logs on the Cisco side, and checking its spanning tree shows no change in the root bridge.
This is the only corresponding thing I see on the cisco side: Nov 21 07:59:21.702: %LINK-3-UPDOWN: Interface GigabitEthernet1/0/24, changed state to up Nov 21 07:59:23.706: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/24, changed state to up
On the Cisco core, spanning tree mode is rapid-pvst. On the Aruba side, here is the spanning tree config: spanning-tree mode rapid-pvst spanning-tree priority 15
I feel like I must be missing something simple, but as I'm new to Aruba, I'm unsure exactly what that may be.
Many thanks in advance!
No comments:
Post a Comment