07-21-2014 09:23 AM - edited 07-21-2014 09:26 AM
I found some issue on below design.
APs :IAP 135
FW (DHCP Pool) : Fortigate
SW " csico 2960XR
vlan101 : 192.168.101.0/24 (SSID:internal)
vlan103 :192.168.103.0/24(SSID : guest)
. provide 2 segments(vlan101 for internal, vlan103 is for guest)
. assign IP into each IAP135 to manage(control) from vlan103 DHCP pool
1. Each wifi-user belong to internal and guest can get ip address through IAP135 whcih connected trunk port.
2. But IAP135 itself cannot get a IP address from DHCP pool.
So I assinged manually ip( but cannot access from vlan101 segment.
So I tried to find exact issue :
I with another IAP135, connected to access port(vlan101) on cisco SW, IAP135 can get IP address from DHCP srv(vlan101)
and can ping / access this IAP135 on vlan101 segment.
what is the problem? native vlan is 1(default).
I believe if i use a native vlan insteat of vlan 101, it may works but I don't like to use vlan 1 as a production.
(of cource I can assing vlan 101 as a native vlan on all devices, but i cannot find a proper command on fortigate and auba AP)
Solved! Go to Solution.
07-21-2014 09:38 AM
I always thank you for your help. this is thrd time!
qucik question for native vlan,
is it possible to assging non-vlan(lan101) into native vlan on Aruba IAP135?
thanks in advance
07-21-2014 09:53 AM
You can do this by clicking on the IAP in the access point list, click edit and go to the Uplink tab. You'll see the "Uplink Management VLAN" option.
Tim Cappalli | Aruba ClearPass TME
@timcappalli | ACMX #367 / ACCX #480 / ACEAP / CWSP