LMS 4.2 and WLC 5508

Hi all,
Recently I have replaced 2 4400 WLC by 5508 wlc's.
I have also replaced both 4400 in LMS by those new 5508. They have the same ip's, so I have removed the old 4400's from LMS and created 2 new devices.
When checking the device center, LMS tells me Data collection, User tracking, Inventory and Fault discovery has succeeded.
When I check the Reachability status in device center it is ok for ping, telnet, SSH, SNMPV2 read, SNMPV2 write. However I am not able to open the configuration through Config editor. He gives me the pop-up "CEDT0042: No latest configuration file exists for the device in Archive."
When I go and check the archive summary report, I can see for both devices the log below:
NMP: Failed to establish SNMP connection to x.x.x.x - Cause: Device is Unreachable. Check the ReadOnly community string. SNMP: Failed to establish SNMP connection to x.x.x.x - Cause: Device is Unreachable. Check the ReadOnly community string.
Any ideas,
Thanks,
Joris

Hello,
I think I have found the problem. WLC 5508 is not compatible with LMS 4.2.2.
I can find this in the release notes:
Cisco Unified Wireless Network Solution Components
The following components are part of the Cisco UWN Solution and are compatible in this release:
Note For more information on the compatibility of wireless software components across releases, see the Cisco Wireless Solutions Software Compatibility Matrix.
•Cisco IOS Release 15.2(2)JB
•Cisco Prime Infrastructure 1.3
•Mobility Services Engine (MSE) 7.4.100.0 software release and context-aware software
Apparently only Prime 1.3 can manage this device.
Joris

