WCS: Tertiary Controller Name is mandatory?

Hi,
I upgraded my WCS to 4.2. After that, everytime I want to configure an accesspoint, I get an error message ""Tertiary Controller Name: This attribute is MANDATORY. Please Specify it".
How can I turn that off? Thanks

Hi Tobias,
It sounds like this Bug has carried over;
CSCsi24972 Bug Details
Tertiary controller - need not be mandatory
Symptom:
WCS 4.1.83.0, with 3 or more WLC linked.
Attempt to modify the configuration of an AP and if you do not have a tertiary defined you get an error telling you that it is mandatory.
Conditions:
WCS 4.1.83. Status
Fixed
Severity
4 - minor
Last Modified
In Last 2 weeks
Product
Cisco Wireless Control System
Technology
1st Found-In
4.1(83.0)
Fixed-In
4.2(26.0)
Related Bug Information WCS 4.1.83.0 Requires Tertiary Controller be set for AP
Symptom: WCS 4.1.83.0, with 3 or more WLC linked. Attempt to modify the configuration of an AP and if you do not have a tertiary defined you get an error telling you that it is mandatory. Conditions: WCS 4.1.83.0, with 3 or more WLC linked Workaround: Define the secondary or primary as the tertiary <
Hope this helps!
Rob

Similar Messages

Getting a lot of this error:The reason code is '4(802.1X Authentication failed 3 times.)'. - Controller Name:

Since we upgraded our WCS system to V6.0.196.0 we are receiving a lot of the following error messages and I haven't figured out why.
Client 'c0:cb:38:3f:a1:0d (anonymous, 0.0.0.0)' which was associated with interface '802.11a/n' of AP 'ACAA01-00.P04-G2C2.1' is excluded. The reason code is '4(802.1X Authentication failed 3 times.)'. - Controller Name: 205-dg20-bb3-4/2

Check you ACS (Radius) logs under failures. You will see why its failing. Sounds like a AD account went bad
or someone is entering the wrong logon ... But check your radius log it will point you in the right direction.

WCS & AP: AP name keeps resetting to mac

Hi,
I just installed an AP in WCS. When I goto the properties of that AP, i am able to change the name just fine but 2-3 minutes later the name resets back to the mac address of the AP.
I tried changing the name thru WCS and the Controller.
Any ideas appreciated.

Hi,
I am having the same issue with one of my WAP's.
It has been deployed for just over 2 weeks now and was fine until this weekend. Saturday evening and now this morning it has changed its name from what I have supplied through the WLC back to the MAC based name.
WLC5508
3502i AP
code 7.0.98.0
Running in HREAP mode.
I have some 16 AP all running off this controller and so far this is the only AP that appears to be having this weird issue.
I do 95% of my configuration through the gui of the WLC and the other 5% through the gui of WCS.
The name giving was done through the WLC.
Any help would be appreciated.
I have also openned a case with the TAC 618060639
Thanks !

How can I add the controller name in the subject of Alarm emails? PI2.1

How can I add the controller name in the Alarm emails in PI2.1? This would make it much easier to scan the mailbox and see what devices are affected.

