Hello, after configuring the WLC5508, i move it to another agency, and since when i try to https to int1 for management i get the prompte for the certificat, and then i click on 'continue' and then blank page.
When I ssh to the same interface: here is what i get:
=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2014.04.17 11:31:44 =~=~=~=~=~=~=~=~=~=~=~= login as: admin Sorry, telnet is not allowed on this port!
i can connect to the Console cable.
Is there something i need to do to grant access to this interface.
I try to plug a pc directly to the interface (with a static ip on the PC) same thing, i try to configure INT2, same result.
As I suspected your configuration is wrong. Typically you should configure WLC connected switchport as trunk. Assuming you want to have WLC management on vlan 1200 (10.12.0.0/22), configure it like this. In this way you can have multiple vlan on your wireless network.
Hello And thanx for this answer, i solve the probleme enabling the management interface in http, and renew the certificat so i could connect to the management interface, then i reDisable the HTTP and leave only the HTTPS.
But ca i ask you a question regarding your answer: right now, my other WLC is managing 200 APs, and the management is untagged (see screenshot attached), but i can managed all my AP which are on different VLAN... Did i missunderstood something from you?
What is the use of having the management interface in trunk on the different VLAN? in my case, the management interface would be in the vlan 50,44,43,401,X. X being the VLAN of the management IP (41).
Is it what youtold me to do? is my actual conf correct? or what's wrong with it?
What I provided to you was a best practice configuration.
Even with management un-tagged it would work. But if you want to implement QoS, then across layer 2 trunk link CoS value is only for tagged vlans. So if you management is un-tagged all your wireless traffic won't preserve any QoS set by WLC (all traffic treat as Best Effort). Refer this for more detail.
Regarding restricting vlan across trunk, again it is best practice. Typically AP management & WLC management put in two different vlans (I believe in your case all in one or I may be wrong). If all in one subnet lots of unnecessary broadcast traffic generated by AP reach WLC, which is unnecessary. So put WLC & AP management in two different vlan & restricting which vlan traffic can go across WLC trunk link using "allow vlan x,y,z) command is consider as a best practice by only permitting WLC management vlan & any dynamic interface user vlans across that (No AP management vlan).
Transferring Crash file from standby:
Login to the Active WLC in HA.
(Cisco Controller) >transfer upload datatype crash
(Cisco Controller) >transfer upload filename <Desired filename>
(Cisco Controller) >transfer up...
This is the start of a display filter cross reference between Wireshark and OmniPeek.
The 1st installment is a table of advanced filters. More filters will be added as time allows.
It is a living doc, so check back for changes every so often
Please feel ...
I have created a Powershell script to automatically add a Wireless Guest User on Cisco WLCs. (tested on 2500 Series)
The script should be completely self explanatory.
Powershell SNMP Module (Install-Module -Name SNMP)
SNMP Write Access to...