Registration with WLC Cisco 2600 TOWER

Similar Questions

• Cisco AIR-LAP1041N-E-K9 does not not with WLC 4402 version 7.0.116.0

  Hi all

  appreciate your support for a problem I started to deal with today. I have a Cisco WLC 4402 running the 7.0.116.0 version and it's great to work with 25 Cisco 1252 access points. We received a new 20 Cisco 1041N APs today and I installed one in our site, but it does not work. He well worked and loaded the flash image and obtained WLC ip through DHCP option address and began to show the below error:

  * 00:00:10.021 Mar 1: % SOAP_FIPS-2-SELF_TEST_IOS_SUCCESS: crypto IOS FIPS self-test passed

  * 00:00:10.033 Mar 1: * CRASH_LOG = YES

  * 00:00:10.333 Mar 1: 1 Port is not presentSecurity base.

  MAC Ethernet address of base: C8:9 C: 1 D: 53:57:5E

  * 00:00:11.373 Mar 1: % SOAP_FIPS-2-SELF_TEST_RAD_SUCCESS: crypto RADIO FIPS self-test passed on Dot11Radio interface 0

  * 00:00:11.465 Mar 1: % LWAPP-3-CLIENTEVENTLOG: reading and initialized AP event log (contains, 1088 messages)

  * 00:00:11.494 Mar 1: State of the voice_diag_test of WLC is false

  * 00:00:12.526 Mar 1: % LINK-3-UPDOWN: Interface GigabitEthernet0, changed State to

  * 00:00:13.594 Mar 1: % LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed State to

  * 00:00:13.647 Mar 1: % SYS-5-RESTART: System restarted.

  Cisco IOS software, software C1040 (C1140-K9W8-M), Version 12.4 (23 c) JA2, VERSION of the SOFTWARE (fc3)

  Technical support: http://www.cisco.com/techsupport

  Copyright (c) 1986-2011 by Cisco Systems, Inc.

  Updated Thursday, April 13, 11 12:50 by prod_rel_team

  * 00:00:13.647 Mar 1: % SNMP-5-start COLD: SNMP agent on host APc89c.1d53.575e knows a cold start

  * 00:08:59.062 Mar 1: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

  * 1 Mar 00:08:59.062: bsnInitRcbSlot: slot 1 has NO radio

  * 00:08:59.138 Mar 1: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset

  * 00:08:59.837 Mar 1: % SSH-5-ACTIVATED: SSH 2.0 has been activated

  * 00:09:00.145 Mar 1: % LINEPROTO-5-UPDOWN: Line protocol on the Interface Dot11Radio0, state change downstairs

  * 00:09:09.136 Mar 1: % ADDRESS_ASSIGN-6-DHCP: Interface GigabitEthernet0 assigned address DHCP 172.16.26.81, mask 255.255.255.0, hostname APc89c.1d53.575e

  * 00:09:17.912 Mar 1: % PARSER-4-BADCFG: unexpected end of the configuration file.

  * 00:09:17.912 Mar 1: State of the voice_diag_test of WLC is false

  * 00:09:17.984 Mar 1: message logging LWAPP to 255.255.255.255.

  * 00:09:19.865 Mar 1: % CDP_PD-4-POWER_OK: full power - supply NEGOTIATED online

  * 00:09:19.886 Mar 1: % LINK-3-UPDOWN: Interface Dot11Radio0, changed State to

  * 00:09:20.873 Mar 1: % LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed State to

  * 00:09:20.874 Mar 1: % SYS-6-LOGGINGHOST_STARTSTOP: logging to host started 255.255.255.255 - initiated CLI

  Translate "CISCO-CAPWAP - CONTROLLER.atheertele.com"... the domain server (172.16.40.240)

  * 00:09:29.029 Mar 1: % CAPWAP-5-DHCP_OPTION_43: the 172.16.100.102 drive address obtained by DHCP

  * 08:27:02.000 may 25: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.100.101 peer_port: 5246

  * 08:27:02.001 may 25: % CAPWAP-5-CHANGED: CAPWAP changed State to

  * 08:27:03.175 may 25: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.16.100.101 peer_port: 5246

  * 08:27:03.177 may 25: % CAPWAP-5-SENDJOIN: send request to join 172.16.100.101

  * 08:27:03.177 may 25: % CAPWAP-5-CHANGED: CAPWAP changed State to ADHERE

  * 08:27:03.329 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state CFG

  * 08:27:03.333 may 25: % DTLS-5-ALERT: WARNING received: close notify alert from 172.16.100.101

  * 25 May 08:27:03.333: % PEER_DISCONNECT-5-DTLS: Peer 172.16.100.101 has closed the connection.

  * 08:27:03.333 may 25: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.16.100.101:5246

  * 08:27:03.378 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

  * 08:27:03.378 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

  * 25 May 08:27:03.378: bsnInitRcbSlot: slot 1 has NO radio

  * 25 May 08:27:03.448: State of the voice_diag_test of WLC is false

  * 08:27:14.000 may 25: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.100.101 peer_port: 5246

  * 08:27:14.001 may 25: % CAPWAP-5-CHANGED: CAPWAP changed State to

  * 08:27:15.185 may 25: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.16.100.101 peer_port: 5246

  * 08:27:15.186 may 25: % CAPWAP-5-SENDJOIN: send request to join 172.16.100.101

  * 08:27:15.186 may 25: % CAPWAP-5-CHANGED: CAPWAP changed State to ADHERE

  * 08:27:15.330 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state CFG

  * 08:27:15.333 may 25: % DTLS-5-ALERT: WARNING received: close notify alert from 172.16.100.101

  * 25 May 08:27:15.334: % PEER_DISCONNECT-5-DTLS: Peer 172.16.100.101 has closed the connection.

  * 08:27:15.334 may 25: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.16.100.101:5246

  * 08:27:15.379 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

  * 08:27:15.379 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

  * 25 May 08:27:15.379: bsnInitRcbSlot: slot 1 has NO radio

  * 25 May 08:27:15.450: State of the voice_diag_test of WLC is false

  * 08:27:26.000 may 25: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.100.101 peer_port: 5246

  * 08:27:26.001 may 25: % CAPWAP-5-CHANGED: CAPWAP changed State to

  * 08:27:27.182 may 25: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.16.100.101 peer_port: 5246

  * 08:27:27.183 may 25: % CAPWAP-5-SENDJOIN: send request to join 172.16.100.101

  * 08:27:27.184 may 25: % CAPWAP-5-CHANGED: CAPWAP changed State to ADHERE

  * 08:27:27.329 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state CFG

  * 08:27:27.333 may 25: % DTLS-5-ALERT: WARNING received: close notify alert from 172.16.100.101

  * 25 May 08:27:27.333: % PEER_DISCONNECT-5-DTLS: Peer 172.16.100.101 has closed the connection.

  * 08:27:27.333 may 25: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.16.100.101:5246

  * 08:27:27.377 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

  * 08:27:27.377 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

  * 25 May 08:27:27.377: bsnInitRcbSlot: slot 1 has NO radio

  * 08:27:27.433 may 25: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively

  * 08:27:27.446 may 25: % PARSER-4-BADCFG: unexpected end of the configuration file.

  * 25 May 08:27:27.447: State of the voice_diag_test of WLC is false

  * 08:27:27.448 may 25: % LINK-3-UPDOWN: Interface Dot11Radio0, changed State to

  * 08:27:27.456 may 25: % LINK-5-CHANGED: Interface Dot11Radio0, changed State to reset

  * 08:27:38.000 may 25: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.100.101 peer_port: 5246

  * 08:27:38.001 may 25: % CAPWAP-5-CHANGED: CAPWAP changed State to

  * 08:27:39.183 may 25: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.16.100.101 peer_port: 5246

  * 08:27:39.184 may 25: % CAPWAP-5-SENDJOIN: send request to join 172.16.100.101

  * 08:27:39.184 may 25: % CAPWAP-5-CHANGED: CAPWAP changed State to ADHERE

  * 08:27:39.326 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state CFG

  * 08:27:39.329 may 25: % DTLS-5-ALERT: WARNING received: close notify alert from 172.16.100.101

  * 25 May 08:27:39.329: % PEER_DISCONNECT-5-DTLS: Peer 172.16.100.101 has closed the connection.

  * 08:27:39.330 may 25: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.16.100.101:5246

  * 08:27:39.375 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

  * 08:27:39.375 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

  * 25 May 08:27:39.375: bsnInitRcbSlot: slot 1 has NO radio

  * 25 May 08:27:39.446: State of the voice_diag_test of WLC is false

  * 08:27:49.000 may 25: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 172.16.100.101 peer_port: 5246

  * 08:27:49.001 may 25: % CAPWAP-5-CHANGED: CAPWAP changed State to

  * 08:27:50.179 may 25: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 172.16.100.101 peer_port: 5246

  * 08:27:50.180 may 25: % CAPWAP-5-SENDJOIN: send request to join 172.16.100.101

  * 08:27:50.180 may 25: % CAPWAP-5-CHANGED: CAPWAP changed State to ADHERE

  * 08:27:50.323 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state CFG

  * 08:27:50.326 may 25: % DTLS-5-ALERT: WARNING received: close notify alert from 172.16.100.101

  * 25 May 08:27:50.326: % PEER_DISCONNECT-5-DTLS: Peer 172.16.100.101 has closed the connection.

  * 08:27:50.326 may 25: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 172.16.100.101:5246

  * 08:27:50.370 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

  * 08:27:50.370 may 25: % CAPWAP-5-CHANGED: CAPWAP changed state of DISCOVERY

  * 25 May 08:27:50.370: bsnInitRcbSlot: slot 1 has NO radio

  * 08:27:50.425 may 25: % LINK-5-CHANGED: Interface Dot11Radio0, changed state down administratively

  * 08:27:50.438 may 25: % PARSER-4-BADCFG: unexpected end of the configuration file.

  I searched the difference in regulatory areas between AIR-LAP1041N -E- K9 and AIR-LAP1041N -A- K9 and no difference was found which may affect the operation of this access point.
  to cite our WLC configuration for regulatory areas is:
  Country set AR codes

   

  Area of regulation 802. 11A:-A

  802.11bg:-a

  My question is should I just include my country in the WLC (IQ) add the field of requlatry (-E) to solve this problem? or change the country will affect the operation of all APs workers?

  Appreciate your kind support,

  Patrick Q.

  Try adding a European country to your regulatory domain.

