Cannot crate ap-manager interface

Hello everybody hope you are doing great!
Yesterday I was in one of our client premises configuring a WLC 5508 with software 7.2, went through the initial configuration wizard with no problem whatsoever, my issue began when trying to configure a ap-manager interface.
In many WLC configuration guides cisco states that for 5508 it is not required to configure an ap-manager interface because the management will suffice, but then they put a side note recommending it's configuration for best practices and better performance. OK so I saw that in an earlier version document and now they do not make the recommendation but the still use the word required and for me that's still is not a limitation.
Well anyways, I can't create the ap manager interface because when I put the VLAN ID it says the it is being used by another interface. Any help?
Thank you in advance

For 5500 series controllers, you are not required to configure an AP-manager interface,
the management interface acts like an AP-manager interface by default.
If desired, you can disable the management interface as an AP-manager
interface and create another dynamic interface as an AP manager.
Make sure that you have disable the option of ap manager on the management interface before creating the new AP manager interface and on the 5508 WLC the AP-manager interface can not be on the same VLAN as the managment interface like on the old WLCs.

Similar Messages

Cannot Access print-manager Interface In KDE

Hello all,
First of all, I have print manager installed. I've tried uninstalling and reinstalling, but the problem still persists. The problem is that no matter what I do, there is no option in the System Settings app on KDE to manage printers. I realise that I can just use the CUPS interface, but that leaves a lot to be desired for me.
I have spent hours scouring the web for any information on this, and it appears that the most common reason for this problem is that people don't have print-manager installed in the first place. That is definitely not the reason I'm having the problem, however.
$ inxi -Fxz
System: Host: MSIGS70-ARCH Kernel: 4.0.4-2-ARCH x86_64 (64 bit gcc: 5.1.0)
Desktop: KDE 4.14.8 (Qt 4.8.6) Distro: Arch Linux
Machine: System: Micro-Star product: GS70 2PE Stealth Pro v: REV:1.0
Mobo: Micro-Star model: MS-1772 v: REV:0.B
Bios: American Megatrends v: E1772IMS.106 date: 04/30/2014
CPU: Quad core Intel Core i7-4710HQ (-HT-MCP-) cache: 6144 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 19961
clock speeds: max: 3500 MHz 1: 2507 MHz 2: 2563 MHz
3: 2709 MHz 4: 2482 MHz 5: 3042 MHz 6: 2500 MHz 7: 2500 MHz
8: 2501 MHz
Graphics: Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller
bus-ID: 00:02.0
Card-2: NVIDIA GK104M [GeForce GTX 870M] bus-ID: 01:00.0
Display Server: N/A driver: intel Resolution: 72x69
Audio: Card-1 Intel 8 Series/C220 Series High Definition Audio Controller
driver: snd_hda_intel bus-ID: 00:1b.0
Card-2 Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller
driver: snd_hda_intel bus-ID: 00:03.0
Sound: Advanced Linux Sound Architecture v: k4.0.4-2-ARCH
Network: Card-1: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller
driver: alx port: c000 bus-ID: 04:00.0
IF: enp4s0 state: down mac: <filter>
Card-2: Intel Wireless 7260 driver: iwlwifi bus-ID: 05:00.0
IF: wlp5s0 state: up mac: <filter>
Drives: HDD Total Size: 2128.4GB (32.7% used)
ID-1: /dev/sdb model: WDC_WD10JPVX size: 1000.2GB
ID-2: /dev/sda model: TOSHIBA_THNSNJ12 size: 128.0GB
ID-3: USB /dev/sdc model: BUP_Slim_SL size: 1000.2GB
Partition: ID-1: / size: 29G used: 5.6G (21%) fs: ext4 dev: /dev/sda5
ID-2: swap-1 size: 17.83GB used: 0.00GB (0%) fs: swap dev: /dev/sdb3
Sensors: System Temperatures: cpu: 29.8C mobo: 27.8C gpu: 27.0
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 205 Uptime: 3 min Memory: 935.7/15971.7MB
Init: systemd Gcc sys: 5.1.0
Client: Shell (bash 4.3.391) inxi: 2.2.21
Thanks so much for any help!
HPG

