WLC IP Conflict with AP-Manager Interface

I am getting an error log in the WLC saying, its IP address is being used by another machine with MAC address A.B.C.D
But this MAC address A.B.C.D is the MAC address of the AP-Manager Interface in the same controller.
have anyone faced an issue like this ?
The same issue is having in another controller also. But I have two more controllers with the same IOS , which are working fine.

Hey Scott...
Thanks for ua quick response.
We have controller 4402.
We have all the two ports connected to core. But we have enabled LAG as well.
It was working perfect since almost an year and half. Recently we had an image upgradation to 6.0.182.0.
Upgradation was done for all the 5 controllers. But two are having this error log since then.
Its not continously coming.. Only sometimes..

Similar Messages

  • LAP registration with ap-manager interface only

    Hi, is it possible to register an APs with no visibility of the management interface? The WLC would have a separate ap-manager interface but in a different vfr then management interface. APs can see the ap-manager interface one but not the management one.

    I don't mind to use for example service port for the isolated management. But i heared the service port has restrictions under HA design.
    Exactly what firmware or model of WLC are you using? 
    You can't use ther Service Port for production.  This port is primarily used for Out-of-Band-Management and for HA SSO.
    The document is dated five years ago and describes the 4.0 SW. My question was if there is any trick or possibility to arrange it under present HW & SW.
    The document may be five years old, but when you are dealing with WLC 4400, WiSM or 2000/2100 then it's still valid.  The APs talk to the controller using the AP-manager interface.  This is the main reason why AP-manager interface and management interface IP addresses is recommended to be in the same subnet.  It will work if either one is on a different subnet but you'll need to do some routing work done.

  • Conflict with font management program

    Hello,
    When I open Dreamweaver I get an endless stream of messages saying that there is a problem with the fonts.  They keep on coming and I have to force quit Dreamweaver, turn of Extensis, and then start up Dreamweaver again.  Please see the attached screen shot.
    My system is Mac OS 10.4.11, and for the past 4 years I've been using Extensis Suitcase to manage my fonts.
    Is there a way to avoid this conflict?  Maybe it's a matter of setting a preference somewhere?  And is there a better font management program?  I'd like to avoid shelling out more $$$ on new software, if possible.
    Thanks for the help!

    Here's a thread that might help:
    http://forums.adobe.com/thread/223254

  • Photoshop CS 6 repeatedly launching, conflict with Application Manager

    I am now getting multiple systems that will not open Photoshop CS 6.  As soon as PS starts to open, Application Manager starts and prevents PS from opening.  The two applications alternate for control with neither being able to open.  This problem is also occurring with Illustrator CS 6 and now has started in Photoshop. 
    When the "fight" starts you have to do a forced shut down (power button for 10 seconds) in order to be able to login.  Then Uninstalling the application, either by the Uninstaller of PS or by using the ELA uninstaller created when the Install package is created.  Systems are Apple 10.8.2 with Adobe Application Manager Enterprise Created installer for Master Suite.
    This has now appeared on six or seven systems of the approximatly 200 that got the install.  The applications ran normally with no problems for about two weeks bu now the problems are popping up for no appearent reason.

    Thank you for the video.  It is exactly what has been reported by me and some others in the Illustrator forum also.  To me a "crash" is when a program fails to open properly and requires a forced power off to recover the computer.  I will add that the same problem as shown will appear again as soon as Photoshop (or Illustrator if that is the broken program) is reopened.  The problem will remain until PS (or AI) is uninstalled and reinstalled.  The version I have for the installer is the older 13.1 but that had worked for several weeks and this problem just started recently and I had not installed (at least knowingly) any changed software be it PS, AI or AAM. prior to that time.  I did have some systems at the latest update and at least one of those failed also.
    I have tried creating an Update package from AAMEE but the package that is created does not install using Apple Remote Desktop nor does it install if the created package is copied to the desktop of the system I am trying to update.
    It is looking to me like the problem is located in the Adobe Application Manager since that app is common to both Photoshop and Illustrator.  I have tried using the AAM that installs as part of the Master Suite and the first thing it does is update itself.  My guess is that this "update" that AAM self-installs is broken and is causing the problem.  That is only my guess based on my observations.  Perhaps someone can come up with a way to prove or disprove my guess.
    My next project for tomorrow will be to try to create a brand new installer with all updates since trying to individually use the Update button in the actual Photoshop  does work but I'll be damned if I am going to visit two hundred seperate machines to have to install the update on each and every system as a stand alone update, especially since I have already had at least one system that I know was on the latest update but still failed in exactly the way your video shows.
    A follow up will be to try to remove the AAM and reinstall a new version from the Adobe web site just to see if that helps, hurts or has no discernable effect.

  • Recent Fingerprint Reader update conflicts with Password Manager

    Hi,
    After udating my Fingerprint Reader software to the most recent 64-bit 5.9.6.7084 version, my Password Manager (ver 3.20.0333.00) can no longer find the device. Am I the only one having this problem?
    Solved!
    Go to Solution.

    You are using the older Password Manager that's bundled with Client Security Solution.  And you need to update it to use the latest fingerprint software.
    http://support.lenovo.com/en_VN/detail.page?LegacyDocID=MIGR-73696
    If you don't need the complexity of Client Security Solution, then another option is to start using the new stand-alone Password Manager 4.0 
    http://support.lenovo.com/en_US/downloads/detail.page?DocID=DS024984

  • How to Resolve Bitnami/MAMP Conflict with Profile Manager

    I've been working on a new Lion Server for several weeks, and most of my services work great. However, I want to set up several development environments for WP, Drupal, and Magento, among other things. I prefer to use something like MAMP Pro or, in this case, Bitnami stacks for my various environments. However, this machine currently is used for managing Wiki, Profile Manager, and Device Manager, among other things. Of course, if you activate the Bitnami MAMPstack, that poses an issue for Profile Manager, as both use the 80 and 443 ports, I presume. So, the question is how can I configure Lion Server to run Bitnami (or MAMP Pro, as an alternate possibility) and not break Profile Manager, Wiki, Device Manager, etc.?

    Let me edit the statement a bit. Device Manager is the term that I intuitively have attached to the link https://server/mydevices, which is nothing more than a web interface for adding profiles to your Mac and iOS devices. Apple doesn't call it that, but I have taken to doing so, so when I'm referring to it, that's what it is.
    Anyway, I haven't tried Wiki on its own, but I know that if I activate MAMP, or BitNami, and I run Profile Manager, it is inaccessible. Obviously, there is a conf setup, or something I am missing here, but I'm not finding it in the server documentation, if it exists at all.

  • WLC 5508 with 6.0.188 -- ap-manager interface..

    6.0.188 code on new 5508 WLC does not show ap-manager interface.
    6.0.188 code on 4404 wlc does have ap-manager interface.
    Both are working fine.
    Why is that?

    The 5500 controllers use the management interface to function as both the management interface and ap-manager.  There will not be an ap-manager in the 5500.

  • Mobility group only works using management interface?

    Hello,  in order to stablish the control traffic between 2 WLC-5508, it's necessary to use the management interface??
    It's possible using a dynamic interface o service port ?
    I think it only works with management interface,  but I don't understand the meaning of this text in the Configuration Manual:
    "Mobility control packets can use any interface address as the source, based on routing table."
    Thank you,

    No... mobility communication is done only with the management interface.
    Thanks,
    Scott
    *****Help out other by using the rating system and marking answered questions as "Answered"*****

  • WLC Duplicate IP address detected for AP-Manager Interface

    I am getting an error log in the WLC saying, its IP address is duplicate by another machine with MAC address A.B.C.D
    But this MAC address A.B.C.D is the MAC address of the AP-Manager Interface in the same controller.
    Model No.                   AIR-WLC2106-K9
    Software Version                 7.0.116.0
    %LWAPP-3-DUP_IP: spam_lrad.c:27626 Adding client 58:b0:35:83:72:86 to  exclusion list due to IP Address conflict with AP 'AP_DUXO_3'
    %LWAPP-3-DUP_AP_IP: spam_lrad.c:27612 Duplicate IP address  detected for AP AP_DUXO_3, IP address of AP  10.184.1.224, this is a  duplicate of IP on another machine (MAC address 58:b0:35:83:72:86)
    Cisco AP Identifier.............................. 1
    Cisco AP Name.................................... AP_DUXO_3
    Country code..................................... US  - United States
    Regulatory Domain allowed by Country............. 802.11bg:-A     802.11a:-A
    AP Country code.................................. US  - United States
    AP Regulatory Domain............................. 802.11bg:-A    802.11a:-N
    Switch Port Number .............................. 1
    MAC Address...................................... cc:ef:48:1a:e4:af
    IP Address Configuration......................... Static IP assigned
    IP Address....................................... 10.184.1.224
    IP NetMask....................................... 255.255.0.0
    Gateway IP Addr.................................. 10.184.20.2
    Domain...........................................
    Name Server......................................
    NAT External IP Address.......................... None
    CAPWAP Path MTU.................................. 1485
    Telnet State..................................... Enabled
    Ssh State........................................ Disabled
    Cisco AP Location................................ DUXO_BOX
    Cisco AP Group Name.............................. default-group
    Does anyone have an issue like this ?

    Are you sure this MAC address 58:b0:35:83:72:86 isn't some type of Apple device?  Its OUI is registered to apple.  How do clients get ip addresses DHCP?  It appears that the IP 10.184.1.224 is statically assigned to your ap-manager and that this client 58:b0:35:83:72:86 is either getting that same IP from DHCP or the client is statically assigning it themselves. 

  • WLC to use Management Interface & Few more getting started Questions

    Hello,
    I'm yet to implement the Wireless LAN in one of our client's corporate office. There 40 x 1130AG LWAPP AP's and 4404 WLC with ACS 4.x for the Authentication of the Wireless Clients who is trying to access the LAN.
    For the WLC to connect to the Dual Core Switch, i need to use only one Management Interface with Distribution System port 1 being the Primary and mapping the DS Port 2 as the Backup port for the Management Interface. Is this Right? or do i have configure Dynamic Interfaces as well. Is management interface for accessing / management and configuration only? Management Interface will communicate with ACS for AAA and AP's who would like to associate with the WLC, is this Right?
    Note: WLC, AP's, Wireless Clients & AP's are in the same IP Subnet.
    Few other question of WLAN's so it helps me during implementation -
    • Can I use the 802.1x Authentication application found in the Windows XP for the Wireless Interface; instead of Cisco Client Application. For this; I have to configure the WLC / Wireless Client to use EAP algorithm; is this Right?
    • With the help of RRM, the channel interference between multiple AP's (3 - 4 AP's) in the same area is controlled by the WLC by changing the Channels used by the AP which is not same on all the AP's. Is this right?
    • How many Client Users will connect per Channels. 802.11 a / g will provide 11 Channels, is this Right?.
    • I'm trying to set in the WLC to limit the Client connections per AP to 25, can this be achieved?
    Please, can anyone help me in calrifying the above points.
    Regards,
    Keshava Raju

    Many Thanks Mr. Dennis for your help & Clarification.
    With ref to your reply point no# 1. I have actually planned to connect one Gig port of the controller to each of the Dual Cisco Core Switch setup. Can i use all 4 Controller Interfaces configured as LAG and Port 1 & 2 connecting to Core Switch 01 and Port 3 & 4 connecting to Core Switch 02?
    I have Final two more questions, Request you to help me calrifying this?
    • I'm willing to configure Multicast communication between the WLC & AP's. For this configuration is it necessary to Connect the WLC in a different VLAN than the VLAN of the AP's. Is it necessary that I have to set the controller to LWAPP Layer 3 mode to support the Multicast communication?
    • Though I do not have implementation experience of the WLAN. My understanding of the Interface settings on the WLC - is I will have to configure one Management Interface for in-band management. Do I have to configure AP-Manager Interface (to support Multicast communication) and to make the WLC to communicate with ACS for Client Authentication. All of the Wireless Devices including the ACS are in one VLAN / IP Subnet, is only one Management Interface is enough for communicating with AP's (with Multicast) and communicating with ACS for forwarding the Authentication messages between the ACS & Wireless Clients?

  • Setting management interface WLC 7.4.121.0

    Hello.
    I have a problem setting Management interface IP in new controller 5508. I get the error "Error in setting management interface IP".I can not place a management controller IP.
    Starting IPv6 Services: ok
    Starting Config Sync Manager : ok
    Starting Hotspot Services: ok
    Starting PMIP Services: ok
    Starting Portal Server Services: ok
    Starting mDNS Services: ok
    Starting Management Services: 
       Web Server:    CLI: ok
       Secure Web: Web Authentication Certificate not found (error). If you cannot access management interface via HTTPS please reconfigure Virtual Interface.
       License Agent: ok
    (Cisco Controller) 
    Welcome to the Cisco Wizard Configuration Tool
    Use the '-' character to backup
    Would you like to terminate autoinstall? [yes]: -
    Invalid response
    Would you like to terminate autoinstall? [yes]: no
    System Name [Cisco_bf:dd:c4] (31 characters max): 
    AUTO-INSTALL: process terminated -- no configuration loaded
    Enter Administrative User Name (24 characters max): admin
    Enter Administrative Password (3 to 24 characters): ********
    Re-enter Administrative Password                 : ********
    Service Interface IP Address Configuration [static][DHCP]: none
    Service Interface IP Address: 1.1.1.1
    Service Interface Netmask: 255.255.255.0
    Enable Link Aggregation (LAG) [yes][NO]: no
    Management Interface IP Address: 192.168.10.1
    Management Interface Netmask: 255.255.255.0
    Management Interface Default Router: 192.168.10.10
    Error in setting management interface IP 
    Management Interface IP Address: 10.10.10.1
    Management Interface Netmask: 255.255.255.0
    Management Interface Default Router: 10.10.10.100
    Error in setting management interface IP 
    Management Interface IP Address: 
    Does anyone faced this issue?
    Thanks. 

    Hi,
    Try these:
    1. With the WLC, Please set flow control(in SecureCRT or hperterminal) to none. Once the changes are made, CLI will start working as usual.
     2. Another  common reason can be related to the virtual interface configuration of the controller. In order to resolve this problem, remove the virtual interface and then re-generate it with this command:
    WLC>config interface address virtual 1.1.1.1
    Then, reboot the controller. After the controller is rebooted, re-generate the webauth certificate locally on the controller with this command:
    WLC>config certificate generate webauth
    In the output of this command, you should see this message: Web Authentication certificate has been generated.
    Now, you should be able to access the secure web mode of the controller upon reboot.
    3. Try to use some diff IP address for service interface don't use 1.1.1.1.
    Regards
    Dont forget to rate helpful posts

  • WLC 5508 - Ignoring Primary discovery request received on non-management interface (2) from AP

    Hello,
    Im receving this error on my syslog server:
    capwap_ac_sm.c:1443 Ignoring Primary discovery request received on non-management interface (2) from AP
    already checked the configuration and everything seems ok. They are registered and with clients associated.
    What could be the cause?
    Thanks in advance,
    Chris

    Thanks Scott for your fast response.
    No, I'm not using LAG.
    What do you mean with separate AP Managers?
    I have one AP Manager on vlan 100 (10.100.0.25) and the Management interface on the same Vlan (10.100.0.26)
    And users use vlan 150 (10.150.0.x).
    The switch port where the AP is plugged is configured with:
    interface GigabitEthernet2/0/20
    switchport access vlan 100
    switchport mode access
    spanning-tree portfast
    On WLC I can also check the AP history:
    Last Error Occurred Reason            Layer 3 discovery request not received on management interface

  • WLC 5508 AP-Manager interface

    Hi, I own a WLC 5508 and I (probably) do not understand AP-Manager interfaces. I have a lab with 2x 1242AG and 1x 1252AG connected to c2960. APs are in vlan 10 (192.168.10.0/24, configured via DHCP), APs are connected to "switchport mode access" interface. c2960 is connected via a trunk to c4506, and WLC is plugged in gi1/3 and gi1/4 (both through twingig). Both ports are configured as "switchport mode trunk". Management interface on WLC is on WLC port 8 (connected to gi1/4), and AP-Manager is on WLC port 1 (connected to gi1/3). Management interface on WLC has "Dynamic AP management" set to disabled, and AP-Manager has it set to enabled. Both, Management and AP-Manager interfaces are tagged, vlan id 12 and 13 (subnets 192.168.12.0/24, 192.168.13.0/24) respectively. APs receive their IP configuration via DHCP (server located in vlan 20, 192.168.20.0, ip helper-address in use), and try to discover WLC by DNS resolution (CISCO-CAPWAP-CONTROLLER.some.domain resolves to AP-Manager IP correctly). But APs do not join to controller, WLC says "Ignoring discovery request received on non-management interface", AP has "not joined" status in Monitor/Statistics/AP Join.
    But if I set management interface as "Dynamic AP enabled", and change DNS to resolve CISCO-CAPWAP-... to it's IP everything works fine - AP joins at once. Please help, how to join LAP to AP-Manager interface? Join to WLC manager is simple, but my design requires at least 2 AP-Manager interfaces.

    Hello,
    I just wanted to mention foremost; a split LAG configuration is not supported on the WLCs.  This "can" be achieved if you are splitting your LAG ports amongst VSS configuration on your two capable devices, but is not a recommended or supported configuration. I would highly suggest a LAG configuration over your individual port.  As far as the "ap-manager" concern you have of managing more than 48 APs, you are correct in that the AP-manager cannot handle more than 48 APs, however only when in an individual port configuration.  The LAG will overcome this limitation.
    George was correct about your DNS entry, this needs to point to the WLC's management interface.  This is why the AP joined when you pointed the DNS entry back to the management address-- as intended.
    This link is anchored to the mgmt, ap-manager, and dynamic interface creation for the 7.0.116.0 Config Guide: http://www.cisco.com/en/US/docs/wireless/controller/7.0MR1/configuration/guide/cg_ports_interfaces.html#wp1286790
    "If" you want to keep an individual port configuration, and need more than 60 APs connected, you will need to create more than one "ap-manager" interface.  You will just make a new dyanamic intreface and place it on the same network as the current ap manager (ie, management interface) and mark it for dynamic ap management.  All APs will still need to only see the management interface for joining; the WLC will assign to the appropriate AP manager as needed.  The WLC will fill up the first AP manager before joining building tunnels through the next AP-manager interface, so in your lab you will not really be able to test this behavior, assuming the 3-4 APs you were using.
    1. You can keep your management interface with "dynamic ap management" enabled so this serves as the first AP manager; if you desire. 
    2. You will need to create another dynamic interface mapped to the next port.  enabled "dynamic ap management" again here, and place this new "ap-manager" interface on the same vlan as the mgmt.  Keep in mind creating a dynamic interface and designating it as an AP manager prevents mapping that interface to a WLAN, see note below.
    *NOTE (from config guide): When you enable this feature, this dynamic interface is configured as an AP-manager interface (only one AP-manager interface is allowed per physical port). A dynamic interface that is marked as an AP-manager interface cannot be used as a WLAN interface.
    I would highly suggest the LAG configuration so there is no need to worry about the ap manager interfaces, regardless of the number of APs communicating. This also allows for growth if WLC needs to be licensed for more and more APs.

  • Help with Cisco 5508 management interface

    Hello,
    I'm trying to verify some behaviors I'm seeing with my 5508 controller setup and forgive me for missing anything obvious, I've zero experience with this hardware and clueless on the best practices. With that said... out of the box I ran through the AutoInstall process.
    I gave my service port an IP address on my subnet, 10.10.8.0/24 vlan 100 and gave the management interface the ip address 10.10.30.5/24 vlan 130
    From my host I can ping the management interace 10.10.30.5 and the interface gateway 10.10.30.1
    I cannot connect to the controller via 10.10.30.5 either through the web GUI or telnet
    I can connect to the controller via 10.10.8.200 both through the web interface and telnet
    while connected to the service port, I can ping the management port IP but I cannot ping the 10.10.30.1 gateway.
    We have attached two test 3502I AP's and they found the controller and pulled correct ip addresses, clients can authenticate and access network resources as well as the Internet so for the most part, things are working but it concerns me that the management interface can't ping its own gateway.
    Keep in mind, I did no other configurations besides what got configured in the AutoInstall process. What should I look at to resolve?
    Thanks!
    Mike

    The service port is for out of band management and should not be connected to the network.  If connected tot he network, it should not have connectivity to the management interface of the wlc. 
    You can create an ACL to block the service port ip to the managment vlan if you want.  I normally do not connect the service port to the network.

  • WLC 5508 management interface

    Hi, I have a particular wireless design that requires one WLC 5508 to be connected to two seperate swithces. Port 1 of WLC is connected trunk to Switch A and Port 2 of WLC is connected to Switch B. Each switch has its own local VLANS. When I connect 1130s LAPs they need to find the management interface initially and then use only AP management interfaces. since there is only one management interface, if I assign management interface on a vlan that is configured on switch A then APs on switch A join fine but those on switch B keep asking for management interface and from capwap debug on WLC it says that join request was received on wrong ineterface ....
    the only work around to this was to make routing between switch A and switch B for the two vlans on which APs reside... but for security purposes - client would like to avoid this
    any help much appreciated ..

    Hi thanks for your reply,
    Yes I agree perfectly with your explanation - On both switches I have UDP forward for 5246 and 5247 and everything works fine.
    You understood exactly what's happening for initial discovery the Guest AP asks for managemnt interface through WLC port 2 but managerment IP is on admin side WLC port 1 and then it drops packet saying that it was received on the wrong port. In fact that is why I put an ACL between the Admin switch and guest switch taht allows only 5426 capwap control - just to allow that initial discovery from guest AP to contact Management interface which can only be assigned to one port and in my case it is on the admin switch side. And that is why I had to make a route between the two independent switches.
    My question is to know if there is any other way with my given design to eliminate this initial discovery to the management inetrface, as my client would like the admin and guest switches to be completely seperated i.e. without the routing. Is there any way that the guest APs can make contact with the AP management interface on their side only skipping the discovery of the management interface ? the guest APs were primed on the admin side so they know the IP. After the initial discovery, if I remove the routing between admin and guest switch, guest APs keep their connectivity without any problems.

Maybe you are looking for