Cisco :: What Version Of SSH That A 2106 Wireless LAN Controller Is Using
Mar 22, 2011
how I can find out what version of SSH that a cisco 2106 wireless LAN controller is using?Is there a CLI I can type to figure that out or do they only support one version?
I am trying to get one AP to join the 2106 controller, it did join once then never again!! Now all I get is: *Jan 22 11:16:22.088: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
after an unplanned power outage the WLAN in our office has stopped routing. Clients can associate and get an IP address from the DHCP server on the controller but cannot get past the controller. A PC on the LAN can ping the default gateway of the SSID (dynamic interface) but cannot ping the client. Attached is a diagram of the setup. I am trying to find out how to add a default/static route via the L3 switch that the controller is connected to but am unable to do so either through the CLI or GUI. The controller (AIR-WLC2106-K9) is operating on ver 5.2.157.0.
I have a question to migrate a customer from a 2106 controller to a 2504 controller. Can I use the configuration file with both controllers having the same version?
Or is there another way not having to do it again manually? The old configuration is OK, only the hardware is end of sale.
I would like to get webauth bundle sample to create custom page for our AP controllers but I'm unable to find the sample .tar within the WCS itself.Some other WCS manuals has references in them that says there should be link to download sample from WCS but clearly 2106 hasn't got one.There's one in download section "webauth bundle 1.0.2.zip" but this is for registered partners and costumers, we are not registered as partners and cannot download the sample ourselves.
I am not able to join 1042 wireless AP with 2106 controller, even i mention that controller ip is 192.168.200.5 it try to join with controller on 192.168.200.6 ip address always. following are the error logs i can see on console.
*Nov 30 19:50:20.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 192.168.200.6 peer_port: 5246 *Nov 30 19:50:20.001: %CAPWAP-5-CHANGED: CAPWAP changed state to *Nov 30 19:50:21.435: %CAPWAP-5-DTLSREQSUCC: DTLS connection created sucessfully peer_ip: 192.168.200.6 peer_port: 5246 *Nov 30 19:50:21.436: %CAPWAP-5-SENDJOIN: sending Join Request to 192.168.200.6 *Nov 30 19:50:21.436: %CAPWAP-5-CHANGED: CAPWAP changed state to JOIN
When I connect the APs to a port on our 3550 switch, the AP gets an IP and associates with the 2106 controller. I can ping the AP from a wired PC and associate a wireless client to it. When I connect them to the PoE ports that are on the controller, it gets an IP and associates with the controller but, I cannot ping it from a wired PC or wireless client but, I can associate a wireless client to it.
The AP manager and Management interfaces, under PHYSICAL OPERATION are configured for port 1, which is the port that connects the Controller to the rest of the network. Since the whole network is using VLAN 1, I set the VLANs for the Management interface and AP interface to 0, untagged. I noticed when I set the AP manager interface to 1 I get the same results.
New to working with Wireless and the Cisco Meshing concept so have a few questions to ask.I currently have the majority of the mesh setup and configured. I have a setup with two RAPs with 9 MAPS connecting to each RAP.
First question is how many MAPS can connect to a RAP generally?Secondly how can I block other cisco AP's that are not in my mesh network from trying to connect to my AP's
The below is constantly hammering the logs for 6 devices that are Cisco close to my mesh that are not mine.
8 Sat Nov 12 23:31:53 2011 Mesh child node '58:35:d9:aa:db:4f' has changed its parent to mesh node '88:f0:77:b7:c6:e0' from mesh node '88:f0:77:b7:c6:c0'. Mesh Node '58:35:d9:aa:db:4f' failed to join controller, MAC address not in MAC filter list.
I have only added the MAC addresses of my AP's in to my AP Policy under security. Would these other AP's affect the mesh in any way?What I am seeing is the AP's constantly changing the child to parent relationship. I have inherited this network and they have about 20 AP's all within a square mile which is absolutely overkill. Would this close proximity of AP's together be the cause for the constant child parent changes?
How close should I have RAP's together. The network was setup so two raps are about 20 metres apart and the AP's on one side connect to RAP1 and the other to RAP2?How do you deal with Radar? The install is pretty much next to an airfield with radar running and a few times I have seen all the AP's disconnect and change channels.
using a Cisco 5508 controller (code version 7.4.100.0) with an ACS appliance running version 4.1 or 4.2?I've found that the ACS constantly reports a 'Bad request from NAS' (Invalid message authenticator in EAP request). message. This usually indicates a mismatched shared secret but this isn't the case.The controller works fine opposite a Microsoft NPS Radius Server.
We have Cisco 4402 Wireless Lan Controller with Software Version 3.2.171.6 and we want to upgrade it to latest version.
What is the latest version to upgrade the WLC?
Also since WLC is running on very lower version is it possible to upgrade to the latest version directly or we have to move it step by step to upgrade this to latest version?
I know that the recommendation from Cisco for the mobility anchor feature to work well is to use the same IOS version on the anchor WLC and local WLC controller. Now I´ll install on a new site a 5508 local WLC with a newer IOS version which is installed on the other controllers ( Guest and local ). Later I´ve planned to update also the other controllers to the same IOS version. Now my question is, must I upgrade all other controller at the same time ?
I'm seeing the alert "CPU Receive Multicast Queue is full on Controller" on the WCS from one of my controllers. This is during peak hours and on a pretty busy WLC. I can't find any related lines in the logfiles. I'm currently running software version 7.0.220.0 on a WISMs.
I added this wlc in lms and tried to collect inventory. But it is failing after taking long hours.(LMS Version 3.2.1,WLC 4404 -Version 7.0.116)(SNMP walk is successful & using SNMP V2c)I hope the specific package is available in LMS as i could find the WLC 4404 in Device update->Sys Obj ID -> <id of 4404 WLC> Any bug could be the reson for this...?
I will install next week at a customers side a new Pair of 5508 Controller. They have at the moment one old 4404 with about 70 APs.So the bought the new 5508 with HA Pair.For the HA i will need 7.3 i read in the High Availability (AP SSO) Deployment Guide.There are now two 7.3 Versions, or i can choose the new 7.4 Version.
So what software version will be the best at the moment?I will install also a Cisco Prime Infrastructure on a ESX host.For the 7.3 in can use the 1.2 , but for the 7.4 i must take the 1.3.
Is there currently any ACS version working with Windows Server 2008 R2 domain controllers?Our server stuff has recently upgraded the Domain Controllers to 2008r2 and turned off the 2003 servers. This didn't make our ACS 4.1.4 really happy.I've read now serveral posts regarding issues with ACS and Server 2008r2 and hope to find a solution (besides switching to LDAP, yukk).
McAffee scan of acs 1113 appliance running the 4.2 build 124 patch 12 version reports that a medium vulnerability exists because the system has SSH version 1. Any way to specify only version 2 or turn off SSH?
We recently purchased a bundle of 3 1042N AP's with a 2106 WLC. I am able to get the controller on the network and am able to manage it through the https web gui. I am now trying to add one of the AP's to the controller and am getting an infinite loop on the AP upon bootup. I tried looking up the solution but could not find a good article that pertained to the problem I was having. One thing I did notice is the time on the AP is way offset, but when I do a clock set to change it to the actual date it doesnt stick on the next reload.
Here is the output:
using ÿÿÿÿ ddr static values from serial eeprom ddr init done
I got my final assignment from school, and my teacher asked me to configure 2 Access Points (1200 series) directly on a Wireless Controler (Cisco 2106). I can't ask my teacher for any questions, cause he doesn't know how to configure it also, THAT's why he's asking me to do it.I've learned a lot of things about the default static interfaces (the "management" and "ap_manager" interface), but i can't seem to fully understand how to configure it.I want to use the Internal DHCP server of the WLC. How I can get those 2 Access Points working on the WLC. I only seem to get DHCP issues.
This is what i've done:
- Leave the configuration of the "management" and the "ap_manager" default (172.16.1.30 and 172.16.1.30). Bound to port 1
- Made a new interface "AP1" with IP-Address 10.0.0.10 (/24), default gateway 10.0.0.1. Primary DHCP server: 172.167.1.30
- Made a new interface "AP2" with IP-Address 192.168.1.10 (/24), default gateway 192.168.1.1. Primary DHCP server: 172.167.1.30
- Made 2 DHCP scopes within the 192.168.1.0 and 10.0.0.0 networks.
For some reason, when i boot up both AP's, the won't get any DHCP address.
We have a 2106 that was configured by a former employee. No one left in the company is qualified to configure it. The wireless guest access used to work fine. We'd configure a guest user account. They would connect to the guest wireless, open a web browser and login. For some reason now there is no prompt for login. People can connect to it and get an IP address, but that's it. No login prompt or anything else from there.User Login Policies was set to 0 and I put it to 8. That didn't do anything. Under Web Auth > Web Login Page it's set to Internal (Default).
I setup a mini wireless LAN network lab with a not for resale 2106 wireless lan controller and a sales air-lap1242ag access point. I do not have a DHCP and DNS in my lab environment. I have configured the WLC with the basic configuration using the CLI wizard, i also configured the WLC as a DHCP server for clients that will be connecting to the APs associated to the controller.
I powered up the AP and connect the ethernet port directly to the controller, the controller issued an IP address to the AP, the AP downloaded a new operating system from the controller but failed to join the controller.
I check both debug message on the controller console and the trap messages on the controller's GUI and it say the AP could not download a configuration from the controller and it is beacuse of invalid license. Below is the trap message:
Configuration Phase Statistics Requests ReceivedResponses SentUnsuccessful Request ProcessedReason For Last Unsuccessful AttemptLast Successful Attempt TimeLast Unsuccessful Attempt TimeLast Error SummaryLast AP Message Decryption FailureLast AP Connection FailureLast Error Occurred Last Error Occurred ReasonLast Join Error Timestamp
Also, I tried to log into the GUI of the AP using the both the username and password ''Cisco'' but I cannot get into the device. I can only get in through the CLI. In the CLI, almost all the commands I enter gives an error the it is disabled. I don't know what to do any more, I want to know if the access point is faulty or i am not doing the right thing.
I have a WLC 2106 and 1242AG.it's a hotspot configuration.So in WLC, under controller tab, i have set my ap-manager ip, my management ip, my virtual ip (1.1.1.1) and my hotspot network range ip.I set also a DHCP range for the hotspot network.
In Wlans tab, i set my hotspot wlan, with no layer 2 security and for layer 3, i set none for layer 3 security and i use web policy authentication.I use local authentication and i created under security menu, under AAA tab, 3 local net users.
From pc number 1, i get ip from dhcp, and i have authentication web page, authentication is ok and i can surf on web.From pc number2, when user 1 from pc 1 is connected, i get ip from dhcp but i have not the authentication web page, i have not DNS resolution.when i try https:1.1.1.1/login.html, i have no answer.
And when user 1 is de-authenticated, the user 2 can surf on web.So only one user can surf at the same time. not good for a Hotspot.
I have a problem with Cisco WLC 2106 (SW: 7.0.98.0) and LAP1262. The client roams to new AP, associates with the new AP and authentication (WPA2 with EAP-TLS) runs fine until WPA2 key exchange.
The first WPA2-Key-paket from AP (1 / 4) is sent twice. On a closer look at those packets with Wire shark, i've found out the first is encapsulated into a 11n-frame (A-MSDU). The resent frame isn't. This figure shows the first WPA-Key-packet:
The next figure shows the 2nd key-packet, without 11n-encapsulation: The problem, that occurs a very long roaming-time with about 5 seconds. As you can see on second figure, the second wpa-key is sent 5 seconds after the first.
Some details: Client: Tablet PC with Intel 6230 agn Controller: Cisco WLC 2106 AP: LAP 1262 Controller SW: 7.0.98.0 Encryption: WPA2-AES Authentication: EAP-TLS
This problem occurs just on 5-GHz interface with 40 MHz channel bandwidth.
I have been having problems with a 2106 WLC which seems to have developed a fault. I cannot console into the device (although I can console into the ap1131ag showing no fault with the RJ45 - 9 Pin) and the device is no longer showing up in any of the possible I.P ranges.
Its showing a power light and a status light on the front panel, the Ethernet ports light up like a Christmas tree when a device is connected and the power supply is putting out a solid 47.7v.
Has anyone experienced anything like this before and can anyone suggest anyway of breathing life back into it?
I have a very basic WLAN setup with a 2106 controller and 3 (will be 4) 1140 APs.As part of securing the network I have been testing the rouge detection. The system has no trouble detecting and shutting down honeypots. I would like to also automatically shut down Rouge on Wire points. The system sees my test AP just fine. And I have it completely open (no security). But the system never detects that the rouge is on our network so no action is taken. I can connect just fine to the test AP with no encription using DHCP and communicate with everything on the network just fine.Is there some setting I am missing that allows the APs to detect that an AP is on wire?