Cisco Deleting AP Which Has Not Been Plumbed

Managing a large-scale wireless network can often feel like herding cats, especially when hardware changes occur faster than your documentation can keep up. One of the most common frustrations for network administrators is dealing with “ghost” devices that clutter their dashboard, leading to confusion during troubleshooting and reporting. If you are currently facing issues with Cisco Deleting AP which Has Not Been Plumbed, you are not alone; this is a standard housekeeping task that ensures your Cisco Wireless LAN Controller (WLC) remains efficient and accurate.

In this guide, we will walk you through exactly why these un-plumbed (unconnected) access points appear, how to identify them, and the precise steps to remove them from your system. Whether you prefer using the Command Line Interface (CLI) or the web-based GUI, we have got you covered with clear, actionable instructions.

Why Do Un-Plumbed Access Points Appear on My Cisco WLC?

Before we dive into the deletion process, it is crucial to understand why these access points (APs) show up in your controller’s database if they are not physically connected (“plumbed”) to the network. Understanding the root cause helps prevent future clutter.

Typically, an AP appears as “un-plumbed” or in a “Disconnected” state for one of three reasons:

1. Hardware Replacement: An old AP was removed, but its entry was never manually deleted from the controller. The new AP might have a different MAC address, leaving the old record behind.
2. Configuration Reset: If an AP was reset to factory defaults or moved to a different controller without being properly disassociated, the original controller may still retain its configuration profile.
3. DHCP and DNS Issues: Sometimes, an AP attempts to join a controller based on DHCP Option 43 or DNS records but fails due to network segmentation or firewall rules. It registers briefly as “pending” before dropping off, yet remains in the database.

According to Cisco’s general networking principles, maintaining a clean database is vital for license management. Many Cisco WLC models operate on a license count basis. If your controller thinks it is managing 50 APs, but 10 of them are ghost entries, you are wasting valuable licenses and potentially hitting capacity limits unnecessarily.

For more context on how Cisco structures its wireless architecture, you can refer to the general overview on Wikipedia.

How to Identify Orphaned or Un-Plumbed APs

You cannot delete what you cannot find. The first step in Cisco Deleting AP which Has Not Been Plumbed is accurate identification. You need to distinguish between an AP that is temporarily offline (due to power loss) and one that is permanently removed.

Using the GUI (Web Interface)

1. Log in to your Cisco WLC web interface.
2. Navigate to Wireless > Access Points > All APs.
3. Look at the Status column.
   • Registered: The AP is active and communicating.
   • Down: The AP was previously registered but is currently unreachable. This is your target.
4. Click on the AP name to view details. Check the Last Seen timestamp. If it has been days or weeks since the last communication, it is safe to assume the device is no longer in use.

Using the CLI (Command Line Interface)

For those who prefer speed and precision, the CLI is invaluable. Use the following command to list all APs and their states:

bash1

Look for APs with the status Down. To get more specific details about a particular AP, use:

bash1

If the output shows no recent uptime or indicates a configuration mismatch, mark this AP for deletion.

Step-by-Step Guide: Deleting APs via GUI

Removing an access point through the graphical interface is user-friendly and reduces the risk of typos. Follow these steps carefully.

1. Navigate to the AP List: Go to Wireless > Access Points > All APs.
2. Select the Target AP: Find the AP that is marked as “Down” or “Un-plumbed.” Click the checkbox next to the AP name.
3. Initiate Deletion: At the top of the list, look for the drop-down menu labeled “Select Command.” Choose Delete or Remove.
4. Confirm the Action: A pop-up window will appear asking for confirmation. It will warn you that this action is irreversible. Click OK or Apply.
5. Verify Removal: Refresh the page. The AP should no longer appear in the list. If it reappears immediately, check if there is an automated provisioning script or a rogue device attempting to rejoin the network.

Step-by-Step Guide: Deleting APs via CLI

For network engineers managing multiple controllers or automating tasks, the CLI is the preferred method. It is faster and can be scripted.

