5508 controller

Similar Questions

• 2602AP will not register with the 5508 controller

  Hello all-

  We have a 5508 controller that manages the HA to about 20 branches - each branch has its own subnet. We have a single branch (subnet) with new 2602 AP who will not register with the controller. All communications to that subnet appear normal and there is no ACL in place between the AP and the controller. The AP is able to resolve the IP address of the controller via DNS and start the registration process, but then timeout. We have installed 2602 AP successfully to other areas of the branch and they fit without any problems - it is a problem only in one branch. I have attached a few debug messages below for a single point of access (it's a production environment, so I analyzed useless info) and also included messages from the console to a different access point (the console AP messages are the same). There are currently 9 AP here and none of them will record this. Any ideas?

  Capwap debug events:

  * spamApTask0: 11 Dec 14:39:32.904: 44:2 b: 03:9 has: Discovery d1:10 request 10.29.9.190:44306

  * spamApTask0: 11 Dec 14:39:32.904: 44:2 b: 03:9 has: d1:10 join priority Processing status = 0, priority 1 of incoming Ap, MaxLrads = 300, joined Aps = 272

  * spamApTask0: 11 Dec 14:39:32.904: 44:2 b: 03:9's: Discovery d1:10 response to 10.29.9.190:44306

  * spamApTask0: 11 Dec 14:39:32.904: 44:2 b: 03:9's: Discovery d1:10 response to 10.29.9.190:44306

  * spamApTask0: 11 Dec 14:39:32.992: 44:2 b: 03:9 has: d1:10 DISCOVERY LWAPP APPLICATION received at 68:ef:bd:8e:48:6f on port "13"

  * spamApTask0: 14:39:32.992 Dec 11: Discovery 44:2 b request: 03:9 has: d1:10 elements in LWAPP of AP supporting CAPWAP

  * spamApTask0: 14:39:42.903 Dec 11: connection of DTLS 44:2 b: 03:9 has: d1:10 not found, creating new connection for 10:29:9:190 (44306) 10:5:13:4 (5246)

  * spamApTask0: 14:57:52.301 Dec 11: DTLS closed connection events receivedserver e8:ba:70:dc:d1:c0 (10:5:13:4 / 5246) client (10:29:9:190 / 44306)

  * spamApTask0: 11 Dec 14:57:52.301: e8:ba:70:dc:d1:c0 no entry there for AP (10:29:9:190 / 44306)

  * spamApTask0: 11 Dec 14:57:52.301: e8:ba:70:dc:d1:c0 entry no. AP exist in the temporary database for 10.29.9.190:44306

  * spamApTask0: 11 Dec 14:57:53.828: 44:2 b: 03:9 has: Discovery d1:10 request 10.29.9.190:44306

  * spamApTask0: 11 Dec 14:57:53.828: 44:2 b: 03:9 has: d1:10 join priority Processing status = 0, priority 1 of incoming Ap, MaxLrads = 300, joined Aps = 272

  * spamApTask0: 11 Dec 14:57:53.828: 44:2 b: 03:9's: Discovery d1:10 response to 10.29.9.190:44306

  * spamApTask0: 11 Dec 14:57:53.828: 44:2 b: 03:9's: Discovery d1:10 response to 10.29.9.190:44306

  * spamApTask0: 11 Dec 14:57:53.916: 44:2 b: 03:9 has: d1:10 DISCOVERY LWAPP APPLICATION received at 68:ef:bd:8e:48:6f on port "13"

  * spamApTask0: 14:57:53.916 Dec 11: Discovery 44:2 b request: 03:9 has: d1:10 elements in LWAPP of AP supporting CAPWAP

  * spamApTask0: 14:58:03.824 Dec 11: connection of DTLS 44:2 b: 03:9 has: d1:10 not found, creating new connection for 10:29:9:190 (44306) 10:5:13:4 (5246)

  Debug Capwap errors:

  * spamApTask0: 11 Dec 15:17:33.715: e8:ba:70:dc:d1:c0 abolition PT 10.29.9.190 which has not been surveyed

  * spamApTask0: 11 Dec 15:17:33.716: e8:ba:70:dc:d1:c0 DTLS connection has been closed

  Debug Capwap Details:

  * spamApTask0: 11 Dec 15:24:29.419: 44:2 b: 03:9 has: d1:10 CAPWAP control received Msg to 10.29.9.190:44306

  * spamApTask0: 11 Dec 15:24:35.542: 44:2 b: 03:9 has: d1:10 CAPWAP control received Msg to 10.29.9.190:44306

  * spamApTask0: 11 Dec 15:24:41.555: 44:2 b: 03:9 has: d1:10 CAPWAP control received Msg to 10.29.9.190:44306

  * spamApTask0: 11 Dec 15:24:49.555: 44:2 b: 03:9 has: d1:10 CAPWAP control received Msg to 10.29.9.190:44306

  * spamApTask0: 11 Dec 15:25:29.420: 44:2 b: 03:9 has: d1:10 CAPWAP control received Msg to 10.29.9.190:44306

  * spamApTask0: 15:25:29.420 Dec 11: connection of DTLS 44:2 b: 03:9's: d1:10 0x1a1703c8 closed by controller

  * spamApTask0: 15:25:29.421 Dec 11: msg closed connection CAPWAP DTLS

  Journal of the Console from the AP:

  Translate "CISCO-CAPWAP - CONTROLLER.ad.pps.k12.va.us"... the domain server (10.29.8.3)

  * 00:00:57.511 Mar 1: % 3-CAPWAP-ERRORLOG: did not get the server DHCP server log settings. [OK]

  * 00:01:10.511 Mar 1: % 3-CAPWAP-ERRORLOG: go join a capwap controller

  * 16:05:56.000 11 dec: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.5.13.4 peer_port: 5246

  * 16:06:17.495 11 dec: % CDP_PD-2-POWER_LOW: all disabled radios - NEGOTIATED WS-C3560E-24PD (68bc.0c03.8015)

  * 11 Dec 16:06:28.231: DTLS_CLIENT_ERROR:... /CAPWAP/base_capwap/DTLS/base_capwap_dtls_connection_db.c:2051 retransmission count Max reached!

  Kern of logging mechanism

  ^

  Invalid entry % detected at ' ^' marker.

  emergency logging trap

  ^

  Invalid entry % detected at ' ^' marker.

  Kern of logging mechanism

  ^

  Invalid entry % detected at ' ^' marker.

  emergency logging trap

  ^

  Invalid entry % detected at ' ^' marker.

  * 16:06:55.999 11 dec: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 10.5.13.4:5246

  * 16:06:55.999 3 dec: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255

  * 16:07:06.367 11 dec: % 3-CAPWAP-ERRORLOG: go join a capwap controller

  * 16:07:07.000 11 dec: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.5.13.4 peer_port: 5246

  * 11 Dec 16:07:39.151: DTLS_CLIENT_ERROR:... /CAPWAP/base_capwap/DTLS/base_capwap_dtls_connection_db.c:2051 retransmission count Max reached!

  Kern of logging mechanism

  ^

  Invalid entry % detected at ' ^' marker.

  emergency logging trap

  ^

  Invalid entry % detected at ' ^' marker.

  Kern of logging mechanism

  ^

  Invalid entry % detected at ' ^' marker.

  emergency logging trap

  ^

  Invalid entry % detected at ' ^' marker.

  * 16:08:06.999 11 dec: % DTLS-5-SEND_ALERT: send FATAL: close notify alert at 10.5.13.4:5246

  * 16:08:06.999 11 dec: % CLIENTERRORLOG-3-LWAPP: LWAPP LED Init: incorrect led State 255

  * 16:08:17.367 11 dec: % 3-CAPWAP-ERRORLOG: go join a capwap controller

  * 16:08:17.000 11 dec: % CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.5.13.4 peer_port: 5246

  *Dec 17 15:53:47.463: %CAPWAP-3-ERRORLOG: Selected MWAR 'IRC-WLC-5508'(index 0).
  *Dec 17 15:53:47.463: %CAPWAP-3-ERRORLOG: Go join a capwap controller
  *Dec 17 15:53:47.000: %CAPWAP-5-DTLSREQSEND: DTLS connection request sent peer_ip: 10.5.13.4 peer_port: 5246
  *Dec 17 15:54:23.131: DTLS_CLIENT_ERROR: ../capwap/base_capwap/dtls/base_capwap_dtls_connection_db.c:2051 Max retransmission count reached!
  

  Get much better.

  WAP has selected the 5508 with good firmware.  WAP sends a JOIN request to 10.5.13.4 but cannot recover anything.

  Firewall?  Routing loop?

  What so-called "remote site", how is it connected to your office?  Dark fiber?  INTERNET SERVICE PROVIDER?

  You know what?  Can you post the output in the following commands:

  1 WAP: sh of stocks;

  2 WLC: sh sysinfo

  Nuts, I should already posed for these info before.

• migration of APs to the 5508 controller 4402

  Hello all,.

  We have two controllers (4402 and 5508) to one of the site.

  Customers of services at present.

  Both controllers have the same set of SSID but uses only a single group of AP.

  What would be the best means to move APs on 4402 to 5508?

  4402 services series years 1230 and 1240 AP. And looking at the note accompanying the WLC 7.6 code located on 5508,

  years 1240 only are supported. So, we will need to get the replacement of the years 1230.

  Someone suggested to go into every single years 1240 and change high availability for point to 5508 as primary and secondary 4402

  (just in case the AP don't is not the controller) 5508 Once this is done, I can add the AP in the access point default of the group to broadcase the same SSID.

  Is it enough for the task of migration?

  Also, what is the requirement of default design for the number of necessary uplinks?

  We have about 150 APs currently on 5508 that uses Group LAG of 1 4 uplinks.

  Regarding the 4402, it is service 60 APs with 1 2 uplinks.

  Thus with the APs on 4408 joining the 5508, 5508 serves about 210APs. 4 1 enough uplink is?

  What is the best practice recommended requirement of uplink AP?  APs on 5508 are 3602 s and 3702 s.

  Thank you in advance.

  P.S. BTW two controllers are part of the same mobility group

   Someone suggested going into every single 1240s and change the high availability to point to 5508 as primary and 4402 as secondary.(just in case the AP does not join the 5508 controller.) Once that is done, I can add the AP into the default AP group to broadcase the same SSIDs.Is that enough for migration task?

  Yes, it is sufficient. Unless 5508 have the same available on 4402 AP group name, all years 1240 migration goes into default-group & you may need to add to the good group of AP. It is advisable to have same AP group created between the controllers where AP configured for failover.

  Don't forget 1240 last took in charge in 8.0.x code. In order to better plan as well before moving on to 8.1 replacement code (expect less than 1-2 months of time). See below for more details compatibility matrix

  http://www.Cisco.com/c/en/us/TD/docs/wireless/compatibility/matrix/compatibility-matrix.html

   Also what is the default design requirement for the number of uplinks needed? We have about 150 APs currently on 5508 which uses LAG group of 4 1G uplinks.Thus with APs on 4408 joining the 5508, 5508 will roughly serve 210APs. is 4 1G uplink sufficient? 

  4G LAG is more that sufficient for 250 AP, I'm sure that together the traffic will be much less of 4G if monitor you the traffic volume of the art on this trunk links.

   What is the best practice recommended AP to uplink requirement? APs on 5508 are 3602s and 3702s.

  I guess that all of these AP connected to 1 Gbps switch compatible PoE ports +. If your binding rising intercommutation is 1 Gbit/s, which would be the bottleneck, WLC to SW LAG before becoming a bottleneck.

  HTH

  Rasika

  Pls note all useful responses *.

• 5508 controller & redundancy network/path

  I read in other threads that it is possible to use several Interfaces AP (disabled LAG) and have a port connected to a switch and the second trunk port connected to a second switch, with two switches in question connected with each other and running HSRP (our two 6500 hearts). My understanding on 5508 controller is very limited and I have just thrown into this, because it is a "high priority" project and is said today to sketch something for a meeting later, but if I connect it all together, it's then not create a loop? I guess my question is, is the data/network traffic through the 5508 in a trunk (port1) to another (port2) and I'll finish by fighting errors on my carrots, that data would be to pass a downlink of reference1 to port1 (for example), then again down port2 and on another soul?

  I read through the version 6 of the document as we speak, but it is not particularly clear on the delivery of the goods.

  Thank you!

  Alan

  Correct... you cannot divide ports if the WLC is configured for LAG.  For your use, with 6 AP, then Yes, I don't see why using a port connected to different switches will cause performance problems.  If it is a trial and you later decide that you will have 2 WLC, then connecto a swithc and develop WLC to the other switch and use LAG.

  Scott

• Successor to the 5508 controller?

  Hello

  I am currently using some 440 x controllers and I guess it's almost time to upgrade. I don't really want to buy a 5508, just because it is already > 4 years and so probably not very future proof (we have a 5-year window). On the other hand, the controller of 5760 seems to miss several features and has not even more since WLC 8.0 has been released. Currently, I'm also quite confused on the controller of Cisco strategy...

  Anyway, did anyone of you has heard a successor 5508 or what's going to happen with the two not synchronized release threads (ios and wlc based)?

  Thank you

  Patrick

   Anyway, has anybody of you heard about a 5508 successor or about what will happen with the two not synchronized release threads (ios and wlc based)?

  The answer is 'yes '.  The long answer is "talk to your Cisco AM / SE" and NOT to your authorized dealer/seller of the Cisco.

  The new materials are planned for mid - to end-2015.  That's all what I can say with respect to the subject of what is going to replace the venerable 5508.

  Now, the time to strategy.  Cisco SALES' mantra since always this: IF, for example, the 5508 announced today, users have about three to five years to find financing to replace them.   Here's the deal: the wireless IOS, not aircraft operating system, does not do well.  Not at all.  So that alone dictates the WISN/5508-2 is going to be around for a few years.

  Now, your biggest concern isn't when the EoS will be announced to the 5508/WISN-2.  Your biggest concern is your APs.  Have you read / seen the Release Notes for the firmware 8.0?  All APs 802.11 g only, as the 1130 and 1240, will be NOT permitted features 8.0.  They can join a controller with firmware 8.0, but they will have no 8.x features enabled.  So my hunch is this: the next major release, perhaps 8.1, all non - CleanAir APs, such as the 1040, 1140 won't 8.1 features enabled and the list will light.

• Can I set up two GALs of 5508 controller to two different switches?

  I have a WLC 5508 with a two port going to the n5k LAG switch. I want to add a SHIFT of 6 ports to a different switch (3750E) for redundancy. I can do or the OFFSET needs to be on the same switch?

  Thank you

  -mike

  Hi Mike,.

  The only restriction with respect links aggregation is that all physical links associated with a simple OFFSET must go to the same switch. In the case of Nexus 5 K this can also be 'pair' forming a field of vPC, or for the Catalyst 3750, rocker, which are part of the same battery.

  If you have two LAGS, you can connect the links in GAL 1 to the Nexus 5 K and the links to LAG 2 the Catalyst 3750.

  EDIT:

  In addition it seems that there is a restriction, at least until the 7.6 version, where the WLC only supports a single LAG. See GAL - aggregation of links for more details.

  Concerning

• AP1262N-A-K9 sees no 5508 controller

  I have just received from three AP1262 of Cisco, replaced my broken AP1262 that were the subject of the limited lifetime warranty. I plugged the up to my network and they receive DHCP addresses but the AP do not connect the controllers. I have two 5508 controllers running software version 7.2.110.0. I noticed the AP is running JB2 IOS 15.2 (2). In the past, the AP1262, I received were circulated JA1 IOS 12.4 (25th). According to the Cisco compatibility matrix, JB2 IOS 15.2 (2) should the controllers have the version of the 7.4.110.0 software. Is it possible to downgrade the AP1262 of 15.2 (2) JB2 to 12.4 (25th) JA1, without a service contract linked to my Cisco account?

  Hi Chris,

  As your AP came with an image independent, first you must load a recovery image using the mode key.

  first upload an image as "ap3g1-rcvk9w8 - tar.152 - 4.JA1.tar' on your TFTP server & renamed it as"ap3g1-k9w7 - tar.default» You must configure your PC (TFTP server) in the range of 10.0.0.x/8 when using this process. Then, you can load this recovery to your access point image & then you can connect it to the WLC environment to register.

  Please follow the below post for step by step process.

  http://mrncciew.com/2013/12/13/AP-conversion-using-mode-button/

  Let us know if you have questions once you do this

  HTH

  Rasika

  Pls note all useful responses *.

• 5508 controller Ethernet ports

  Forum

  We are giving demonstrations a box 5508 for a client installation.  I was asked by the customer the other day if the 8-port ethernet on the WLC are for plugging AP in.  I told them I don't, I thought just a network connection would be sufficient because this guy will be able to be sent to all the other networks of the AP are on.  I was not able to explain what all the ports were for, but he told them that I would like to know.

  Can someone of you give an example of why real life there are 8 ports ethernet on the box?

  Thank you

  Kevin

  The original idea is to group 8 as an Etherchannel ports for the connection of 8 Gbps. You have that bandwidth when you have 500 joined APs.

  You can connect the ports on different switches if they are non-grouped.

  Connect directly on APs it would work (it works on the 2106 which is made for that), but it's not very practical. This makes the need to create the AP Manager by port interface, you do not have redundancy and APs are not accessible from the network

• Problem setting 5508 wireless controller

  Hello

  I am now to configure the 5508 controller, I have enable 802.11n and test with client 802, 11n.

  But the display of the client software speed is 144 m, I've resolved to use WPA2-AES, enable WMM, than any other setting to activate 802.11n 300 M?

  Thank you

  Hi ANgus,

  I guess you found what is G radio... this the MAXIMUM N speed we can get on radio G!

  Let me know if that answers your question...

  Concerning
  Surendra
  ====
  Please do not forget to note positions that answered your question and mark as answer or was useful

• AP cannot participate. DTLS connection closed by controller

  Hi guys,.

  1140 aPs no record with the 5508 controller. Here are some results of debugging:

  IP access point: 100,31

  WLC IP:100.2

  activate debugging capwap events

  * spamApTask1: 11:25:04.958 Nov 01: Discovery 30:e4:db:d3:a4:ca request 192.168.100.31:47690

  * spamApTask1: 11:25:04.958 Nov 01: 30:e4:db:d3:a4:ca join priority Processing status = 0, priority 1 of incoming Ap, MaxLrads = 100, joined Aps = 0

  * spamApTask1: 11:25:04.958 Nov 01: Discovery 30:e4:db:d3:a4:ca response to 192.168.100.31:47690

  * spamApTask1: 11:25:04.958 Nov 01: Discovery 30:e4:db:d3:a4:ca response to 192.168.100.31:47690

  * spamApTask1: 11:25:14.959 Nov 01: DTLS 30:e4:db:d3:a4:ca not found, creating new connection connection for 192:168:100:31 (47690) 192:168:100:2 (5246)

  * spamApTask1: 11:25:15.101 Nov 01: DTLS closed connection events receivedserver 30:e4:db:d3:a4:ca (192:168:100:2 / 5246) client (192:168:100:31 / 47690)

  * spamApTask1: Nov 01 11:25:15.101: 30:e4:db:d3:a4:ca no entry there for AP (192:168:100:31 / 47690)

  * spamApTask1: 11:25:15.101 Nov 01: 30:e4:db:d3:a4:ca entry no. AP exist in the temporary database for 192.168.100.31:47690

  **************************************************************

  turn debugging capwap package

  > * spamApTask1: Nov 01 11:36:20.039: <  start="" of="" capwap="" packet ="">>

  * spamApTask1: 11:36:20.039 01 Nov: mesg 192.168.100.31 Recd, Port 47690 CAPWAP control

  * spamApTask1: 11:36:20.039 Nov 01: 4, HLEN, Radio ID 0, WBID 1

  * spamApTask1: 11:36:20.039 Nov 01: Msg Type: CAPWAP_DISCOVERY_REQUEST

  * spamApTask1: 11:36:20.039 Nov 01: Msg length: 73

  * spamApTask1: 11:36:20.039 Nov 01: Msg SeqNum: 0

  * spamApTask1: 11:36:20.039 01 Nov:

  * spamApTask1: Nov 01 11:36:20.039: Type: CAPWAP_MSGELE_DISCOVERY_TYPE, length 1

  * spamApTask1: 11:36:20.039 Nov 01: Type of discovery: CAPWAP_DISCOVERY_TYPE_UNKNOWN

  * spamApTask1: 11:36:20.039 01 Nov:

  * spamApTask1: Nov 01 11:36:20.039: Type: CAPWAP_MSGELE_WTP_DESCRIPTOR, length 40

  * spamApTask1: 11:36:20.039 Nov 01: X-rays taken Maximum supported: 0

  * spamApTask1: 11:36:20.039 Nov 01: Radios in use: 0

  * spamApTask1: 11:36:20.039 Nov 01: encryption features: 0x00 0x01

  * spamApTask1: 11:36:20.039 01 Nov:

  * spamApTask1: Nov 01 11:36:20.039: Type: CAPWAP_MSGELE_WTP_FRAME_TUNNEL, length 1

  * spamApTask1: 11:36:20.039 Nov 01: Mode of raster WTP Tunnel: NATIVE_FRAME_TUNNEL_MODE

  * spamApTask1: 11:36:20.039 01 Nov:

  * spamApTask1: Nov 01 11:36:20.039: Type: CAPWAP_MSGELE_WTP_MAC_TYPE, length 1

  * spamApTask1: 11:36:20.039 Nov 01: WTP Mac Type: SPLIT_MAC

  * spamApTask1: 11:36:20.039 01 Nov:

  * spamApTask1: Nov 01 11:36:20.039: Type: CAPWAP_MSGELE_VENDOR_SPECIFIC_PAYLOAD, length 10

  * spamApTask1: 11:36:20.039 Nov 01: identifier of the seller: 0 x 00409600

  * spamApTask1: 11:36:20.039 01 Nov:

  IE: UNKNOWN IT IS 207

  * spamApTask1: Nov 01 11:36:20.039: IE length: 4

  * spamApTask1: 11:36:20.039 Nov 01: decode the routine unavailable, Hex Dump printing

  * spamApTask1: 11:36:20.039 Nov 01: 00000000: 01 00 00 01...

  * spamApTask1: Nov 01 11:36:20.039: <  end="" of="" capwap="" packet ="">>

  **************************************************************

  turn debugging capwap errors

  * spamApTask1: 11:45:15.244 Nov 01: 30:e4:db:d3:a4:ca abolition PT 192.168.100.31 which has not been surveyed

  * spamApTask1: 11:45:15.245 Nov 01: 30:e4:db:d3:a4:ca DTLS connection has been closed

  **************************************************************

  turn debugging capwap detail

  * spamApTask1: 11:52:45.298 Nov 01: 30:e4:db:d3:a4:ca CAPWAP control received Msg to 192.168.100.31:47690

  * spamApTask1: 11:52:45.298 Nov 01: DTLS 30:e4:db:d3:a4:ca 0x1454bc38 connection closed by controller

  * spamApTask1: 11:52:45.299 Nov 01: msg closed connection CAPWAP DTLS

  Check your time on the wlc. There offshore so that's why the AP ate only joined do not.

  Sent from my iPhone

• WLC 5508 Management interfaces

  I'll put up a new 5508.  I have used the config of a 4402, have successfully connected to the path of Service to manage the device, but for some reason any cannot connect to the management interface.  In this case, port 1.

  The service port is connected to a catalyst switch and grabbed an IP (subnet 10.2.x.x) no problem.  I can access the 5508 via https using MS.  However, port 1 is connected to the same Catalyst switch, but on one vlan different (10.20.x.x subnet).  Both ends show that interfaces are in place, I can ping the interface from any other host on the network, but when I try to run the device via https I can't connect.  We use the WCS and I can't add the device to the WCS.  About all I can do is ping this interface.

  I probably forgot something very basic, but I'm stumped.

  We have the same Cisco 5508 controller and we discovered that if you use a computer on the same subnet that the Service interface, you won't not be able to connect to the management of a via HTTP or SSH, even though you 'll be able to ping. We changed the IP address of the service interface, and then we were able to connect to the management of a site.

• connectivity between 5508 and two different 4507 switches

  Hello

  I've implemented with 5508 controller which is connected to two different chassis (Cisco 4507 switches). I have some doubt about the configuration of the interface on 5508 WLC.

  How can I configure the AP Manager interface with two physical ports on different chassis?

  If I have understood correctly, we can configure the AP manager interface with a single port

  In my introduction, we configured HSRP chassis mentioned...

  Please light up on this confused concept.

  How can I configure interfaces with two physical ports on two different chassis?

  If someone could send examples of configuration, it would be very useful for me to procees with.

  Already there are request to that effect in the cisco forum, but I did not understand correctly.

  Response would be appreciated.

  Hello

  I advise you to go through the doc:

  http://www.cisco.com/en/US/docs/wireless/controller/7.0/configuration/guide/c70mint.html.

  For Cisco 5500 series controllers, you are not required to configure an interface AP manager. The management interface is as an AP-Manager interface by default, and access points can join this interface.

  HTH,

  Tiago

  --

  If this helps you or answers to your question if it you please mark it as 'responded' or write it down, if other users can easily find it.

• Placement of WLAN Interface 5508

  Hello

  I'm deploying a 5508 controller in a test environment.

  However, I have a question.

  My switches "of basis' and 'access' are separated by a link of L3. (a link point to point routed 10 GB)

  Has the 'access' layer 2 VLANS, one for voice and one for data. APs, get an IP address from the subnet data and you sign up for the controller in this way.

  Management interface is physically attached to the heart, a 4.4.8.0/reseau 25 for any other 'shared' devices such as the UCS Manager, etc..

  By default, the devices associating want to get their IP address to this VLAN (e.g. the 4.4.8.0/25 network). However, there is no scope for the local network, this interface is on.

  I would create a separate VLAN for wireless guests and hosts to get their addresses in this range.

  Is there a problem with me filing a separate interface of the WLC directly in the VLAN database on this access switch and letting the management interface in the subnet 'shared '. In this way, the DHCP server on my farm will see the DHCP from subnet 8.8.4.0/25 data req.

  I know that in most scenarios, create you a port channel, resources shared until the WLC and allow several diff. VLANS for different SSIDS, however, in my lab is not simply possible since my limits of L2 are within the base only. My sites talk / MDFs are all 3-layer set for extending over one VLAN outside of the kernel is not possible.

  As long as the WLC does not participate in spanning tree, I don't see a problem with falling one another physical port separated in my switch to access and use this as the interface that the APs register since and so, route their DHCP req.s of.

  Thank you

  If your installation is basically a layer 3 for closets.  Usually you create another interface on the WLC and put it on the vlan that you want to clear these users.  Because you do not LAG, you probably have a connected to your port/25 network 4.4.8.0, and then you have 2 port connected to your network 8.8.4.0/25.  Port 2 in your lab, does not mean that you must place in your kernel, you can connect that to your access sides if you wish.  Just make sure you have dhcp for the installation of clients.

• WLC 5508 WIRELESS problem SSID

  Hello

  I recently got a 5508 controller. I use 1 SSID for employees on the main site (using certificate authentication). I want to use the same SSID with different DHCP servers on remote sites, (AP configure with the HREAP mode). So I tried to configure different WLAN ID using the same SSID (I spend in addition to the IP address of the DHCP server). When I try to enable the SSID, I got the following error: "WLAN SSID and L2 security policy with duplicate. I tried to use "Group AP" and put the different WLAN ID in different group AP but it doesn't work.

  Someone at - it an idea?

  Thanks in advance

  Kind regards

  Eric

  Hello

  At the time, we specify the WLAN to use local switching, VLAN HREAP mapping will do the job... It's... the central site clients will grab the IP address of the DHCP Server central according to the dynamic interface mapped to the WLAN and toward the remote father remore users will grab the IP address of the remote DHCP configured based o NTHE VLAN mapping pool WLAN on the AP HREAP for...

  Let me know if this answers your question!

  Concerning

  Surendra

• 4402-25 and 25-5508 fault tolerance?

  We have a Cisco 4402-25 running the 7.0.98 software version and we are interested in getting a new controller of 5508.  My question is can I load balance between these two or an act as a master and the other a slave?  Thank you

  We have a Cisco 4402-25 running software version 7.0.98 and we are interested in getting a new 5508 controller.  My question is can I load balance between these two or can one act as a master and the other a slave?
  

  The most common scenario of those made the access point for joining WLC 1 as a main controller and set up WLC 2 as a secondary controller.  Cisco recommended (or admitted) this inter-controleur roaming should be avoided at all costs.

  Roaming inter-controleur, still at the stage of since 3.X, this is "early childhood" is always in perfect.

  I hope this helps.