Similar Messages

  • Converged Access Design Help (Catalyst 3850 and WLC 5508...Mobility Oracle)

    Hello,
    I am an engineer working with a Cisco Gold Partner in Saudi Arabia. We have a large university as our client where they are constructing a new
    building and require our services to build the network infrastructure. Therefore, we are to implement the routing and switching infrastructure as
    well as the Wireless solution.
    At present, I have no issues in implementing the R&S infrastructure as it is very straight forward but it has implications on the deployment of
    the wireless solution which I explain further below. The R&S infrastructure comprises of the typical Core, Distribution, and Access layers and we
    are focusing on the local distribution and access switches with regards to the new building. The client has a converged Layer 3 network spanning
    from distribution layer to core layer and they are running EIGRP for this convergence. This is not a problem and has already been implemented.
    Yet, the challenge arises in deploying the WLAN infrastructure. The client already has a Cisco WLAN infrastructure in place where they have a
    large number of LAPs that are registered with their controllers in the Data Center. They have two WLC 5508 where one is the Primary and the other
    the Secondary. The local distribution switch to which the WLC are connected also is the gateway for the SVIs for the SSIDs that are configured on
    the controllers. This means that once the packets from the AP come in to the WLC, they are tagged with the correct VLAN and sent to the directly
    connected distribution switch which then routes it into the rest of the Layer 3 network. Interestingly, the WLC 5508 are running AireOS 7.6 and
    support the "New Mobility" feature. The two controllers have formed a Mobility Group (MG) between each other.
    Now, the new building will have two Catalyst 3850 switches installed where each one has a total of 40 AP licenses pre-installed and activated
    i.e. a total of 80 APs can be supported by the two switches. A total of 67 LAPs will be deployed in the new building which can be accommodated
    between the two switches and their integrated controller.
    Yet, based on my understanding and research about Converged Access is that, ideally, the Catalyst 3850 will only run the Mobility Agent (MA)
    feature while a central controller would provide the Mobility Controller (MC) service. unfortunately, there are not enough licenses on the
    existing WLC 5508 nor can we migrate the new licenses that will facilitate such a split deployment.
    This means that I would need to configure the two Catalyst 3850 as independent MC and form a MG between them. I have done this and tested this
    already and the mobility is working fine. But my concern is not about getting the Catalyst 3850 to work as this is simple but rather it is
    focused on creating a common Mobility Domain (MD) so that clients can roam from this new building to the rest of the campus while maintaining the
    state of their connections to the WLAN infrastructure.
    To make things more complicated, since the new building will have its own Layer 3 distribution switch and the Catalyst 3850 switches will connect
    to this distribution switch, it means that new VLANs and SVIs need to be created for the SSIDs broadcast in the new building. This means that new
    subnets need to be assigned to the SSIDs.
    As such, I have the following questions:
    Q1) If we create new SVIs for the SSIDs (same SSIDs names will be used in the new building as in the rest of the university campus) this means
    that new subnets will be assigned to these SSIDs. Now, I believe I have two options...one is to make the new Catalyst 3850s to be in the same MG
    as the existing WLC 5508 which then cater for Layer 3 client roaming or I have to treat this as a totally seperate WLAN network and follow on to
    the solution as per the next question. Please advise which is a better option?
    Q2) I could create separate MG i.e. the new building Catalyst 3850s can be in one MG and the existing controllers can be in another MG. I can
    then have one of the existing WLC 5508 (the primary one) to run the Mobility Oracle (MO) feature so as to create a single Mobility Domain (MD).
    Would this facilitate in Layer 3 client roaming and RRM for all the controllers in the same MD?
    Q3) If I do create a MD, how is this accomplished in such an environment since the documentation is severely limited in this regard?
    Please advise at your earliest. To assist further, I have attached a topology diagram which may aid in explaining the situation with more
    clarity. If these things are clarified, I will be better able to wrap my head around the technology and in turn service my clients better.
    Regards,
    Amir

    Hi Amir,
    Q1) If we create new SVIs for the SSIDs (same SSIDs names will be used in the new building as in the rest of the university campus) this means that new subnets will be assigned to these SSIDs. Now, I believe I have two options...one is to make the new Catalyst 3850s to be in the same MG as the existing WLC 5508 which then cater for Layer 3 client roaming or I have to treat this as a totally seperate WLAN network and follow on to the solution as per the next question. Please advise which is a better option?
    I would configure them in the same mobility group. Also configure same SPG for those two 3850 stacks if users are frequently roaming within these two buildings.
    Q2) I could create separate MG i.e. the new building Catalyst 3850s can be in one MG and the existing controllers can be in another MG. I can then have one of the existing WLC 5508 (the primary one) to run the Mobility Oracle (MO) feature so as to create a single Mobility Domain (MD). Would this facilitate in Layer 3 client roaming and RRM for all the controllers in the same MD?
    MO is not required (it is only for very large scale deployments)
    Q3) If I do create a MD, how is this accomplished in such an environment since the documentation is severely limited in this regard?
    Yes, documents are hard to find :(
    These notes may be useful to you based on my experience. I am running IOS-XE 3.6.1 in my production.
    http://mrncciew.com/2014/05/06/configuring-new-mobility/
    http://mrncciew.com/2013/12/14/3850ma-with-5760mc/
    HTH
    Rasika
    *** Pls rate all useful responses ****

  • ISE and WLC 5508 IP and MAc address

    Hi!
    Is it possible that we recibe IP address and Mac address Client at the same time in ISE ?
    The wlc permits choose radius Call station ip type MAC or IP, but not both.
    Thanks you,

    If you are using dot1x then no, the mac address is sent since the client does not receive an ip address till authetication succeeds.
    Sent from Cisco Technical Support Android App

  • ISE 1.2 / WLC 5508 EAP-TLS expired certificate error, but wireless still working

    Hi I have a customer that we've deployed ISE 1.2 and WLC 5508s at.  Customer is using EAP-TLS with and everything appears to setup properly.  Users are able to login to the network and authenticate, however, frequently, I'm getting the following error in ISE authentication logs:
    12516 EAP-TLS failed SSL/TLS handshake because of an expired certificate in the client certificates chain
    OpenSSL messages are:
    SSL alert: code=Ox22D=557 : source=local ; type=fatal : message="X509
    certificate ex pi red"'
    4 727850450.3616:error.140890B2: SS L
    rOYbne s: SSL 3_  G ET _CL IE NT  _CE RT IF ICAT E:no ce rtific ate
    relurned: s3_ srvr.c: 272 0
    I'm not sure if this is cosmetic or if this is something that I should be tracking down.  System isn't in full production yet, but every client seems to be working and there is no expired cert in the chain.  Any ideas what to check?

    Hello Dino,
      thanks very much for your reply.
      The client uses a machine-certificate, the PKI is not a microsoft one, but a third party PKI.   The certificate is fresh and valid, the root-cert is installed and checked to be validated against it for the login.
    Clock is correct too. The same setup works flawlessly in Windows 7 and XP.
    EKU is set on the certificate (1.3.6.1.5.5.7.3.2)
    I suspect the cert-setup itself, but don't get a clue where this might stuck...
    Björn

  • Windows Sharing problem from WLC 5508 to wired LAN

    Dear All,
    I'm having problem with windows sharing (file/printer sharing) from Wireless lan client which is connected to AP3500 and
    WLC 5508 then to Nexus 7010. It's already using ip command, for example \\192.168.84.65
    WLC os version 7.0.116.0 (using AP groups)
    Nexus os version 4.2(6)
    The weird thing is i can connect using windows sharing from wired LAN to wireless user however not vice versa.
    for better explanation, here are the scenarios
    1. Wireless lan to wired LAN using windows sharing - failed
    1. Wired LAN to Wireless lan using windows sharing - success.
    I've been analyzing by making sure that all the to end, there would be no firewall within source pc(s) and destination pc(s) and also
    the ACL inside Nexus.
    Been dying here to find solution for this, due to the customer is using it for file and printer sharing service.
    Anyone has idea to solve this problem, i'm looking forward for any suggestion coming.
    Arrai.

    Peer to peer within wlc is using default setting which is allowed and as you may know, peer to peer permission only related between wireless client not wired one. CMIIW.

  • WLC 5508 - Failed to connect from LMS 3.2

    Hello.
    I am trying to include a WLC 5508 in our LMS 3.2.
    I have defined the device and credentials, but the LMS server cannot get access to it.
    If I try to check de device credentials from the Device Center I get a "failed to connect", but if I a try a telnet session, also from Device Center, I get a connection.
    I checked the credentails are OK.
    Thank you.

    Hi,
    You need to download and install the last package : WLC.RME431.v2-1.zip : http://www.cisco.com/cisco/software/cart.html?imageGuId=E3A42793DA29A1B6AC3024C088F9FBC2B324EC8B&i=rs
    You must install : MDF 1.37
    You must install packages before WLC.RME431.v2-1.zip:
    SharedSwimWLC.RME431.v1-2.zip
    SharedDcmaWLC.RME431.v1-1.zip
    SharedSwimIOS.RME431.v2-5-4.zip
    LibSwim.RME431.v2-5-3.zip
    LibCommon.RME431.v2-4-2.zip
    Elisabeth
    WLC.RME431.v2-1.readme:
    Supported Devices
    =================
    Device Type : Cisco 5500 Series Wireless LAN Controllers
           Cisco 3750 Switch with Wireless LAN Controller
    Devices/Modules Supported :
    Cisco 5508 Wireless LAN Controller : 1.3.6.1.4.1.9.1.1069
    Cisco 3750 24+2 port 10/100/1000 Switch with integrated Cisco 4402 Wireless Controller: 1.3.6.1.4.1.9.1.747
    Features Supported:
    Inventory Manager : Yes
    Syslog Analyzer : Yes
    Config.Mgmt  : Yes
    Software Mgmt : Yes
    Minimum Software : 6.0.188.0
    Hardware and Software Requirements
    ==================================
    Hardware and software requirements are the same as those needed for Resource Manager
    Essentials 4.3.1 installation.
    You must install Resource Manager Essentials 4.3.1 and MDF 1.37 before installing the
    device package.
    For a detailed list of requirements, as well as instructions for installing Resource
    Manager Essentials 4.3.1, go to Cisco.com.
    For documentation on Resource Manager Essentials, see:
    http://www.cisco.com/en/US/products/sw/cscowork/ps2073/tsd_products_support_series_home.html
    Package Dependencies
    ====================
    To install the WLC Package, you must install the
    following dependent packages:
    SharedSwimWLC.RME431.v1-2.zip
    SharedDcmaWLC.RME431.v1-1.zip
    SharedSwimIOS.RME431.v2-5-4.zip
    LibSwim.RME431.v2-5-3.zip
    LibCommon.RME431.v2-4-2.zip

  • EAP-TLS with WLC 5508, Microsoft NPS and custom EKU OID´s

    We are trying to implement EAP-TLS with client certificates that have a custom EKU OID to distinguish the WLAN clients. The Microsoft Press Book
    Windows Server 2008 PKI and Certificate Security gives an example on how to configure a policy in NPS that matches specific EKU OID´s. At the moment we have two policies that have an allowed-certificate-oid configured that matches the OID´s in our certificates, but our setup is not working as expected. Authentications will only be successful, if the client authenticates with the certificate that is matched by the first policy rule.
    For example:
    Policy 1: allowed-certificate-OID --> corporate
    Policy 2: allowed-certificate-OID --> private
    Client authenticates with EKU corporate --> success
    Client authenticates with EKU private --> reject
    My expectation was, that if Policy 1 will not match the NPS goes over to Policy 2 and tries to authenticate the client.
    Has anyone a simmilar setup or can help to figure out what is going wrong?
    We have a WLC 5508 with Software Version                 7.4.100.0 and a NPS on a Windows Server 2008 R2
    regards
    Fabian

    The policy rejects and the NPS goes to the next policy, only if the user does not belong to the configured group.
    This means I need to have one AD group per application policy, but that will not solve my problem. A user could belong to more than one group, depending on how many devices he/she has. It will work with one group only for each user, because the first policy that matches a AD group, the user belongs to, could have a OID that is not in the certificate. This would cause a recejct with reason code 73:
    The purposes that are configured in the Application Policies extensions, also called Enhanced Key Usage (EKU) extensions, section of the user or computer certificate are not valid or are missing. The user or computer certificate must be configured with the Client Authentication purpose in Application Policies extensions. The object identifier for Client Authentication is 1.3.6.1.5.5.7.3.2.
    The certificate does include this OID but not the custom EKU.

  • 2 Cisco WLC 5508 controllers and software upgrade 7.6.130 + FUS 1.9

    Hi
    I have two WLC 5508 controllers that need 7.6.130 and FUS 1.9 installed. (Current version 7.3 and FUS 1.7)
    Configuration: One controller is at Site A and the other controller is at Site B (two different states..)
    They're configured so that if Site A goes down, Site A AP's will failover to Site B and vice versa ..
    - What would be the recommended approach for upgrading the software to 7.6.130.0 (from 7.3) and also upgrading FUS 1.9 (from 1.7)?
    My plan was to download 7.6.130.0 to both controllers and pre-download the software to all AP's (about 100 total between both sites) and then reboot the controllers at night at the same time? Or one before the other? 
    Step 2. Install FUS 1.9 to each controller.
    I'm concerned over what might happen during the upgrade and AP failover etc..
    Thanks

    This is what I would do:
    Upload v7.6.130.0 to all WLCs and then use the pre image download to push the image to all access points. 
    Dont reboot the wlc
    Image swap in the access points so that v7.6.130.0 is primary
    Move all access point to one of the WLCs (A)
    Enable ap AAA authentication on the WLC that has no access points and the one you will work on first.  This prevents access points from joining  
    Reboot the WLC (A)
    Upload the FUS 1.9.0.0
    Reboot WLC (A) this takes up to 45 minutes
    When the WLC (A) comes back online, uncheck ap AAA authentication
    Move access points from WLC (B) to WLC (A)
    Enable ap  AAA authentication on  WLC (B)
    Perform all the other task you did earlier on WLC (A)
    That's it.
    -Scott

  • ISE Profiling for Wireless Devices (WLC 5508) like Laptops and Mobile Devices

    Hi,
    We have integrated WLC 5508 to cisco ise 3315 with ios 1.1.1 and using Guest Sponsor portal for wireless guest users.
    Where we have created open ssid in wlc and redirect web login portal in wlc for guest  users. We have enable all respective node in policy service for profiling and also configure snmp in wlc as well as in ise.
    When guest user is connected to open ssid its get redirected to web login page of ise portal and when it gets login we are  only able to see the username which guest user login but not the end device in monitoring log.
    Wireless End devices are not able to get profiled can any one tell me what configuration I need to do on ise or wlc side to profiled end guest wireless device like android,iphone and laptops
    Thanks
    Pranav

    Hi Tarikh,
    I only want to identify the end devices for wilress guest user. I have configured MAB Authentication and configure autorization policy where in mention identity group any condition as wlc web authentication and athorization profile only guest mentioning plain access for the same.
    Can you help me how I can achived profiling for wirless guest devices. I have configured all profiling probes . Enable snmp on wlc as well as in network devices.
    What else I need to configured to achived just identiting device nothing but profiling and which should reflect in authnetication logs.
    Thanks
    Pranav

  • IPhones not taking ipv4 addresses on Unified Wireless (WLC 5508 and AP 3602)

    This is a really odd one...
    Earlier this week we started having issues with our BYOD wireless network (802.1x, WPA2+AES) but only with Apple devices (iphone and ipad). Employees with Android or Windows phones are not having any problems at all.
    A brief summary of what's observable for the issue:
    Radius authentication succeeds (PASS observable in ACS logs)
    IPhone status viewed on both controllers (foreign anchor in DMZ as well as corporate WLC) shows phone associated.
    Debug client output shows an IPv4 address is actually being assigned to the phone however it appears to ignore it and restart the DHCP request process so debug output shows what looks to be a loop of DHCP request and offer stages.
    Infrastructure notes
    Cisco WLC 5508s are all running 7.4.121.0 (tried rolling back to 7.2.110.0 .....didn't help)
    APs are all 3602I-N-K9
    DHCP for the BYOD network is running on the anchor in the DMZ however this was temporarily moved to a switch (had no effect).
    Any ideas?
    DHCP Loop:
    *mmListen: Apr 30 11:44:50.476: a4:c3:61:7a:1a:4f 0.0.0.0 RUN (20) Fast Path rule (contd...) 802.1P = 0, DSCP = 0, TokenID = 15206  Local Bridging Vlan = 93, Local Bridging intf id = 12
    *mmListen: Apr 30 11:44:50.476: a4:c3:61:7a:1a:4f 0.0.0.0 RUN (20) Successfully plumbed mobile rule (IPv4 ACL ID 255, IPv6 ACL ID 255)
    *pemReceiveTask: Apr 30 11:44:50.476: a4:c3:61:7a:1a:4f Set bi-dir guest tunnel for a4:c3:61:7a:1a:4f as in Export Anchor role
    *pemReceiveTask: Apr 30 11:44:50.476: a4:c3:61:7a:1a:4f 0.0.0.0 Added NPU entry of type 1, dtlFlags 0x4
    *pemReceiveTask: Apr 30 11:44:50.476: a4:c3:61:7a:1a:4f Pushing IPv6: fe80:0000:0000:0000: 0c00:0c94:459e:a9db , and MAC: A4:C3:61:7A:1A:4F , Binding to Data Plane. SUCCESS !!
    *DHCP Socket Task: Apr 30 11:44:50.479: a4:c3:61:7a:1a:4f DHCP received op BOOTREQUEST (1) (len 308,vlan 92, port 13, encap 0xec05)
    *DHCP Socket Task: Apr 30 11:44:50.479: a4:c3:61:7a:1a:4f DHCP selecting relay 1 - control block settings:
                            dhcpServer: 172.24.13.251, dhcpNetmask: 0.0.0.0,
                            dhcpGateway: 0.0.0.0, dhcpRelay: 172.24.16.251  VLAN: 93
    *DHCP Socket Task: Apr 30 11:44:50.479: a4:c3:61:7a:1a:4f DHCP selected relay 1 - 172.24.13.251 (local address 172.24.16.251, gateway 172.24.16.254, VLAN 93, port 13)
    *DHCP Socket Task: Apr 30 11:44:50.479: a4:c3:61:7a:1a:4f DHCP transmitting DHCP DISCOVER (1)
    *DHCP Socket Task: Apr 30 11:44:50.479: a4:c3:61:7a:1a:4f DHCP   op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 1
    *DHCP Socket Task: Apr 30 11:44:50.479: a4:c3:61:7a:1a:4f DHCP   xid: 0x7e549f4a (2119475018), secs: 0, flags: 0
    *DHCP Socket Task: Apr 30 11:44:50.479: a4:c3:61:7a:1a:4f DHCP   chaddr: a4:c3:61:7a:1a:4f
    *DHCP Socket Task: Apr 30 11:44:50.479: a4:c3:61:7a:1a:4f DHCP   ciaddr: 0.0.0.0,  yiaddr: 0.0.0.0
    *DHCP Socket Task: Apr 30 11:44:50.479: a4:c3:61:7a:1a:4f DHCP   siaddr: 0.0.0.0,  giaddr: 172.24.16.251
    *DHCP Socket Task: Apr 30 11:44:50.479: a4:c3:61:7a:1a:4f DHCP selecting relay 2 - control block settings:
                            dhcpServer: 172.24.13.251, dhcpNetmask: 0.0.0.0,
                            dhcpGateway: 0.0.0.0, dhcpRelay: 172.24.16.251  VLAN: 93
    *DHCP Socket Task: Apr 30 11:44:50.479: a4:c3:61:7a:1a:4f DHCP selected relay 2 - NONE
    *DHCP Proxy Task: Apr 30 11:44:50.479: a4:c3:61:7a:1a:4f DHCP received op BOOTREPLY (2) (len 572,vlan 0, port 0, encap 0x0)
    *DHCP Proxy Task: Apr 30 11:44:50.479: a4:c3:61:7a:1a:4f DHCP sending packet in EoIP tunnel to foreign 10.65.31.8 (len 346)
    *DHCP Proxy Task: Apr 30 11:44:50.479: a4:c3:61:7a:1a:4f DHCP transmitting DHCP OFFER (2)
    *DHCP Proxy Task: Apr 30 11:44:50.479: a4:c3:61:7a:1a:4f DHCP   op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
    *DHCP Proxy Task: Apr 30 11:44:50.479: a4:c3:61:7a:1a:4f DHCP   xid: 0x7e549f4a (2119475018), secs: 0, flags: 0
    *DHCP Proxy Task: Apr 30 11:44:50.480: a4:c3:61:7a:1a:4f DHCP   chaddr: a4:c3:61:7a:1a:4f
    *DHCP Proxy Task: Apr 30 11:44:50.480: a4:c3:61:7a:1a:4f DHCP   ciaddr: 0.0.0.0,  yiaddr: 172.24.16.102
    *DHCP Proxy Task: Apr 30 11:44:50.480: a4:c3:61:7a:1a:4f DHCP   siaddr: 0.0.0.0,  giaddr: 0.0.0.0
    *DHCP Proxy Task: Apr 30 11:44:50.480: a4:c3:61:7a:1a:4f DHCP   server id: 0.0.0.0  rcvd server id: 172.24.13.251
    *DHCP Socket Task: Apr 30 11:44:51.649: a4:c3:61:7a:1a:4f DHCP received op BOOTREQUEST (1) (len 308,vlan 92, port 13, encap 0xec05)
    *DHCP Socket Task: Apr 30 11:44:51.649: a4:c3:61:7a:1a:4f DHCP selecting relay 1 - control block settings:
                            dhcpServer: 172.24.13.251, dhcpNetmask: 0.0.0.0,
                            dhcpGateway: 0.0.0.0, dhcpRelay: 172.24.16.251  VLAN: 93
    *DHCP Socket Task: Apr 30 11:44:51.649: a4:c3:61:7a:1a:4f DHCP selected relay 1 - 172.24.13.251 (local address 172.24.16.251, gateway 172.24.16.254, VLAN 93, port 13)
    *DHCP Socket Task: Apr 30 11:44:51.649: a4:c3:61:7a:1a:4f DHCP transmitting DHCP DISCOVER (1)
    *DHCP Socket Task: Apr 30 11:44:51.649: a4:c3:61:7a:1a:4f DHCP   op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 1
    *DHCP Socket Task: Apr 30 11:44:51.649: a4:c3:61:7a:1a:4f DHCP   xid: 0x7e549f4a (2119475018), secs: 1, flags: 0
    *DHCP Socket Task: Apr 30 11:44:51.649: a4:c3:61:7a:1a:4f DHCP   chaddr: a4:c3:61:7a:1a:4f
    *DHCP Socket Task: Apr 30 11:44:51.649: a4:c3:61:7a:1a:4f DHCP   ciaddr: 0.0.0.0,  yiaddr: 0.0.0.0
    *DHCP Socket Task: Apr 30 11:44:51.649: a4:c3:61:7a:1a:4f DHCP   siaddr: 0.0.0.0,  giaddr: 172.24.16.251
    *DHCP Socket Task: Apr 30 11:44:51.649: a4:c3:61:7a:1a:4f DHCP selecting relay 2 - control block settings:
                            dhcpServer: 172.24.13.251, dhcpNetmask: 0.0.0.0,
                            dhcpGateway: 0.0.0.0, dhcpRelay: 172.24.16.251  VLAN: 93
    *DHCP Socket Task: Apr 30 11:44:51.649: a4:c3:61:7a:1a:4f DHCP selected relay 2 - NONE
    *DHCP Proxy Task: Apr 30 11:44:51.649: a4:c3:61:7a:1a:4f DHCP received op BOOTREPLY (2) (len 572,vlan 0, port 0, encap 0x0)
    *DHCP Proxy Task: Apr 30 11:44:51.649: a4:c3:61:7a:1a:4f DHCP sending packet in EoIP tunnel to foreign 10.65.31.8 (len 346)
    *DHCP Proxy Task: Apr 30 11:44:51.649: a4:c3:61:7a:1a:4f DHCP transmitting DHCP OFFER (2)
    *DHCP Proxy Task: Apr 30 11:44:51.649: a4:c3:61:7a:1a:4f DHCP   op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
    *DHCP Proxy Task: Apr 30 11:44:51.650: a4:c3:61:7a:1a:4f DHCP   xid: 0x7e549f4a (2119475018), secs: 0, flags: 0
    *DHCP Proxy Task: Apr 30 11:44:51.650: a4:c3:61:7a:1a:4f DHCP   chaddr: a4:c3:61:7a:1a:4f
    *DHCP Proxy Task: Apr 30 11:44:51.650: a4:c3:61:7a:1a:4f DHCP   ciaddr: 0.0.0.0,  yiaddr: 172.24.16.102
    *DHCP Proxy Task: Apr 30 11:44:51.650: a4:c3:61:7a:1a:4f DHCP   siaddr: 0.0.0.0,  giaddr: 0.0.0.0
    *DHCP Proxy Task: Apr 30 11:44:51.650: a4:c3:61:7a:1a:4f DHCP   server id: 0.0.0.0  rcvd server id: 172.24.13.251
    *DHCP Socket Task: Apr 30 11:44:53.754: a4:c3:61:7a:1a:4f DHCP received op BOOTREQUEST (1) (len 308,vlan 92, port 13, encap 0xec05)
    *DHCP Socket Task: Apr 30 11:44:53.755: a4:c3:61:7a:1a:4f DHCP selecting relay 1 - control block settings:
                            dhcpServer: 172.24.13.251, dhcpNetmask: 0.0.0.0,
                            dhcpGateway: 0.0.0.0, dhcpRelay: 172.24.16.251  VLAN: 93
    *DHCP Socket Task: Apr 30 11:44:53.755: a4:c3:61:7a:1a:4f DHCP selected relay 1 - 172.24.13.251 (local address 172.24.16.251, gateway 172.24.16.254, VLAN 93, port 13)
    *DHCP Socket Task: Apr 30 11:44:53.755: a4:c3:61:7a:1a:4f DHCP transmitting DHCP DISCOVER (1)
    *DHCP Socket Task: Apr 30 11:44:53.755: a4:c3:61:7a:1a:4f DHCP   op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 1
    *DHCP Socket Task: Apr 30 11:44:53.755: a4:c3:61:7a:1a:4f DHCP   xid: 0x7e549f4a (2119475018), secs: 3, flags: 0
    *DHCP Socket Task: Apr 30 11:44:53.755: a4:c3:61:7a:1a:4f DHCP   chaddr: a4:c3:61:7a:1a:4f
    *DHCP Socket Task: Apr 30 11:44:53.755: a4:c3:61:7a:1a:4f DHCP   ciaddr: 0.0.0.0,  yiaddr: 0.0.0.0
    *DHCP Socket Task: Apr 30 11:44:53.755: a4:c3:61:7a:1a:4f DHCP   siaddr: 0.0.0.0,  giaddr: 172.24.16.251
    *DHCP Socket Task: Apr 30 11:44:53.755: a4:c3:61:7a:1a:4f DHCP selecting relay 2 - control block settings:
                            dhcpServer: 172.24.13.251, dhcpNetmask: 0.0.0.0,
                            dhcpGateway: 0.0.0.0, dhcpRelay: 172.24.16.251  VLAN: 93
    *DHCP Socket Task: Apr 30 11:44:53.755: a4:c3:61:7a:1a:4f DHCP selected relay 2 - NONE
    *DHCP Proxy Task: Apr 30 11:44:53.755: a4:c3:61:7a:1a:4f DHCP received op BOOTREPLY (2) (len 572,vlan 0, port 0, encap 0x0)
    *DHCP Proxy Task: Apr 30 11:44:53.755: a4:c3:61:7a:1a:4f DHCP sending packet in EoIP tunnel to foreign 10.65.31.8 (len 346)
    *DHCP Proxy Task: Apr 30 11:44:53.755: a4:c3:61:7a:1a:4f DHCP transmitting DHCP OFFER (2)
    *DHCP Proxy Task: Apr 30 11:44:53.755: a4:c3:61:7a:1a:4f DHCP   op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
    *DHCP Proxy Task: Apr 30 11:44:53.755: a4:c3:61:7a:1a:4f DHCP   xid: 0x7e549f4a (2119475018), secs: 0, flags: 0
    *DHCP Proxy Task: Apr 30 11:44:53.755: a4:c3:61:7a:1a:4f DHCP   chaddr: a4:c3:61:7a:1a:4f
    *DHCP Proxy Task: Apr 30 11:44:53.755: a4:c3:61:7a:1a:4f DHCP   ciaddr: 0.0.0.0,  yiaddr: 172.24.16.102
    *DHCP Proxy Task: Apr 30 11:44:53.755: a4:c3:61:7a:1a:4f DHCP   siaddr: 0.0.0.0,  giaddr: 0.0.0.0
    *DHCP Proxy Task: Apr 30 11:44:53.755: a4:c3:61:7a:1a:4f DHCP   server id: 0.0.0.0  rcvd server id: 172.24.13.251
    *DHCP Socket Task: Apr 30 11:44:58.594: a4:c3:61:7a:1a:4f DHCP received op BOOTREQUEST (1) (len 308,vlan 92, port 13, encap 0xec05)
    *DHCP Socket Task: Apr 30 11:44:58.594: a4:c3:61:7a:1a:4f DHCP selecting relay 1 - control block settings:
                            dhcpServer: 172.24.13.251, dhcpNetmask: 0.0.0.0,
                            dhcpGateway: 0.0.0.0, dhcpRelay: 172.24.16.251  VLAN: 93
    *DHCP Socket Task: Apr 30 11:44:58.594: a4:c3:61:7a:1a:4f DHCP selected relay 1 - 172.24.13.251 (local address 172.24.16.251, gateway 172.24.16.254, VLAN 93, port 13)
    *DHCP Socket Task: Apr 30 11:44:58.594: a4:c3:61:7a:1a:4f DHCP transmitting DHCP DISCOVER (1)
    *DHCP Socket Task: Apr 30 11:44:58.594: a4:c3:61:7a:1a:4f DHCP   op: BOOTREQUEST, htype: Ethernet, hlen: 6, hops: 1
    *DHCP Socket Task: Apr 30 11:44:58.594: a4:c3:61:7a:1a:4f DHCP   xid: 0x7e549f4a (2119475018), secs: 8, flags: 0
    *DHCP Socket Task: Apr 30 11:44:58.594: a4:c3:61:7a:1a:4f DHCP   chaddr: a4:c3:61:7a:1a:4f
    *DHCP Socket Task: Apr 30 11:44:58.594: a4:c3:61:7a:1a:4f DHCP   ciaddr: 0.0.0.0,  yiaddr: 0.0.0.0
    *DHCP Socket Task: Apr 30 11:44:58.594: a4:c3:61:7a:1a:4f DHCP   siaddr: 0.0.0.0,  giaddr: 172.24.16.251
    *DHCP Socket Task: Apr 30 11:44:58.595: a4:c3:61:7a:1a:4f DHCP selecting relay 2 - control block settings:
                            dhcpServer: 172.24.13.251, dhcpNetmask: 0.0.0.0,
                            dhcpGateway: 0.0.0.0, dhcpRelay: 172.24.16.251  VLAN: 93
    *DHCP Socket Task: Apr 30 11:44:58.595: a4:c3:61:7a:1a:4f DHCP selected relay 2 - NONE
    *DHCP Proxy Task: Apr 30 11:44:58.595: a4:c3:61:7a:1a:4f DHCP received op BOOTREPLY (2) (len 572,vlan 0, port 0, encap 0x0)
    *DHCP Proxy Task: Apr 30 11:44:58.595: a4:c3:61:7a:1a:4f DHCP sending packet in EoIP tunnel to foreign 10.65.31.8 (len 346)
    *DHCP Proxy Task: Apr 30 11:44:58.595: a4:c3:61:7a:1a:4f DHCP transmitting DHCP OFFER (2)
    *DHCP Proxy Task: Apr 30 11:44:58.595: a4:c3:61:7a:1a:4f DHCP   op: BOOTREPLY, htype: Ethernet, hlen: 6, hops: 0
    *DHCP Proxy Task: Apr 30 11:44:58.595: a4:c3:61:7a:1a:4f DHCP   xid: 0x7e549f4a (2119475018), secs: 0, flags: 0
    *DHCP Proxy Task: Apr 30 11:44:58.595: a4:c3:61:7a:1a:4f DHCP   chaddr: a4:c3:61:7a:1a:4f
    *DHCP Proxy Task: Apr 30 11:44:58.595: a4:c3:61:7a:1a:4f DHCP   ciaddr: 0.0.0.0,  yiaddr: 172.24.16.102
    *DHCP Proxy Task: Apr 30 11:44:58.595: a4:c3:61:7a:1a:4f DHCP   siaddr: 0.0.0.0,  giaddr: 0.0.0.0
    *DHCP Proxy Task: Apr 30 11:44:58.595: a4:c3:61:7a:1a:4f DHCP   server id: 0.0.0.0  rcvd server id: 172.24.13.251
    *DHCP Socket Task: Apr 30 11:45:07.059: a4:c3:61:7a:1a:4f DHCP received op BOOTREQUEST (1) (len 308,vlan 92, port 13, encap 0xec05)
    *DHCP Socket Task: Apr 30 11:45:07.059: a4:c3:61:7a:1a:4f DHCP selecting relay 1 - control block settings:
                            dhcpServer: 172.24.13.251, dhcpNetmask: 0.0.0.0,

    Thanks Scott,  here you go...
    On Foreign:
    WLAN Identifier.................................. 2
    Profile Name..................................... BAI-Beta
    Network Name (SSID).............................. BAI-Beta
    Status........................................... Enabled
    MAC Filtering.................................... Disabled
    Broadcast SSID................................... Disabled
    AAA Policy Override.............................. Disabled
    Network Admission Control
      Client Profiling Status ....................... Disabled
       DHCP ......................................... Disabled
       HTTP ......................................... Disabled
      Radius-NAC State............................... Disabled
      SNMP-NAC State................................. Disabled
      Quarantine VLAN................................ 0
    Maximum number of Associated Clients............. 0
    Maximum number of Clients per AP Radio........... 200
    Number of Active Clients......................... 42
    Exclusionlist Timeout............................ 60 seconds
    Session Timeout.................................. 86400 seconds
    User Idle Timeout................................ 300 seconds
    --More-- or (q)uit
    User Idle Threshold.............................. 0 Bytes
    NAS-identifier................................... CHTWLC
    CHD per WLAN..................................... Enabled
    Webauth DHCP exclusion........................... Disabled
    Interface........................................ management
    Multicast Interface.............................. Not Configured
    WLAN IPv4 ACL.................................... unconfigured
    WLAN IPv6 ACL.................................... unconfigured
    mDNS Status...................................... Enabled
    mDNS Profile Name................................ default-mdns-profile
    DHCP Server...................................... Default
    DHCP Address Assignment Required................. Enabled
    Static IP client tunneling....................... Disabled
    PMIPv6 Mobility Type............................. none
    Quality of Service............................... Bronze
    Per-SSID Rate Limits............................. Upstream      Downstream
    Average Data Rate................................   0             0
    Average Realtime Data Rate.......................   0             0
    Burst Data Rate..................................   0             0
    Burst Realtime Data Rate.........................   0             0
    Per-Client Rate Limits........................... Upstream      Downstream
    Average Data Rate................................   0             0
    Average Realtime Data Rate.......................   0             0
    --More-- or (q)uit
    Burst Data Rate..................................   0             0
    Burst Realtime Data Rate.........................   0             0
    Scan Defer Priority.............................. 5,6
    Scan Defer Time.................................. 100 milliseconds
    WMM.............................................. Disabled
    WMM UAPSD Compliant Client Support............... Disabled
    Media Stream Multicast-direct.................... Disabled
    CCX - AironetIe Support.......................... Enabled
    CCX - Gratuitous ProbeResponse (GPR)............. Disabled
    CCX - Diagnostics Channel Capability............. Disabled
    Dot11-Phone Mode (7920).......................... Disabled
    Wired Protocol................................... None
    Passive Client Feature........................... Disabled
    Peer-to-Peer Blocking Action..................... Disabled
    Radio Policy..................................... All
    DTIM period for 802.11a radio.................... 1
    DTIM period for 802.11b radio.................... 1
    Radius Servers
       Authentication................................ 172.24.13.20 1812
       Accounting.................................... Disabled
       Dynamic Interface............................. Disabled
       Dynamic Interface Priority.................... wlan
    Local EAP Authentication......................... Disabled
    --More-- or (q)uit
    Security
       802.11 Authentication:........................ Open System
       FT Support.................................... Disabled
       Static WEP Keys............................... Disabled
       802.1X........................................ Disabled
       Wi-Fi Protected Access (WPA/WPA2)............. Enabled
          WPA (SSN IE)............................... Disabled
          WPA2 (RSN IE).............................. Enabled
             TKIP Cipher............................. Disabled
             AES Cipher.............................. Enabled
                                                                   Auth Key Management
             802.1x.................................. Enabled
             PSK..................................... Disabled
             CCKM.................................... Disabled
             FT-1X(802.11r).......................... Disabled
             FT-PSK(802.11r)......................... Disabled
             PMF-1X(802.11w)......................... Disabled
             PMF-PSK(802.11w)........................ Disabled
          FT Reassociation Timeout................... 20
          FT Over-The-DS mode........................ Enabled
          GTK Randomization.......................... Disabled
          SKC Cache Support.......................... Disabled
    --More-- or (q)uit
          CCKM TSF Tolerance......................... 1000
       WAPI.......................................... Disabled
       Wi-Fi Direct policy configured................ Disabled
       EAP-Passthrough............................... Disabled
       CKIP ......................................... Disabled
       Web Based Authentication...................... Disabled
       Web-Passthrough............................... Disabled
       Conditional Web Redirect...................... Disabled
       Splash-Page Web Redirect...................... Disabled
       Auto Anchor................................... Enabled
       FlexConnect Local Switching................... Disabled
       flexconnect Central Dhcp Flag................. Disabled
       flexconnect nat-pat Flag...................... Disabled
       flexconnect Dns Override Flag................. Disabled
       FlexConnect Vlan based Central Switching ..... Disabled
       FlexConnect Local Authentication.............. Disabled
       FlexConnect Learn IP Address.................. Enabled
       Client MFP.................................... Optional
       PMF........................................... Disabled
       PMF Association Comeback Time................. 1
       PMF SA Query RetryTimeout..................... 200
       Tkip MIC Countermeasure Hold-down Timer....... 60
    AVC Visibilty.................................... Disabled
    --More-- or (q)uit
    AVC Profile Name................................. None
    Flow Monitor Name................................ None
    Call Snooping.................................... Disabled
    Roamed Call Re-Anchor Policy..................... Disabled
    SIP CAC Fail Send-486-Busy Policy................ Enabled
    SIP CAC Fail Send Dis-Association Policy......... Disabled
    KTS based CAC Policy............................. Disabled
    Assisted Roaming Prediction Optimization......... Disabled
    802.11k Neighbor List............................ Disabled
    802.11k Neighbor List Dual Band.................. Disabled
    Band Select...................................... Disabled
    Load Balancing................................... Disabled
    Multicast Buffer................................. Disabled
     Mobility Anchor List
     WLAN ID     IP Address            Status
     2           172.24.13.251        Up
    802.11u........................................ Disabled
    MSAP Services.................................. Disabled
    On Anchor:
    WLAN Identifier.................................. 1
    Profile Name..................................... BAI-Beta
    Network Name (SSID).............................. BAI-Beta
    Status........................................... Enabled
    MAC Filtering.................................... Disabled
    Broadcast SSID................................... Disabled
    AAA Policy Override.............................. Disabled
    Network Admission Control
      Client Profiling Status ....................... Disabled
       DHCP ......................................... Disabled
       HTTP ......................................... Disabled
      Radius-NAC State............................... Disabled
      SNMP-NAC State................................. Disabled
      Quarantine VLAN................................ 0
    Maximum number of Associated Clients............. 0
    Maximum number of Clients per AP Radio........... 200
    Number of Active Clients......................... 48
    Exclusionlist Timeout............................ 60 seconds
    Session Timeout.................................. 86400 seconds
    User Idle Timeout................................ 300 seconds
    --More-- or (q)uit
    User Idle Threshold.............................. 0 Bytes
    NAS-identifier................................... CHADWLC01
    CHD per WLAN..................................... Enabled
    Webauth DHCP exclusion........................... Disabled
    Interface........................................ bai-beta
    Multicast Interface.............................. Not Configured
    WLAN IPv4 ACL.................................... unconfigured
    WLAN IPv6 ACL.................................... unconfigured
    mDNS Status...................................... Enabled
    mDNS Profile Name................................ default-mdns-profile
    DHCP Server...................................... Default
    DHCP Address Assignment Required................. Enabled
    Static IP client tunneling....................... Disabled
    PMIPv6 Mobility Type............................. none
    Quality of Service............................... Bronze
    Per-SSID Rate Limits............................. Upstream      Downstream
    Average Data Rate................................   0             0
    Average Realtime Data Rate.......................   0             0
    Burst Data Rate..................................   0             0
    Burst Realtime Data Rate.........................   0             0
    Per-Client Rate Limits........................... Upstream      Downstream
    Average Data Rate................................   0             0
    Average Realtime Data Rate.......................   0             0
    --More-- or (q)uit
    Burst Data Rate..................................   0             0
    Burst Realtime Data Rate.........................   0             0
    Scan Defer Priority.............................. 5,6
    Scan Defer Time.................................. 100 milliseconds
    WMM.............................................. Disabled
    WMM UAPSD Compliant Client Support............... Disabled
    Media Stream Multicast-direct.................... Disabled
    CCX - AironetIe Support.......................... Enabled
    CCX - Gratuitous ProbeResponse (GPR)............. Disabled
    CCX - Diagnostics Channel Capability............. Disabled
    Dot11-Phone Mode (7920).......................... Disabled
    Wired Protocol................................... None
    Passive Client Feature........................... Disabled
    Peer-to-Peer Blocking Action..................... Disabled
    Radio Policy..................................... All
    DTIM period for 802.11a radio.................... 1
    DTIM period for 802.11b radio.................... 1
    Radius Servers
       Authentication................................ 172.24.13.20 1812
       Accounting.................................... Disabled
       Dynamic Interface............................. Disabled
       Dynamic Interface Priority.................... wlan
    Local EAP Authentication......................... Disabled
    --More-- or (q)uit
    Security
       802.11 Authentication:........................ Open System
       FT Support.................................... Disabled
       Static WEP Keys............................... Disabled
       802.1X........................................ Disabled
       Wi-Fi Protected Access (WPA/WPA2)............. Enabled
          WPA (SSN IE)............................... Disabled
          WPA2 (RSN IE).............................. Enabled
             TKIP Cipher............................. Disabled
             AES Cipher.............................. Enabled
                                                                   Auth Key Management
             802.1x.................................. Enabled
             PSK..................................... Disabled
             CCKM.................................... Disabled
             FT-1X(802.11r).......................... Disabled
             FT-PSK(802.11r)......................... Disabled
             PMF-1X(802.11w)......................... Disabled
             PMF-PSK(802.11w)........................ Disabled
          FT Reassociation Timeout................... 20
          FT Over-The-DS mode........................ Enabled
          GTK Randomization.......................... Disabled
          SKC Cache Support.......................... Disabled
    --More-- or (q)uit
          CCKM TSF Tolerance......................... 1000
       WAPI.......................................... Disabled
       Wi-Fi Direct policy configured................ Disabled
       EAP-Passthrough............................... Disabled
       CKIP ......................................... Disabled
       Web Based Authentication...................... Disabled
       Web-Passthrough............................... Disabled
       Conditional Web Redirect...................... Disabled
       Splash-Page Web Redirect...................... Disabled
       Auto Anchor................................... Enabled
       FlexConnect Local Switching................... Disabled
       flexconnect Central Dhcp Flag................. Disabled
       flexconnect nat-pat Flag...................... Disabled
       flexconnect Dns Override Flag................. Disabled
       FlexConnect Vlan based Central Switching ..... Disabled
       FlexConnect Local Authentication.............. Disabled
       FlexConnect Learn IP Address.................. Enabled
       Client MFP.................................... Optional
       PMF........................................... Disabled
       PMF Association Comeback Time................. 1
       PMF SA Query RetryTimeout..................... 200
       Tkip MIC Countermeasure Hold-down Timer....... 60
    AVC Visibilty.................................... Disabled
    --More-- or (q)uit
    AVC Profile Name................................. None
    Flow Monitor Name................................ None
    Call Snooping.................................... Disabled
    Roamed Call Re-Anchor Policy..................... Disabled
    SIP CAC Fail Send-486-Busy Policy................ Enabled
    SIP CAC Fail Send Dis-Association Policy......... Disabled
    KTS based CAC Policy............................. Disabled
    Assisted Roaming Prediction Optimization......... Disabled
    802.11k Neighbor List............................ Disabled
    802.11k Neighbor List Dual Band.................. Disabled
    Band Select...................................... Disabled
    Load Balancing................................... Disabled
    Multicast Buffer................................. Disabled
     Mobility Anchor List
     WLAN ID     IP Address            Status
     1           172.24.13.251        Up
    802.11u........................................ Disabled
    MSAP Services.................................. Disabled

  • WLC 5508 with version 7.0.98.0 and AIR-LAP1242ag

    hi, recently i have deployed wlc 5508 with ap 1262. initially i had trouble with the existing version on the wlc (6..0.199.0) which AIR-LAP1262N-E-K9 was not registering with wlc. i have upgraded the wlc to 6.0.199.4 ver still it was not registering. finally i have upgraded to 7.0.98.0 and all the 40 AP's ( AIR-LAP1262N-E-K9 ) are addedd and its working fine.
    Now my issue is, at the same site i have 12 nos of AIR-LAP1242ag autnomous AP's which i need to convert to lightweight ap and register with wlc. where i am stuck currently. after loading the recovery image (c1240-rcvk9w8-tar.123-7.JX9.tar) the ap reboots and can see it register with wlc within seconds contollers pushed the new image and once the ap reboots, never register again.
    does anyone has any idea?

    After adding the country codes GB and RU.. in my test setup 1242 is registered...i will have it run for couple hours and see the result
    ref: below
    (Cisco Controller) >show ap uptime
    Number of APs.................................... 2
    Global AP User Name.............................. Not Configured
    Global AP Dot1x User Name........................ Not Configured
    AP Name              Ethernet MAC       AP Up Time               Association Up Time
    AP1cdf.0f66.79ca     1c:df:0f:66:79:ca  0 days, 00 h 43 m 35 s   0 days, 00 h 42 m 36 s
    AP001e.be27.a7e6     00:1e:be:27:a7:e6  0 days, 00 h 16 m 56 s   0 days, 00 h 07 m 15
    This issue sorted...thanks

  • LAG WLC 5508 7.0.235 and Nexus 7K 5.2(3a)

    I can't get the WLC to form a LAG, the 5508 has 2 SFPs direct to Nexus 7k.  Enabled LAG and rebooted.  The 5508s port 2 just stays Link Down in WLC.
    hostname n7k-01
    int port-channel 31
    vpc 31
    int eth1/12
    description WLC-5508-Port1
    switchport
    switchport mode trunk
    channel-group 31 mode active
    no shut
    show run int eth1/12
    Ethernet1/12 is up
      Dedicated Interface
      Belongs to Po31
    hostname n7k-02
    int port-channel 31
    vpc 31
    int eth1/7
    description WLC-5508-Port2
    switchport
    switchport mode trunk
    channel-group 31 mode active
    no shut
    show run int eth1/7
    Ethernet 1/7 is down (Link not connected)
      Dedicated Interface
      Belongs to Po31

    Controller cannot establish SXP connection with a Cisco Nexus 7000 Series switch.
    Symptom: An SXP connection from the controller to the Cisco Nexus 7000 Series switch reports the On state on the controller side while the switch reports the Waiting for Response state.
    Conditions: Establishing SXP connection between the controller and ASA.
    Workaround: Add an intermediate device that supports SXPv2 between the controller and the Cisco Nexus 7000 Series switch.

  • WLC 5508 and mobility groups

    Hi,
    We are using 2 WLC 5508 running 7.0.98.0 sw (AP's are 1142) at our primary site. They are hosting 3 different WLAN/SSID's, one for guest and the
    other 2 are for corporate access. We have put the WLC's in a mobility group, say "AAAA".
    Now we have the need for our UK peer site to publish a corp WLAN that exists in UK - at our site, and when trying to configure for that (following the c70cg.pdf) - I put the WLC's for UK in a new mobility group, say "BBBB". But i can't add our WLC's into that mobilty group
    (i get a duplicate mac address message).
    What's the correct way of configuring this, does all WLCs need to be in the same mobility group?
    Is there some reason why we can't have 2 mobility groups? Is there any upside/downside to configuring 2 mob. groups?
    Any clearification would be greatly appreciated
    BR
    //Mikael

    I think you are misunderstanding , so far what you did on your local swedish site is correct. Your two swedish WLCs have to be in their own same mobility group so you can give seamless roaming to your wireless users across your swedish area without interruption.
    On a WLC mobility group config page, you can have only one entry  per WLC, this is why you are getting the duplicate error message.
    WEBGUI - CONTROLLER - MOBILITY MANAGEMENT - MOBILITY GROUPS
    If you want to put your 4 WLCs so they exchange mobility messages, the following has to happen on all 4 WLCs.
    xx:xx:xx:xx:xx:xx  192.168.1.1  uk
    yy:yy:yy:yy:yy:yy 192.168.1.2 uk
    zz:zz:zz:zz:zz:zz  172.17.1.1  sweden
    aa:aa:aa:aa:aa:aa  172.17.1.2  sweden
    Note when you add WLC on the mobility section, the WLC start sending messages to each like, hey i have this client and you have that client and so on. But this has nothing to do with what you are trying to achieve.
    With regards to the execs that are coming, yes, replicate the SSID and point it to the Radius Server they have in UK, add your swedish WLC(s) as a NAS on the Radius Server and it should work as if they were in UK. that should be enough and i advise you to do the following for mobility groups config.
    on the two UK WLCs
    xx:xx:xx:xx:xx:xx  192.168.1.1  uk
    yy:yy:yy:yy:yy:yy 192.168.1.2 uk
    on the two Swedish WLCs
    zz:zz:zz:zz:zz:zz  172.17.1.1  sweden
    aa:aa:aa:aa:aa:aa  172.17.1.2  sweden
    hope i cleared it out for you. greeting from cold Belgium tonight :-) and hope the execs will enjoy Sweden!

  • WLC 5508, Prime Infrastructure, 7921 phones and QoS

    Hi everybody!
    I have deployed about 50 wireless cisco phones int the network with 27 APs with the WLC 5508.
    I'm trying to investigate phones behaviour (I have some loss of audio).
    And I use Prime Infrastructure for monitoring.
    I run the Voice Diagnostic on the selected two phones.
    and in the Charts I see the next:
    1. for one phone "Downlink AC Queue Usage" shows all the traffic of "voice packets". but "Uplink AC Queue Usage" shows all the traffic of the "Best efforts packets".
    2. for the second phone "Downlink AC Queue Usage" shows all the traffic of "Best efforts packets". and "Uplink AC Queue Usage" shows all the traffic of the "Video packets".
    that is strange, very strange. the WLAN of these phones uses platinum QoS. none of other WLANs uses "gold" QoS.
    does this mean I have a QoS misconfiguration?
    where may the failure be? WLC? switches? router?
    please, any suggestions...

    I noticed few misconfigurations as per your response
    1. Are you configured AP as FlexConnect ?  If not AP connected switchport should be configured as ACCESS port & trust DSCP. If it is configured as FlexConnect, then you can configure switchport as turnk & in that case you  have to trust CoS using "mls qos trusct cos" command.
    2. WLC connected trunk ports always to be configured to trust CoS not DSCP. Otherwise WLC set QoS value ignored by your switch.
    3. If you WLAN is set for Platinum then you have to configure Platinum QoS profile for 802.1p & set value as 6.
    I would suggest you to verify QoS value preserve across you switch network. You have to take some wireshark packet caputres (as shown in my reference link) and make sure your voice packet DSCP goes into rest of your network as EF. You need to do this for upstream & downstream (from 7921 perspective) traffic. Here is the traffic flow if AP connected to switchport 1 & WLC connnected to switchport 2.
    7921 <-> AP <-> Switch port 1 <->  Switchport 2 <->  WLC <-> Switchport2 <-> Rest of your network
    Once you do this, then you can go to Prime & check those charts to reflect QoS values correctly. Otherwise you do not know where these QoS value get stripped/or modified in your network.
    HTH
    Rasika
    **** Pls rate all useful responses ****

  • WLC 5508 and AIR CAP 1602I

    Hello,
    We've got a problem with the AP (AIR CAP 1602I) which is managed by WLC 5508(7.4.100.60)
    Users connect to the AP with VOIP phones(Avaya).. and there are following problems during calls
    -robot voice
    -strong noise(even if call is not made, just speaker is on)
    Strange thing is that there is no problem with older APs which are managed with the same WLC.
    Any idea?
    Thanks in advance

    Well that can be a cause also. I would look at using 7.4.110.0 which is MR1. If that doesn't help, then open a TAC case as it might be something else. Going to v7.5 I don't think will fix the issue.
    Many times I would go the the manufacture and find out if the support a certain code or not. It's nice when they do test to make sure it still works. Some manufactures do test and will suggest code versions and that's when you have to decide if the 1602 was really needed or just keep adding 1262's since there was only 3 added.
    Sent from Cisco Technical Support iPhone App

Maybe you are looking for