• ACS RADIUS timeout with WLC 7.0 5.0

  Hi guys,.

  I'm setting up a device Cisco Secure ACS 1120 running 5.0.0.21 ACS to manage the RADIUS of a Cisco WLC 5508 device query running the 7.0.116.0 version.

  • These devices have open communication on all ports - no firewall or ACL
  • they have successful ping communication

  The following statements illustrate some but not all debugging I did to make sure that each device works properly in isolation.

  • Using the simple windows (radserv2.exe) instead of the Cisco ACS RADIUS server
    • This works and the WLC gets answer my fortune Server RADIUS
  • Using a simple windows EAP client to query the ACS using the RADIUS protocol
    • This works and the FAC processes the RADIUS request and sends a response
  • Placed a customer wireshark on the network to inspect the time-out.
    • Wireshark saves the package to the WLC for GBA using port 1812 but does not see responses to GBA package

  At the moment I have the

  1. WLC accepting wireless client association and
  2. sending the query RADIUS (EAP - TLS, PEAP and EAP-FAST) for GBA,
  3. the WLC receives no answer and generates a timeout message and separates the client.
     1. Note this is not a rejection or a similar message, the simple ACS does not even the package. i.e. There is absolutely nothing in the logs of ACS to suggest that he had even received a package of radius of the WLC.

  In summary the WLC and GBA properly operate independently, but they do not communicate via radius.

  Any help appreciated thanks

  It seems that you use ACS 5.0 without tasks.

  For your information, the version of the product is now up to 5.2 and 5.3 ACS should soon be released

  I recall there was a problem with ACS 5.0 with WLC operations that has been resolved in patch for 5.0

  I'm not sure of the specific CDETS but can be:

  CSCsy17858 Any manipulation of Tunnel-Type & Tunnel-Client-Endpoint uploading incorrect

  ACS 5.0 has a rollup with all the patches being accumulated approach

  My recommendation would be to download the patch 8 for ACS 5.0: 5.0.0.21.8

  Patch can be downloaded from CEC

  To install a patch set a repository on ACS (cumulative patches are larger than 32 MB, you can not use TFTP to it), copy the patch file in the repository, click ACS CLI:

  # acs patch installs repository

• Cannot save with WLC 4402 LAP

  Hi all

  I have cisco WLC (AIR-WLC4402-12-K9) with two LAP (AIR-LAP1131AG-A-K9) connected to move and one of the TOUR is able to register with WLC while the other was autonomous AP which has been converted to KNEES who fails to register with WLC. I see that the AP is able to enter the Ip address and even joined the WLC but fails to register. Please help us solve this problem. I have attached all papers relevant to this case. Waiting for your answer.

  FYI I aimed below URL, but could not able to figureout the reason.

  http://www.Cisco.com/en/us/products/ps6366/products_tech_note09186a00808f8599.shtml

  I don't understand.  You have TWO 2 1131AG.  We joined for the last two days and another recently joined.  Say the other keeps "bouncing"?

  Have you checked if the WAP is declining because of the power?

