05-07-2023 12:52 PM
Hi all,
I have some problems setting up my WLC2504 with a SG300 Switch configured as a Layer3 Router.
Basically, I have followed the tutorial I found on this site.
What I have done to both devices, is listed in the step-by-step documents that are attached as .jpg image files.
If I follow these exact steps, sometimes simplified with only the configuration steps for only one VLAN but all other VLAN's have been setup the same way, I can't access both management interfaces of the switch and WLC.
For this, I have created port Gi1 on the switch a Trunk port for the three VLAN's, 10,20 and 30.
I have connected this port to my laptop and gave it a static IP address of 192.168.10.200
Strange thing is, logged in from the console port of the SG300, I can ping both Access Points, the WLC and (of course) the SG300 itself. But not my laptop. From my laptop, I can't ping any devices.
Is there anything else I should configure?
Or can someone help me troubleshoot this issue?
Both devices are running on the latest firmware:
Solved! Go to Solution.
05-07-2023 01:00 PM - edited 05-07-2023 01:02 PM
Hi
Let me see if I understood this correct:
"For this, I have created port Gi1 on the switch a Trunk port for the three VLAN's, 10,20 and 30.
I have connected this port to my laptop and gave it a static IP address of 192.168.10.200"
If you connected your laptop to interface G1 which you configured as trunk it wont work as you laptop wont understand vlan tagging.
You need to connect your laptop either in a access port or in a layer3 port. I would recommend in a access port in the same vlan as you the Management interface of the WLC. Then put an IP address on the same network as your WLC management interface
05-07-2023 01:00 PM - edited 05-07-2023 01:02 PM
Hi
Let me see if I understood this correct:
"For this, I have created port Gi1 on the switch a Trunk port for the three VLAN's, 10,20 and 30.
I have connected this port to my laptop and gave it a static IP address of 192.168.10.200"
If you connected your laptop to interface G1 which you configured as trunk it wont work as you laptop wont understand vlan tagging.
You need to connect your laptop either in a access port or in a layer3 port. I would recommend in a access port in the same vlan as you the Management interface of the WLC. Then put an IP address on the same network as your WLC management interface
05-08-2023 03:03 AM - edited 05-08-2023 03:04 AM
Hi @Flavio Miranda ,
Thanks for the info and indeed that was my fault indeed!
When I change this as you suggestion, I can reach all devices on the Management VLAN.
Also I'm able to connect to the Management GUI's of both the WLC and the SG300 switch.
However, when I log into the WLC GUI, I see that there are no access points available or visible.
When I look at the DHCP info of the switch with the command show ip dhcp pool network Management I can see the two connected Acces Point with an assigned IP address of 192.168.10.50 and 192.168.10.51
Both of them are in the Management (VLAN10) network and both can be pinged from the switch and laptop.
I'm not behind the setup right now, but will also try to look what information I get from the Console Port of the Access Points.
If I'm not mistaken, I see the Green LED lit constantly on the Access Point, meaning it's in normal operating condition and at least one wireless client has been associated with it.
05-08-2023 03:10 AM - edited 05-08-2023 03:10 AM
Good to know.
If the AP has green solid led but it is not on the WLC, I might ask if those APs are capwap AP? This behaior suggest to me that this is autonomous AP. But, you can check that easilly with console into AP.
The normal bahavior for a capwap AP not joined in the WLC is blinking RED, BLUE and AMBAR.
As you now have access to the WLC, make sure you have all in place like Licensing activate( even evalution need to be activated) , data and time and correct country to access point. All this can affect AP to join.
05-08-2023 07:25 AM
Hi @Flavio Miranda ,
Thanks for all the help but I have found the issue once connected to the Console port of the Access Point.
I have seen this setup working before on another location, so I knew it wasn't a compatibility issue and I also knew they were CAPWAP Access Points.
The problem was that with the WLC Controller, that was set to a default time and date somewhere in 2000 and therefore made the installed certificate invalid.
Since I was testing without a working internet connection, the NTP Server couldn't update the system time.
Once I manually corrected the time in the WLC controller, the Access Points came on-line almost immediately.
Thanks you very much for the time answering my questions and helping me pointing into the right direction.
05-08-2023 07:52 AM
Glad to hear you sorted that out.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide