Cisco :: 5508 Uploaded Via FTP To Controller Successfully
Mar 29, 2012
Web Auth on 5508 running 7.2.103.0.
Issue 1: I have been trying to configured Webauth bundle however it seems that is not working.
1. login.tar created use picozip contains 3 files: login.html, terms.html, and logo.jpg.
2, uploaded via FTP to controller successfully..
3, no issue when i tried to preview on the controller
However users unable to see the login page when connected to guest wifi. when the user tried to connect cisco.com, on the browser address shows that the page redirected to url... however internet explorer / firefox display "Connection reset error".During this time, if i ask the user to type url... they can see the default login page, so no issue on connectivity to the service port.
Issue 2: Since i couldnt make that work, i have use default webauth internal. its all good. then when i tried to upload customlogo.jpg (18k size). User able to see the login page however not the logo. it shows broken image icon on the web browser. --> i can see the logo when i did preview on the controller.
Issue 3: last resort if i couldnt get the answer by sunday, how do i delete or remove the customlogo ?? so by monday users will not be seeing any errors on the page.
How to successfully deployed a WGB with a 5508 WLC?5508 code is 6.0.202.0 and the WGB is an AP1131AG?The documentation is ambiguous in that it states you can't use VLANs and then shows VLANs being used.I have a WLAN called wgb-link set up on the WLC with WPA-2 AES and PSK. The WLAN points to a logical interface called wgb-link which is configured to be in VLAN 9 and the default gateway is the VLAN SVI on the core switch.On the WGB I have configured the same SSID and security setup.
I am using the 5GHz radio and have set it to be a work group bridge.I have a sub interface dot11radio 1.9 configured:
encapsulation dot1q 9 native bridge group 1
I also have an ethernet sub interface configured:
encapsulation dot 1q 9 native bridge group 1
Int BVI1 is configured with an IP address in VLAN 9.The WGB links up fine and I can see it as a client on the WLC.
From the WGB CLI I can ping the interface on the WLC and the SVI on the core switch and any other device on the network in any VLAN.From the WLC I can ping the BVI1 address of the WGB.From the core switch I can ping the WLC interface and the WGB BVIi interface.
If I connect a laptop to the WGB ethernet port with a static IP address in VLAN 9 I cannot ping from the laptop to the WLC interface or the SVI on the core. I can only ping to the BVI address of the WGB.
I know that the 3600 series APs are not supported on the 4404 WLC. However, would the following scenario be supported? I would like to use the 4404 (software rel. 7.0) as a guest anchor with a 5508 (software release 7.2) as the foreign controller supporting series 3600 APs. I ask because the APs do not need to join the guest anchor.
We have a customer that have 2 5508 as primary and backup controller and a 4400 as an anchor controller. We plan to upgrade the 5508 to 7.3.112.0 and the 4400 is already 7.0.116.0. Will there be any issue if the anchor controller is not the same code as the foreign controller? Do I also have to upgrade the acnhor controller to 7.0.240.0?
I uploaded my web page on Internet via File Zilla. My web page consisted of 10~ HTML files . Some of HTML pages cannot be opened by any browser ( The requested URL /scenos.html was not found on this server ), however, when i open my web locally ( from my hard drive) everything works perfectly
I'm only able to restore my settings from a backup taken in July 2011. Any backups that I take, say today for example, won't restore. Any attempts to restore them is returned with "The restored configuration file has been uploaded in failure." I haven't changed my router. The firmware remains the same. I'm using Firefox, though I believe I've always used Firefox to interface with the router.
I want to use a 5508 as an anchor controller for a wireless guest deployment....but the client has internal 4402's controllers, with software version 7.0.235.0...is it possible tu mix these two controllers for a Wireless Guest Access Deployment??
A wlan on my controller is configured for WPA2, AES encryption and a PSK. A vendor will supply me with a wireless device for this wlan. The vendor asks if we use AES 128 or AES 256. I had always believed we use AES256 but I can't verify this. How can I verify this to the vendor?
Seems that all solutions are null and void for us because we are not using SNMP v3 or H.
We are using SNMP v2, We have upgraded our WCS to latest version as well as the controllers. I have 6 controllers currently added although they are on WiSM blades.
We are unable to add the 5508 Controllers, we keep recieving this error -
No response from device, check SNMP communities, version or network for issues.
I have confirmed all connectivity is working, even with a debug on the controller you can see it sending SNMP packets to the WCS, although still same error.
I just bought a Cisco-Linksys router E2500. Installation went fine, Internet is ok...
Just a small issue when I'm trying to upload a file to a distant FTP server. Any file < 1KB is fine but when the file is larger than 1KB, I can't upload it anymore (it just doesn't complete the upload).
I tried passive/active mode for my FTP connection. I tried port forwarding. Now I deactivated the router firewall and I put myself in the DMZ. I also tried to upgrade the router's firmware to the latest official version, and to the DD-WRIT latest version.
But still I can't upload files larger than 1KB. With my previous router, it was working pretty fine.
The ultimate test was to connect myself on a VPN server and try to upload the file to the FTP through the VPN server. And it worked!!!
But I don't want to be always connected to a VPN when I want to transfer files to my FTP server...
I have a wireless controller 5508 and all my interfaces can be accessed via https or ssh from a wireless client. Management access from a wireless client is disabled so I don't understand why this is happening.
We have a customer that is looking to allow only static IP addresses onto the wireless network via the new 5508 we are putting into place. I can see where to require DHCP but not the opposite.
I have a 5508 controller at our headquarters and am installing some 3502 AP's at a remote branch. Unfortunatly, the remote branch has a different Vlan setup for some reason and the vlan that is used for the WLC (90) is designated for telephony at this branch. Can I put the AP's on a different VLAN (10) without having any issues? I will still use DHCP option 43 to point them back to the controller. Below are the configs for the WLC interfaces and what I am proposing for the AP interfaces:
Cisco 5508 Series Wireless Controller for up to 100 APs 802.11a/g/n Ctrlr-based AP w/CleanAir; Ext Ant; E Reg Domain..For Mobility i want to settup the device such that the SSID would be the same with thesame security key and in different subnet.
I can not get our 3602i AP's to register with our 5508 controller which is running 7.2.103.0 code. We keep seeing an error in the log on the WLC "AAA Authentication Failure for UserName:c46413c08e92 User Type: WLAN USER" and on the Access Point we are seeing [code]
I entered the CAPWAP ap controller ip address directly into the AP so it shouldn't be an option 43 DHCP issue
I use WLC 5508 (ver 7.0.116.0) with aironet 1140. I need to connect my APs to different controller .After log in via ssh to AP i am trying to do:
capwap ap controller ip add x.x.x.x reset
But after reload, AP is still joined to the old WLC. So another idea was to log to that WLC and put:
config ap primary-base WLC2 AP_NAME x.x.x.x
and after that:
config ap reset AP_NAME
But still nothing, it's joined to another controller although "show ap client config" shows that primary-base switch is x.x.x.x ?How can i force it to join to other controller?
We are looking to upgrade our 5508 wireless controller from 7.0.98.0 to 7.0.220.0. Reason being, we have experienced a lot of access points disassociating from the controller as well as client authentication issues. Upgraded from 7.0.98.0 to 7.0.220.0 and any issues during the upgrade or after the upgrade?
We have a WLC (5508) in our main office in Brisbane that is hosting two WLANs. One provides wireless access to our internal network and the second provides wireless guest access. The guest WLAN is anchored to a controller sitting in the DMZ at our Data Centre.
In the DMZ the anchor controller has a management interface and an interface in the DMZ for the wireless guest access. I am using the DHCP server on the anchor DMZ to provide IPs etc to wireless guest clients. The default gateway is 10.8.144.1 which is a VIP or a pair of firewalls.
Initially everything works fine. Guests connect to the guest network, have to authenticate via a web portal (Cisco ISE server) and then can go on an use the internet. Works perfectly until the firewalls fail over and the secondary firewall takes over the VIP address. All access to the internet is lost at that point. If I try to disconnect and then reconnect a wireless client it connects, as in it will get an IP address, but DNS resolution stops and I do not get redirected to the web auth portal. If the firewalls are failed back to the primary then everything works again, no issues. However, if I reboot the WLC while the secondary firewall has the VIP IP everything will work fine as it did on the primary. If the firewalls now fail over to the primary again everything goes to ****. Until either the firewalls are failed back or the anchor WLC is rebooted.
Initially I thought this was an issue on the firewall, but this doesn't appear to be the case. When the firewall fails over it sends out a gratuitous ARP advising of the change in MAC address for the 10.8.144.1 IP address. The WLC seems to update its ARP table because if I run the command "show arp switch" it has the 10.8.144.1 IP address with the MAC address of the active firewall. From the client perspective I have run a wireshark and captured packets on the wireless interface when trying to connect. The laptop is continuously send ARP requests for 10.8.144.1 but gets not reply. Without this the client cannot send an ethernet frame to the gateway and hence get to the DNS server and WEB portal. Internet access breaks. Doing a TCP dump on the active firewall shows it receiving and then sending a reply to the ARP request. It just never gets to the wireless client. Debugging ARP packets on the anchor WLC seems to indicate that the controller is receiving the ARP replies from the firewall. So I'm at a loss as to why things should break when the firewalls fail over.
I have a 3750 switch in the DMZ with SVI of 10.8.144.4. I thought I could get a work around where I would make this the default gateway. The theory being that this interface MAC address would never change. However I was wrong. Even with this IP set as the gateway address for the wireless clients I see the exact same bahaviour when the firewalls fail over. I can't explain it other than to say that the gratuitous ARP sent by the firewalls seems to kill the ability of ARP replies to be sent back to the wireless client.
I'm a trainee in Network and Telecommunication, and I have to do a "model" with a controller, an AP, and a RADIUS server. Communication and configuration of the lightweight AP has been done.
I use an autonomous access point 1220 as the RADIUS server (no considering it as an AP), and I'm a beginner in RADIUS configuration. I get a "Processing AAA Error 'No Server' (-7) for mobile 00:24:d6:8f:2c:7e" when I launch a debug targetting my PC, connecting to the LAP.
Precursory : 10.137.125.71 is the IP address of the ap1220, working as the RADIUS server 10.137.125.15 is the IP address of the controller. 00:24:d6:8f:2c:7e is the MAC address of my PC, connecting to the Wi-Fi. ping works to the RADIUS, to the controller. Each devices are connected by a layer 3 Switch, and ping each others. The Wi-Fi works when I don't use 802.1X (or when I don't use RADIUS authentication at all)
What I did on the RADIUS server (ap1220 autonomous) :
aaa new-model radius-server local nas 10.137.125.15 key password
Have a controller based depolyment with (2) 5508s and an 1121 ACS appliance running 5.1 code. Controllers are setup identically and we are radius authenticating users to AD via the ACS. Everything works great on the primary controller, but when I test failover to the secondary controller, my authentication fails and I get the following error message in my ACS logs:
12126 EAP-FAST cryptobinding verification passed 12147 Machine Authentication is disabled 12161 Cannot provision Authorization PAC when the stateless session resume is disabled 12106 EAP-FAST authentication phase finished successfully 11503 Prepared EAP-Success
Just replaced a 2106(ver 5.1) with a 5508 (ver.7.2)...Everything was OK.. AP's got on 5508 and we shut the 2106. (AP's are on L2 with controller)During some investigation of why new LAP's from a location via VPN/GRE don't show up in controller, i type the following command on 5508: test ap pmtu enable all....All AP's on 5508 is now in Not Joined state..Have powered up the old 2106 and put AP's on that .. This is OK ....Have rebooted/downgraded/upgraded the 5508 controller but with same result.....No AP's can join this controller (exept from a oeap600)
So we have a Cisco 5508 controller that is managing 15 AP's in one of our buildings.I am running 2 wlans, one is internal access via (wpa) radius, peap and domain login...that works well now
The other is a guest lan, that is only allowed to surf the web.
The question from our security group, is there a way to restrict wireless access to ONLY a corporate approved list of devices.
As it stands right now, we only support Blackberry's as our mobility device. All local data is encrypted. The issue here is our testing shows that with an Iphone (not approved) it is very easy to connect to the WPA network if a user knows how to enter in their domain credentials. From there they can browse our internal web servers and download corporate data to a non approved, non encrypted device such as the iphone.
I upgraded a controller yesterday 5508 it went from a low code version 6.x to 6.0.196.0 then to 7.0.116.0. However although all the access points joined code 6.0.196.0 they refused to join 7.0.116.0. The aps are all 1242s.
The country codes etc were all fine so I do not understand what was going on.
*spamApTask0: Jun 26 16:07:44.734: 00:3a:99:db:f3:20 Discovery Request from 10.0.0.183:55065 *spamApTask0: Jun 26 16:07:44.734: 00:3a:99:db:f3:20 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 25, joined Aps =0*spamApTask0: Jun 26 16:07:44.735: 00:3a:99:db:f3:20 Discovery Response sent to 10.0.0.183:55065 [code] ......
I have one controller 5508 that will hold 50 LAP 1262 and another Controller that will hold another 50 outdoor mesh access point 1552. Both controllers (not redundant) are at the HQ while the access points are distributed between HQ and 3 branches.
The requirements is to have the SAME 4 SSIDs on MESH and LAP each have a security type (, wep,wpa,dot1x...) on HQ and Branches. Now, in the HQ I don't think I will face a problem since the WLCs is on the same LAN, so 5 interface v lans will be configured one for the WLCs and access point and another 4 interface v lans for the 4 SSIDs.
Now, for the remote sites I need to create another vlan on the switch with DHCP and option 43 ..... for the access point to register with the controller.
But here, do I have to create another 4 interface v lans (4 different sub nets) that should be bidden to the SSID as in the HQ?
Or the Access point will encapsulate all the traffic including the client traffic? Note that I have outdoor mesh access point and Lightweight access point and the BW link between the HQ and branch is 100M.
Also Can I have roaming between the same SSID that broadcasted on MESH and LAP knowing that each have different controller.
[URL] I have one Controller 5508 is my Central Office and I have some Ap's working in local mode in my Central Office, additional I have more Ap's in a remote Office they're are working as H-REAP and I can handles across my WLC. Now my enterprise decided bouth another WLC and wants to deploy a active-passive scenario. This new Controller should manages all the AP's when the central WLC fails...
My questions are... I need to have the same ip addressing on both sites? or they can be different. I nedd to configure some on my Ap's that are working as local mode, for allow the secondary WLC manage them when mi central WLC fails
I received a 5508 WLC, that I wanted to configure as a guest anchor for our DMZ. I stepped through the console configuration. Now that the setup is complete, can I attach my laptop directly to the copper SFP, and access the WLC web portal? I gave my laptop an IP address, in the same subnet, but still can't connect to the portal, or ping the WLC IP address.
We have 3 5508 WLCs (A, B, & C) and several LAPs (1140, 3500, 3600). The APs learn the controllers IP addresses through DHCP Option 43. When we setup a new site we put the IP address of the controller we want the AP to join first. Lately, I've noticed that regardless of which WLC IP I put first when I setup Option 43 the LAPs are always joining a particular controller.