as unprivileged user, it won't open and returns the following:
$ kcmshell5 kcm_printer_manager
kf5.kservice.sycoca: Trying to open ksycoca from "/home/aaron/.cache/ksycoca5"
kf5.kservice.sycoca: Trying to open global ksycoca from "/home/aaron/.local/share/kservices5/ksycoca5"
kf5.kservice.sycoca: Trying to open ksycoca from "/home/aaron/.cache/ksycoca5"
kf5.kservice.sycoca: Trying to open global ksycoca from "/home/aaron/.local/share/kservices5/ksycoca5"
kf5.kservice.sycoca: Still no database...
Could not find module 'kcm_printer_manager'. See kcmshell5 --list for the full list of modules.
As sudo, it opens the window but says, "print service is unavailable. Bad file descriptor." and I am forced to exit the window. Outputs this in terminal:
$ sudo kcmshell5 kcm_printer_manager
kf5.kservice.sycoca: Trying to open ksycoca from "/home/aaron/.cache/ksycoca5"
libkcups: CUPS-Get-Printers last error: 1282 Bad file descriptor
libkcups: CUPS-Get-Printers last error: 1282 Bad file descriptor
libkcups: -1 last error: 1282 Bad file descriptor
libkcups: Create-Printer-Subscriptions last error: 1282 Bad file descriptor
libkcups: Request failed 1282 -1
libkcups: Create-Printer-Subscriptions last error: 1282 Bad file descriptor
libkcups: Request failed 1282 -1
Thanks for the quick help, by the way!
Last edited by hotpepperguy (2015-05-30 17:56:05)

ASA 5515 management interface

I started to configure a new ASA 5515 to replace an 5510. When I attempted to remove the "management-only" command from the Management0/0 interface I was greeted with the following error:
"ERROR: It is not allowed to make changes to this option for management interface on this platform."
Does this mean we can't use the managment interface anymore on these newer ASAs? I was planning on using that port when we bought it. If this is the case, let this be a warning to whoever is counting the managment port as a 7th interface on the 5515!

Update: I just found out that you can't use the management interface for failover purposes either. Argggggg.
"Management interface cannot be configured for failover on this platform."

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 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.

Is it possible to access the http web interface over the fa1 management interface?

Hello All,
    I am remotely connected into a Cat 4500 + Supervisor V module via console cable and point to point connection from laptop to fa1 management interface on SupV. SupV module is running IOS 15.0(2)SG8.
    I am not able to physically change the patch cable from fa1 management interface to gi2/3 or any other switch port for a couple days and would like to see if it is possible to access the http server through this fa1 port since I am working remotely. I can ping the laptop from fa1 and tftp ok but cannot access the http/https server. Is this even possible without connecting the laptop into a regular switch port like gi 2/3 gi 2/4 etc..? The reason I ask is I would like to use Cisco Networking Assistant gui for some things but need access to https server first over the fa1 link.
Any suggestions would be much appreciated.
Thanks!
-S

Here is the ACL list. I have not made any entries into this list and all of these are default at this time. Do I need to make an explicit allow ACL for http?
Thanks!
-S
#show access-list
Extended IP access list system-cpp-all-routers-on-subnet
    10 permit ip any host 224.0.0.2
Extended IP access list system-cpp-all-systems-on-subnet
    10 permit ip any host 224.0.0.1
Extended IP access list system-cpp-dhcp-cs
    10 permit udp any eq bootpc any eq bootps
Extended IP access list system-cpp-dhcp-sc
    10 permit udp any eq bootps any eq bootpc
Extended IP access list system-cpp-dhcp-ss
    10 permit udp any eq bootps any eq bootps
Extended IP access list system-cpp-energywise-disc
    10 permit udp any eq any eq 0
Extended IP access list system-cpp-hsrpv2
    10 permit udp any host 224.0.0.102
Extended IP access list system-cpp-igmp
    10 permit igmp any 224.0.0.0 31.255.255.255
Extended IP access list system-cpp-ip-mcast-linklocal
    10 permit ip any 224.0.0.0 0.0.0.255
Extended IP access list system-cpp-ospf
    10 permit ospf any 224.0.0.0 0.0.0.255
Extended IP access list system-cpp-pim
    10 permit pim any 224.0.0.0 0.0.0.255
Extended IP access list system-cpp-ripv2
    10 permit ip any host 224.0.0.9
Extended MAC access list system-cpp-bpdu-range
    permit any 0180.c200.0000 0000.0000.000c
Extended MAC access list system-cpp-cdp
    permit any host 0100.0ccc.cccc
Extended MAC access list system-cpp-cgmp
    permit any host 0100.0cdd.dddd
Extended MAC access list system-cpp-dot1x
    permit any host 0180.c200.0003
Extended MAC access list system-cpp-lldp
    permit any host 0180.c200.000e