Thanx for your reply. No, although helpful, that's not what I meant. In outlook, the first line of the header contains the full username follow by a horizontal line. Under that, the default headers like To:, From:, Subject: etc follow.
I need that firstline printed so we know instantly from which user the email was printed (the To: field often is the same name of the sender of the mail, therefor you won't know WHO printed it...).

What is specify controller name

what do i put as controller name

I believe your question is concerning "Distributed Replay Client Configuration"
Controller Name: - This is an optional parameter, and the default value is
<blank>. Enter the name of the controller that the client computer will communicate with for the
Distributed Replay Client Service.

Pass controller name runtime

Hi,
I want to develope reusable FXML components. I want to pass controller name runtime to FXML, so that everyone can write down own controller and pass the attributes to FXML.
e.g.
I will have AnchorPane.FXML. Button should contain <fx:define> component for controller name
So that
<AnchorPane id="AnchorPane" xmlns:fx="http://javafx.com/fxml" fx:controller="*+_XXXXXXXXXX_+*" >
This can be included in some XXX.FXML, but XXXXXXXXXX should be passed throgh <var name="controller" value="${controller}"/>, so that button properties like name,size can be passed using own controller.
Is there any way I can do so?
Thanks in advance.

I want to develope reusable FXML components. I want to pass controller name runtime to FXML, so that everyone can write down own controller and pass the attributes to FXML.This isn't currently possible. However, in JavaFX 2.1, you can provide a custom controller factory implementation to FXMLLoader that will allow your application to manage the controller instantiation process. Maybe this will help you address your use case.
XXXXXXXXXX should be passed throgh <var name="controller" value="${controller}"/>, so that button properties like name,size can be passed using own controller.From a pure design standpoint, the controller probably should not be sourcing values like name and size. Name should probably come from a resource bundle, and size should be defined by the view. The controller is primarily meant to manage the interaction between the model and the view, and respond to user input events fired by the view.

HBA controller name changes after upgrading to solaris 11.2 from solaris 11.1

we have upgraded OS on control domain from Sol 11.1 to Sol 11.2 . After upgrade controller name of HBAs and NPIV wwns changed ( like if it is c2 prior to upgrade , post upgrade controller name changes to c8). Due to this we have to redo virtual disk mapping for all ldoms hosted on this machine. . Would it be possible to preserve the HBA controller names across OS versions ? we even observed this issue while upgrading SRU of solaris 11.2 system. We have to upgrade around 20 systems to solaris 11.2 and with this issue upgrade seems to be a tedious task. Any idea if there is any fix or workaround for it ?

Are your disks only connected to one single HBA?
We use MPXIO to MultiPath over Multiple HBAs. Controller never changed here for the MPXIO devices.
Best regards,
Marcel

WCS vs Controller License Question - 5500 series.

In the WCS License Center, there are two sets of license options: WCS and Controller. Am I to understand correctly that:
- WCS License count is how many APs can be monitored by WCS?
- Controller License count is how many APs can be connected to a WLC?
Thanks!
-Robert

Think of each controller license as independent license. Although you have 2 AP licenses at 25 each you can aggregate 50 access points to the controllers (25 each). This would of course negate full redundancy.
But you can steer access points incase of failure in the above example.
Suppose you have 30 access points ( 15ap location 1 and 15ap location 2). You are over 5 access points over for full redundancy.
Suppose location 1 is a higher priority then location 2 and you want to make sure you have all the aps up at location 1. You can add a priority to the access points at location 1 so they connect to the controller before aps at location 2.
Just an fyi

Mass MRP Codes and Controller names creation/updation in configuration

Hi all,
Can any one guide me how to do mass creation of MRP Codes and controller names plant wise and also updation of existing
mrp controller names in configuration ?.
Is there any SAP standard tools available or need to do it manually or any other ways to acheive it ?.
Thanks in advance.

Hello,
You can use Script Recording and Playback:
1- Save step by step how one MRP controller is created.
2- Adjust the script.
3- Complete an excel file with the entries.
4- Run the script.
Kind Regards,
Mariano

BAPI function module name and mandatory fields

Give the name of BAPI function module for pricing change into the transaction VA05 ?
What are the mandatory fields ?
Please give a exemple code to do this.

Hi,
VA05 is for list of sales order. But if you want to change pricing of material stocks go for follwoing fn module.
BAPI_SALESORDSTCK_PRICE_CHANGE
If you want other BAPI for sales related, just go to SE37, give BAPISALE and press F4, you will get all the BAPI fn modules.
Rewards points if helpful.
Regards,
CS.

WCS and Controller upgrade questions

Hi,
with the WCS should I install both the EXE file and the BIN fil or just the BIN file?
Also, for upgrading the Controllers where can I find the ER file. I have downloaded the 4.2.209.0 image but, can't find the 4.2.205.0 ER.aes. Does anyone know where this is?
where on the controller can I tell if I already have the ER file?
Thanks, Pat.

Hi Patrick,
The link which i posted is for 4404.. for 4402 here is the link..
http://www.cisco.com/cisco/software/release.html?mdfid=279911193&flowid=7586&softwareid=280926587&release=4.2.112.0%20BOOT&rellifecycle=&relind=AVAILABLE&reltype=all
The latest ER that we hav for 4402 is 4.2.112..
Q1>> To get the software image I goto wireless, Wireless LAN Controllers, standalone Controllers, Cisco 4400 Series Wireless LAN Controllers, 4402, Software on Chassis hten Wireless LAN Cotroller software, but don't see the ER file.
ANS - Yes you are right.. the above is the procedure to download the image.. "ER is nothing but the BOOT IMAGE, if you click on BOOT then the image will pop up as ER, the non BOOT will be in .aes format or something..
lemme know if this answered your question..
Regards
Surendra
====
Please dont forget to rate the posts which answered your question and mark it as answered or was helpfull

Configure Bank account holder name field mandatory

Hi,
We want to make the account holder field under bank details field group as mandatory. The individual field group settings under IMG does not allows to maintain the individual field settings for bank details field group.
Is there any other way to make this field mandatory?
Thanks and regards,
Kaushik Das

Hi,
We want to make the account holder field under bank details field group as mandatory. The individual field group settings under IMG does not allows to maintain the individual field settings for bank details field group.
Is there any other way to make this field mandatory?
Thanks and regards,
Kaushik Das

WLC 2504 can't change WAP name or switch off CDP via WLC gui

Hi All,
Please can you assist? I have 1 x Cisco WLC 2504 & 2 x Cisco WAP AIR-CAP1602I-E-K9 running 7.4.100.60.
All three devices are installed and working correcty within a corporate environment. However, there are a few tweaks that I would like to do, to tidy up the configuration and switch certain elements on or off. For example, my core networking hardware is Huawei and I would like to switch off 'CDP' on the WAP's as the associated error messages are filling up my logging buffer on my switch. So, I https to my WLC, locate the WAP in question, goto 'interfaces' and untick the box for 'CDP state' hit apply, then I get the following error message "controller name is mandatory when controller ip address is configured" and then the tick reappears!
At present I have two WAP's. Both have static IP addresses and both are reachable on the network. The one WAP did allow me to change the name to something meaningful, but the other WAP would not let me and still has the default MAC address as its name. I have the same issue, when I try to change the name on the WAP it says "controller name is mandatory when controller ip address is configured"
I have also tried to CLI directly in to the WAP to make these alterations, but as soon as i launch 'putty' it quits out. I guess this is locked down once the WAP's associate with the WLC.
And around I go.... Someone must have been in this situation, what am i missing? Thanks in advance!

Hi Andy,
By default SSH & Telnet is disabled for WLC controlled APs. So you have to enable it first via WLC GUI in order to access the AP via telnet or SSH.
Wireless -> Select your AP -> Advanced -> Tick Telnet/SSH boxes.
If you could not change AP name via WLC GUI (it may be a bug), but as I said earlier try to change it via WLC CLI (not AP CLI itself). SSH to your WLC & then try the following.Old AP name is the one with its mac address.
(WLC) >config ap name
(WLC) >save config
Are you sure you want to save? (y/n) y
Configuration Saved
HTH
Rasika
*** Pls rate all useful responses ****

3502i APs not joining controller

So basically my infrastructure consists of four 4402 WLCs running on 7.0.235.3. I'm trying to get new access points to join to the environment, but I am having difficulty doing so. All currently joined APs work fine and are operating well. I'm getting a red, green, off blink code which means it's trying to join, but never does. The other one I get a constantly blinking green but it never joins either. I've setup option 43 in DHCP, added cisco-capwap-controller entries in DNS thinking it was because those are missing, and still cannot get these two access points to join. Can anyone think why it would not be joining?
The access points and WLC are all on the Same VLAN by the way.

Hello,
In a Cisco Unified Wireless network, the LAPs must first discover and       join a WLC before they can service wireless clients.
Originally, the controllers only operated in Layer 2 mode. In Layer 2       mode, the LAPs are required to be on the same subnet as the management       interface and the Layer 3 mode AP-manager interface is not present on the       controller. The LAPs communicate with the controller using Layer 2       encapsulation only (ethernet encapsulation) and do not Dynamic Host       Configuration Protocol (DHCP) an IP address.
When Layer 3 mode on the controller was developed, a new Layer 3       interface called AP-manager was introduced. In Layer 3 mode, the LAPs would       DHCP an IP address first and then send their discovery request to the       management interface using IP addresses (Layer 3). This allowed the LAPs to be       on a different subnet than the management interface of the controller. Layer 3       mode is the dominate mode today. Some controllers and LAPs can only perform       Layer 3 mode.
However, this presented a new problem: how did the LAPs find the       management IP address of the controller when it was on a different subnet?
In Layer 2 mode, they were required to be on the same subnet. In Layer       3 mode, the controller and LAP are essentially playing hide and seek in the       network. If you do not tell the LAP where the controller is via DHCP option 43,       DNS resolution of "Cisco-lwapp-controller@local_domain", or statically       configure it, the LAP does not know where in the network to find the management       interface of the controller.
In addition to these methods, the LAP does automatically look on the       local subnet for controllers with a 255.255.255.255 local broadcast. Also, the       LAP remembers the management IP address of any controller it joins across       reboots. Therefore, if you put the LAP first on the local subnet of the       management interface, it will find the controller's management interface and       remember the address. This is called priming. This does not help find the       controller if you replace a LAP later on. Therefore, Cisco recommends using the       DHCP option 43 or DNS methods.
When the LAPs discover the controller, they do not know if the       controller is in Layer 2 mode or Layer 3 mode. Therefore, the LAPs always       connect to the management interface address of the controller first with a       discovery request. The controller then tells the LAP which mode it is in the       discovery reply. If the controller is in Layer 3 mode, the discovery reply       contains the Layer 3 AP-manager IP address so the LAP can send a join request       to the AP-manager interface next.
Note: By default both management and AP-manager interfaces are left           untagged on their VLAN during configuration. In case these are tagged, make           sure they are tagged to the same VLAN in order to properly receive discovery           and join response from the WLC.
The LWAPP AP goes through this process on startup for Layer 3       mode:
The LAP boots and DHCPs an IP address if it was not previously           assigned a static IP address.
The LAP sends discovery requests to controllers through the various           discovery algorithms and builds a controller list. Essentially, the LAP learns           as many management interface addresses for the controller list as possible via:
DHCP option 43 (good for global companies where offices and             controllers are on different continents)
DNS entry for             cisco-capwap-controller (good for local             businesses - can also be used to find where brand new APs join)
Note: If you use CAPWAP, make sure that there is a DNS entry for                 cisco-capwap-controller.
Management IP addresses of controllers the LAP remembers             previously
A Layer 3 broadcast on the subnet
Over the air provisioning
Statically configured information
From this list, the easiest method to use for deployment is to have           the LAPs on the same subnet as the management interface of the controller and           allow the LAP’s Layer 3 broadcast to find the controller. This method should be           used for companies that have a small network and do not own a local DNS           server.
The next easiest method of deployment is to use a DNS entry with           DHCP. You can have multiple entries of the same DNS name. This allows the LAP           to discover multiple controllers. This method should be used by companies that           have all of their controllers in a single location and own a local DNS server.           Or, if the company has multiple DNS suffixes and the controllers are segregated           by suffix.
DHCP option 43 is used by large companies to localize the information           via the DHCP. This method is used by large enterprises that have a single DNS           suffix. For example, Cisco owns buildings in Europe, Australia, and the United           States. In order to ensure that the LAPs only join controllers locally, Cisco           cannot use a DNS entry and must use DHCP option 43 information to tell the LAPs           what the management IP address of their local controller is.
Finally, static configuration is used for a network that does not           have a DHCP server.You can statically configure the information necessary to           join a controller via the console port and the AP’s CLI. For information on how           to statically configure controller information using the AP CLI, refer to           Manually           Configuring Controller Information Using the Access Point CLI.
For a detailed explanation on the different discovery algorithms that           LAPs use to find controllers, refer to           LAP           Registration with WLC.
For information on configuring DHCP option 43 on a DHCP server, refer           to           DHCP           OPTION 43 for Lightweight Cisco Aironet Access Points Configuration           Example.
Send a discovery request to every controller on the list and wait for           the controller's discovery reply which contains the system name, AP-manager IP           addresses, the number of APs already attached to each AP-manager interface, and           overall excess capacity for the controller.
Look at the controller list and send a join request to a controller           in this order (only if the AP received a discovery reply from it):
Primary Controller system name (previously configured on             LAP)
Secondary Controller system name (previously configured on             LAP)
Tertiary Controller system name (previously configured on             LAP)
Master controller (if the LAP has not been previously configured             with any Primary, Secondary, or Tertiary controller names. Used to always know             which controller brand new LAPs join)
If none of the above are seen, load balance across controllers             using the excess capacity value in the discovery response.
If two controllers have the same excess capacity, then send the             join request to the first controller that responded to the discovery request             with a discovery response. If a single controller has multiple AP-managers on             multiple interfaces, choose the AP-manager interface with the least number of             APs.
The controller will respond to all discovery requests without             checking certificates or AP credentials. However, join requests must have a             valid certificate in order to get a join response from the controller. If the             LAP does not receive a join response from its choice, the LAP will try the next             controller in the list unless the controller is a configured controller             (Primary/Secondary/Tertiary).
When it receives the join reply, the AP checks to make sure it has           the same image as that of the controller. If not, the AP downloads the image           from the controller and reboots to load the new image and starts the process           all over again from step 1.
If it has the same software image, it asks for the configuration from           the controller and moves into the registered state on the controller.
After you download the configuration, the AP might reload again to           apply the new configuration. Therefore, an extra reload can occur and is a           normal behavior.

LWAPP discovery problem

I am currently setting up a 4402 controller and lwapps. Our wireless right now is all managed by corp and is a combination of autonomous and lwapp. Here is my problem.
I have setup option43 in my dhcp scope. When I connect a fresh radio to the same subnet as the controller I see that the radio goes to the controller but then there is a message and the radio goes to the corp controller.
Here is the boot log from a new radio.
%LWAPP-3-CLIENTEVENTLOG: Controller address 10.200.190.10(MINE) obtained through DHCP
%LWAPP-3-CLIENTEVENTLOG: Did not get log server settings from DHCP.
%LWAPP-3-CLIENTEVENTLOG: Performing DNS resolution for CISCO-LWAPP-CONTROLLER.gtna.gt.ds
%LWAPP-3-CLIENTEVENTLOG: Controller address 10.148.198.7(CORP) obtained through DNS
I see that message about a log server. Did I miss something?
thanks
tony

Hi Guys,
I just thought that I would link this info for the LWAPP Layer 3 startup. +5 points for both Wesley and Leo for your ongoing great work here :)
The LWAPP AP goes through this process on startup for Layer 3 mode:
The LAP boots and DHCPs an IP address if it was not previously assigned a static IP address.
The LAP sends discovery requests to controllers through the various discovery algorithms and builds a controller list. Essentially, the LAP learns as many management interface addresses for the controller list as possible via:
DHCP option 43 (good for global companies where offices and controllers are on different continents)
DNS entry for âcisco-lwapp-controllerâ (good for local businesses - can also be used to find where brand new APs join)
Management IP addresses of controllers the LAP remembers previously
A Layer 3 broadcast on the subnet
Over the air provisioning
Statically configured information
From this list, the easiest method to use for deployment is to have the LAPs on the same subnet as the management interface of the controller and allow the LAP's Layer 3 broadcast to find the controller. This method should be used for companies that have a small network and do not own a local DNS server.
The next easiest method of deployment is to use a DNS entry with DHCP. You can have multiple entries of the same DNS name. This allows the LAP to discover multiple controllers. This method should be used by companies that have all of their controllers in a single location and own a local DNS server. Or, if the company has multiple DNS suffixes and the controllers are segregated by suffix.
DHCP option 43 is used by large companies to localize the information via the DHCP. This method is used by large enterprises that have a single DNS suffix. For example, Cisco owns buildings in Europe, Australia, and the United States. In order to ensure that the LAPs only join controllers locally, Cisco cannot use a DNS entry and must use DHCP option 43 information to tell the LAPs what the management IP address of their local controller is.
Finally, static configuration is used for a network that does not have a DHCP server.You can statically configure the information necessary to join a controller via the console port and the AP's CLI. For information on how to statically configure controller information using the AP CLI, refer to Manually Configuring Controller Information Using the Access Point CLI.
For a detailed explanation on the different discovery algorithms that LAPs use to find controllers, refer to LAP Registration with WLC.
For information on configuring DHCP option 43 on a DHCP server, refer to DHCP OPTION 43 for Lightweight Cisco Aironet Access Points Configuration Example.
Send a discovery request to every controller on the list and wait for the controller's discovery reply which contains the system name, AP-manager IP addresses, the number of APs already attached to each AP-manager interface, and overall excess capacity for the controller.
Look at the controller list and send a join request to a controller in this order (only if the AP received a discovery reply from it):
Primary Controller system name (previously configured on LAP)
Secondary Controller system name (previously configured on LAP)
Tertiary Controller system name (previously configured on LAP)
Master controller (if the LAP has not been previously configured with any Primary, Secondary, or Tertiary controller names. Used to always know which controller brand new LAPs join)
....continued on next page

WCS: Tertiary Controller Name is mandatory?

Similar Messages

Maybe you are looking for