I set up my wlc virtual interfaces, my dhcp scopes etc... now i just want to make sure i dont interrupt things on our core switch by addidn a trunck in the wrong place etc. here is a pic of our vlans on a procurve switch. can i just add the port H20 as a trunk or do i have to make A1 a trunk also since that connects directly to our router? will i have to change anything on the other vlan?
i only ask this because im working remotely because of surgery and if something needs to be physically reset, theres no one to do it.
Not a fan of GUI's on switches but in this case, you can select the port and theres a menu to change to trunk, lacp or something else.. so only the port from the WLC to the core switch would need to be a trunk? id probably want to change the mode to 100 full duplex too... there were tons of errors on this port.
the guest vlan is going to be 172.22.5.0/24 and use itself for dhcp.
i added a subinterface to our router for the new vlan 5. on our core switch (connected directly to the router) i was wondering if i need to only trunk the port the WLC is connected to (H20) of if i have to do that AND the port that connects to the router.(A1). and if i have to trunk A1, will that cause a problem with the native vlan the rest of the company runs on?
oh sorry, physical is very basic. 2 sites connected via EVPL (router on a stick at each location) Site 1 has the core switch, the WLC is connected to port H20 and the switch is connected to the router via port A1. my question is, does A1 have to be a trunk also? Along with H20? Also, the untagged traffic will pass without issue, correct?
Like mentioned above WLC is an Layer-2 device, so your uplink switch needs to be configured as Trunk to allow all vlan traffic from & to between WLC and the switch. If you need routing through external router from that switch & WLC then yes you need to configure trunk and sub interfaces on the router.