• Cisco 2600 router as an IPSec client

  Hello

  Currently I use a Cisco VPN client software to connect to a remote server for IPSec on the workstations.

  I want to set up the IPSec client on Cisco 2600 router that connects to the remote server IPSec so that workstations can access subnet VPN without using VPN software.

  Can someone guide me on how to configure the IPSec client on the router?

  Thank you

  Hi Adam,.

  Sorry for my late reply, I'm a little sick.

  I have checked the logs and did small repro. For me, it seems that the server does not support NEM:

  It is disabled with NEM VPN server:

  Nov 30 00:13:56 [IKEv1 DEBUG]: Group = gsa3mle3, name of user = cisco, IP = 10.10.10.2, MODE_CFG: request received for the DHCP for DDNS hostname is: R1!

  Nov 30 00:13:56 [IKEv1]: Group = gsa3mle3 username = cisco, IP = 10.10.10.2, material Connection Client rejected!  Network Extension mode is not allowed for this group!

  The customer:

  * 1 Mar 00:45:56.387: ISAKMP: (1007): lot of 10.10.10.13 sending my_port 500 peer_port 500 (I) CONF_ADDR

  * 00:45:56.439 Mar 1: ISAKMP (0:1007): received 10.10.10.13 packet dport 500 sport Global 500 (I) CONF_ADDR

  * 1 Mar 00:45:56.439: DGVPN:crypt_iv after decrypt, its: 650BE464

  7BCF116E8E4DFF6C

  * 00:45:56.443 Mar 1:

  * 00:45:56.443 Mar 1: ISAKMP: content of the packet of information (flags, 1, len 92):

  * 00:45:56.447 Mar 1: HASH payload

  * 00:45:56.447 Mar 1: delete payload

  * 00:45:56.459 Mar 1: ISAKMP: content of the packet of information (flags, 1, len 80):

  * 00:45:56.459 Mar 1: HASH payload

  * 00:45:56.459 Mar 1: delete payload

  * 1 Mar 00:45:56.459: DGVPN: crypt_iv after encrypting, its: 650BE464

  Change it to client mode and try it.

  Kind regards

  Michal

• iOS 9.3 do bluetooth hands-free connection to my Audi stuttering. Using google maps with instructions of the Tower burn on bluetooth still works very well. It's an iPhone 6. Another 6s to 9.2 iOS iPhone works very well with the hands-free bluetooth.

  iOS 9.3 made connection kit hands free bluetooth to my Audi stuttering.

  Both the speaker and the stuttering/pulse microphone so that you cannot speak/hear.

  Using googlemap-app with instructions of the Tower burn via bluetooth still works very well, his is perfect.

  It's an iPhone 6s and the car is an Audi A6 2010 with the Moose Bluetooth adapter business.

  Another 6s to 9.2 iOS iPhone works fine with bluetooth hands-free, just like my phone before the upgrade.

  I tried to disable the twinning, remove all old in the car and the iPhone and pair Bluetooth devices again.

  Anyone alse experinceing this?

  And tip on how to fix it?

  I have the same problem with Audi Q7 2008 and iPhone-6s - iOS - 9.3.

• The CTS-CTRL-DVC8 is compatible with the Cisco MX200 G1 telepresence?

  Hi team,

  Please confirm whether CTS-CTRL-DVC8 = (Cisco TelePresence Touch device) is compatible with the Cisco MX200 G1 telepresence.

  Thank you very much.

  Sorry, misread the Gen1 in your message.  Yes, the 8 Touch works with old Gen 1 MX200 of TC software running.  This is mentioned on the MX200 data sheet.  Older hardware (MX Gen1 and C40/60/90) press the 8 only and cannot be upgraded to the new software for THIS.

• Problem with switch Cisco SG300

  Hi guys,.

  I have a problem with switch Cisco SG300-20. After the failure of the switch boots in a kind of mode. It requires

  MAC address and serial number to be entered manually for the device. I tried to find information on this mode, but without success.

  My question is: what is this mode and how to make the start switch in this mode?

  How can I turn on the switch in this mode on purpose if it happens again and I enter the wrong information by accident.

  Thank you

  Hi Aegx, this is a rare case where the switch basically forget his identity. Although the switch is recoverable, it is recommended the switch RMA.

  If you are certain that you have neither taken under warranty, all the information that is asked is on the bottom of the switch sticker. If the thumbnail is is not present you wouldn't able to do this is correct.

  In addition, if you make a typographical error, the switch will have undesirable failures that are permanent, such as the inability to update software.

