APs fallback to DHCP

Hi,
all our APs are with static IPs. Now and then APs fallback to DHCP mode and I can't figure out why. Can I disable the IP fallback feature?
Regards,
Petri

no this can't be disabled. This feature is in place to keep the wireless network up and running. If an AP can't communicate with the static address that it has, it falls back to using DHCP to try and communicate.
IMHO, you are better served with having the AP be dhcp vs. static, as the AP is managed via the WLC instead of individually
Sent from Cisco Technical Support iPad App

Similar Messages

  • Aps not finding secondary controller

    I have just installed a secondary WLC 4402 where a client has 1121 APs and 1010 APs and I am slightly confused.
    We have 2 CISCO-LWAPP-CONTROLLER entries in DNS
    The WLCs are WLC1 and WLC2
    The 1010 APs fail over to the secondary controller perfectly well.
    The 1121 APs do not fail over.
    I have given the APs primary and secondary controller names of WLC1 and WLC2.
    Is this due to Option 43 not being configured correctly.
    I believe though I have not investigated that there is a single entry for the 1121 APs in the DHCP scope for option 43 of the original conmtroller but there is no entry for the 1010 APs.
    They are using the same DHCP scope in a layer 2 implementation.
    Any help appreciated

    When the ap has joined a wlc, the dns and dhcp option 43 is not used. The information created in the mobility group (mac address, ip address and mobility group name) is used. This is how ap's learn of the other wlc. Setting the ap's primary and secondary and or tertiary wlc is required for ap's to be able to join the other wlc. Option 43 and dns is used if the ap goes throught the proccess of finding a wlc if the primary, secondary and or tertiary wlc is not found. It seems to me that the ap's have properly joined a wlc, there for, you need to verify why the 1121'a are not joining the secondary.
    First of all, is the mobility group configured correctly and is ap fallback enabled or not. Also, verify that you can mping and eping the controllers. Is the wlc set to layer 2 or layer 3 mode? I think that the 1121 needs the wlc to be in layer 3, but I will check.
    What you should also do is console into the ap and post the log so we can see what errors the ap is getting.
    Here is a link. Search for layer 2
    http://www.cisco.com/en/US/prod/collateral/wireless/ps5678/ps6306/prod_bulletin0900aecd80321a2c_ps6521_Products_Bulletin.html
    Here is a link for AP Fallback:
    http://www.cisco.com/en/US/tech/tk722/tk721/technologies_tech_note09186a00807a85b8.shtml

  • Wireless dhcp issue after upgrading WLC to 7.6.100

    Hi All,
    We have upgraded our controllers to version 7.6.100. After upgrading, the access points also upgraded their version to 15.2(4)JB3. But, the problem is that after this process the APs do not get IP. It stays on this state:
    *Sep 26 03:55:36.334: %CAPWAP-3-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.
    Not in Bound state.
    The DCHP configuration is OK, since it is working in other two controllers we have and that we are not upgrading untill this issue is solved.
    If we connect the APs via console and configure a static IP and controller's IP, the AP registers and works fine. But, the access points are located in 20 remote sites, so we would like to avoid going site by site.
    Has anyone suffered this issue and knows how to "recover" those access points?
    Thank you very mucho for your help!

    Hi,
    Thank you for your answer conraddaniel.
    But, our issue was an error on the DHCP. The DHCP server pool for the APs was configured with lease time infinite (on a Cisco 6500). After capturing the packets and debugging on the AP we realized that the AP were receiving wrong values:
    DHCP: Scan: Renewal time: 2147483647
    DHCP: Scan: Rebind time: 536870911
    So, on the AP debugging we saw:
    DHCP: Scan: Renewal time larger than Rebind time
    On Cisco documentation:
    T1 Timer(Renewal) After a certain portion of the lease time has expired, you attempt to contact the server that initially granted the lease in order to renew the lease so its IP address can still be used.
    T2 Timer(Rebinding) If renewal with the original leasing server fails, because, for example, the server was taken offline, then you ideally try to rebind to any active DHCP server and try to extend its current lease with any server that allows it to do so.
    These T1 and T2 timers can be any values, but must be less than the IP address lease duration. T1 Timer must be less than T2. Generally T1 is set to 50 percent of the lease duration and T2 is set to 87.5 percent of the lease duration. Use this rule to set T1 and T2 timers.
    On the previous version of the WLC, the DHCP was configured in the same way and we confirmed that the APs received same times, but they ignored those wrong values.
    The workaround was to modify the lease time of the DHCP pool (1 day). This way, both timers had valid values and the APs accepted the DHCP OFFER. We still do not know why with lease infinite these timers have wrong values (a bug?).

  • APs not Join WiSM

    Hello, I am Claudio
    I have problems with register the APs in the module WiSM, the AP join statistics is null.
    The IPs from APs are local DHCP in the module.
    The softtware version in the WiSM is 7.0.116. The APs are 1140. The IOS version on the Cat6500 is 12.2.33SXI4a.
    Some of you had a similar problem.
    Thanks, best regards

    The option 43 is......
    ip dhcp pool APs
    network 172.23.24.0 255.255.255.0
    default-router 172.23.24.1
    option 43 hex f108ac140194ac140196
    The problem is not the option 43, the problem is between the module WiSM and SUP720.
    I Replace WiSM for a WLC4402 and APs were recorded without problems
    debug WiSM.....
    URA_NUNOA_SW_6500_CLH#
    Aug 31 16:27:20.818: WiSM-Evt:dman_cntrl_db_search_by_mac: Found mac 68ef.bd2f.2d22 for slot/port 2/1
    Aug 31 16:27:20.822: WiSM-Evt:dman_reg_arp_added: cntrl 2/1 got an ip 172.20.1.178 68ef.bd2f.2d22/68ef.bd2f.2d                            22
    Aug 31 16:27:20.822: WiSM-Evt:dman_cntrl_db_search_by_mac: Found mac 68ef.bd30.58e2 for slot/port 2/2
    Aug 31 16:27:20.822: WiSM-Evt:dman_reg_arp_added: cntrl 2/2 got an ip 172.20.1.179 68ef.bd30.58e2/68ef.bd30.58                            e2
    Aug 31 16:27:35.822: WiSM-Evt:dman_proc_keepalive_tmr_handler: keepalive timer expired for 2/1
    Aug 31 16:27:35.822: WiSM-Evt:dman_proc_keepalive_tmr_handler: keepalive timer expired for 2/2
    Aug 31 16:27:55.822: WiSM-Evt:dman_proc_keepalive_tmr_handler: keepalive timer expired for 2/1
    Aug 31 16:27:55.822: WiSM-Evt:dman_proc_keepalive_tmr_handler: keepalive timer expired for 2/2
    Aug 31 16:28:00.822: WiSM-Evt:dman_cntrl_db_search_by_mac: Found mac 68ef.bd30.58e2 for slot/port 2/2
    Aug 31 16:28:00.822: WiSM-Evt:dman_reg_arp_added: cntrl 2/2 got an ip 172.20.1.179 68ef.bd30.58e2/68ef.bd30.58                            e2
    Aug 31 16:28:00.822: WiSM-Evt:dman_cntrl_db_search_by_mac: Found mac 68ef.bd2f.2d22 for slot/port 2/1
    Aug 31 16:28:00.822: WiSM-Evt:dman_reg_arp_added: cntrl 2/1 got an ip 172.20.1.178 68ef.bd2f.2d22/68ef.bd2f.2d                            22
    Aug 31 16:28:15.822: WiSM-Evt:dman_proc_keepalive_tmr_handler: keepalive timer expired for 2/1
    Aug 31 16:28:15.822: WiSM-Evt:dman_proc_keepalive_tmr_handler: keepalive timer expired for 2/2
    Aug 31 16:28:35.822: WiSM-Evt:dman_proc_keepalive_tmr_handler: keepalive timer expired for 2/1
    Aug 31 16:28:35.822: WiSM-Evt:dman_proc_keepalive_tmr_handler: keepalive timer expired for 2/2
    Aug 31 16:28:40.818: WiSM-Evt:dman_cntrl_db_search_by_mac: Found mac 68ef.bd2f.2d22 for slot/port 2/1
    Aug 31 16:28:40.818: WiSM-Evt:dman_reg_arp_added: cntrl 2/1 got an ip 172.20.1.178 68ef.bd2f.2d22/68ef.bd2f.2d22
    Aug 31 16:28:40.822: WiSM-Evt:dman_cntrl_db_search_by_mac: Found mac 68ef.bd30.58e2 for slot/port 2/2
    Aug 31 16:28:40.822: WiSM-Evt:dman_reg_arp_added: cntrl 2/2 got an ip 172.20.1.179 68ef.bd30.58e2/68ef.bd30.58e2
    Aug 31 16:28:55.822: WiSM-Evt:dman_proc_keepalive_tmr_handler: keepalive timer expired for 2/1
    Aug 31 16:28:55.822: WiSM-Evt:dman_proc_keepalive_tmr_handler: keepalive timer expired for 2/2

  • Will the 2504 WLC internal DHCP give IP addresses to clients?

    Is there a way to configure the 2504 WLC so that its internal DHCP only services the LAPs?
    I don't want the controller to give out IP addressed to wireless clients.
    Thanks

    No. 
    DHCP on the WLC is never intended to offer DHCP services to any "wired" side devices, which includes your APs.  These DHCP pools are specifically to hand addresses out to wireless clients attached to WLANs of the specific WLC it is configured on.  Even then, unless you absolutely cannot offer DHCP somewhere else, DHCP on the WLC is not a suggested practice.
    DHCP Pool Configuration and Restrictions.
    http://www.cisco.com/c/en/us/td/docs/wireless/controller/7-6/configuration-guide/b_cg76/b_cg76_chapter_01000110.html

  • DHCP Requests Starts Failing

    I have a school with 550 iPads.  We are using two 5508 WLCs sharing the number of APs.  The DHCP server and the default gateway for the network are on the firewall.  The clients are able to get a DCHP.  After some time, maybe about longer than a month, the clients are no longer able to get DCHP addresses.  A reboot of both controllers takes care of this.  Presently we are runing 7.2.110 OS.  I am going to upgrade to the latest 7.4.100, and reload tonight. 
    Any insight you could give me for this effort, would be great.

    Thanks. I am gettings these arp errors
    *DHCP Proxy DTL Recv Task: Sep 19 17:44:24.507: %DTL-3-ARP_CLIENT_IP_DUPLICATED: dtl_arp.c:1806 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID  ac:3c:0b:07:15:d1 and IP Address  172.18.1.156, Old client MAC-ID was 84:29:99:
    *DHCP Proxy DTL Recv Task: Sep 19 17:44:23.998: %DTL-3-ARP_CLIENT_IP_DUPLICATED: dtl_arp.c:1806 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID  8c:70:5a:74:86:cc and IP Address  172.18.5.76, Old client MAC-ID was 00:23:14:7
    *apfReceiveTask: Sep 19 17:44:22.794: %RRM-3-RRM_LOGMSG: rrmChanUtils.c:290 RRM LOG: Airewave Director: Could not find valid channel lists for 802.11bg
    *DHCP Proxy DTL Recv Task: Sep 19 17:44:22.540: %DTL-3-ARP_CLIENT_IP_DUPLICATED: dtl_arp.c:1806 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID  ac:3c:0b:09:b6:b8 and IP Address  172.18.1.31, Old client MAC-ID was 84:29:99:1
    *DHCP Proxy DTL Recv Task: Sep 19 17:44:22.534: %DTL-3-ARP_CLIENT_IP_DUPLICATED: dtl_arp.c:1806 ARP entry overwrite, conflict detected via ARP Request from client with MAC-ID  3c:e0:72:cd:19:a0 and IP Address  172.18.0.135, Old client MAC-ID was 84:29:99:
    Any idea how to clear them.I have restarted Windows DHCP server

  • APs registering to anchor controller

    What would make some of our APs register with the anchor controller rather than the primary? All APs are getting DHCP information pointing them to the primary controller, they are all in the same VLAN, etc but for whatever reason some register with the anchor controller. I’m not sure how this is even possible to be honest…
    Any thoughts?

    So, is your anchor controller in the same mobility group as the 'internal'?
    And to explain.
    DHCP option 43, DNS, L2 broadcast etc.  Are simply Discovery Mechanisms for an AP.
    When the AP sends the Discovery Request to a WLC, the WLC responds with a Discovery Reply.  In the Discovery Reply, is a list of all the WLC in the mobility group, their current AP count, their max AP count, and their excess availability.
    Using this information the AP will join the WLC with the Greatest Excess Availability.
    So DHCP Option 43 points to WLCA.  In the Mobility group are WLCA(100), WLCB(100), WLCC(50).
    WLCA has 53 AP
    WLCB has 51 AP
    WLCC has 0 AP.
    Which WLC will the next AP join.  It will join WLCC, as WLCC has the Greatest Excess Availability.
    Make Sense?
    HTH,
    Steve
    Please remember to rate useful posts, and mark questions as answered

  • Access Provisioning and N+1

    I have setup 3 new controllers in and N+1 configuration. Two are active and one is an HA-SKU backup controller which either of the primary's can failover to. The setup looks good and has been verified. Now it is time to provision access points. I have about 220 access points which sit in a different VLAN, and believe I need to configure a DHCP option to point towards a controller which brings these questions to mind. (I'd like to break these up between the primary controllers, 110 each)
    If I create a DHCP option that forces the AP to register with one controller doesn't this defeat the purpose of N+1?
    Or
    After the AP botos this will allow me to provision it and then I can specify one of two primary's and the backup controller?
    If I specify the primary controller for an AP which is booting via DHCP with an option to point it to the first controller will the AP config override that and allow it to operate on the other primary controller which I just defined?
    The controller config was fairly easy, but this is where I got confused.

    Hi Matthew,
    So this is the setup:
    Controller 1 <--> Controller 2 <--> SKU controller
    220 APs in different vlans
    now you want to laod balance the APs between the two active controllers and keep the SKU as backup for all the APs.
    Use DHCP optin 43 to help the APs on each VLAN to learn about that controller
    The AP will learn about this WLC and will join it
    For other APs in different VLAN let them learn the IP for the other WLC and they will join it.
    After the APs joined the correct WLC, you can add the backup controller for them (SKU) from the GUI
    If you want each WLC to exculsively allow particular APs to join (and don't accept the other controller APs) you can use AP policy (security -> AAA -> AP policy)
    Keep in mind that SKU WLC is just backup and wont allow APs to join if the primary WLC is active hence it wont affect the load balancing
    After the AP joins the WLC you can indeed change the primary/ secondary WLC (Wireless -> access point -> select this one -> HA ) or you can do it globally (wireless -> access point -> global configurations -> HA part )
    I hope this answered your question!
    Cheers,
    Nour

  • Cisco AIR-LAP 1522 PROBLEM

    Hello to everyone. They brought me a LAP1522 referring that it is not working properly. I am trying to connect to console port but the problem is that I only get log messages but I cannot edit something or type any commands. I have attached the log messages if you can catch something from there. Ignore the messages about not finding controller because the AP has been removed from the real network to my office.
    IOS Bootloader - Starting system.
    Xmodem file system is available.
    flashfs[0]: 18 files, 2 directories
    flashfs[0]: 0 orphaned files, 0 orphaned directories
    flashfs[0]: Total bytes: 31868928
    flashfs[0]: Bytes used: 15537664
    flashfs[0]: Bytes available: 16331264
    flashfs[0]: flashfs fsck took 23 seconds.
    Reading cookie from flash parameter block...done.
    Base Ethernet MAC address: 00:27:0c:27:3f:00
    Low Power PoE - enabling LAN Ethernet port only
    Loading "flash:/c1520-k9w8-mx.124-21a.JHB/c1520-k9w8-mx.124-21a.JHB"...###################################################################################################################################################################################################
    File "flash:/c1520-k9w8-mx.124-21a.JHB/c1520-k9w8-mx.124-21a.JHB" uncompressed and installed, entry point: 0x3000
    executing...
                  Restricted Rights Legend
    Use, duplication, or disclosure by the Government is
    subject to restrictions as set forth in subparagraph
    (c) of the Commercial Computer Software - Restricted
    Rights clause at FAR sec. 52.227-19 and subparagraph
    (c) (1) (ii) of the Rights in Technical Data and Computer
    Software clause at DFARS sec. 252.227-7013.
               cisco Systems, Inc.
               170 West Tasman Drive
               San Jose, California 95134-1706
    Cisco IOS Software, C1520 Software (C1520-K9W8-M), Version 12.4(21a)JHB, RELEASE SOFTWARE (fc1)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2010 by Cisco Systems, Inc.
    Compiled Tue 06-Jul-10 14:49 by prod_rel_team
    Proceeding with system init
    Proceeding to unmask interrupts
    Initializing flashfs...
    flashfs[1]: 18 files, 2 directories
    flashfs[1]: 0 orphaned files, 0 orphaned directories
    flashfs[1]: Total bytes: 31352832
    flashfs[1]: Bytes used: 15537664
    flashfs[1]: Bytes available: 15815168
    flashfs[1]: flashfs fsck took 5 seconds.
    flashfs[1]: Initialization complete....done Initializing flashfs.
    Warning:  the compile-time code checksum does not appear to be present.
    Radio0  present A600 8000 A8020000 0 A8030000 30
    Radio1  present A600 8000 B8020000 0 B8030000 13
    Radio2 not present 0 0 0 0 0 11
    This product contains cryptographic features and is subject to United
    States and local country laws governing import, export, transfer and
    use. Delivery of Cisco cryptographic products does not imply
    third-party authority to import, export, distribute or use encryption.
    Importers, exporters, distributors and users are responsible for
    compliance with U.S. and local country laws. By using this product you
    agree to comply with applicable laws and regulations. If you are unable
    to comply with U.S. and local laws, return this product immediately.
    A summary of U.S. laws governing Cisco cryptographic products may be found at:
    http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
    If you require further assistance please contact us by sending email to
    [email protected].
    %Error opening flash:/c1520-rcvk9w8-mx/info (No such file or directory)cisco AIR-LAP1522AG-E-K9   (PowerPC 8349) processor (revision A0) with 49142K/16384K bytes of memory.
    Processor board ID FCW1346W00Q
    PowerPC 8349 CPU at 533Mhz, revision number 0x0031
    Last reset from power loss
    LWAPP image version 6.0.199.0
    4 Gigabit Ethernet interfaces
    2 802.11 Radio(s)
    32K bytes of flash-simulated non-volatile configuration memory.
    Base ethernet MAC Address: 00:27:0C:27:3F:00
    Part Number                          : 73-10918-04
    PCA Assembly Number                  : 800-28909-04
    PCA Revision Number                  : A0
    PCB Serial Number                    : FOC13430YBS
    Top Assembly Part Number             : 800-29338-04
    Top Assembly Serial Number           : FCW1346W00Q
    Top Revision Number                  : F0
    Product/Model Number                 : AIR-LAP1522AG-E-K9
    % Please define a domain-name first.
    flash:/mesh_start_cfg.txt: No such file or directoryThe filesystem containing the variables may not be initialized yet.
    Press RETURN to get started!
    Translating "CISCO-LWAPP-CONTROLLER"...domain server (255.255.255.255)
    *Mar  1 00:00:07.231: %SOAP_FIPS-2-SELF_TEST_IOS_SUCCESS: IOS crypto FIPS self test passed
    *Mar  1 00:00:07.575: m8349_ether_enable: MACCFG1 sync timeout
    *Mar  1 00:00:08.079: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 0
    *Mar  1 00:00:08.579: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 1
    *Mar  1 00:00:08.655: %LWAPP-3-CLIENTEVENTLOG: Read and initialized AP event log (contains, 1297 messages)
    *Mar  1 00:00:08.683: AP identified to be in Huck Jr/1240/1130 configuration
    *Mar  1 00:00:09.615: %LINK-3-UPDOWN: Interface Ethernet4, changed state to up
    *Mar  1 00:00:09.615: %LINK-3-UPDOWN: Interface GigabitEthernet0, changed state to up
    *Mar  1 00:00:09.615: %LINK-3-UPDOWN: Interface GigabitEthernet1, changed state to up
    *Mar  1 00:00:09.615: %LINK-3-UPDOWN: Interface GigabitEthernet2, changed state to up
    *Mar  1 00:00:09.615: %LINK-3-UPDOWN: Interface GigabitEthernet3, changed state to up
    *Mar  1 00:00:10.667: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to down
    *Mar  1 00:00:10.667: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1, changed state to down
    *Mar  1 00:00:10.667: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2, changed state to down
    *Mar  1 00:00:10.667: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet3, changed state to down
    *Mar  1 00:00:10.695: %SYS-5-RESTART: System restarted --
    Cisco IOS Software, C1520 Software (C1520-K9W8-M), Version 12.4(21a)JHB, RELEASE SOFTWARE (fc1)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2010 by Cisco Systems, Inc.
    Compiled Tue 06-Jul-10 14:49 by prod_rel_team
    *Mar  1 00:00:10.695: %SNMP-5-COLDSTART: SNMP agent on host wifikal.Laiki-agora is undergoing a cold start
    *Mar  1 00:00:10.759: Warning: Failed to run startup script
    *Mar  1 00:00:10.771: %MESH-6-BVI_CREATED: Mesh BVI1 interface created
    *Mar  1 00:00:10.791: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
    *Mar  1 00:00:10.791: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Mar  1 00:00:11.791: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
    *Mar  1 00:00:11.791: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Mar  1 00:00:12.771: %LINK-3-UPDOWN: Interface BVI1, changed state to down
    *Mar  1 00:00:18.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet4, changed state to up
    *Mar  1 00:00:20.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to up
    Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
    *Mar  1 00:00:22.787: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-LWAPP-CONTROLLER
    flash:/mesh_start_cfg.txt: No such file or directoryThe filesystem containing the variables may not be initialized yet.
    *Mar  1 00:00:25.771: No Mesh startup file found
    *Mar  1 00:00:29.763: Logging LWAPP message to 0.0.0.0.
    *Mar  1 00:00:31.787: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
    *Mar  1 00:00:31.787: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
    *Mar  1 00:00:31.987: %SSH-5-ENABLED: SSH 2.0 has been enabled
    *Mar  1 00:00:45.355: %CDP_PD-2-POWER_LOW: All radios disabled - LOW_POWER_CLASSIC_NO_INJECTOR_CONFIGURED WS-C2960-8TC-L (0025.b413.b802)
    *Mar  1 00:00:45.355:  -Verify the required power-injector is installed on this port: WS-C2960-8TC-L(Fas 0/2).
    *Mar  1 00:00:45.355:  -If a power-injector is installed, issue the command:"power inline negotiation injector installed"
    *Mar  1 00:01:26.015: %MESH-6-ADJACENCY_STATE_MACHINE_STARTED: Mesh adjacency state machine started
    *Mar  1 00:01:34.515: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
    *Mar  1 00:01:36.515: %LINK-3-UPDOWN: Interface BVI1, changed state to up
    *Mar  1 00:01:37.515: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to up
    *Mar  1 00:01:39.563: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
    *Mar  1 00:03:05.575: %LWAPP-3-FALLBACK_DHCP: Invalid Static Gateway, so fallback to DHCP.
    *Mar  1 00:03:15.583: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
    *Mar  1 00:03:15.703: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 20.20.20.37, mask 255.255.255.0, hostname wifikal.Laiki-agora
    *Mar  1 00:03:15.703: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
    *Mar  1 00:03:17.583: %CAPWAP-3-ERRORLOG: Invalid event 29 & state 4 combination.
    *Mar  1 00:03:17.583: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message.
    *Mar  1 00:03:17.583: %CAPWAP-3-ERRORLOG: Failed to handle timer message.
    *Mar  1 00:03:17.583: %CAPWAP-3-ERRORLOG: Failed to process timer message.
    *Mar  1 00:03:17.583: %CAPWAP-3-ERRORLOG: Discovery interval timer expiry handler failed.
    Translating "CISCO-CAPWAP-CONTROLLER.TelestoHQ"...domain server (62.169.194.48)
    *Mar  1 00:03:20.751: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
    Translating "CISCO-LWAPP-CONTROLLER.TelestoHQ"...domain server (62.169.194.48)
    *Mar  1 00:03:21.759: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
    *Mar  1 00:03:21.815: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER.TelestoHQ
    *Mar  1 00:03:21.871: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-LWAPP-CONTROLLER.TelestoHQ
    *Mar  1 00:04:37.583: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join timer expired
    *Mar  1 00:04:37.583: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join failed expired
    *Mar  1 00:04:37.583: %MESH-6-LINK_UPDOWN: Mesh station 0027.0c27.3ffc link Down

    Search this doc for "reset"
    http://www.cisco.com/en/US/docs/wireless/technology/mesh/design/guide/MeshAP_52.html
    Reset Button
    The access point has a reset button located on the bottom of the unit (see Figure 3). The reset button is recessed in a small hole that is sealed with a screw and a rubber gasket. The reset button is used to perform these functions:
    •Reset the access point—press the reset button for less than 10 seconds. LEDs turn off during the reset and then reactivate when the reset is complete.
    •Disable battery backup power—Press the reset button for more than 10 seconds. LEDs turn off, then on, and then stay off.
    –You can also disable the battery remotely by entering this command:
    config mesh battery-state disable AP_name
    •Switch off LEDS—Press the reset button for more than 10 seconds. LEDs turn off, then on, and then stay off.
    Figure 3 Reset Button Location
    1
    Reset button location
    Sent from Cisco Technical Support iPhone App

  • Discovery response message header encapsulation failed

    Hey All,
    i get this from an AP any ideas why this may be happening?
    Last Error Occurred
    Failed to send Lwapp discovery response
    Last Error Occurred Reason
    Discovery response message header encapsulation failed
    Last Join Error Timestamp
    Sep 19 15:56:36.771
    running WLC version
    7.0.98.0

    This is what it tells me:
    flashfs[0]: 4 files, 2 directories
    flashfs[0]: 0 orphaned files, 0 orphaned directories
    flashfs[0]: Total bytes: 7741440
    flashfs[0]: Bytes used: 1755648
    flashfs[0]: Bytes available: 5985792
    flashfs[0]: flashfs fsck took 9 seconds.
    Reading cookie from flash parameter block...done.
    Base ethernet MAC Address: 00:13:19:c8:f9:b6
    Initializing ethernet port 0...
    Reset ethernet port 0...
    Reset done!
    ethernet link up, 100 mbs, full-duplex
    Ethernet port 0 initialized: link is up
    Loading "flash:/c1200-rcvk9w8-mx/c1200-rcvk9w8-mx"...################################################################################################################################################################################
    File "flash:/c1200-rcvk9w8-mx/c1200-rcvk9w8-mx" uncompressed and installed, entry point: 0x3000
    executing...
                  Restricted Rights Legend
    Use, duplication, or disclosure by the Government is
    subject to restrictions as set forth in subparagraph
    (c) of the Commercial Computer Software - Restricted
    Rights clause at FAR sec. 52.227-19 and subparagraph
    (c) (1) (ii) of the Rights in Technical Data and Computer
    Software clause at DFARS sec. 252.227-7013.
               cisco Systems, Inc.
               170 West Tasman Drive
               San Jose, California 95134-1706
    Cisco IOS Software, C1200 Software (C1200-RCVK9W8-M), Version 12.3(7)JX9, RELEASE SOFTWARE (fc1)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2007 by Cisco Systems, Inc.
    Compiled Tue 17-Jul-07 00:44 by tinhuang
    Image text-base: 0x00003000, data-base: 0x0033DA20
    Initializing flashfs...
    flashfs[1]: 4 files, 2 directories
    flashfs[1]: 0 orphaned files, 0 orphaned directories
    flashfs[1]: Total bytes: 7741440
    flashfs[1]: Bytes used: 1755648
    flashfs[1]: Bytes available: 5985792
    flashfs[1]: flashfs fsck took 2 seconds.
    flashfs[1]: Initialization complete....done Initializing flashfs.
    cisco AIR-AP1231G-A-K9     (PowerPC405GP) processor (revision B0) with 14838K/1536K bytes of memory.
    Processor board ID FTX0907J0E8
    PowerPC405GP CPU at 196Mhz, revision number 0x0145
    Last reset from power-on
    1 FastEthernet interface
    32K bytes of flash-simulated non-volatile configuration memory.
    Base ethernet MAC Address: 00:13:19:C8:F9:B6
    Part Number                          : 73-8704-08
    PCA Assembly Number                  : 800-23211-09
    PCA Revision Number                  : A0
    PCB Serial Number                    : FOC09024TMB
    Top Assembly Part Number             : 800-23304-08
    Top Assembly Serial Number           : FTX0907J0E8
    Top Revision Number                  : A0
    Product/Model Number                 : AIR-AP1231G-A-K9
    Press RETURN to get started!
    *Mar  1 00:00:04.402: %SYS-5-RESTART: System restarted --
    Cisco IOS Software, C1200 Software (C1200-RCVK9W8-M), Version 12.3(7)JX9, RELEASE SOFTWARE (fc1)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2007 by Cisco Systems, Inc.
    Compiled Tue 17-Jul-07 00:44 by tinhuang
    *Mar  1 00:00:05.380: %LINK-3-UPDOWN: Interface FastEthernet0, changed state to up
    *Mar  1 00:00:06.380: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0, changed state to up
    ap>
    ap>en
    ap#debug lwapp console cli
    LWAPP console CLI allow/disallow debugging is on
    ap#debug lwapp client event
    LWAPP Client EVENT display debugging is on
    ap#debug lwapp client error
    LWAPP Client ERROR display debugging is on
    ap#debug capwap client event
               ^
    % Invalid input detected at '^' marker.
    ap#debug capwap client error
               ^
    % Invalid input detected at '^' marker.
    ap#
    ap#
    ap#
    ap#
    *Mar  1 00:00:23.416: LWAPP_CLIENT_EVENT: lwapp_ip_address_change - ADDING IP 10.0.0.1, 255.255.255.0; resolvemethod 1, ip_dhcp_addr 0
    *Mar  1 00:00:23.419: LWAPP_CLIENT_EVENT: lwapp_set_ip_address - Seting Static IP 10.0.0.1        255.255.255.0   on FastEthernet0
    *Mar  1 00:00:23.419: LWAPP_CLIENT_EVENT: lwapp_set_ip_address - Seting Default Gateway IP to 10.0.0.2
    *Mar  1 00:00:23.425: LWAPP_CLIENT_EVENT: spamResolveStaticGateway  - gateway NOT found
    *Mar  1 00:00:23.425: %LWAPP-5-CHANGED: LWAPP changed state to DISCOVERY
    *Mar  1 00:00:23.431: LWAPP_CLIENT_EVENT: parse_lwapp_config: hostname AP0013.19c8.f9b6
    end
    *Mar  1 00:00:23.447: LWAPP_CLIENT_EVENT: lwapp_crypto_init_mic_keys_and_certs : MIC not present
    *Mar  1 00:00:23.453: LWAPP_CLIENT_EVENT: lwapp_crypto_init_ssc_keys_and_certs found key(1) label CISCO_IOS_SSC_Keys
    *Mar  1 00:00:23.458: LWAPP_CLIENT_EVENT: lwapp_crypto_init_ssc_keys_and_certs Certs Keylen 294
    *Mar  1 00:00:23.459: LWAPP_CLIENT_EVENT: lwapp_crypto_init_ssc_keys_and_certs Public Key Match Found CISCO_IOS_SSC_Keys
    *Mar  1 00:00:24.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway  - gateway NOT found
    *Mar  1 00:00:34.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR
    *Mar  1 00:00:34.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway  - gateway NOT found
    *Mar  1 00:00:44.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR
    *Mar  1 00:00:44.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway  - gateway NOT found
    *Mar  1 00:00:54.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR
    *Mar  1 00:00:54.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway  - gateway NOT found
    *Mar  1 00:01:04.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR
    *Mar  1 00:01:04.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway  - gateway NOT found
    *Mar  1 00:01:14.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR
    *Mar  1 00:01:14.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway  - gateway NOT found
    *Mar  1 00:01:24.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR
    *Mar  1 00:01:24.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway  - gateway NOT found
    *Mar  1 00:01:34.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR
    *Mar  1 00:01:34.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway  - gateway NOT found
    *Mar  1 00:01:44.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR
    *Mar  1 00:01:44.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway  - gateway NOT found
    *Mar  1 00:01:54.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR
    *Mar  1 00:01:54.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway  - gateway NOT found
    *Mar  1 00:02:04.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR
    *Mar  1 00:02:04.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway  - gateway NOT found
    *Mar  1 00:02:04.389: LWAPP_CLIENT_EVENT: lwapp_check_image_good: image is good now
    *Mar  1 00:02:14.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR
    *Mar  1 00:02:14.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway  - gateway NOT found
    AP0013.19c8.f9b6#
    *Mar  1 00:02:24.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR
    *Mar  1 00:02:24.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway  - gateway NOT found
    *Mar  1 00:02:34.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR
    *Mar  1 00:02:34.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway  - gateway NOT found
    *Mar  1 00:02:44.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR
    *Mar  1 00:02:44.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway  - gateway NOT found
    *Mar  1 00:02:54.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR
    *Mar  1 00:02:54.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway  - gateway NOT found
    *Mar  1 00:03:04.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR
    *Mar  1 00:03:04.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway  - gateway NOT found
    *Mar  1 00:03:14.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR
    *Mar  1 00:03:14.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway  - gateway NOT found
    *Mar  1 00:03:24.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR
    *Mar  1 00:03:24.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway  - gateway NOT found
    *Mar  1 00:03:34.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR
    *Mar  1 00:03:34.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway  - gateway NOT found
    *Mar  1 00:03:44.036: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR
    *Mar  1 00:03:44.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway  - gateway NOT found
    *Mar  1 00:03:44.036: LWAPP_CLIENT_EVENT: spamResolveStaticGateway  - gateway NOT found
    *Mar  1 00:03:44.036: LWAPP_CLIENT_EVENT: spamStartDhcp - AP IP FALLBACK TO DHCP
    Translating "CISCO-LWAPP-CONTROLLER.org.org"...domain server (10.1.0.254)
    *Mar  1 00:03:53.074: LWAPP_CLIENT_EVENT: lwapp_ip_address_change - ADDING IP 10.0.1.254, 255.255.255.0; resolvemethod A, ip_dhcp_addr 1
    *Mar  1 00:03:53.181: %DHCP-6-ADDRESS_ASSIGN: Interface FastEthernet0 assigned DHCP address 10.0.1.254, mask 255.255.255.0, hostname AP0013.19c8.f9b6
    [OK]
    *Mar  1 00:03:53.181: LWAPP_CLIENT_EVENT: lwapp_ip_address_change - ADDING IP 10.0.1.254, 255.255.255.0; resolvemethod A, ip_dhcp_addr 1
    *Mar  1 00:03:54.057: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR
    *Mar  1 00:03:54.057: LWAPP_CLIENT_EVENT: spamResolveStaticGateway  - gateway found
    *Mar  1 00:03:54.183: LWAPP_CLIENT_EVENT: lwapp_name_lookup - add (0) 10.0.254.253
    *Mar  1 00:03:54.183: LWAPP_CLIENT_EVENT: lwapp_name_lookup - add (1) 10.0.254.254
    *Mar  1 00:04:04.057: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR
    *Mar  1 00:04:04.057: LWAPP_CLIENT_EVENT: spamResolveStaticGateway  - gateway NOT found
    *Mar  1 00:04:15.063: %LWAPP-5-CHANGED: LWAPP changed state to JOIN
    *Mar  1 00:04:20.063: LWAPP_CLIENT_ERROR_DEBUG: spamHandleJoinTimer: Did not recieve the Join response
    *Mar  1 00:04:20.063: LWAPP_CLIENT_ERROR_DEBUG: No more AP manager IP addresses remain.
    *Mar  1 00:04:20.063: %SYS-5-RELOAD: Reload requested by LWAPP CLIENT. Reload Reason: DID NOT GET JOIN RESPONSE.
    *Mar  1 00:04:20.064: %LWAPP-5-CHANGED: LWAPP changed state to DOWN
    And this is on the controller:
    (Cisco Controller) >show ap join stats summary 00:13:19:c8:f9:b6
    Is the AP currently connected to controller................ No
    Time at which the AP joined this controller last time...... Not applicable
    Type of error that occurred last........................... Failed to send Lwapp discovery response
    Reason for error that occurred last........................ Discovery response message header encapsulation failed
    Time at which the last join error occurred................. Nov 29 17:23:35.793
    (Cisco Controller) >show ap join stats detailed 00:13:19:c8:f9:b6
    Discovery phase statistics
    - Discovery requests received.............................. 97
    - Successful discovery responses sent...................... 94
    - Unsuccessful discovery request processing................ 100
    - Reason for last unsuccessful discovery attempt........... Discovery response message header encapsulation failed
    - Time at last successful discovery attempt................ Dec 03 20:07:22.259
    - Time at last unsuccessful discovery attempt.............. Nov 29 17:23:35.793
    Join phase statistics
    - Join requests received................................... 0
    - Successful join responses sent........................... 0
    - Unsuccessful join request processing..................... 0
    - Reason for last unsuccessful join attempt................ Not applicable
    - Time at last successful join attempt..................... Not applicable
    - Time at last unsuccessful join attempt................... Not applicable
    Configuration phase statistics
    - Configuration requests received.......................... 0
    - Successful configuration responses sent.................. 0
    - Unsuccessful configuration request processing............ 0
    - Reason for last unsuccessful configuration attempt....... Not applicable
    - Time at last successful configuration attempt............ Not applicable
    --More-- or (q)uit
    - Time at last unsuccessful configuration attempt.......... Not applicable
    Last AP message decryption failure details
    - Reason for last message decryption failure............... Not applicable
    Last AP disconnect details
    - Reason for last AP connection failure.................... Not applicable
    - Last AP disconnect reason................................ Not applicable
    Last join error summary
    - Type of error that occurred last......................... Failed to send Lwapp discovery response
    - Reason for error that occurred last...................... Discovery response message header encapsulation failed
    - Time at which the last join error occurred............... Nov 29 17:23:35.793
    AP disconnect details
    - Reason for last AP connection failure.................... Not applicable
                                                                               Ethernet Mac : 00:00:00:00:00:00  Ip Address : 10.0.1.254
    (Cisco Controller) >

  • WISM and AP homing

    Hi
    We have just deployed approx 290 AP's and we have three WISM's (A,B,C) with 150 primary to A (secondary is B), 150 primary to B (secondary is A).
    Ignoring the fact that there are two controllers per WISM, when we shut WISM A down we get approx 250+ on B and the rest on WISM C.
    This number varies but we never manage to get all 290 AP's on WISM B. Its as if WISM B is so busy that numerous AP's give up and try something else.
    The interesting thing is we have NOT coded WISM C into any AP configs.
    So my questions are:
    1. Why haven't all 300 AP's managed to register with WISM B (as coded).
    2. If WISM C has been learnt by some other means is this expected behaviour to register to any WISM even if its not in your primary/secondary/tertiary settings.
    This is not how I understood it should work from Cisco. I do not want these particular AP's to register to WISM C. On the flipside, I could understand the rationale of wanting an AP to register to any controller if possible rather than be isolated.
    Has any one had similar experiences ?
    Are there any plans to prioritise which AP's can register to a controller i.e. If I had 310 AP's but only the backup capacity for 300 it would be nice to have a feature to predict which of the 300 register rather than the unpredicatable method of present.
    regards
    Paul

    I have deployed aprox 350 aps, since they are divided up among three different campuses, we never had one with more that 120 aps, recently we added 50 more aps, but one of the controller maxed out at 150, the other controller has failed to respond to the aps even though dhcp option 43 has its ip address configured.
    how were you able to have the aps load balance or fail over to the secondary controller.

  • Reseting a 1242 LAP's Ethernet interface

    Is there a way to reset a 1242's IP and Gateway (both are configured as the same IP due to a cut'n'paste error in the WCS ... so the AP is not reachable and the the fallback to DHCP won't work, because the AP can reach his false gateway...)
    The AP is on a remote location so, i only can ask the user for onside support. Is there a easy way to get the AP back to do DHCP?

    Hi,
    Reboot the AP multiple times.. this has worked for me while troubleshooting with several customers.. however when ever this doesnt work.. we need to get the console access to the AP and then issue the below command..
    en
    debug lwapp console cli or debug capwap console cli
    clear lwapp private-config or clear capwap private-config
    end
    LWAPP ap ip
    LWAPP ap controller ip
    or
    debug lwapp console cli or debug capwap console cli
    int fa 0
    ip addr dhcp
    end
    This will do it...
    lemme know if this answers your question
    Regards
    Surendra
    ====
    Please dont forget to rate the usefull posts which answered your question or was helpfull

  • Cisco LAP 1522

    Sorry for this stupid question,
    but is there anyway to access directly a LAP 1522 using a console port?
    Best Regards.

    Yes all the settings are as you suggested. Scott the problem is that it does not allow me to type anything. I have attached the log messages if you can catch something from there. Ignore the messages about not finding controller because the AP has been removed from the real network to my office.
    IOS Bootloader - Starting system.
    Xmodem file system is available.
    flashfs[0]: 18 files, 2 directories
    flashfs[0]: 0 orphaned files, 0 orphaned directories
    flashfs[0]: Total bytes: 31868928
    flashfs[0]: Bytes used: 15537664
    flashfs[0]: Bytes available: 16331264
    flashfs[0]: flashfs fsck took 23 seconds.
    Reading cookie from flash parameter block...done.
    Base Ethernet MAC address: 00:27:0c:27:3f:00
    Low Power PoE - enabling LAN Ethernet port only
    Loading "flash:/c1520-k9w8-mx.124-21a.JHB/c1520-k9w8-mx.124-21a.JHB"...###################################################################################################################################################################################################
    File "flash:/c1520-k9w8-mx.124-21a.JHB/c1520-k9w8-mx.124-21a.JHB" uncompressed and installed, entry point: 0x3000
    executing...
                  Restricted Rights Legend
    Use, duplication, or disclosure by the Government is
    subject to restrictions as set forth in subparagraph
    (c) of the Commercial Computer Software - Restricted
    Rights clause at FAR sec. 52.227-19 and subparagraph
    (c) (1) (ii) of the Rights in Technical Data and Computer
    Software clause at DFARS sec. 252.227-7013.
               cisco Systems, Inc.
               170 West Tasman Drive
               San Jose, California 95134-1706
    Cisco IOS Software, C1520 Software (C1520-K9W8-M), Version 12.4(21a)JHB, RELEASE SOFTWARE (fc1)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2010 by Cisco Systems, Inc.
    Compiled Tue 06-Jul-10 14:49 by prod_rel_team
    Proceeding with system init
    Proceeding to unmask interrupts
    Initializing flashfs...
    flashfs[1]: 18 files, 2 directories
    flashfs[1]: 0 orphaned files, 0 orphaned directories
    flashfs[1]: Total bytes: 31352832
    flashfs[1]: Bytes used: 15537664
    flashfs[1]: Bytes available: 15815168
    flashfs[1]: flashfs fsck took 5 seconds.
    flashfs[1]: Initialization complete....done Initializing flashfs.
    Warning:  the compile-time code checksum does not appear to be present.
    Radio0  present A600 8000 A8020000 0 A8030000 30
    Radio1  present A600 8000 B8020000 0 B8030000 13
    Radio2 not present 0 0 0 0 0 11
    This product contains cryptographic features and is subject to United
    States and local country laws governing import, export, transfer and
    use. Delivery of Cisco cryptographic products does not imply
    third-party authority to import, export, distribute or use encryption.
    Importers, exporters, distributors and users are responsible for
    compliance with U.S. and local country laws. By using this product you
    agree to comply with applicable laws and regulations. If you are unable
    to comply with U.S. and local laws, return this product immediately.
    A summary of U.S. laws governing Cisco cryptographic products may be found at:
    http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
    If you require further assistance please contact us by sending email to
    [email protected].
    %Error opening flash:/c1520-rcvk9w8-mx/info (No such file or directory)cisco AIR-LAP1522AG-E-K9   (PowerPC 8349) processor (revision A0) with 49142K/16384K bytes of memory.
    Processor board ID FCW1346W00Q
    PowerPC 8349 CPU at 533Mhz, revision number 0x0031
    Last reset from power loss
    LWAPP image version 6.0.199.0
    4 Gigabit Ethernet interfaces
    2 802.11 Radio(s)
    32K bytes of flash-simulated non-volatile configuration memory.
    Base ethernet MAC Address: 00:27:0C:27:3F:00
    Part Number                          : 73-10918-04
    PCA Assembly Number                  : 800-28909-04
    PCA Revision Number                  : A0
    PCB Serial Number                    : FOC13430YBS
    Top Assembly Part Number             : 800-29338-04
    Top Assembly Serial Number           : FCW1346W00Q
    Top Revision Number                  : F0
    Product/Model Number                 : AIR-LAP1522AG-E-K9
    % Please define a domain-name first.
    flash:/mesh_start_cfg.txt: No such file or directoryThe filesystem containing the variables may not be initialized yet.
    Press RETURN to get started!
    Translating "CISCO-LWAPP-CONTROLLER"...domain server (255.255.255.255)
    *Mar  1 00:00:07.231: %SOAP_FIPS-2-SELF_TEST_IOS_SUCCESS: IOS crypto FIPS self test passed
    *Mar  1 00:00:07.575: m8349_ether_enable: MACCFG1 sync timeout
    *Mar  1 00:00:08.079: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 0
    *Mar  1 00:00:08.579: %SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: RADIO crypto FIPS self test passed on interface Dot11Radio 1
    *Mar  1 00:00:08.655: %LWAPP-3-CLIENTEVENTLOG: Read and initialized AP event log (contains, 1297 messages)
    *Mar  1 00:00:08.683: AP identified to be in Huck Jr/1240/1130 configuration
    *Mar  1 00:00:09.615: %LINK-3-UPDOWN: Interface Ethernet4, changed state to up
    *Mar  1 00:00:09.615: %LINK-3-UPDOWN: Interface GigabitEthernet0, changed state to up
    *Mar  1 00:00:09.615: %LINK-3-UPDOWN: Interface GigabitEthernet1, changed state to up
    *Mar  1 00:00:09.615: %LINK-3-UPDOWN: Interface GigabitEthernet2, changed state to up
    *Mar  1 00:00:09.615: %LINK-3-UPDOWN: Interface GigabitEthernet3, changed state to up
    *Mar  1 00:00:10.667: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to down
    *Mar  1 00:00:10.667: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1, changed state to down
    *Mar  1 00:00:10.667: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2, changed state to down
    *Mar  1 00:00:10.667: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet3, changed state to down
    *Mar  1 00:00:10.695: %SYS-5-RESTART: System restarted --
    Cisco IOS Software, C1520 Software (C1520-K9W8-M), Version 12.4(21a)JHB, RELEASE SOFTWARE (fc1)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2010 by Cisco Systems, Inc.
    Compiled Tue 06-Jul-10 14:49 by prod_rel_team
    *Mar  1 00:00:10.695: %SNMP-5-COLDSTART: SNMP agent on host wifikal.Laiki-agora is undergoing a cold start
    *Mar  1 00:00:10.759: Warning: Failed to run startup script
    *Mar  1 00:00:10.771: %MESH-6-BVI_CREATED: Mesh BVI1 interface created
    *Mar  1 00:00:10.791: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to reset
    *Mar  1 00:00:10.791: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to reset
    *Mar  1 00:00:11.791: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
    *Mar  1 00:00:11.791: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
    *Mar  1 00:00:12.771: %LINK-3-UPDOWN: Interface BVI1, changed state to down
    *Mar  1 00:00:18.507: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet4, changed state to up
    *Mar  1 00:00:20.575: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to up
    Translating "CISCO-CAPWAP-CONTROLLER"...domain server (255.255.255.255)
    *Mar  1 00:00:22.787: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-LWAPP-CONTROLLER
    flash:/mesh_start_cfg.txt: No such file or directoryThe filesystem containing the variables may not be initialized yet.
    *Mar  1 00:00:25.771: No Mesh startup file found
    *Mar  1 00:00:29.763: Logging LWAPP message to 0.0.0.0.
    *Mar  1 00:00:31.787: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER
    *Mar  1 00:00:31.787: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
    *Mar  1 00:00:31.987: %SSH-5-ENABLED: SSH 2.0 has been enabled
    *Mar  1 00:00:45.355: %CDP_PD-2-POWER_LOW: All radios disabled - LOW_POWER_CLASSIC_NO_INJECTOR_CONFIGURED WS-C2960-8TC-L (0025.b413.b802)
    *Mar  1 00:00:45.355:  -Verify the required power-injector is installed on this port: WS-C2960-8TC-L(Fas 0/2).
    *Mar  1 00:00:45.355:  -If a power-injector is installed, issue the command:"power inline negotiation injector installed"
    *Mar  1 00:01:26.015: %MESH-6-ADJACENCY_STATE_MACHINE_STARTED: Mesh adjacency state machine started
    *Mar  1 00:01:34.515: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
    *Mar  1 00:01:36.515: %LINK-3-UPDOWN: Interface BVI1, changed state to up
    *Mar  1 00:01:37.515: %LINEPROTO-5-UPDOWN: Line protocol on Interface BVI1, changed state to up
    *Mar  1 00:01:39.563: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
    *Mar  1 00:03:05.575: %LWAPP-3-FALLBACK_DHCP: Invalid Static Gateway, so fallback to DHCP.
    *Mar  1 00:03:15.583: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
    *Mar  1 00:03:15.703: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 20.20.20.37, mask 255.255.255.0, hostname wifikal.Laiki-agora
    *Mar  1 00:03:15.703: %MESH-6-CAPWAP_RESTART: Mesh Capwap re-started
    *Mar  1 00:03:17.583: %CAPWAP-3-ERRORLOG: Invalid event 29 & state 4 combination.
    *Mar  1 00:03:17.583: %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message.
    *Mar  1 00:03:17.583: %CAPWAP-3-ERRORLOG: Failed to handle timer message.
    *Mar  1 00:03:17.583: %CAPWAP-3-ERRORLOG: Failed to process timer message.
    *Mar  1 00:03:17.583: %CAPWAP-3-ERRORLOG: Discovery interval timer expiry handler failed.
    Translating "CISCO-CAPWAP-CONTROLLER.TelestoHQ"...domain server (62.169.194.48)
    *Mar  1 00:03:20.751: %CAPWAP-5-CHANGED: CAPWAP changed state to DISCOVERY
    Translating "CISCO-LWAPP-CONTROLLER.TelestoHQ"...domain server (62.169.194.48)
    *Mar  1 00:03:21.759: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
    *Mar  1 00:03:21.815: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER.TelestoHQ
    *Mar  1 00:03:21.871: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-LWAPP-CONTROLLER.TelestoHQ
    *Mar  1 00:04:37.583: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join timer expired
    *Mar  1 00:04:37.583: %MESH-3-TIMER_EXPIRED: Mesh Lwapp join failed expired
    *Mar  1 00:04:37.583: %MESH-6-LINK_UPDOWN: Mesh station 0027.0c27.3ffc link Down

  • HH3 constantly resetting links

    I've got two problems They might be related-
    1. All devices are resetting "ip leases" every 30 seconds on my hh3- so connections to internet are interrupted every 30 seconds- error logs show this is happening on both wired and wireless ip address for all devices every 30 seconds. Productive internet sessions are not practical with this situation. secure sessions disconnect- home network printers don't work, etc. etc.
    2. my speed on infinity varies from zero to 1-2 meg, occasionally bursts up to 25 meg, but mostly zero.
    Details and thoughts-
    Fibre- I have a DLM enabled cabinet 50 metres from my house, but BT engineers chose to connect my coppper to a DLM enabled cabinet 1/2 mile away- makes no sense to me why, maybe thats not supposed to make any difference, maybe it was laziness.   ( Even if the fibre is perfect, unecessarily long copper runs over telephone poles, etc. reduces the available stable signal "spectrum" quite alot, and the stability is subject to things as simple as a rainy cold spell, that might get some of the wiring that isn't insulated well enough a bit damp- these are called intermittent faults and are notoriously difficult to resolve- quicker to run new known working copper and terminate onto fibre DLM as near as possible to the customer premise point of interface or point of presence.)
    I've had many calls with india, who have been very friendly and confirmed with tap 3 tests, with resets, etc. etc.
    In addition, on my own, I've done wireless scans just to eliminate wifi noise as a source of the problem- and to see if rogue wifi APs were causing beacons to misbehave, or if rogue DHCP servers were associating my devices using wifi- disassociating them from my hub- - all very interesting- expecially that all 25 wifi devices in my neighbourhood are set to channel 11... but no rogue wifi aps, and no rogue dhcp servers.
    Although BT haven't yet reached this conclusion- I suspect its a dodgey hh3 device. The HH3 device is manufactured by BNA Systems, and has the most current firmware, and it seems like its been problematic for alot of customers. Its behaviour is inexplicable and doesn't match up with any normal behaviour. So immediate troubleshooting should have been to swap the hh3 with a known working hh3. That hasn't been suggested in the entire two weeks. And its far more expensive to send an engineer to my house, than to send a replacement hh3. But thats whats they are doing!
    I have a spare belkin and a spare Asus that I could try and use if necessary but I might add complication to the resolution by BT, so I wont do that just yet.
    I also wonder if the two problems are related-  I'm pretty sure infinity is a burst service- a stable baseline bandwidth, and some burstable limits-  coupled with the "spread spectrum" DSL type learning to adapt to the actual line conditions to offer as much within the min/max bandwith speeds-
    I think this means that the intelligent adaptive fibre DLM see so little traffic coming from my line, and so many interruptions, that it restarts its learning process or decides that it needs to only provide very little baseline broadband, and little burst- but I'm getting zero bandwith over broadband connection now regularly, so there might be a disconnection issue there as well for some reason from the modem.
    the Open reach modem might also be able to signal the hub to restart every 30 seconds- but the blue lights stay on the whole time- so I don't think so- everything I see still leads back to the HH3 being defective.
    I have reset the lease period to the maximum 21 days, the hub still resets every 30 seconds, despite showing in the error log that a huge amount of minutes are remaining on the lease. Its impossible that all devices independently decided to start requesting new leases every 30 seconds as a problem- and I've eliminated that rogue APs or rogue DHCPs are a problem- but all the devices ( wired and wireless) are being disassociated from the hh3, and on reassociation, the HH3 dhcp server recognises the device but is disregarding the the remaining lease time for the device, and issues a new lease. So the reassociation protocol between hh3 and all my devices is broken-
    shouldn't the immediate test by BT be to replace suspect hh3 with a known working hh3?
    Status of solution-
    India scheduled a BT engineer "specialist" on infinity team to come to my house this week-presumably to see what the problem my be in my setup. I certainly hope the engineer brings a spare- known working hh3 replacement device!
    Has anyone had a similar situation, and what did they do to resolve?
    Would it be helpful to post the solution that is finallly applied to my setup?
    Regards

    Thanks for your input Bart. Yours is exactly the kind of situation I want to avoid; repeated engineer visits, replacement routers and only temporary improvements before the connection goes back to being crappy again. Unfortunately it seems that lots of people are going through this which is why I thought I'd try to get the mods opinion on this before I start the inevitable rigmarole of calling India and everything else that will follow. I requested mod support the same day of my original post so hopefully I'll get a response from a mod today or the start of next week, if you keep an eye on this post maybe you'll see something that'll help you too.
    I moved from Be because their fibre optic isn't going to be available for another year or 2 and I didn't want to wait, now I'm wishing I did wait. I should have expected substandard hardware and substandard service from BT because those were the reasons I moved away from BT in the first place all those years ago! (I was with Be for about 5 years, and I must say they were superb).
    BT should send us decent third-party (netgear, linksys, d-link, anything!) routers and be done with it.
    I certainly won't be recommending BT Infinity to anyone (not anyone I like anyway!).

  • APs unable to receive IP address from DHCP (core 6500 series switch)

    Dear Friends,
    a week ago I had stable wireless network APs were getting IPS from 6500 series switch (DHCP) but unfortunately some WISM got rebooted and now APs are unable to receive IP address from Core 6500 DHCP, to cater this issue  I have another DHCP server configured on windows 2008  i created another subnet and and put APs in that vlan now all APs are are successfully receiving IPS from windows DHCP server I don't know why APs are not able to receive IPs from core 6500 series DHCP.
    please advice
    Thanks
    Faysal

    Thanks george for stepping up here is DHCP config
    ip dhcp excluded-address 10.10.30.1 10.10.30.20
    ip dhcp excluded-address 10.10.8.1 10.10.8.10
    ip dhcp excluded-address 192.168.10.1 192.168.10.5
    ip dhcp excluded-address 10.9.20.1 10.9.20.30
    ip dhcp pool vlan_30
    network 10.10.30.0 255.255.254.0
    default-router 10.10.30.1
    option 60 ascii """"""""""""""""""""""""CiscoAPc1250""""""""""""""""""""""""
    option 43 hex f110.0a0a.1e0b.0a0a.1e0d.0a0a.1e0f.0a0a.1e11
    dns-server 10.10.2.11
    lease infinite
    ip dhcp pool WiSM1_SP
    network 192.168.10.0 255.255.255.248
    default-router 192.168.10.1

Maybe you are looking for

  • Function Module for CO-PA document creation

    Hi, we need to crate the CO-PA document through program. Is there any funcion module/BAPI available for the same? Scenario here is... We are restricting CO-PA document not to be created at the time of invoice creation. Later some point of time in the

  • How do you identify mail in the junk folder as "not junk"?

    I came across this answer on the Apple support site: Tell Mail that a message is legitimate by marking it as not junk. Click Not Junk in the banner of the message; or select the message, then click the Not Junk button in the Mail toolbar. Unfortunate

  • Changing the output layout of standard transaction FPWLM

    Hi All, We have a requirement where we need to change the output layout of the standard transaction FPWLM which is used fo the management of worklist for collecion management. In this transaction under the current worklist if we select the worklist I

  • VMware View Planner multi-remote PCoIP test with linked clones

    So I was able to run the VMware view Planner local mode test no problem, however, I am having some troubles trying to do it with linked clones here.  I think part of my problem is that the instructions I am following in the user guide here are a bit

  • Apple forcing change to Mountain Lion by producing poor updates for other OS versions?

    I've been holding off on 10.7.5 and I don't want to go to Mountain Lion. I wonder if Apple really cares about supporting the older OS versions by producing updates that don't result in all the apparent problems people are facing with the 10.7.5 updat