Extended MAC access list system-cpp-mcast-cfm
    permit any 0180.c200.0030 0000.0000.000f
Extended MAC access list system-cpp-pppoe-disc
    permit any any protocol-family pppoe-disc
Extended MAC access list system-cpp-sstp
    permit any host 0100.0ccc.cccd
Extended MAC access list system-cpp-ucast-cfm
    permit any host 000d.6558.d5fd

5508 WLC HA pair - change management interface settings

Hi,
We have a pair of 5508 WLC's in a HA configuration that is working well at the moment, however I have noticed that the management interface is configured as untagged. I would like to change this to tagged and change the attached switch to trunk for these devices but if I try and edit the management interface through the GUI the VLAN and IP address section is greyed out and cannot be changed. While I could attempt it through the CLI and am comfortable doing that, the fact that it cannot be changed through the GUI implies that this should not be changed and so I am after further information. I don't have any lab equipment other than the HA pair in production so I cannot try changing it through the CLI at the moment.
The WLC's are in LAG mode if that makes any difference. I realise there may be downtime required for making this change but I am trying to work out the steps to get this done without having to drastically reconfigure things.
Any assistance would be appreciated.

Introduction of New Interfaces for HA Interaction
Redundancy Management Interface
The IP address on this interface should be configured in the same subnet as the management interface. This interface will check the health of the Active WLC via network infrastructure once the Active WLC does not respond to Keepalive messages on the Redundant Port. This provides an additional health check of the network and Active WLC, and confirms if switchover should or should not be executed. Also, the Standby WLC uses this interface in order to source ICMP ping packets to check gateway reachability. This interface is also used in order to send notifications from the Active WLC to the Standby WLC in the event of Box failure or Manual Reset. The Standby WLC will use this interface in order to communicate to Syslog, the NTP server, and the TFTP server for any configuration upload.
Redundancy Port
This interface has a very important role in the new HA architecture. Bulk configuration during boot up and incremental configuration are synced from the Active WLC to the Standby WLC using the Redundant Port. WLCs in a HA setup will use this port to perform HA role negotiation. The Redundancy Port is also used in order to check peer reachability sending UDP keep-alive messages every 100 msec (default timer) from the Standby WLC to the Active WLC. Also, in the event of a box failure, the Active WLC will send notification to the Standby WLC via the Redundant Port. If the NTP server is not configured, a manual time sync is performed from the Active WLC to the Standby WLC on the Redundant Port. This port in case of standalone controller and redundancy VLAN in case of WISM-2 will be assigned an auto generated IP Address where last 2 octets are picked from the last 2 octets of Redundancy Management Interface (the first 2 octets are always 169.254).

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 Connection

I'm setting up a new 5508. I've used the config from a 4402, have successfully connected to the Service port to manage the device, but for some reason cannot connect to the Management interface. In this case, port 1.
The service port is connected to a Catalyst switch and grabbed an ip address (10.2.x.x subnet) no problem. I can access the 5508 via https using the SP. However, port 1 is connected to the same Catalyst switch, but on a different vlan (subnet 10.20.x.x). Both ends show that the interfaces are up, I can ping the interface from any other host on the network, but when I try to manage the device via https I cannot connect. We are using WCS and I cannot add the device from the WCS. About all I can do is ping that interface.
I've probably overlooked something very basic, but I'm baffled.

Thanks for the reply.
No, definitely not that. I have all of those enabled. I have the SP connected to another vlan on the same switch and can manage through that port(https, telnet). I've tried about every combination of trunk port, access port, etc. I'm beginning to suspect the GBICs (10baseT), but both ends show that I am connected at 1000 and I can ping the ip address of the management interface.

AP Manager interface and Virtual Interface

What do each of these interfaces do on the 526 WMAC? I am not sure I understand the functionality and did not find the answer to this in the documentation.
Thanks

Well from a WLC, the management is used to access and manage the wlc. It is also used for communication with the mobility group. AP-Manager is the interface the wlc and the ap's use and the virtual interface is used by internal dhcp, mobility group, webauth, etc. The virtual interface is not routable in your network, it is mainly used by the wlc's for various features.
Here is from a Cisco Doc:
The management interface is the default interface for in-band management of the controller and connectivity to enterprise services such as AAA server. If the service port is in use, the management interface must be on a different subnet than the service port.
The AP-Manager interface is used as the source IP address for all Layer 3 communications between the controller and the lightweight access points. The AP-Manager must have a unique IP address and should be on the same subnet as the management interface.
The virtual gateway interface is used to support mobility management, DHCP relay, and embedded Layer 3 security, like guest web authentication and VPN termination. The virtual interface must be configured with an unassigned and unused gateway IP address. If multiple controllers are configured in a mobility group, the virtual interface must be the same on all controllers for seamless roaming.
The service-port interface is mapped only to the physical service port. The service port interface must have an IP address on a different subnet from the management and AP-Manager interfaces. A default-gateway cannot be assigned to the service-port interface, but static routes can be defined through the controller command-line interface for remote network access to the service port.