Prerequisite: Ensure you have admin privileges on the WLC.

Step 1: Access the Controller SSH into your Cisco WLC using your preferred terminal emulator (e.g., PuTTY or SecureCRT).

Step 2: Verify the AP Name Before deleting, double-check the exact name of the AP to avoid accidental deletion of active units.

bash1

Step 3: Execute the Delete Command Use the config ap delete command. Replace <AP-Name> with the actual name of the orphaned AP.

bash1

Step 4: Confirm the Deletion The system will prompt you: “Are you sure you want to delete this AP? (y/N)”. Type y and press Enter.

Step 5: Save Configuration Changes made in the CLI are often temporary until saved. Ensure you save the running configuration to the startup configuration.

bash1

You will be asked to confirm again. Type y to finalize.

Troubleshooting: What If the AP Won’t Delete?

Sometimes, you may encounter errors when attempting Cisco Deleting AP which Has Not Been Plumbed. Here are common scenarios and solutions.

Pro Tip: If an AP keeps coming back, check your DHCP scopes. If Option 43 is pointing to this WLC, any device plugged into that network segment will attempt to join. You may need to filter by MAC address on the switch port where the physical cable was previously connected.

Best Practices for Maintaining a Clean AP Database

Prevention is better than cure. To avoid accumulating un-plumbed APs in the future, adopt these best practices:

• Standardize Naming Conventions: Use a consistent naming scheme (e.g., FLR-ROOM-AP01). This makes it easier to identify which physical location an AP belongs to.
• Document Hardware Changes: Whenever an AP is replaced, update your network inventory spreadsheet immediately.
• Regular Audits: Schedule a monthly review of your “Down” AP list. Delete any device that has been offline for more than 30 days.
• Use Prime Infrastructure or DNA Center: If you have access to Cisco’s management platforms, use their automation tools to sync inventory and automatically flag disconnected devices.

FAQ Section

1. Does deleting an AP from the WLC erase its local configuration?

No. Deleting an AP from the WLC only removes its entry from the controller’s database. The AP itself retains its last known configuration until it is factory reset. If you plug it back in, it will attempt to rejoin the controller using its stored credentials.

2. Will deleting an un-plumbed AP free up a license?

Yes, in most cases. Once the AP is successfully deleted and the configuration is saved, the license slot associated with that AP is released and becomes available for a new device. However, always verify your license count in the Management > Licenses section after deletion.

3. Can I bulk delete multiple un-plumbed APs?

Via the GUI, you can select multiple checkboxes and apply the “Delete” command simultaneously. Via CLI, there is no native “bulk delete” command; you must execute the config ap delete command for each AP individually, though this can be scripted using Python or Expect scripts for large deployments.

4. What is the difference between “Disabling” and “Deleting” an AP?

Disabling an AP keeps its configuration and license allocation intact but prevents it from broadcasting SSIDs. Deleting an AP removes it entirely from the controller’s memory, freeing up the license and requiring re-provisioning if it is ever reconnected. For un-plumbed APs, deletion is the recommended action.

5. Why does my AP show as “Plumbed” but still not work?

“Plumbed” generally refers to the physical layer connectivity. If an AP is plumbed but not working, check VLAN assignments, PoE (Power over Ethernet) budget on the switch, and firewall rules allowing CAPWAP traffic (UDP ports 5246 and 5247).

Conclusion

Dealing with Cisco Deleting AP which Has Not Been Plumbed is a routine but essential part of network hygiene. By regularly cleaning up orphaned access points, you ensure accurate license usage, simplify troubleshooting, and maintain a professional network infrastructure. Whether you choose the GUI for its visual clarity or the CLI for its speed, the process is straightforward once you know the right commands.

Remember, a clean network is a secure network. Take a moment today to audit your WLC and remove those ghost entries. If you found this guide helpful, please share it with your fellow network engineers on LinkedIn or Twitter. Let’s help each other build better, cleaner networks!