• Trouble getting a Cisco 2600 series AP to stay connected to WLC 5508

  Hello

  I recently loaded the independent our old APs upgrade to LWAPs.  We have a WLC 5508 to our Virtual Co - Lo and I use Flexconnect to accommodate local switch and dhcp on our sites.  I have updated more than 50 APs and joined them to the controller.  These include only the 1130AG and 1240AG models.  However they work perfectly and stay connected to the controller.  I'm having is with a new batch of 2600 series APs stay connected to the controller.  I tried to do research in what may cause disconnect it but have yet to find a solution.  I use DNS to resolve queries for CAPWAP & LWAPP APs to the controller on our EXTENSIVE network.  Read other messages I thought that this is perhaps a problem with packages to drop but have had our provider that manages Sonicwalls at both ends of the WAN confirm for me that there is no packet loss.  Here are the logs that I collected through the puttty of the WLC & AP.  Any help would be greatly appreciated.

  AP, I do the test on:

  NAME: "AP2600', DESCR: 'Cisco Aironet 2600 Series (IEEE 802.11n) Access Point.

  PID: AIR-CAP2602I-A-K9, VID: V01, SN: FTX1740J8V1

  WLC in question:

  Name of the manufacturer... Cisco Systems Inc..

  Product name... Cisco controller

  Version of the product... 7.3.112.0

  Bootloader Version... 1.0.1

  Retrieving Image Version field... 6.0.182.0

  Firmware version... Console USB 1.3, 1.6 Env FPGA, 1.27

  Build Type....................................... DATA + WPS

  System name... wificontroller

  Location of the system... Corp

  Contact System... Net engineer

  ObjectID of system... 1.3.6.1.4.1.9.1.1069

  Redundancy mode... People with disabilities

  IP Address....................................... 10.250.32.8

  Last Reset....................................... Software reset

  Time system... 190 days 3 hours 34 minutes 24 seconds

  Location of the time zone of the system... (GMT - 5:00) Eastern (USA and Canada)

  The country is set... USA - United States

  Operating environment... Utilities (0 to 40 ° C)

  Limits the internal temperature alarm... 0 to 65 ° C

  -Other - or ITU (q)

  ... Internal temperature 38 C

  Outdoor temperature... + 20 C

  Fan Status....................................... Ok

  State of 802. 11 b network... Activated

  State of 802. 11A network... Activated

  Number of wireless LANs... 14

  Number of Active Clients... 71

  Built-in MAC address... C8:9 C: D: 8 1: 52:E0

  Power supply 1... Currently, OK

  Power supply 2... Absent

  Maximum number of taken access points supported... 100

  Here is the result which leaves on concluded that the AP joins the WLC for a short period and then goes offline

  WT-4thFlr-AP3 #.

  * 15:42:04.419 Dec 14: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (CAPWAP_WTP_EVENT_REQUEST

  ., 3)

  * 15:42:11.443 Dec 14: EVT-4-AVT %: write flash: / done event.capwap

  * 15:42:11.483 Dec 14: LWAPP-3-CLIENTERRORLOG %: switch to standalone mode

  * 15:42:11.487 Dec 14: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION

  * 15:42:11.487 Dec 14: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 10.250.32.8:5246

  * 15:42:11.571 Dec 14: % FEDS-6-persons with DISABILITIES: Signature of IDS is removed and disabled.

  * 15:42:21.575 Dec 14: % 3-CAPWAP-ERRORLOG: MWAR selected ' wificontroller'(index 0).

  * 15:42:21.575 Dec 14: % 3-CAPWAP-ERRORLOG: go join a capwap controller

  * 15:42:12.000 Dec 14: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.250.32.8 peer_port: 5246

  * 15:42:14.303 Dec 14: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 10.250.32.8 peer_port: 5246

  * 15:42:14.303 Dec 14: % CAPWAP-5-SENDJOIN: send request to join 10.250.32.8

  * 15:42:15.127 Dec 14: "Promiscuous" from Ethernet mode

  * 15:42:15.535 Dec 14: LWAPP-4-CLIENTEVENTLOG %: OfficeExtend Localssid recorded Flash AP

  * 15:42:15.667 Dec 14: ac_first_hop_mac - IP:10.1.2.250 Hop IP:10.1.2.250 IDB:BVI1

  * 15:42:15.667 Dec 14: AC setting hop first MAC: 0017.c575.a23c

  * 15:42:15.855 Dec 14: % CAPWAP-5-JOINEDCONTROLLER: AP joined controller wificontroller

  * 15:42:15.911 Dec 14: LWAPP-4-CLIENTEVENTLOG %: No. Flex ACL to load map configuration file. To connect to the controller to get the configuration file

  * 15:42:15.911 Dec 14: LWAPP-4-CLIENTEVENTLOG %: No. Flex ACL to load map configuration file. To connect to the controller to get the configuration file

  * 15:42:15.911 Dec 14: LWAPP-4-CLIENTEVENTLOG %: map No. LS Flex to load ACL configuration file. To connect to the controller to get the configuration file

  * 15:42:15.915 Dec 14: LWAPP-4-CLIENTEVENTLOG %: no central Dhcp configuration file map to load. To connect to the controller to get the configuration file

  * 15:42:15.915 Dec 14: % LWAPP-3-CLIENTERRORLOG: connected mode

  * 15:42:23.639 Dec 14: FEDS-6-ACTIVATED %: Signature of IDS is loaded and enabled

  * 15:42:34.615 Dec 14: CLEANAIR-6-State: Slot 0 disabled

  * 15:42:34.615 Dec 14: CLEANAIR-6-State: Slot 1 disabled

  * 15:45:43.783 Dec 14: % 3-CAPWAP-ERRORLOG: County of Retransmission for package exceeded max (CAPWAP_WTP_EVENT_REQUEST

  (. 11).

  * 15:45:43.787 Dec 14: LWAPP-3-CLIENTERRORLOG %: switch to standalone mode

  * 15:45:43.787 Dec 14: % 3-CAPWAP-ERRORLOG: dating BACK to the DISCOVERY of FASHION

  * 15:45:43.787 Dec 14: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 10.250.32.8:5246

  * 15:45:43.867 Dec 14: % FEDS-6-persons with DISABILITIES: Signature of IDS is removed and disabled.

  * 15:45:53.867 Dec 14: % 3-CAPWAP-ERRORLOG: MWAR selected ' wificontroller'(index 0).

  * 15:45:53.867 Dec 14: % 3-CAPWAP-ERRORLOG: go join a capwap controller

  * 15:45:44.000 Dec 14: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.250.32.8 peer_port: 5246

  * 15:45:46.315 Dec 14: % CAPWAP-5-DTLSREQSUCC: DTLS connection created successfully peer_ip: 10.250.32.8 peer_port: 5246

  * 15:45:46.315 Dec 14: % CAPWAP-5-SENDJOIN: send request to join 10.250.32.8

  * 15:45:46.487 Dec 14: "Promiscuous" from Ethernet mode

  * 15:45:49.903 Dec 14: LWAPP-4-CLIENTEVENTLOG %: OfficeExtend Localssid recorded Flash AP

  * 15:45:50.031 Dec 14: ac_first_hop_mac - IP:10.1.2.250 Hop IP:10.1.2.250 IDB:BVI1

  * 15:45:50.031 Dec 14: AC setting hop first MAC: 0017.c575.a23c

  Here are the results of the client debugging capwap event about to access:

  WT-4thFlr-AP3 #debug capwap customer event

  Display debugging EVENT customer CAPWAP is on

  WT-4thFlr-AP3 #.

  * 15:54:58.335 Dec 14: % 3-CAPWAP-EVENTLOG: Echo interval has expired.

  * 15:54:58.335 Dec 14: % 3-CAPWAP-EVENTLOG: sending package to AC

  * 15:54:58.335 Dec 14: % 3-CAPWAP-EVENTLOG: echo sent to 10.250.32.8 request

  * 15:54:58.343 Dec 14: % 3-CAPWAP-EVENTLOG: reset reTransmissionCnt to 0

  * 15:54:58.343 Dec 14: % 3-CAPWAP-EVENTLOG: queue empty.

  * 15:54:58.343 Dec 14: % 3-CAPWAP-EVENTLOG: echo response from 10.250.32.8

  * 15:55:08.000 Dec 14: % 3-CAPWAP-EVENTLOG: setting the time at 15:55:08 UTC 14 December 2013

  * 15:55:25.579 Dec 14: % 3-CAPWAP-EVENTLOG: sending package to AC

  * 15:55:25.587 Dec 14: % 3-CAPWAP-EVENTLOG: reset reTransmissionCnt to 0

  * 15:55:25.587 Dec 14: % 3-CAPWAP-EVENTLOG: queue empty.

  * 15:55:25.587 Dec 14: % CAPWAP-3-Journal of EVENTS: event Wtp 10.250.32.8 response

  * 15:55:25.827 Dec 14: % 3-CAPWAP-EVENTLOG: sending package to AC

  * 15:55:25.835 Dec 14: % 3-CAPWAP-EVENTLOG: reset reTransmissionCnt to 0

  * 15:55:25.835 Dec 14: % 3-CAPWAP-EVENTLOG: queue empty.

  * 15:55:25.835 Dec 14: % CAPWAP-3-Journal of EVENTS: event Wtp 10.250.32.8 response

  * 15:55:55.835 Dec 14: % 3-CAPWAP-EVENTLOG: Echo interval has expired.

  * 15:55:55.835 Dec 14: % 3-CAPWAP-EVENTLOG: sending package to AC

  * 15:55:55.835 Dec 14: % 3-CAPWAP-EVENTLOG: echo sent to 10.250.32.8 request

  * 15:55:55.843 Dec 14: % 3-CAPWAP-EVENTLOG: reset reTransmissionCnt to 0

  * 15:55:55.843 Dec 14: % 3-CAPWAP-EVENTLOG: queue empty.

  * 15:55:55.843 Dec 14: % 3-CAPWAP-EVENTLOG: echo response from 10.250.32.8

  * 15:55:56.000 Dec 14: % 3-CAPWAP-EVENTLOG: setting the time at 15:55:56 UTC 14 December 2013

  * 15:56:25.735 Dec 14: % 3-CAPWAP-EVENTLOG: sending package to AC

  * 15:56:25.743 Dec 14: % 3-CAPWAP-EVENTLOG: reset reTransmissionCnt to 0

  * 15:56:25.743 Dec 14: % 3-CAPWAP-EVENTLOG: queue empty.

  * 15:56:25.743 Dec 14: % CAPWAP-3-Journal of EVENTS: event Wtp 10.250.32.8 response

  * 15:56:25.983 Dec 14: % 3-CAPWAP-EVENTLOG: sending package to AC

  * 15:56:25.991 Dec 14: % 3-CAPWAP-EVENTLOG: reset reTransmissionCnt to 0

  * 15:56:25.991 Dec 14: % 3-CAPWAP-EVENTLOG: queue empty.

  * 15:56:25.991 Dec 14: % CAPWAP-3-Journal of EVENTS: event Wtp 10.250.32.8 response

  * 15:56:55.991 Dec 14: % 3-CAPWAP-EVENTLOG: Echo interval has expired.

  * 15:56:55.991 Dec 14: % 3-CAPWAP-EVENTLOG: sending package to AC

  * 15:56:55.991 Dec 14: % 3-CAPWAP-EVENTLOG: echo sent to 10.250.32.8 request

  * 15:56:55.999 Dec 14: % 3-CAPWAP-EVENTLOG: reset reTransmissionCnt to 0

  * 15:56:55.999 Dec 14: % 3-CAPWAP-EVENTLOG: queue empty.

  * 15:56:55.999 Dec 14: % 3-CAPWAP-EVENTLOG: echo response from 10.250.32.8

  * 15:56:56.000 Dec 14: % 3-CAPWAP-EVENTLOG: setting the time at 15:56:56 UTC 14 December 2013

  Here are the results of debug capwap client package in detail:

  WT-4thFlr-AP3 #.

  * 14 Dec 15:59:01.823: <   start="" of="" capwap="" packet ="">>

  * 15:59:01.823 Dec 14: control of CAPWAP mesg sent to 10.250.32.8, Port 5246

  * 15:59:01.823 Dec 14: Type Msg: CAPWAP_ECHO_REQUEST

  * 15:59:01.823 Dec 14: Msg length: 0

  * 15:59:01.823 Dec 14: Msg SeqNum: 44

  * 14 Dec 15:59:01.823: <  end="" of="" capwap="" packet ="">>

  * 14 Dec 15:59:01.831: <   start="" of="" capwap="" packet ="">>

  * 15:59:01.831 Dec 14: mesg 10.250.32.8 Recd, Port 5246 CAPWAP control

  * 15:59:01.831 Dec 14: HLEN 2, Radio ID 0, WBID 1

  * 15:59:01.831 Dec 14: Type Msg: CAPWAP_ECHO_RESPONSE

  * 15:59:01.831 Dec 14: Msg length: 15

  * 15:59:01.831 Dec 14: Msg SeqNum: 44

  * 15:59:01.831 Dec 14:

  * 15:59:01.831 Dec 14: Type: CAPWAP_MSGELE_VENDOR_SPECIFIC_PAYLOAD, length 11

  * 15:59:01.831 Dec 14: the vendor identifier: 0 x 00409600

  * 15:59:01.831 Dec 14:

  * 15:59:01.831 Dec 14:

  IE: UNKNOWN IT IS ABOUT 151

  * 15:59:01.831 Dec 14: IE length: 5

  * 15:59:01.831 Dec 14: decode the routine unavailable, Hex Dump printing

  * 15:59:01.831 Dec 14:

  52 80 46 00 AC

  * 14 Dec 15:59:01.831: <  end="" of="" capwap="" packet ="">>

  * 14 Dec 15:59:20.931: <   start="" of="" capwap="" packet ="">>

  * 15:59:20.931 Dec 14: mesg 10.250.32.8 Recd, Port 5246 CAPWAP control

  * 15:59:20.931 Dec 14: HLEN 2, Radio ID 0, WBID 1

  * 15:59:20.931 Dec 14: Type Msg: CAPWAP_CONFIGURATION_UPDATE_REQUEST

  * 15:59:20.931 Dec 14: Msg length: 93

  * 15:59:20.931 Dec 14: Msg SeqNum: 38

  * 15:59:20.931 Dec 14:

  * 15:59:20.931 Dec 14: Type: CAPWAP_MSGELE_VENDOR_SPECIFIC_PAYLOAD, length 89

  * 15:59:20.931 Dec 14: the vendor identifier: 0 x 00409600

  * 15:59:20.931 Dec 14:

  * 15:59:20.931 Dec 14:

  IE: RRM_NEIGHBOR_CTRL_PAYLOAD

  * 15:59:20.931 Dec 14: IE length: 83

  * 15:59:20.931 Dec 14: decode the routine unavailable, Hex Dump printing

  * 15:59:20.931 Dec 14:

  00 0 HAS FA 20 08 01 00 07 0A 20 08 03 00 01 FA F4

  01 00 00 3 B4 2ND 2ND 06 94 51 79 25 C7 B2 B4 E7

  22 FD BE F6 04 00 00 00 00 00 00 00 00 50 52 4F

  53 2D 57 69 46 69 00 00 00 00 00 00 00 00 00 00

  00 00 00 00 00 00 00 00 00 00 00 00 00 01 06 0B

  01 01 01

  * 14 Dec 15:59:20.931: <  end="" of="" capwap="" packet ="">>

  * 14 Dec 15:59:20.931: <   start="" of="" capwap="" packet ="">>

  * 15:59:20.931 Dec 14: control of CAPWAP mesg sent to 10.250.32.8, Port 5246

  * 15:59:20.931 Dec 14: Type Msg: CAPWAP_CONFIGURATION_UPDATE_RESPONSE

  * 15:59:20.931 Dec 14: Msg length: 8

  * 15:59:20.931 Dec 14: Msg SeqNum: 38

  * 15:59:20.931 Dec 14:

  * 15:59:20.931 Dec 14: Type: CAPWAP_MSGELE_RESULT_CODE, length 4

  * 15:59:20.931 Dec 14: result of Code: CAPWAP_SUCCESS

  * 14 Dec 15:59:20.931: <  end="" of="" capwap="" packet ="">>

  * 14 Dec 15:59:21.139: <   start="" of="" capwap="" packet ="">>

  * 15:59:21.139 Dec 14: mesg 10.250.32.8 Recd, Port 5246 CAPWAP control

  * 15:59:21.139 Dec 14: HLEN 2, Radio ID 0, WBID 1

  * 15:59:21.139 Dec 14: Type Msg: CAPWAP_CONFIGURATION_UPDATE_REQUEST

  * 15:59:21.139 Dec 14: Msg length: 111

  * 15:59:21.139 Dec 14: Msg SeqNum: 39

  * 15:59:21.139 Dec 14:

  * 15:59:21.139 Dec 14: Type: CAPWAP_MSGELE_VENDOR_SPECIFIC_PAYLOAD, length 107

  * 15:59:21.139 Dec 14: the vendor identifier: 0 x 00409600

  * 15:59:21.139 Dec 14:

  * 15:59:21.139 Dec 14:

  IE: RRM_NEIGHBOR_CTRL_PAYLOAD

  * 15:59:21.139 Dec 14: IE length: 101

  * 15:59:21.139 Dec 14: decode the routine unavailable, Hex Dump printing

  * 15:59:21.143 Dec 14:

  01 0 TO FA 20 08 01 F4 00 07 0A 20 08 00 01 0C FA

  01 00 00 3 B4 2ND 2ND 06 94 51 79 25 C7 B2 B4 E7

  22 FD BE F6 04 00 00 00 00 00 00 00 00 50 52 4F

  53 2D 57 69 46 69 00 00 00 00 00 00 00 00 00 00

  00 00 00 00 00 00 00 00 00 00 00 00 00 24 28 2

  30 34 38 3 40 95 99 9 01 01 01 01 01 01 01 A1

  01 01 01 01 01

  * 14 Dec 15:59:21.143: <  end="" of="" capwap="" packet ="">>

  * 14 Dec 15:59:21.143: <   start="" of="" capwap="" packet ="">>

  * 15:59:21.143 Dec 14: control of CAPWAP mesg sent to 10.250.32.8, Port 5246

  * 15:59:21.143 Dec 14: Type Msg: CAPWAP_CONFIGURATION_UPDATE_RESPONSE

  * 15:59:21.143 Dec 14: Msg length: 8

  * 15:59:21.143 Dec 14: Msg SeqNum: 39

  * 15:59:21.143 Dec 14:

  * 15:59:21.143 Dec 14: Type: CAPWAP_MSGELE_RESULT_CODE, length 4

  * 15:59:21.143 Dec 14: result of Code: CAPWAP_SUCCESS

  * 14 Dec 15:59:21.143: <  end="" of="" capwap="" packet ="">>

  * 14 Dec 15:59:25.547: <   start="" of="" capwap="" packet ="">>

  * 15:59:25.547 Dec 14: control of CAPWAP mesg sent to 10.250.32.8, Port 5246

  * 15:59:25.547 Dec 14: Type Msg: CAPWAP_WTP_EVENT_REQUEST

  * 15:59:25.547 Dec 14: Msg length: 14

  * 15:59:25.547 Dec 14: Msg SeqNum: 45

  * 15:59:25.547 Dec 14:

  * 15:59:25.547 Dec 14: Type: CAPWAP_MSGELE_VENDOR_SPECIFIC_PAYLOAD, length 10

  * 15:59:25.547 Dec 14: the vendor identifier: 0 x 00409600

  * 15:59:25.547 Dec 14:

  * 15:59:25.547 Dec 14:

  IE: RRM_LOAD_DATA_PAYLOAD

  * 15:59:25.547 Dec 14: IE length: 4

  * 14 Dec 15:59:25.547: slot ccaLoad 0 rxLoad 0 txLoad 0 33

  * 14 Dec 15:59:25.547: <  end="" of="" capwap="" packet ="">>

  * 14 Dec 15:59:25.555: <   start="" of="" capwap="" packet ="">>

  * 15:59:25.555 Dec 14: mesg 10.250.32.8 Recd, Port 5246 CAPWAP control

  * 15:59:25.555 Dec 14: HLEN 2, Radio ID 0, WBID 1

  * 15:59:25.555 Dec 14: Type Msg: CAPWAP_WTP_EVENT_RESPONSE

  * 15:59:25.555 Dec 14: Msg length: 0

  * 15:59:25.555 Dec 14: Msg SeqNum: 45

  * 14 Dec 15:59:25.555: <  end="" of="" capwap="" packet ="">>

  * 14 Dec 15:59:25.795: <   start="" of="" capwap="" packet ="">>

  * 15:59:25.795 Dec 14: control of CAPWAP mesg sent to 10.250.32.8, Port 5246

  * 15:59:25.795 Dec 14: Type Msg: CAPWAP_WTP_EVENT_REQUEST

  * 15:59:25.795 Dec 14: Msg length: 14

  * 15:59:25.795 Dec 14: Msg SeqNum: 46

  * 15:59:25.795 Dec 14:

  * 15:59:25.795 Dec 14: Type: CAPWAP_MSGELE_VENDOR_SPECIFIC_PAYLOAD, length 10

  * 15:59:25.795 Dec 14: the vendor identifier: 0 x 00409600

  * 15:59:25.795 Dec 14:

  * 15:59:25.795 Dec 14:

  IE: RRM_LOAD_DATA_PAYLOAD

  * 15:59:25.795 Dec 14: IE length: 4

  * 14 Dec 15:59:25.795: slot ccaLoad 1 rxLoad 0 txLoad 0 0

  * 14 Dec 15:59:25.795: <  end="" of="" capwap="" packet ="">>

  * 14 Dec 15:59:25.803: <   start="" of="" capwap="" packet ="">>

  * 15:59:25.803 Dec 14: mesg 10.250.32.8 Recd, Port 5246 CAPWAP control

  * 15:59:25.803 Dec 14: HLEN 2, Radio ID 0, WBID 1

  * 15:59:25.803 Dec 14: Type Msg: CAPWAP_WTP_EVENT_RESPONSE

  * 15:59:25.803 Dec 14: Msg length: 0

  * 15:59:25.803 Dec 14: Msg SeqNum: 46

  * 14 Dec 15:59:25.803: <  end="" of="" capwap="" packet ="">>

  * 14 Dec 15:59:30.375: <   start="" of="" capwap="" packet ="">>

  * 15:59:30.375 Dec 14: mesg 10.250.32.8 Recd, Port 5246 CAPWAP control

  * 15:59:30.375 Dec 14: HLEN 2, Radio ID 0, WBID 1

  * 15:59:30.375 Dec 14: Type Msg: CAPWAP_CONFIGURATION_UPDATE_REQUEST

  * 15:59:30.375 Dec 14: Msg length: 17

  * 15:59:30.375 Dec 14: Msg SeqNum: 40

  * 15:59:30.375 Dec 14:

  * 15:59:30.375 Dec 14: Type: CAPWAP_MSGELE_VENDOR_SPECIFIC_PAYLOAD, length 13

  * 15:59:30.375 Dec 14: the vendor identifier: 0 x 00409600

  SlotId: 0

  Mobile Mac Addr: BC:52:B7:E3:17:CB

  * 14 Dec 15:59:30.375: <  end="" of="" capwap="" packet ="">>

  * 14 Dec 15:59:30.375: <   start="" of="" capwap="" packet ="">>

  * 15:59:30.375 Dec 14: control of CAPWAP mesg sent to 10.250.32.8, Port 5246

  * 15:59:30.375 Dec 14: Type Msg: CAPWAP_CONFIGURATION_UPDATE_RESPONSE

  * 15:59:30.379 Dec 14: Msg length: 8

  * 15:59:30.379 Dec 14: Msg SeqNum: 40

  * 15:59:30.379 Dec 14:

  * 15:59:30.379 Dec 14: Type: CAPWAP_MSGELE_RESULT_CODE, length 4

  * 15:59:30.379 Dec 14: result of Code: CAPWAP_SUCCESS

  * 14 Dec 15:59:30.379: <  end="" of="" capwap="" packet ="">>

  * 14 Dec 15:59:30.387: <   start="" of="" capwap="" packet ="">>

  * 15:59:30.387 Dec 14: mesg 10.250.32.8 Recd, Port 5246 CAPWAP control

  * 15:59:30.387 Dec 14: HLEN 2, Radio ID 0, WBID 1

  * 15:59:30.387 Dec 14: Type Msg: CAPWAP_WTP_EVENT_RESPONSE

  * 15:59:30.387 Dec 14: Msg length: 0

  * 15:59:30.387 Dec 14: Msg SeqNum: 47

  * 14 Dec 15:59:30.387: <  end="" of="" capwap="" packet ="">>

  * 14 Dec 16:00:00.387: <   start="" of="" capwap="" packet ="">>

  * 16:00:00.387 Dec 14: control of CAPWAP mesg sent to 10.250.32.8, Port 5246

  * 16:00:00.387 Dec 14: Type Msg: CAPWAP_ECHO_REQUEST

  * 16:00:00.387 Dec 14: Msg length: 0

  * 16:00:00.387 Dec 14: Msg SeqNum: 48

  * 14 Dec 16:00:00.387: <  end="" of="" capwap="" packet ="">>

  * 14 Dec 16:00:00.395: <   start="" of="" capwap="" packet ="">>

  * 16:00:00.395 Dec 14: mesg 10.250.32.8 Recd, Port 5246 CAPWAP control

  * 16:00:00.395 Dec 14: HLEN 2, Radio ID 0, WBID 1

  * 16:00:00.395 Dec 14: Type Msg: CAPWAP_ECHO_RESPONSE

  * 16:00:00.395 Dec 14: Msg length: 15

  * 16:00:00.395 Dec 14: Msg SeqNum: 48

  * 16:00:00.395 Dec 14:

  * 16:00:00.395 Dec 14: Type: CAPWAP_MSGELE_VENDOR_SPECIFIC_PAYLOAD, length 11

  * 16:00:00.395 Dec 14: the vendor identifier: 0 x 00409600

  * 16:00:00.395 Dec 14:

  * 16:00:00.395 Dec 14:

  IE: UNKNOWN IT IS ABOUT 151

  * 16:00:00.395 Dec 14: IE length: 5

  * 16:00:00.395 Dec 14: decode the routine unavailable, Hex Dump printing

  * 16:00:00.395 Dec 14:

  52 80 81 00 AC

  * 14 Dec 16:00:00.395: <  end="" of="" capwap="" packet ="">>

  Try reducing the mtu on ap 2600.

• Used light aPs with WLC

  After reading the Cisco documentation, it seems that the light AP are reduced ceiling/wall decorations when the WLC is off the network or otherwise inaccessible.  Is this true?  They they plan no client connectivity if the WLC fails?  All customer traffic moving a tower to the WLC before being sent to its destination?  It is in particular with respect to APs and a WLC 5508 1142n.

  Thank you!

  Hi fdouble08,

  This would be correct. In case of death of the WLC LWAPP access your points lose connectivity as well and becomes ArtCisco. It has mode calle HREAP that allows local switching if the controller fails, but it is used mainly for remote offices. You can learn more about HREAP here...

  http://www.Cisco.com/en/us/docs/wireless/controller/6.0/Configuration/Guide/c60hreap.html

  Originating traffic to ap LWAPP is sent to the controller for the correct distribution of LAN.

  GEO

• Controller of domain and DNS behind RRAS without VPN connected directly to the internet with a Cisco router

  I hava a ME Cisco 3400 with physical single port available for a cable connection.

  The ISP give me an IP address interface = 89.120.29.89 to act as a gateway to the IP Address of the host, which is provided for in the order 89.120.29.90.

  The host computer is a dual Xeon computer with two NICs for LAN and WAN.

  Fields of application: to install a windows 2008 R2 between public and private network server.

  Even though I know it's not recomanded, I put the DNS role and directories Active Directory roles installed on the same computer, the computer above, (I do not have enough computer for roles different place on different computers)

  The desired configuration:

  To have installed with his roles behind a WS2008R2 has RRAS. without a VPN.

  b with VPN

  and for WAN access for the client computers of the private LAN Windows 7 OS. (The basin of LAN address 192.168.0.1 - 255).

  First step : to have internet access in the browser (I use Google chrome) (without taking into account the DNS and AD)

  Network configuration:

  Map NETWORK WAN, at the top of the stack of liaison in the Control Panel/network connections and sharing:

  Host IP: 89.120.29.90

  Mask: 255.255.255.252

  Gateway: 89.120.29.89

  DNS: 193.231.100.130 my ISP name server address.

  OK, I can browse the internet.

  Second stage. (Consider DNS and Active Directories)

  DNS instaled role for this computer.

  AD installed as a global catalog.

  NETWORK WAN server that is directly connected to the Cisco router:

  Conection area 3

  Properties:

  Client for Microsoft Netwaork: not verified

  Network Load Balancing: not verified

  File and shared printer: not verified

  QoSPacketScheduler: not verified;

  Microsoft Network Monitor 3 pilot: not verified

  IPv4                                                     ;  checked

  Pilot a Link Layer Topology Mapper i/o: checked

  Link layer Discover responder: checked

  IPv4 tab

  Host IP: 89.120.29.90

  Mask: 255.255.255.252

  Gateway: 89.120.29.89

  DNS: 193.231.100.130 my ISP name server address.

  under the tab advanced

  IP settings : even that, tab IPV4 with automatic metric check;

  DNS tab :

  Add primary and connection suffixes DNS specific: not verified

  Add suffixes primary DNS suffixes parents: not verified

  Add this DNS suffixes: no

  Registry deals with this connection in DNS: not verified;

  Use this connection DNS suffix in DNS registration: not verified;

  WINS tab : enable search LMHOST: not verified

  Enable NetBios over TCP IP: don't check;

  Disable NetBios on TCP IP: checked;

  Connection to the local network 2

  Properties :

  Client for Microsoft Netwaork: checked

  Network Load Balancing: no

  File and shared printer: checked

  QoS Packet Scheduler: not verified;

  Microsoft Network Monitor 3 pilot: not verified

  IPv4 checked

  Pilot a Link Layer Topology Mapper i/o: checked

  Link layer Discover responder: checked

  IPv4 tab

  NETWORK LAN CARD: 192.168.0.101

  Mask: 255.255.255.0

  Gateway: 192.168.0.1

  under Advanced tab:

  IP settings : even that, tab IPV4 with automatic metric check;

  DNS tab :

  Add primary and connection suffixes DNS specific: checked

  Add suffixes primary DNS suffixes parents: not verified

  Add this DNS suffixes: no

  Registry deals with this connection in DNS: checked;

  Use this connection DNS suffix in DNS registration: checked;

  WINS tab : enable search LMHOST: not verified

  Enable NetBios over TCP IP: check;

  Disable NetBios on TCP IP: not verified;

  Install RRAS as NAT (NAT) under any condition imposed by DHCP(not installed) in ideea that RRAS will generate the private IP address of the DHCP allocator.

  In any case, for the beginning, I have a fix IP, do not get IP automatically.

  At this point, it gets the configuration simple posible for RRAS follows:

  3, LAN connection that corespond to the WAN interface IP:

  "NAT configured for the following Internet interface: Local Area Connection 3.
  The clients on the local network will assign the IP addresses of the following range:

  network address: 192.168.0.0. netmask 255.255.0.0.

  After Windows RRAS are open:

  The Network Interfaces tab:

  NICs are enabled and connected;

  UAL remotely & policies:

  Launch NPS,

  on the NPS server tab:

  Allow access to successful Active Directory directories:

  Properties: authentication: port 1812,1645

  kept port 1813,1646;

  on the accounting tab: nothing;

  under NPS policies:

  Grant permission for the RRAS server under builin\Administrator of the accounts;

  On strategy and the type of server unspecified (NAT do not exist as an entry in the drop-down list server dwn)

  under the static road: nothing;

  under the IPv4 tab or both are there(there IP) and are up

  under NAT

  Connection to the local network 3: public interface connected to the internet

  enable NAT on this interface:

  under the address pool: ISP addresses public;(two addresses)

  under the terms of service and the ports: Web server: http 80.

  (I have I have a static IP address for the client computer in mind, I set up a single customer).

  At the client computer :

  configured as domain customer and added to the users AD and computer AD

  logon to the domain:

  Local Area Connection

  Properties:

  Client for Microsoft Netwaork: checked

  Network Load Balancing: not verified

  File sharing and printer: checked

  QoS Packet Scheduler: checked;

  Microsoft Network Monitor 3 pilot: not verified

  IPv4                                                     ;  checked

  Pilot a Link Layer Topology Mapper i/o: checked

  Link layer Discover responder: checked

  IPv4 tab

  Host IP: 192.168.0.101

  Mask: 255.255.0.0

  Gateway: 192.168.0.1

  DNS: (auto-add the same to the local machine).

  under the tab advanced

  IP settings : even that, tab IPV4 with automatic metric check;

  DNS tab :

  Add primary and connection suffixes DNS specific: checked

  Add suffixes primary DNS suffixes parents: not verified

  Add this DNS suffixes: no

  Registry deals with this connection in DNS: checked;

  Use this connection DNS suffix in DNS registration: checked;

  WINS tab : enable search LMHOST: not verified

  Enable NetBios over TCP IP: checked;

  Disable NetBios on TCP IP: not verified;

  right now the 192.168.0.101 client cannot connect to internet through RRAS.

  ;

  This issue is beyond the scope of this site and must be placed on Technet or MSDN

  http://social.technet.Microsoft.com/forums/en-us/home

  http://social.msdn.Microsoft.com/forums/en-us/home

• WLC CISCO - VMWare and additional network ports

  Hello world

  Hardware wise, I managed a 8540 and a CISCO 5508 wireless lan controllers, so know around the GUI.

  With the release of the VMWare Cisco WLC, it is ideal for a development and test lab environment. However anyone who has used will know it out of the box it does support 2 network cards (one for service and the other for management / data).

  The question:

  How to add additional network ports? In VMWare, it's easy, but how do you get the CISCO config to recognize? I have searched the forums and other areas, but can't seem to find someone who did this.

  See you soon

  Christian

  Hello

  Yes you are right, you can use only 2 network cards on VmWLC. never tried adding other network cards.

  But what you want to do? Is to add a virtual interface on your WLC?

  If so, you can configure your VmWare interface as a trunk and then create all your WLC virtual interface by defining the id vlan. Which makes sense for you?

  Thank you

  PS: Please don't forget to rate and score as correct answer if this answered your question.

• Problem with the Cisco ASA 5525 X SFR and Firesight high school

  Hi team,

  We have two ASA 5525 X installed on them and Firesight in a Linux VM whose two SFRs are registered with SFR failover mode. We use the SAA secondary off the hook if the primary fails to turn on the secondary manually switch the wan cable. I turn on the ASA secondary every weekend to take the configuration of the primary for the ASA and the SFR and close by button walk / stop.

  Last week I turn on high school ASA and the Firesight couldn't see the secondary SFR and show the message below:

  Module device heartbeat: device > don't send heartbeats.

  (I should mention I can Pinger the IP ADDRESS)

  I tried to study the problem without success.

  I also deleted the sensor just Firesight devices management in case something is stuck, and I'm trying to re added without success.

  I'm new in firepower so... any ideas?

  Thank you

  Finally, this problem has been resolved by the redefinition of firepower:

  see detailed here procedure to perform this redefinition;

  http://www.Cisco.com/c/en/us/support/docs/security/ASA-firepower-service...

  Before that, it appeared that firepower was not very healthy:

  After a success "" configure Manager add xxxxx"command.

  the command of managers show show nothing;

  He should have shown this result:

  > Display managers
  Host: 193.193.2.75
  Registration key: AZERTY
  Inscription: pending
  State of the PRC:

  on the other hand, in expert mode, the following command shows several processes (and not in the normal state):

  sudo pmtool status | grep-i down

  Last point,

  After the recreation and reconfigure all this fire power, installed in the ASA secondary standby, was considered to be OK under Firesight health Monitor,.

  but after 10mins, it appeared in critical condition with the following message:

  "Interface"DataPlaneInterface0"receives not all packages.

  This is normal and due to the fact that Eve ASA receives no flow and the same goes for firepower inside this ASA;

  by performing a failover from the primary to the secondary ASA, this critical message disappeared for firepower inside the ASA Sec and appeared for firepower inside the ASA elementary school

• Question of access with WLC 2106

  Hi, I have a WLC 2106 and APs 2 1250 connected to it. the controller works really well. all APs are associated.

  The problem I have is that, after only a few days I can't connect to the GUI or console.

  I can still ping and trace the controller.

  After I have turn off the controller and turn on again, it works again.

  Show the internal temperature 56 C would this cause the problem?

  Hi, there is a known issue with version 5.0 of WLC and the GUI timeout. Cash, http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Wireless%20-%20Mobility&topic=General&topicID=.ee6e8b8&fromOutline=&CommCmd=MB%3Fcmd%3Ddisplay_location%26location%3D.2cc15418

• Problem with WLC and a 3rd-party NMS SNMP AP Assoc/cancellation interruption

  Hello

  I'm troubleshooting an issue, why our NMS is not able to automatically clear an alarm generated trap of an AP that has been separated and is associated with again.

  When debugging on the WLC snmp trap generation, I discovered that when the AP disassociates the WLC sends the trap of bsnAPDisassociated , which is perfectly defined and I can also find in the SNMP Object Navigator. However when the AP reassociates again the WLC sends the ciscoLwappApAssociatedtrap.

  Part 3 NMS is not able to understand it, but our WCS system does, that's why I then took a peek in the MIB file installed.

  I discovered that ciscoLwappApAssociated is a sheet of ciscoLwappApMIBNotifs (1.3.6.1.4.1.9.9.513.0. 4), which I have neither

  Cannot be found in the Cisco SNMP Object Navigator or the downloadable MIB.

  As the MIB in the WCS is a XML file I didn't how to get information in the 3rd-party NMS.

  Anyone have any idea on how to solve this problem or there at - it update CISCO-LWAPP-AP-MIB available somewhere?

  Our WLCs are running the latest version of the software (7.0.116.0) as well as our WCS (7.0.172.0)

  Thanks in advance!

  Kind regards

  Patrick

  Such discrepancies sometimes occur. Best is a matter of TAC in order to tackle the problem through a bug or have a new MIB published on cisco.com if necessary