Need verification of management interface usage on 5510

Hi,
I seem to get conflicting information on using the Management port as a regular routed interface on the ASA5510
This is the text in question:
The management interface can be used for the traffic that passes through the firewall as well. The Security Plus License for the ASA 5510 is required in order to use the management0/0 port as a regular interface. With a base license on the 5510, the management0/0 port cannot be used as a regular interface.
I believe that I saw another post that mentioned it was part of the standard IOS if you had a later version.
Can anybody validate this, one way or the other?
Thanks,
Dave

No, you dont need a license for it,just follow this doc, it was introduced in version 7.0.1:
http://www.cisco.com/en/US/docs/security/asa/asa82/command/reference/m.html#wp2028112
Thanks,
Varun Rao
Security Team,
Cisco TAC

Home Hub 3.0B Management interface unresponsive.

This month (2 weeks ago) I upgraded to Infinity 2 and got a new Home Hub 3.0 Type B.
I was able to get it all working as I wanted to - home network using 172.16.0.1/23 (because of conflicts with vpning into work which already routes 192.168./16 and 10./8)
However, often, very often, trying to access the Hub web interface on 172.16.0.1 or via bthomehub.home simply fails to respond. Regardless of the browser, or me using telnet to simulate a HTTP call.
#host bthomehub.home 172.16.0.1
Using domain server:
Name: 172.16.0.1
Address: 172.16.0.1#53
Aliases:
bthomehub.home has address 172.16.0.1
# telnet 172.16.0.1 80
Trying 172.16.0.1...
Connected to 172.16.0.1.
Escape character is '^]'.
GET /
And it just hangs.
Even though the web management interface is unresponsive, the internet seems to work ok, though wifi is sporadic.
Rebooting the hub doesn't seem to help. I read some reports of badly fitted heatsinks on these Type B's - so could mine be over heating and causing this lock up? If I leave it and try again in a few hours it may work again. Yesterday the internet connection dropped twice and when I was able to login to the web interface, the Event log showed that the hub had spontaneously rebooted itself.
Do I have a bad home hub?

Hi pgregg,
Have you tried a full reset of the hub yet? Not just a reboot?
Chris
BT Mod Team.
If you like a post, or want to say thanks for a helpful answer, please click on the Ratings star on the left-hand side of the post.
If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.

I am trying to create a new profile, but I cannot open profile manager in Mac OS 10.5.8. I get the following error: "dyld: unknown required load command 0x80000022 Trace/BPT trap".

Hello,
I am trying to repair my Firefox profile, but I cannot open profile manager in Mac OS 10.5.8. When I follow the directions for opening profile manager in my Terminal utility, I get the following error: "dyld: unknown required load command 0x80000022 Trace/BPT trap".
At this point, Firefox (v 5.0 or previous versions), is not running.
Thanks.

[http://asqueella.blogspot.com/2010/12/dyld-unknown-required-load-command.html Here's an Explanation]. Basically you need to add "arch -i386 " at the beginning of the command because 10.5 is 32-bit only and more recent versions of Firefox default to 64-bit.

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.

I accidently deleted my ap-manager interface How can I get it back? WLC440

I accidently deleted my ap-manager interface How can I get it back? WLC4400
Thanks in advance..
admin_users 1 301 10.147.1.8 Dynamic No
hvac 1 268 172.19.15.8 Dynamic No
management 1 447 10.147.8.8 Static No
nwlan 1 862 10.147.6.8 Dynamic No
service-port N/A N/A 192.168.168.200 Static No
switch mgmt 1 1 192.168.15.8 Dynamic No
virtual N/A N/A 1.1.1.1 Static No
voice 1 860 10.147.4.8 Dynamic No

Take a look at this documentation:
http://www.cisco.com/en/US/docs/wireless/controller/5.2/configuration/guide/c52mint.html#wpmkr1159694
It should help with creating ap-manager interfaces.

Cannot crate ap-manager interface

Similar Messages

Maybe you are looking for