If my post was useful, please Accept Solution and Give Kudos.
Ideas expressed here are solely my own and not necessarily that of HPE Aruba.
Original Message:
Sent: Mar 13, 2024 09:45 AM
From: t.antony
Subject: Device not getting dhcp or network from trunk
Thank you. It turned out to be something silly on my part :)
I mislabeled the port and I was tagging VLAN 6 to the wrong one.
But after double checking the using the sh lldp ... command, and sh mac-add | in .., I figured out the right uplink port, and everything works now.
Original Message:
Sent: Mar 12, 2024 03:49 PM
From: 802.zak
Subject: Device not getting dhcp or network from trunk
If you look at LLDP does everything line up? Anything missing or labeled?
Based on your config snippets the tags should be all you need. Do you have Spanning Tree enabled? Not that you need to necessarily, but it could be something getting in the way.
------------------------------
If my post was useful, please Accept Solution and Give Kudos.
------------------------------
Zak Chalupka
Principal Engineer - HPE Aruba
ACDX | ACMP | ACSP | ACCP
wifizak@hpe.com
------------------------------
Ideas expressed here are solely my own and not necessarily that of HPE Aruba.
Original Message:
Sent: Mar 12, 2024 03:40 PM
From: t.antony
Subject: Device not getting dhcp or network from trunk
Thank you, I ran the first command, and I see interface 17 for VLAN 6, but nothing on the new building switch for VLAN 6.
'Core-24-lower' It should be showing Port 25 since that's my uplink to the other switch.
Core-24-lower# sh mac-address vlan 6 Status and Counters - Address Table - VLAN 6 MAC Address Port ----------------- ----- 00005e-000134 17Newbldg-Core# sh mac-address vlan 6 Status and Counters - Address Table - VLAN 6 MAC Address Port ----------------- -----
Original Message:
Sent: Mar 12, 2024 03:29 PM
From: 802.zak
Subject: Device not getting dhcp or network from trunk
A good place to start troubleshooting maybe to look for MAC addresses on both switches.
Run a "show mac-address vlan 6" on both switches, compare the tables - specifically look to see if your downstream laptop MAC addresses are populating on your Core.
Run a "show lldp info remote-device" to ensure you have the switches and interfaces correct - also to be sure you didn't miss any aggregation switches.
------------------------------
If my post was useful, please Accept Solution and Give Kudos.
------------------------------
Zak Chalupka
Principal Engineer - HPE Aruba
ACDX | ACMP | ACSP | ACCP
wifizak@hpe.com
------------------------------
Ideas expressed here are solely my own and not necessarily that of HPE Aruba.
Original Message:
Sent: Mar 12, 2024 02:35 PM
From: t.antony
Subject: Device not getting dhcp or network from trunk
This is the port setting on my switch unlinking from WatchGuard interface 2 (VLAN 6 Tagged). If I plug in a laptop on port 18, the laptop gets connection to VLAN 6. Also, I'm testing on both switches with the same laptop and Ethernet cable. I also tried a different port on the new switch Untagged VLAN 6, and I still don't get an IP address.
Core-24-lower# sh vlans Status and Counters - VLAN Information Maximum VLANs to support : 256 Primary VLAN : DEFAULT_VLAN Management VLAN : VLAN ID Name | Status Voice Jumbo ------- -------------------------------- + ---------- ----- ----- 1 DEFAULT_VLAN | Port-based No No 4 CNC WiFi | Port-based No No 5 CMM | Port-based No No 6 Bechdon | Port-based No No 100 voice | Port-based Yes No 302 wireless | Port-based No NoRunning configuration:interface 17 name "Bechdon VLAN Uplink" tagged vlan 6 exitinterface 18 name "Bechdon Test Port" untagged vlan 6 exitinterface 25 name "Uplink to new bldg" tagged vlan 1,4-6,100,302 exit
This is the switch at new building. If I plug in a laptop on port 15, the laptop gets no connection to VLAN 6.
Newbldg-Core# sh vlans Status and Counters - VLAN Information Maximum VLANs to support : 256 Primary VLAN : DEFAULT_VLAN Management VLAN : VLAN ID Name | Status Voice Jumbo ------- -------------------------------- + ---------- ----- ----- 1 DEFAULT_VLAN | Port-based No No 4 CNC Wireless | Port-based No No 5 CMM | Port-based No No 6 Bechdon | Port-based No No 100 Voice | Port-based Yes No 302 Wireless | Port-based No NoRunning configuration:interface 15 name "Steve" untagged vlan 6 exitinterface 49 name "Uplink" tagged vlan 1,4-6,100,302 exit
Original Message:
Sent: Mar 12, 2024 02:28 PM
From: t.antony
Subject: Device not getting dhcp or network from trunk
This is my first time creating a VLAN interface on the Watchguard. But I have have interface 2 as type VLAN, and then I have a VLAN "Bechdon VLAN" associated with interface 2. Below are also my network and VLAN settings.
VLAN is set to Tagged on watchguard. Then I have a cable connecting from interface 2 on WG to interface 17 on an Aruba switch Tagged VLAN 6. Then if I assign interface 18 on the same Aruba switch as Untagged VLAN 6, I get a DHCP address like I'm supposed to. We have another building, then I already have existing networks already there which I setup. So just like all the existing network, I have interface 25 on the switch Tagged VLAN 6 among the existing ones, then on the switch at new building Tagged VLAN 6 on the uplink port.
This is where the problem and confusion is. When I assign a port on the switch at new building Untagged VLAN 6, I don't get an IP address, and even if I setup a static IP on the "Bechdon VLAN", I can't ping anything. I have VLAN 6 on all the switches, so its not because its missing VLAN 6.
What am I doing wrong? All my switches are Aruba.
This is my configuration.
Interface 2 on Watchguard VLAN 6 (Tagged) to interface 17 (Tagged VLAN 6) on Aruba switch. Interface 18 (Untagged VLAN 6), I get an IP address on VLAN 6.
Interface 25 on the same switch as above (Tagged VLAN 6) to interface 49 (Tagged VLAN 6) on the new building switch. Interfaces 25/49 are my existing uplink ports for other networks also, and these are working fine.
Then interface (Unagged VLAN 6) on a port on the new building switch, the laptop doesn't get a DHCP.