09-29-2021 02:43 AM
Hello,
My C9115 with EWC was working fine and after a power outage no more SSID broadcasted and remote web administration no more accessible. The IP address was even not possible to ping.
After a full reset with the mode button, I try to do again the 0 day setup with CLI commands via the console. I can set the IP address on the GigabitEthernet0 but as soon as I send the "write mem" command I got an error message: "Failed to save vrrp-ip.txt". The web administration address is still not accessible.
Is AP dead or possible to recover it with commands?
Thanks for your help
Solved! Go to Solution.
10-08-2021 01:43 AM
Hi Arshad,
Actually I did the factory reset but didn't change the fact that I still couldn't connect to the Web interface after setting an IP address (of my local NW) on the GigabitEthernet0 interface. Actually I forgot that after a full reset the AP is in DHCP mode. So I plugged it on my company lan to get an IP and I was able to access the web interface. Now I put a fixed IP address on the interface as well as for the AP (otherwise impossible to connect to Interface) in order to use it on my local network.
Now everything is working fine. Thanks for you help
09-29-2021 04:18 AM
Can you re-image the EWC AP and try again.
09-29-2021 05:46 AM
Thanks for your answer. I don't even have an IP address to connect to a TFTP server. How can I do? It seems there's a USB port, can I use a USB drive for that?
09-29-2021 04:21 AM
- Is there anything else in the logs (show logging) after you issue write mem ?
M.
09-29-2021 05:47 AM
Yes.
Here it is.
------------------------------------------------------------
WLC9115#show logging
Syslog logging: enabled (0 messages dropped, 3 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)
No Active Message Discriminator.
No Inactive Message Discriminator.
Console logging: level debugging, 95 messages logged, xml disabled,
filtering disabled
Monitor logging: level debugging, 0 messages logged, xml disabled,
filtering disabled
Buffer logging: level debugging, 95 messages logged, xml disabled,
filtering disabled
Exception Logging: size (4096 bytes)
Count and timestamp logging messages: disabled
Persistent logging: disabled
Trap logging: level informational, 92 message lines logged
Logging Source-Interface: VRF Name:
Log Buffer (4096 bytes):
cess wncmgrd
*Apr 2 13:48:55.559: %SYS-5-CONFIG_I: Configured from memory by console
*Apr 2 13:48:55.565: %IOSXE_OIR-6-INSCARD: Card (rp) inserted in slot R1
*Apr 2 13:48:55.565: %IOSXE_OIR-6-INSCARD: Card (fp) inserted in slot F0
*Apr 2 13:48:55.568: %IOSXE_OIR-6-ONLINECARD: Card (fp) online in slot F0
*Apr 2 13:48:55.569: %IOSXE_OIR-6-INSCARD: Card (fp) inserted in slot F1
*Apr 2 13:48:55.569: %IOSXE_OIR-6-ONLINECARD: Card (fp) online in slot F1
*Apr 2 13:48:55.569: %IOSXE_OIR-6-INSCARD: Card (cc) inserted in slot 0
*Apr 2 13:48:55.569: %IOSXE_OIR-6-INSCARD: Card (cc) inserted in slot 1
*Apr 2 13:48:55.449: %PMAN-3-PROC_EMPTY_EXEC_FILE: Chassis 1 R0/0: pvp: Empty executable used for process mobilityd
*Apr 2 13:48:57.710: %PMAN-3-PROC_EMPTY_EXEC_FILE: Chassis 1 R0/0: pvp: Empty executable used for process fman_rp
*Apr 2 13:48:58.208: %PMAN-3-PROC_EMPTY_EXEC_FILE: Chassis 1 R0/0: pvp: Empty executable used for process emd
*Apr 2 13:48:58.724: %PMAN-3-PROC_EMPTY_EXEC_FILE: Chassis 1 R0/0: pvp: Empty executable used for process bt_logger
*Apr 2 13:48:58.886: %PMAN-3-PROC_EMPTY_EXEC_FILE: Chassis 1 R0/0: pvp: Empty executable used for process bt_logger
*Apr 2 13:48:59.259: %PMAN-3-PROC_EMPTY_EXEC_FILE: Chassis 1 R0/0: pvp: Empty executable used for process wstatsd
*Apr 2 13:48:59.834: %SSH-5-ENABLED: SSH 1.99 has been enabled
*Apr 2 13:49:00.086: %SYS-5-RESTART: System restarted --
Cisco IOS Software [Gibraltar], C9800-AP Software (C9800-AP-K9_IOSXE-UNIVERSALK9-M), Version 16.12.2s, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2019 by Cisco Systems, Inc.
Compiled Sat 21-Dec-19 02:05 by mcpre
*Apr 2 13:48:59.761: %PMAN-3-PROC_EMPTY_EXEC_FILE: Chassis 1 R0/0: pvp: Empty executable used for process wncmgrd
*Apr 2 13:49:00.950: %CRYPTO_ENGINE-5-KEY_ADDITION: A key named TP-self-signed-2050145580.server has been generated or imported by crypto-engine
*Apr 2 13:49:01.410: %PMAN-3-PROC_EMPTY_EXEC_FILE: Chassis 1 R0/0: pvp: Empty executable used for process mobilityd
*Apr 2 13:49:04.031: %PKI-2-NON_AUTHORITATIVE_CLOCK: PKI functions can not be initialized until an authoritative time source, like NTP, can be obtained.
*Apr 2 13:49:03.508: %PMAN-3-PROC_EMPTY_EXEC_FILE: Chassis 1 R0/0: pvp: Empty executable used for process fman_rp
*Apr 2 13:49:03.942: %PMAN-3-PROC_EMPTY_EXEC_FILE: Chassis 1 R0/0: pvp: Empty executable used for process emd
*Apr 2 13:49:04.838: %PNP-6-PNP_DISCOVERY_STOPPED: PnP Discovery stopped (Startup Config Present)
*Apr 2 13:49:04.921: %PMAN-3-PROC_EMPTY_EXEC_FILE: Chassis 1 R0/0: pvp: Empty executable used for process bt_logger
*Apr 2 13:49:05.062: %PMAN-3-PROC_EMPTY_EXEC_FILE: Chassis 1 R0/0: pvp: Empty executable used for process bt_logger
*Apr 2 13:49:05.467: %PMAN-3-PROC_EMPTY_EXEC_FILE: Chassis 1 R0/0: pvp: Empty executable used for process wstatsd
*Apr 2 13:49:05.905: %PMAN-3-PROC_EMPTY_EXEC_FILE: Chassis 1 R0/0: pvp: Empty executable used for process wncmgrd
*Apr 2 13:49:06.661: %CRYPTO_ENGINE-5-KEY_ADDITION: A key named CISCO_IDEVID_SUDI_LEGACY has been generated or imported by pki-sudi
*Apr 2 13:49:07.236: %CRYPTO_ENGINE-5-KEY_ADDITION: A key named CISCO_IDEVID_SUDI has been generated or imported by pki-sudi
*Apr 2 13:49:07.475: %PMAN-3-PROC_EMPTY_EXEC_FILE: Chassis 1 R0/0: pvp: Empty executable used for process mobilityd
*Apr 2 13:49:09.535: %PMAN-3-PROC_EMPTY_EXEC_FILE: Chassis 1 R0/0: pvp: Empty executable used for process fman_rp
*Apr 2 13:49:09.965: %PMAN-3-PROC_EMPTY_EXEC_FILE: Chassis 1 R0/0: pvp: Empty executable used for process emd
*Apr 2 13:49:10.891: %PMAN-3-PROC_EMPTY_EXEC_FILE: Chassis 1 R0/0: pvp: Empty executable used for process bt_logger
*Apr 2 13:49:11.031: %PMAN-3-PROC_EMPTY_EXEC_FILE: Chassis 1 R0/0: pvp: Empty executable used for process bt_logger
*Apr 2 13:49:31.110: %SMART_LIC-6-EXPORT_CONTROLLED: Usage of export controlled features is not allowed
*Apr 2 13:49:31.111: %CALL_HOME-6-CALL_HOME_ENABLED: Call-home is enabled by Smart Agent for Licensing.
*Apr 2 14:08:42.024: Failed to save vrrp-ip.txt
10-02-2021 02:34 AM
Can you make sure that there are no any other WLC of any kind is reachable in the same broadcast domain(VLAN). Just try to isolate your WLC on its own VLAN with gateway reachability and try again.
10-06-2021 02:18 AM
Hi,
There's no other WLC on the same LAN. This AP is connected on it's own switch with other equipment but no AP.
BTW, I could get rid of the previous error (Failed to save vrrp-ip.txt) by issuing the command "write erase" seen in another thread here.
It seem that nvram has been flushed but I can still see that some settings are persistent in the AP config (like datarates etc...) even right after 0day setup is completed. Finally the interface is still not accessible from my network.
Is there a way to restart from zero? I would like to totally erase all settings of the embedded WLC as well as the AP. Actually I was trying to configure the loopback interface and DHCP pool before the power outage, maybe it has rebooted with incorrect settings, but no idea which one it is...
Thanks
10-06-2021 04:18 AM
To factory reset;
EWC#wireless ewc-ap factory-reset
10-08-2021 01:43 AM
Hi Arshad,
Actually I did the factory reset but didn't change the fact that I still couldn't connect to the Web interface after setting an IP address (of my local NW) on the GigabitEthernet0 interface. Actually I forgot that after a full reset the AP is in DHCP mode. So I plugged it on my company lan to get an IP and I was able to access the web interface. Now I put a fixed IP address on the interface as well as for the AP (otherwise impossible to connect to Interface) in order to use it on my local network.
Now everything is working fine. Thanks for you help
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide