show version\n<\/code><\/pre>\nExamine the image filename displayed in the output:
\n* Autonomous images<\/strong> contain the string k9w7<\/code> in the filename (for example, ap3g2-k9w7-tar.153-3.JPJ.tar<\/code>).
\n* Lightweight images<\/strong> contain k9w8<\/code> or rcvk9w8<\/code> (recovery image) in the filename (for example, ap3g2-k9w8-tar.153-3.JPJ.tar<\/code>).
\n* Catalyst 9100 series APs<\/strong> running under Catalyst 9800 WLC management typically show Capwap architecture, whereas those with EWC capabilities display embedded controller images.<\/p>\n
\n<\/span>Cisco AP Default Credentials, IP Addresses, and Console Settings<\/span><\/h2>\nWhen provisioning a factory-fresh or recently wiped Cisco access point, refer to the following hardware-line matrix for default network parameters, serial port communication settings, and standard administrative credentials.<\/p>\n
\n\n\n| Product Family \/ Line<\/th>\n | Operating Mode<\/th>\n | Default IP Address \/ Subnet Behavior<\/th>\n | Default Username \/ Password<\/th>\n | Console Serial Settings<\/th>\n<\/tr>\n<\/thead>\n |
\n\nCisco Aironet Series<\/strong> (1600, 2600, 2700, 3700, 3800)<\/em><\/td>\nAutonomous (k9w7<\/code>)<\/td>\nRequests dynamic DHCP; falls back to 10.0.0.1 \/24<\/code> if no DHCP server is detected within ~30s<\/td>\nUsername:<\/strong> Cisco<\/code>
Password:<\/strong> Cisco<\/code>
(Enable secret: Cisco<\/code>)<\/em><\/td>\n| 9600 baud, 8 data bits, no parity, 1 stop bit, no flow control (9600 8-N-1)<\/td>\n<\/tr>\n | \nCisco Aironet Series<\/strong> (1600, 2600, 2700, 3700, 3800)<\/em><\/td>\nLightweight (k9w8<\/code>)<\/td>\n| Requests dynamic DHCP only; queries Option 43 \/ DNS for WLC IP<\/td>\n | Username:<\/strong> Cisco<\/code>
Password:<\/strong> Cisco<\/code>
(Overridden by WLC AP credentials once joined)<\/em><\/td>\n9600 baud, 8-N-1, no flow control<\/td>\n<\/tr>\n | \nCisco Catalyst 9100 Series<\/strong> (9105, 9115, 9120, 9130)<\/em><\/td>\n| Lightweight \/ CAPWAP<\/td>\n | Dynamic DHCP<\/td>\n | Username:<\/strong> Cisco<\/code>
Password:<\/strong> Cisco<\/code>
(Overridden by Catalyst 9800 WLC global AP credentials)<\/em><\/td>\n9600 or 115200 baud, 8-N-1, no flow control<\/td>\n<\/tr>\n | \nCisco Catalyst 9100 Series<\/strong> (EWC Software)<\/em><\/td>\n| Embedded Wireless Controller<\/td>\n | Dynamic DHCP; broadcasts initial Day-0 provisioning SSID (CiscoAirProvision-<xxxx><\/code>)<\/td>\n| Configured by user during initial Day-0 Web Setup wizard<\/td>\n | 9600 baud, 8-N-1, no flow control<\/td>\n<\/tr>\n | \nCisco Business Wireless (CBW)<\/strong> (100 \/ 200 Series)<\/em><\/td>\n| Primary AP \/ Standalone<\/td>\n | Dynamic DHCP; falls back to 192.168.1.1<\/code> or broadcasts setup SSID (CiscoBusiness-Setup<\/code>)<\/td>\n| Configured by user during initial Web UI setup wizard<\/td>\n | 9600 baud, 8-N-1, no flow control<\/td>\n<\/tr>\n | \nCisco Small Business WAP<\/strong> (WAP121, WAP321, WAP371, WAP571)<\/em><\/td>\n| Standalone \/ Cluster<\/td>\n | Dynamic DHCP; falls back to 192.168.1.245 \/24<\/code> if DHCP is unavailable<\/td>\nUsername:<\/strong> cisco<\/code>
Password:<\/strong> cisco<\/code>
(All lowercase)<\/em><\/td>\n9600 baud, 8-N-1, no flow control<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n (Note: All default passwords on enterprise Cisco IOS devices are case-sensitive.)<\/em><\/p>\n
\n<\/span>Connecting to a Cisco Access Point via Console Cable (CLI)<\/span><\/h2>\nA physical console connection provides direct out-of-band management. This is the most reliable method to configure, inspect, or troubleshoot any Cisco AP, regardless of its IP assignment or firmware type.<\/p>\n +---------------+ Serial \/ USB Cable +---------------------+\n| Admin Workstation | ========================= | Cisco Access Point |\n| (PuTTY \/ 9600 8-N-1)| | (RJ45\/Micro-USB Port)|\n+---------------+ +---------------------+\n<\/code><\/pre>\n<\/span>Step 1: Secure Required Cabling and Adapters<\/span><\/h3>\nDepending on the AP model:
\n* RJ-45 Console Port:<\/strong> Use a standard light-blue Cisco rollover cable (RJ-45 to DB9 female) paired with a USB-to-RS232 serial adapter.
\n* Micro-USB \/ USB-C Console Port:<\/strong> Newer Catalyst 9100 and Aironet models feature a direct USB console port. Connect using a standard USB-to-Micro-USB or USB-C cable. (Install the Cisco USB console driver if prompted by your operating system.)<\/p>\n<\/span>Step 2: Identify the Assigned Serial Interface<\/span><\/h3>\nConnect the cable to your workstation:
\n* Windows:<\/strong> Open Device Manager<\/strong> > expand Ports (COM & LPT)<\/strong> > note the allocated identifier (e.g., COM3<\/code> or COM5<\/code>).
\n* macOS \/ Linux:<\/strong> Open a terminal and run ls \/dev\/tty.*<\/code> or dmesg | grep tty<\/code> to find the device node (e.g., \/dev\/tty.usbserial-1410<\/code>).<\/p>\n<\/span>Step 3: Launch and Configure Your Terminal Emulator<\/span><\/h3>\nOpen a terminal client (such as PuTTY, Tera Term, or SecureCRT) and configure the following parameters:
\n* Connection Type:<\/strong> Serial
\n* Serial line:<\/strong> Your identified COM port (e.g., COM3<\/code>)
\n* Speed (Baud rate):<\/strong> 9600<\/code> (Use 115200<\/code> if connecting to select Catalyst 9100 recovery modes)<\/em>
\n* Data bits:<\/strong> 8<\/code>
\n* Stop bits:<\/strong> 1<\/code>
\n* Parity:<\/strong> None<\/code>
\n* Flow control:<\/strong> None<\/code><\/p>\n<\/span>Step 4: Initiate the Session and Authenticate<\/span><\/h3>\n\n- Power on the AP (via PoE switch or external power injector).<\/li>\n
- Click Open<\/strong> in your terminal client.<\/li>\n
- Press Enter<\/strong> once or twice to trigger the command prompt.<\/li>\n
- When prompted, supply the default credentials:
\n text
\n User Access Verification
\n Username: Cisco
\n Password: Cisco<\/code><\/li>\n- Enter privileged EXEC mode:
\n text
\n ap> enable
\n Password: Cisco
\n ap#<\/code>
\nFrom the ap#<\/code> prompt, you have full administrative control to view interfaces, apply base network configurations, or monitor system logs.<\/li>\n<\/ol>\n
\n<\/span>Connecting Directly to the AP Web GUI via Ethernet<\/span><\/h2>\nIf your access point runs an Autonomous, Cisco Business, or Small Business image, you can manage it directly through a standard web browser by establishing an isolated link between your computer’s network interface card (NIC) and the AP.<\/p>\n <\/span>Step 1: Supply Power to the Access Point<\/span><\/h3>\nEnterprise APs generally rely on Power over Ethernet (PoE). Connect an 802.3af\/at-compliant PoE injector or a PoE-enabled switch port to the AP\u2019s primary Ethernet port (labeled PoE-In<\/code> or GE 0<\/code>). If using a PoE injector:
\n* Connect the Data Out \/ PoE<\/strong> port to the AP.
\n* Connect the Data In \/ LAN<\/strong> port to your computer’s Ethernet port.<\/p>\n<\/span>Step 2: Configure a Static IP on Your Computer<\/span><\/h3>\nBecause the AP is isolated from a local network router, it will either assign an auto-fallback IP or expect communication within its default factory subnet:
\n1. Open your computer’s network adapter settings.
\n2. Manually assign an IPv4 address within the AP’s default fallback range:
\n * For Aironet Autonomous APs (fallback 10.0.0.1<\/code>):<\/strong>
\n IP: 10.0.0.5<\/code> | Subnet Mask: 255.255.255.0<\/code> | Default Gateway: 10.0.0.1<\/code>
\n * For Cisco Small Business WAP series (fallback
| | | | | | | | | | | | | | | | |