Migrate AP from WiSM to Virtual WLC

Hello all,
We have WiSM installed in Core Switch 6500 having 300+ AP registered on it.
We want to migrate our AP's to new Virtual WLC. What is the best way to migrate AP to new vWLC with less down time.
Can we migrate AP's from WiSM to Virtual WLC in bulk ( all in one time)? I read some where in form that AP version 7.3 & above start supporting vWLC. I am not sure if this applies for WisM as well ( i am assuming WiSM & WLC are differnt) ?
My WiSM is running 7.0.240.0 & vWLC is 7.4. please check the WiSM attachments.
Also is there any way to take backup from WiSM and restore on vWLC ?
Regards.

Hi,
First of all, in order to reduce downtime, I would recommend that you upload the 7.4 code on the WiSM and predownload it to all the APs. (Wireless -> Global Configuration - AP Image Pre-download).
Another thing would be to configure the vWLCs as back-up Primary & Secondary Controllers (Wireless -> Global Configuration - High Availabiliy). Doing this your APs will already know about the new WLC when the first will go down and will not have to go through discovery process. (test from AP CLI with show capwap client config)
For the AP mode "mass-conversion" to flexconnect I don't know a better way than from WLC CLI, using:
config ap mode flexconnect submode none AP_NAME_1
config ap mode flexconnect submode none AP_NAME_300
You could use text file to edit the the command with the AP names and than paste it all at once in the WLC. It would be wise to test it first with a few lines.
If you did all this, when your old WLC goes down all your APs should associate to the new WLCs.
Best regards,
Sebastian

Similar Messages

Moving Licences from WLC2504 to Virtual WLC

I have a WLC2504 with 35 licences (two 5 packs and one 25 pack)
The fear is that if this older piece of hardware would die, then so would my 35 licences.
I recently installed a Virtual WLC with 5 licences.
What I would really love to able to do, is somehow migrate my 35 licences from 2504 to the Virtual controller.
Is there a backdoor method to get those licences out of my 2504
I do not have a Smartnet on any of these devices, so no worries of warranties, etc..
Comments, suggestions, opinions and flames are all welcome and appreciated
Bryan Smith
Fort Wayne, Indiana

If I am not mistaken, you will not be able to move a license from a Gen 2 WLC (like the 2500) to the Gen 3 box (like the vWLC).

Question about tunnel two WLAN from the same foreign WLC to the same anchor

Hi all,I met following customer request:
one anchor WLC 4402-12 put in the DMZ of perimeter firewall, one WiSM in the internal network to controll all the AP1252. two WLAN created at the WiSM and anchor WLC: guest wlan(web-auth+lobby admin created guest accounts) and untrusted wlan(web-auth+ACS+AD user database). Both WLANs want to be tunneled from WiSM to Anchor WLC. Guest WLAN has not much users, untrusted WLAN has a lot of users which may be thousands. My question is if this design can work?(I know definately one WLAN can be tunneled, but not sure if there's any potential issues if tunnel two WLANs)
Is there any performance issue? What WLC version is suggested to use?
Thanks for any help!

I haven't ever tried this but suspect that you can form only one tunnel outbound per WLC. The anchor supports multiple inbound tunnels but outbound is the question. When you find out for sure please post it here.

Virtual WLC Ports Confusion -or- ADDING ports to the vWLC

I am a struggling with configuring a virtual wireless controller (vWLC).
I am working with the newest vWLC, 8.0.100.0
I currently own an elderly 2504 WLC with 4 ports. (four physical interfaces on the box)
On this 2504, I use one port for the management of the WLC and for WLC to communicate with the APs.
The APs are on the same network as the 2504. The other port is the interface that all my wireless traffic from the clients use.
Now with this vWLC, the virtual machine has two network interface, but once I get to a point that I am able to login to the vWLC, I only see one 'port'. According to this posting, I am suppose to take the service port and point it too a dummy virtual switch or a 'Black Hole' https://supportforums.cisco.com/document/12098556/vwlc-getting-started-key-points-and-common-issues.
Okay, I've done this and it works, but it not what I am accustomed to.
I enjoy having the web console of the WLC and the AP on separate networks from the wireless clients.
To complicate things my desire is for this new vWLC and my 2504 to work together.
I want over time to migrate APs from the 2504 to the vWLC without re-addressing them.
Can I add "ports" to my vWLC controller? Do I need to rethink my wireless infrastructure?
I am confused and am seeking your help, advice, suggestions, opinions and flames.
Bryan Smith
Butler, Indiana

I think you need to re-look at your wireless design. I would prefer the 2504 over a vWLC, but that's me. I would not of separated the ports also on the WLC. No real reason to, to be honest. Keep AP's on a seperate subnet and the traffic to and from the WLC is tunneled using capwap. Breaking up ports was an old design to be honest and that was also done back them with the 4400's. You have to also look at the pro's and con's of FlexConnect AP's vs local mode. I never create an ap manager interface on the newer WLC's. I have always kept the dynamic ap manager in the managemt. Traffic is tunneled and you control user traffic when it leaves the WLC.
Scott

Migration error from 8.1.7.4 to 9.2.1

Hi to everybody. I'm upgrading my production DB from 8174 to 921 with Manual upgrade. I review all the manual for this upgrading. The problem is a big problem : after launching u0801070.sql, the "Oracle 9i Packages and Types" section has marked as "INVALID". The log files created during the script is not very useful, as it tell me some "view created with compilation error" or "package created with compilation error", but it never tell me which one or where it is in the scripts. Can anybody help me ?

Hi,
I migrated successfully from 8.1.7 to 9.2 before.
You can follow my steps:
migrate steps:
==============================
startup migrate
SPOOL /tmp/upgrade.log
@u0801070.sql
SELECT comp_name, version, status
FROM dba_registry;
@cmpdbmig.sql; --this sql may take some time, please wait...
SELECT comp_name, version, status
FROM dba_registry;
COMP_NAME VERSION STATUS
Oracle9i Catalog Views 9.2.0.7.0 VALID
Oracle9i Packages and Types 9.2.0.7.0 VALID
JServer JAVA Virtual Machine 9.2.0.7.0 VALID
Oracle9i Java Packages 9.2.0.7.0 VALID
Oracle XDK for Java 9.2.0.2.0 UPGRADED
SPOOL OFF
SHUTDOWN IMMEDIATE
startup
@utlrp.sql
SELECT count(*) FROM dba_objects WHERE status='INVALID';
SELECT distinct object_name,owner FROM dba_objects WHERE status='INVALID';
SELECT comp_name, version, status
FROM dba_registry;

Migrate wiki from MLS to MAVS

Dear Folks,
I want to provide a solution on how to migrate the Wiki from a Mountain Lion Server to a Mavericks Server. Both Servers are running but in different locations and they can't communicate directly with each other. Upgrading the MLS was no option - after what I had read in hundreds of threads. The MLS is a 10.8.5 (with the latest version of server.app up until the 15th of October 2013) and Mavericks a 10.9.1 (with the latest version of server.app up until New Years Eve).
I hadn't done it without the help of Andreas from Metalab in Vienna (lovely Hackspace) - so the grace goes to him!!
First things first - he isolated 2 issues on MLS - revolving postgresql Version AND Socket! Thank you Apple-developers you did a great job here - since this product is called „The Server for everyone“ I believe either the title is incorrect or some guys haven’t understood what the a server for everyone implies - since everyone isn’t a geek, nerd, developer etc. - think about it!
Trying to connect to psql on MLS:
bash-3.2# psql
psql: could not connect to server: No such file or directory
          Is the server running locally and accepting
          connections on Unix domain socket "/var/pgsql_socket/.s.PGSQL.5432"?
What?!
bash-3.2# serveradmin status postgres
postgres:state = "RUNNING"
What?!
So he started digging on MLS:
bash-3.2# netstat -na|grep LISTEN
nothing tangible here - nothing ist listening to 5432
Dig deeper on MLS:
bash-3.2# lsof | grep postgre
          #output omitted for clarity
postgres_ 2546      _postgres   10u     unix 0xa319efaa0af41357       0t0         /Library/Server/PostgreSQL For Server Services/Socket/.s.PGSQL.5432
postgres_ 2547      _postgres   10u     unix 0xa319efaa0af3fbe7       0t0         /Library/Server/PostgreSQL For Server Services/Socket/.s.PGSQL.5432
          #output omitted for clarity
postgres_ 2548      _postgres   10u     unix 0xa319efaa0af3fa57       0t0         /Library/Server/PostgreSQL For Server Services/Socket/.s.PGSQL.5432
          #output omitted for clarity
postgres_ 2549      _postgres   10u     unix 0xa319efaa0af3f8c7       0t0         /Library/Server/PostgreSQL For Server Services/Socket/.s.PGSQL.5432
          #output omitted for clarity
postgres_ 3102      _postgres   10u     unix 0xa319efaa0b220357       0t0         /Library/Server/PostgreSQL For Server Services/Socket/.s.PGSQL.5432
          #output omitted for clarity
Hold the horses still - that got him thinking! How does that fit to the output of the psql-command just seconds earlier (and I literally mean seconds!) Can you see it?
The truth is, the Socket is at:
/Library/Server/PostgreSQL For Server Services/Socket/.s.PGSQL.5432
but is expected by psql to be in /var/psql_socket/.s.PGSQL.5432!
Expected What?!
Verified it again on MLS:
bash-3.2# psql
psql: could not connect to server: No such file or directory
          Is the server running locally and accepting
          connections on Unix domain socket "/var/pgsql_socket/.s.PGSQL.5432"?
bash-3.2# psql --help
Yep - when postgresql was compiled obviously somebody was sitting on his fingers - during implementation nobody had told psql the path for the socket at the "new" location?! Ergo - psql is looking for the socket in the default location - where it is not.
Then, with the help, he managed it to get in.
Trying to get in on MLS:
bash-3.2# psql -p "/Library/Server/PostgreSQL For Server Services/Socket/.s.PGSQL.5432"
psql: invalid port number: "/Library/Server/PostgreSQL For Server Services/Socket/.s.PGSQL.5432"
Trying again on MLS:
bash-3.2# psql -h "/Library/Server/PostgreSQL For Server Services/Socket/.s.PGSQL.5432"
psql: could not connect to server: Not a directory
          Is the server running locally and accepting
          connections on Unix domain socket "/Library/Server/PostgreSQL For Server Services/Socket/.s.PGSQL.5432/.s.PGSQL.5432"?
And again - almost there on MLS:
bash-3.2# psql -h "/Library/Server/PostgreSQL For Server Services/Socket/" -p 5432
psql: FATAL: role "root" does not exist
Typo:
bash-3.2# psql -h "/Library/Server/PostgreSQL For Server Services/Socket/" -p 5432 -u colab
psql: invalid option -- u
Try "psql --help" for more information.
And - tata - he was in on MLS:
bash-3.2# psql -h "/Library/Server/PostgreSQL For Server Services/Socket/" -p 5432 template1 collab
psql (9.1.9, server 9.2.4)
WARNING: psql version 9.1, server version 9.2.
         Some psql features might not work.
Type "help" for help.
template1=#
Lets find the databases and roles on MLS:
template1=# \l
                                   List of databases
       Name        |   Owner    | Encoding | Collate | Ctype |    Access privileges
-------------------+------------+----------+---------+-------+------------------ -------
caldav            | caldav     | UTF8     | C       | C     |
collab            | collab     | UTF8     | C       | C     |
device_management | _devicemgr | UTF8     | C       | C     |
postgres          | _postgres | UTF8     | C       | C     |
template0         | _postgres | UTF8     | C       | C     | =c/_postgres           +
                   |            |          |         |       | _postgres=CTc/_postgres
template1         | _postgres | UTF8     | C       | C     | _postgres=CTc/_postgres+
                   |            |          |         |       | =c/_postgres
webauth           | webauth    | UTF8     | C       | C     |
(7 rows)
And there are the roles on MLS:
template1=# \du
                              List of roles
Role name |                   Attributes                   | Member of
------------+------------------------------------------------+-----------
_devicemgr | Create DB                                      | {}
_postgres | Superuser, Create role, Create DB, Replication | {}
caldav     | Create DB                                      | {}
collab     | Superuser, Create role, Create DB              | {}
webauth    | Superuser, Create role, Create DB              | {}
Aaaaah - so there is a role collab and a database collab! Lets connect to the "right" database and dive into it on MLS.
template1=# \q
bash-3.2# psql -h "/Library/Server/PostgreSQL For Server Services/Socket/" -p 5432 collab collab
psql (9.1.9, server 9.2.4)
WARNING: psql version 9.1, server version 9.2.
         Some psql features might not work.
Type "help" for help.
collab=# \d
                   List of relations
Schema |            Name             | Type | Owner
--------+-----------------------------+-------+--------
public | blog_entity                 | table | collab
public | document_entity             | table | collab
public | entity                      | table | collab
public | entity_acls                 | table | collab
public | entity_acls_defaults        | table | collab
public | entity_attrs                | table | collab
public | entity_changesets           | table | collab
public | entity_comment              | table | collab
public | entity_lock                 | table | collab
public | entity_preview              | table | collab
public | entity_private_attrs        | table | collab
public | entity_tag                  | table | collab
public | entity_type                 | table | collab
public | file_entity                 | table | collab
public | filedata_entity             | table | collab
public | filename_reservation        | table | collab
public | global_settings             | table | collab
public | groups                      | table | collab
public | migration_entity            | table | collab
public | migration_status            | table | collab
public | migrationplaceholder_entity | table | collab
public | notification                | table | collab
public | page_entity                 | table | collab
public | podcast_entity              | table | collab
public | podcast_episode_entity      | table | collab
public | preview_queue               | table | collab
public | project_entity              | table | collab
public | relationship                | table | collab
public | savedquery_entity           | table | collab
public | search_index                | table | collab
public | search_stat                 | table | collab
public | session                     | table | collab
public | subscription                | table | collab
public | user_activity               | table | collab
public | user_entity                 | table | collab
public | user_entity_favorites       | table | collab
public | user_entity_read_status     | table | collab
public | user_entity_unread_status   | table | collab
public | user_entity_updates         | table | collab
public | user_entity_watched         | table | collab
public | user_readall_time           | table | collab
(41 rows)
That looks fantastic! Lets start dumping with some help through pg_dump --help and then issuing the following on MLS:
bash-3.2# pg_dump -h "/Library/Server/PostgreSQL For Server Services/Socket/" -p 5432 -f /Volumes/USBSTICK/wikidatabase -U collab collab
pg_dump: server version: 9.2.4; pg_dump version: 9.1.9
pg_dump: aborting because of server version mismatch
What?! How could that be?! The commands refer to an older version?!
Start digging again on MLS!
bash-3.2# which psql
/usr/bin/psql
bash-3.2# which pg_dump
/usr/bin/pg_dump
That's where I stepped in and told Andreas "Hey - ahm - I know of a path completely different…. /Applications/Server.app/.….". Thanks mate!
Dig again on MLS!
bash-3.2# /Applications/Server.app/Contents/ServerRoot/usr/bin/pg_dump --version
pg_dump (PostgreSQL) 9.2.4
Lovely - that one looks good - lets use it. All of that got us finally to the right command on MLS.
bash-3.2# /Applications/Server.app/Contents/ServerRoot/usr/bin/pg_dump -h "/Library/Server/PostgreSQL For Server Services/Socket/" -p 5432 -f /Volumes/USBSTICK/wikidatabase -U collab collab
There it is - the whole Database on the stick - finally - it took Andreas only 5 Minutes - approximately? I am just baffled.
Then I copied the Folders from the /Library/Server/Wiki/FileData of the MLS to the exact same location on the MAVS and sat permission - navigating to /Library/Server/Wiki first:
bash-3.2# chown -R _teamsserver:_teamsserver FileData/
bash-3.2# chmod -R +a "_www allow read" FileData/
I compared the the collab DB on the MLS with the MAVS collab DB to see the differences - BTW - the Socket has moved again on the MLS! Move up in this documentary and you’ll see on how to find it on MAVS.
bash-3.2# lsof | grep 5432
          #output omitted for clarity
postgres_   382    _teamsserver    3u     unix 0x399cdd6eeea1efe1       0t0         /Library/Server/Wiki/PostgresSocket/.s.PGSQL.5432
          #output omitted for clarity
bash-3.2# psql -h "/Library/Server/Wiki/PostgresSocket/" -p 5432 collab collab
psql (9.2.4)
Type "help" for help.
collab=# \d
                   List of relations
Schema |            Name             | Type | Owner
--------+-----------------------------+-------+--------
public | adc_device_entity           | table | collab
public | adc_team_entity             | table | collab
public | blog_entity                 | table | collab
public | bot_entity                  | table | collab
public | botgroup_entity             | table | collab
public | botrun_entity               | table | collab
public | build_agent_registry        | table | collab
public | document_entity             | table | collab
public | email_notification          | table | collab
public | entity                      | table | collab
public | entity_acls                 | table | collab
public | entity_acls_defaults        | table | collab
public | entity_attrs                | table | collab
public | entity_auditlog             | table | collab
public | entity_changesets           | table | collab
public | entity_comment              | table | collab
public | entity_lock                 | table | collab
public | entity_preview              | table | collab
public | entity_private_attrs        | table | collab
public | entity_tag                  | table | collab
public | entity_type                 | table | collab
public | file_entity                 | table | collab
public | filedata_entity             | table | collab
public | filename_reservation        | table | collab
public | global_settings             | table | collab
public | groups                      | table | collab
public | migration_entity            | table | collab
public | migration_status            | table | collab
public | migrationplaceholder_entity | table | collab
public | page_entity                 | table | collab
public | podcast_entity              | table | collab
public | podcast_episode_entity      | table | collab
public | preview_queue               | table | collab
public | relationship                | table | collab
public | savedquery_entity           | table | collab
public | scm_commit_entity           | table | collab
public | scm_server                  | table | collab
public | scmrepogroup_entity         | table | collab
public | search_index                | table | collab
public | search_stat                 | table | collab
public | session                     | table | collab
public | subscription                | table | collab
public | timeseries                  | table | collab
public | timeseries_toc              | table | collab
public | user_activity               | table | collab
public | user_entity                 | table | collab
public | user_entity_favorites       | table | collab
public | user_entity_read_status     | table | collab
public | user_entity_unread_status   | table | collab
public | user_entity_updates         | table | collab
public | user_entity_watched         | table | collab
public | user_readall_time           | table | collab
public | visible_entity_tag          | view | collab
public | wiki_entity                 | table | collab
public | work_queue                  | table | collab
public | work_schedule               | table | collab
public | work_schedule_recurrence    | table | collab
public | work_schedule_status        | table | collab
(58 rows)
Hmmm - 41 tables in the old, and 58 in the new. What am I going to do? To be able to roll back I dumped the MAVS DB before I would do anything else.
I had to decide between trying to take the old MLS DB and just pg_restore it into the MAVS DB, or - trying to upgrade the MLS instance to MAVS. I was afraid doing the upgrade since the MLS was a mess. At the end I would decide to go for the latter - since I had dumps. It took a while but - hey - it worked. Everything in place! Wiki running - everything else, too! The database has now 58 tables - ok - lets dump it. Notice again - no need to specify the proper version of pg_dump, but the Socket has changed from MLS to MAVS - again - you could see this when I connected with psql as well!
Please use (-F c) compression when dumping - otherwise you’ll receive a nasty error when importing it at the MAVS.
bash-3.2# pg_dump -h "/Library/Server/Wiki/PostgresSocket/" -p 5432 -F c -f /Volumes/USBSTICK/MLSafterupgrade2MAVS_collab_db_compressed.pgdump -U collab collab
I then copied the dump to the server - the Desktop of the administrativ account - I did it through screensharing which is accessible after establishing a VPN to the location the server resides in.
Unfortunately the command for pg_restore has a different syntax then the pg_dump. Use pg_dump --help to see the details. I’ll explain it quickly:
-c is to clean entries in the target tables (you must not use capital c)
-d specifies the database into which you would like to restore
-h specifies (again) where the DB is - the socket
-p the port to use
-U is the role that likes to work on the DB
you must not use -f since it’s not needed
bash-3.2# pg_restore -c -d collab -h "/Library/Server/Wiki/PostgresSocket/" -p 5432 /Volumes/OSXDATA/Users/macminiadmin/Desktop/MLScollabdb_compressed.pgdump -U collab
pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error from TOC entry 2466; 2605 16639 CAST CAST (text[] AS public.hstore)
pg_restore: [archiver (db)] could not execute query: ERROR: cannot drop cast from text[] to public.hstore because extension hstore requires it
HINT: You can drop extension hstore instead.
    Command was: DROP CAST (text[] AS public.hstore);
pg_restore: [archiver (db)] Error from TOC entry 1816; 2616 16636 OPERATOR CLASS hash_hstore_ops collab
pg_restore: [archiver (db)] could not execute query: ERROR: cannot drop operator class hash_hstore_ops for access method hash because extension hstore requires it
HINT: You can drop extension hstore instead.
    Command was: DROP OPERATOR CLASS public.hash_hstore_ops USING hash;
          #output omitted for clarity
I saw quite a lot errors (some revolving functions etc.) - however, it worked. Wikis are present again on the MAVS. Not without the initial help of Andreas - thank you once again!
I would like to recommend to everyone joining hackerspaces in their location. I do not know them in other areas - I can only speak for the metalab in Vienna. Fantastic place with fantastic, very knowledgable people. I would also recommend reading a book like PostgreSQL 9 Admin Cookbook - this helped me quit a lot as well. It’s available through various stores - virtual or real - choose what you prefer.

Frustrated, not angry...
Well folks. I think this is goodbye to OS X Server - the server that I thought was much easier to use. I've followed instructions on this forum and several others over the past 7 months. It's cost me so much time and headache.
Migrating wikis from Mountain Lion Server to Mavericks server has yet to work
Upgrading our Mountain Lion Server to Mavericks leaves us without wiki, calendar, and other services
Apple support docs don't do the trick
Phone calls with Apple support techs haven't provided any solutions.
Our current Mountain Lion Server suddenly lost all filesharing authentication capability and Apple enterprise solutions haven't been able to figure this one out.
I'm stuck with a server with broken mountain lion server I have never been able to upgrade and/or migrate and ultimately would be left to copy/paste wikis to a fresh Mavericks server, export/import calendars from each client station, and contacts - I don't even know how that's going to work.
I believe in keeping IT folks employed, but...
The support from Apple seems so marginal (just for the server) and the plethora of problems with upgrading to Mavericks server and/or the manual fight to only potentially get it done seems very un-Apple like and just downright counter to what Apple represents.
So I'll think different...
Our server will be relegated to a client machine with simple file sharing. Perhaps We'll buy Daylite to assume some of the responsibilites. Truth is, even when things were working, it was always flaky in some way.
I really wanted to employ OS X Server in an efficient way, but it's been more trouble than I can accomodate.
Fortunately I am not an average client user nor a novice, so working in terminal is comfortable.
Perhaps in a few years or so, I'll reconsider, but my experience with OS X server on Mountain Lion and Mavericks has affected my trust.
Thanks for all of the help to those who provided instructions, workarounds, directions toward solutions, etc.
For those of you who had a successful migration - consider yourself lucky.
...by the way...after finishing the incredible instructions on this page (and i sincerely mean that despite them not working for me) the result was a wiki page that looked like this
Caught exception "[<CSEntityPlaceholder 0x7fb2d15d5910> valueForUndefinedKey:]: this class is not key value coding-compliant for the key externalID." [NSUnknownKeyException] executing route /app-context/wiki/:
0   CoreFoundation                      0x00007fff8a0fe25c __exceptionPreprocess + 172
1   libobjc.A.dylib                     0x00007fff8da20e75 objc_exception_throw + 43
2   CSService                           0x0000000104bc7957 -[CSLocalServiceProxy forwardInvocation:] + 1229
3   CoreFoundation                      0x00007fff8a05c1c4 ___forwarding___ + 452
4   CoreFoundation                      0x00007fff8a05bf78 _CF_forwarding_prep_0 + 120
5   CSService                           0x0000000104bf9573 __27-[CSAppContextService init]_block_invoke240 + 180
6   CSService                           0x0000000104bdf81a __53-[CSRoutingHTTPConnection httpResponseForMethod:URI:]_block_invoke + 95
7   CSService                           0x0000000104be2d6c -[CSHTTPBackgroundResponse bounce:] + 286
8   Foundation                          0x00007fff9073976b __NSThread__main__ + 1318
9   libsystem_pthread.dylib             0x00007fff8bc58899 _pthread_body + 138
10 libsystem_pthread.dylib             0x00007fff8bc5872a _pthread_struct_init + 0
11 libsystem_pthread.dylib             0x00007fff8bc5cfc9 thread_start + 13

SNMP OID for AssociatedAPs in Virtual WLC 7.4.100.0

Hello Guys!
I need you help for something that I need to do to monitor my Wi-FI network.
I'm using a Virtual WLC (SW Ver 7.4.100.0) where most that 30 APs are associated with, but I would like to monitor each disaciossiation of APs using SNMP. After some search, I have found this OID .1.3.6.1.4.1.14179.2.1.1.1.38 on some forums but it doesn't work, I see random number in my monitoring tool.
Do you know if there is any another OID to use with this software version or maybe if I have to upgrade to ver7.6 or ver8?
Thanks in advance,
Kevin

I'm assuming you don't own a license for Cisco Prime Infrastructure
One thing you can do is send SNMP traps to your monitoring software from the WLC (I've never used virtual WLC but my assumption is most options are the same. If your software doesn't support SNMP Traps consider a different monitoring software...
Go to Management > SNMP > Trap Receivers and set up your receiver
Then to to Management > SNMP > Trap ControlsHere is where you set what traps are sent via SNMP. If you see the "AP" tab you can set several things.
If you only want to see if an AP is dropping off the network and the above doesn't work, you could just put dhcp reservations on your APs and have your software ping it. This of course is only if its off network, not if it simply disassociates.

Virtualized WLC + Prime + MSE solution

Dear all,
we are facing some problem to deploy a virtualized localization solution made of WLC, Prime Infrastructure and MSE.
We constructed, in our lab, on a UCS C220M3 with VMWare 5.1 the following solution:
Virtual WLC version 7.3.101 (ip address 10.0.1.249)
Prime Infrastructure 1.2.0.103 (ip address 10.0.1.250)
Virtual MSE 7.3.101 (ip address 10.0.1.247)
WLC is working properly, can register APs and is properly integrated with the Prime. For the localization solution we deployed three access points:
-one 3502 in flex connect mode
-two 1142 in monitor mode
The problem came out when we started to work with the MSE. MSE has been registered inside Prime and synchronized with maps and controller.
After that we checked the maps but no information was displayed. So we started facing the problem and we found that the NMSP protocol remained inactive even if the troubleshooting windows didn't report any explicit issue.
At this stage we started checking the debug messages and in particular, for the NMSP we countinuously received the follwing message:
*nmspRxServerTask: Nov 17 17:55:09.777: Allocated new NMSP connection 0
*nmspRxServerTask: Nov 17 17:55:09.778: sslConnectionInit: SSL_new() conn ssl 0x2aaaae71ab88
*nmspRxServerTask: Nov 17 17:55:09.778: sslConnectionInit: SSL_do_handshake for conn ssl 0x2aaaae71ab88, conn state: INIT, SSL state: HANDSHAKING
*nmspRxServerTask: Nov 17 17:55:09.778: -- returns WANT_READ for conn ssl 0x2aaaae71ab88
*nmspRxServerTask: Nov 17 17:55:09.778: sslConnectionInit() success with Connection state: INIT, SSL state: HANDSHAKING
*nmspRxServerTask: Nov 17 17:55:09.785: doSSLRecvLoop: Handshake has not completed for conn 0
*nmspRxServerTask: Nov 17 17:55:09.785: sslConnectionInit: SSL_do_handshake for conn ssl 0x2aaaae71ab88, conn state: INIT, SSL state: HANDSHAKING
*nmspRxServerTask: Nov 17 17:55:09.785: -- returns WANT_READ for conn ssl 0x2aaaae71ab88
*nmspRxServerTask: Nov 17 17:55:10.100: doSSLRecvLoop: Handshake has not completed for conn 0
*nmspRxServerTask: Nov 17 17:55:10.100: sslConnectionInit: SSL_do_handshake for conn ssl 0x2aaaae71ab88, conn state: INIT, SSL state: HANDSHAKING
*nmspRxServerTask: Nov 17 17:55:10.100: -- handshake failed for conn ssl 0x2aaaae71ab88,error = error:00000000:lib(0):func(0):reason(0)
*nmspRxServerTask: Nov 17 17:55:10.100: freeing Nmsp conn ssl 0x2aaaae71ab88, conn id 0
Also the statistics for the NMSP protocol emphatized an SSL error:
(Cisco Controller) >show nmsp statistics summary
NMSP Global Counters
Client Measure Send Fail......................... 0
Send RSSI with no entry.......................... 0
APP msg too big.................................. 0
Failed Select on Accept Socket................... 0
Failed SSL write................................. 0
Partial SSL write................................ 0
SSL write returned zero.......................... 0
SSL write attempts to want read.................. 0
SSL write attempts to want write................. 0
SSL write got default error...................... 0
SSL write max data length sent................... 0
SSL write max attempts to write in loop.......... 0
SSL read returned zero........................... 0
SSL read attempts to want read................... 0
SSL read attempts to want write.................. 0
SSL read got default error....................... 0
Failed SSL read - Con Rx buf freed............... 0
Failed SSL read - Con/SSL freed.................. 0
Max records read before exiting SSL read......... 0
--More-- or (q)uit
Highest Prio Tx Q full........................... 0
Normal Prio Tx Q full............................ 0
Highest Prio Tx Q Sent........................... 0
Normal Prio Tx Q Sent............................ 0
Highest Prio Tx Q count.......................... 0
Normal Prio Tx Q count........................... 0
Messages sent by APPs to Highest Prio TxQ........ 0
Max Measure Notify Msg........................... 0
Max Info Notify Msg.............................. 0
Max Highest Prio Tx Q Size....................... 0
Max Normal Prio Tx Q Size........................ 0
Max Rx Size...................................... 1
Max Info Notify Q Size........................... 0
Max Client Info Notify Delay..................... 0
Max Rogue AP Info Notify Delay................... 0
Max Rogue Client Info Notify Delay............... 0
Max Client Measure Notify Delay.................. 0
Max Tag Measure Notify Delay..................... 0
Max Rogue AP Measure Notify Delay................ 0
Max Rogue Client Measure Notify Delay............ 0
Max Client Stats Notify Delay.................... 0
Max RFID Stats Notify Delay...................... 0
RFID Measurement Periodic........................ 0
--More-- or (q)uit
RFID Measurement Immediate....................... 0
SSL Handshake failed............................. 1319
NMSP Rx detected con failure..................... 0
NMSP Tx detected con failure..................... 0
NMSP Tx buf size exceeded........................ 0
NMSP Tx Invalid msg id .......................... 0
Reconnect Before Conn Timeout.................... 0
Rogue AP Info Changed DB Full.................... 0
Rogue AP Meas Changed DB Full.................... 0
Rogue Client Info Changed DB Full................ 0
Rogue Client Meas Changed DB Full................ 0
Looking around the Internet we found a similar case where the issue was solved dealing with the authorization list upon the wireless lan controller but after the suggested check we saw that the MSE is correctly authorized inside the controller: Here's the "show auth-list" on the WLC:
(Cisco Controller) >show auth-list
Authorize MIC APs against AAA ................... disabled
Authorize LSC APs against Auth-List ............. disabled
APs Allowed to Join
AP with Manufacturing Installed Certificate.... no
AP with Self-Signed Certificate................ no
AP with Locally Significant Certificate........ no
Mac Addr                  Cert Type    Key Hash
00:0c:29:68:c8:57         LBS-SSC      6d6703ef9cccfb5a430e04b3ad128f8170fb435c
that perfectly matches what was on the MSE:
cmd> show server-auth-info
invoke command: com.aes.server.cli.CmdGetServerAuthInfo
AesLog queue high mark: 50000
AesLog queue low mark: 500
Server Auth Info
MAC Address: 00:0c:29:68:c8:57
Key Hash: 6d6703ef9cccfb5a430e04b3ad128f8170fb435c
Certificate Type: SSC
Finally I tried to look around the MSE logs and here what I found tailing the locserver errors:
==> /opt/mse/logs/locserver/locserver-error-0-0.log <==
11/17/12 17:54:13.513 ERROR[locp] [36] Error in ConnectHandler(endPoint) <LocpSessionTarget mode=CLIENT><LocpEndPoint status=HANDSHAKE totalBytesSent=72000 totalBytesReceived=1315800><LocpEndPoint.Key host=10.0.1.249 port=16113/></LocpEndPoint></LocpSessionTarget>
11/17/12 17:54:13.513 ERROR[com.aes] [36] [ConnectHandler:handle-09] THROW
javax.net.ssl.SSLHandshakeException: General SSLEngine problem
        at com.sun.net.ssl.internal.ssl.Handshaker.checkThrown(Handshaker.java:1015)
        at com.sun.net.ssl.internal.ssl.SSLEngineImpl.checkTaskThrown(SSLEngineImpl.java:485)
        at com.sun.net.ssl.internal.ssl.SSLEngineImpl.writeAppRecord(SSLEngineImpl.java:1128)
        at com.sun.net.ssl.internal.ssl.SSLEngineImpl.wrap(SSLEngineImpl.java:1100)
        at javax.net.ssl.SSLEngine.wrap(SSLEngine.java:452)
        at com.aes.server.locp.transport.IOChannelSecure.doHandshake(IOChannelSecure.java:230)
        at com.aes.server.locp.transport.LocpTransportService$ConnectHandler.handle(LocpTransportService.java:354)
        at com.aes.server.locp.transport.ChannelEventDispatcherImpl$HandlerTask.run(ChannelEventDispatcherImpl.java:348)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:662)
Caused by: javax.net.ssl.SSLHandshakeException: General SSLEngine problem
        at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174)
        at com.sun.net.ssl.internal.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1528)
        at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:243)
        at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:235)
        at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1206)
        at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:136)
        at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:593)
        at com.sun.net.ssl.internal.ssl.Handshaker$1.run(Handshaker.java:533)
        at java.security.AccessController.doPrivileged(Native Method)
        at com.sun.net.ssl.internal.ssl.Handshaker$DelegatedTask.run(Handshaker.java:952)
        at com.aes.server.locp.transport.IOChannelSecure.doTasks(IOChannelSecure.java:265)
        at com.aes.server.locp.transport.IOChannelSecure.doHandshake(IOChannelSecure.java:193)
        ... 8 more
Caused by: sun.security.validator.ValidatorException: No trusted certificate found
        at sun.security.validator.SimpleValidator.buildTrustedChain(SimpleValidator.java:346)
        at sun.security.validator.SimpleValidator.engineValidate(SimpleValidator.java:111)
        at sun.security.validator.Validator.validate(Validator.java:218)
        at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:126)
        at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:209)
        at com.sun.net.ssl.internal.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:249)
        at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1185)
        ... 15 more
Everything seems to bring to a certificate error but I don't know, from a side if this is the right direction of investigfation and, from the other, where to check for this certificate and how to find a solution.
May someone give us some help?
Thank in advance to all.
Regards.
Marco

Hi Pongsatorn,
This is caused by a bug with the ID - CSCub42987. And yes, it only applies to the Virtual WLC's.
Here is the work-around: (need to be performed from the CLI of the MSE as follows)
1. cmdshell
2. config unauthenticated-nmsp true
3. exit
4. service msed restart
Ram.

Cisco LAP 2602 can not join Virtual WLC

dear all,
i just install Virtual WLC and i remove WLC 2504 , i install & configured it , but LAP can not join. it was work fine with WLC 2504.
i used the same network topology with the old WLC.
i receive this error logs.
*spamApTask4: Feb 04 06:01:30.082: <<<< Start of CAPWAP Packet >>>>
*spamApTask4: Feb 04 06:01:30.082: CAPWAP Control mesg Recd from 10.192.200.93, Port 26711
*spamApTask4: Feb 04 06:01:30.082: HLEN 4, Radio ID 0, WBID 1
*spamApTask4: Feb 04 06:01:30.082: Msg Type : CAPWAP_DISCOVERY_REQUEST
*spamApTask4: Feb 04 06:01:30.082: Msg Length : 155
*spamApTask4: Feb 04 06:01:30.082: Msg SeqNum : 0
*spamApTask4: Feb 04 06:01:30.082:
*spamApTask4: Feb 04 06:01:30.082: Type : CAPWAP_MSGELE_DISCOVERY_TYPE, Length 1
*spamApTask4: Feb 04 06:01:30.082: Discovery Type : CAPWAP_DISCOVERY_TYPE_UNKNOWN
*spamApTask4: Feb 04 06:01:30.082:
*spamApTask4: Feb 04 06:01:30.082: Type : CAPWAP_MSGELE_WTP_BOARD_DATA, Length 62
*spamApTask4: Feb 04 06:01:30.083: Vendor Identifier : 0x00409600
*spamApTask4: Feb 04 06:01:30.083: WTP_SERIAL_NUMBER : AIR-CAP2602E-I-K9
*spamApTask4: Feb 04 06:01:30.083:
*spamApTask4: Feb 04 06:01:30.083: Type : CAPWAP_MSGELE_WTP_DESCRIPTOR, Length 40
*spamApTask4: Feb 04 06:01:30.083: Maximum Radios Supported : 2
*spamApTask4: Feb 04 06:01:30.083: Radios in Use : 2
*spamApTask4: Feb 04 06:01:30.083: Encryption Capabilities : 0x00 0x01
*spamApTask4: Feb 04 06:01:30.083:
*spamApTask4: Feb 04 06:01:30.083: Type : CAPWAP_MSGELE_WTP_FRAME_TUNNEL, Length 1
*spamApTask4: Feb 04 06:01:30.083: WTP Frame Tunnel Mode : NATIVE_FRAME_TUNNEL_MODE
*spamApTask4: Feb 04 06:01:30.083:
*spamApTask4: Feb 04 06:01:30.083: Type : CAPWAP_MSGELE_WTP_MAC_TYPE, Length 1
*spamApTask4: Feb 04 06:01:30.083: WTP Mac Type : SPLIT_MAC
*spamApTask4: Feb 04 06:01:30.083:
*spamApTask4: Feb 04 06:01:30.083: Type : CAPWAP_MSGELE_VENDOR_SPECIFIC_PAYLOAD, Length 10
*spamApTask4: Feb 04 06:01:30.083: Vendor Identifier : 0x00409600
*spamApTask4: Feb 04 06:01:30.083:
IE : UNKNOWN IE 207
*spamApTask4: Feb 04 06:01:30.083: IE Length : 4
*spamApTask4: Feb 04 06:01:30.083: Decode routine not available, Printing Hex Dump
*spamApTask4: Feb 04 06:01:30.083: 00000000: 03 00 00 01 ....
*spamApTask4: Feb 04 06:01:30.083:
*spamApTask4: Feb 04 06:01:30.083: Type : CAPWAP_MSGELE_VENDOR_SPECIFIC_PAYLOAD, Length 12
*spamApTask4: Feb 04 06:01:30.083: Vendor Identifier : 0x00409600
*spamApTask4: Feb 04 06:01:30.083:
IE : RAD_NAME_PAYLOAD
*spamApTask4: Feb 04 06:01:30.083: IE Length : 6
*spamApTask4: Feb 04 06:01:30.083: Rad Name :
*spamApTask4: Feb 04 06:01:30.083: CEO_AP
*spamApTask4: Feb 04 06:01:30.083: <<<< End of CAPWAP Packet >>>>
*spamApTask4: Feb 04 06:01:30.083: dc:a5:f4:8c:ff:30 Discovery Request from 10.192.200.93:26711
*spamApTask4: Feb 04 06:01:30.083: dc:a5:f4:8c:ff:30 ApModel: AIR-CAP2602E-I-K9
*spamApTask4: Feb 04 06:01:30.083: dc:a5:f4:8c:ff:30 Join Priority Processing status = 0, Incoming Ap's Priority 1, MaxLrads = 200, joined Aps =0
*spamApTask4: Feb 04 06:01:30.083: apModel: AIR-CAP2602E-I-K9
*spamApTask4: Feb 04 06:01:30.083: apType = 26 apModel: AIR-CAP2602E-I-K9
*spamApTask4: Feb 04 06:01:30.083: apType: Ox1a bundleApImageVer: 8.0.110.0
*spamApTask4: Feb 04 06:01:30.083: version:8 release:0 maint:110 build:0
*spamApTask4: Feb 04 06:01:30.083: dc:a5:f4:8c:ff:30 Discovery Response sent to 10.192.200.93 port 26711
*spamApTask4: Feb 04 06:01:30.083: dc:a5:f4:8c:ff:30 Discovery Response sent to 10.192.200.93:26711
Please any help.

dear
yes the wlc 2504  is 8.0.110 but because its damaged i replaced it with new vWLC v 8.0.110.
also i can not put the LAP in flexconnect until its joint.

Conversion from physical to virtual server

Our server technology group wants to convert our physical
server that contains the RoboEngine to a virtual server (using ESX
VMware). We are using RoboHelp 5 to publish WebHelp to the
RoboEngine. Has anyone else converted from a physical to a virtual
server? If so, could you tell me about any problems you
encountered?
Thanks,
Liz

Hello Nelson,
There are quite lot of things in TMG which are dependent on Hardware.
If you want to migrate from physical to virtual server, you can follow the steps here which are recommended/supported way of doing it.
Though this article is for ISA to TMG migration, still you can follow the same steps for Physcial to Virtual migration.
http://technet.microsoft.com/en-us/library/dd440994.aspx
Please let us know, how it goes!

Virtual WLC software

Hi!
I've got a license PAK L-AIR-CTVM-5-K9. So I believe I need to download the virtual WLC software, install it on ESX and load the license file. But I'm unable to download the .ova file from cisco support page because I've no valid service contract.So I'm stuck here. Is there any alternative source on cisco.com to download the controller software itself?

Contact the vendor who sold you the license and tell them to get you a valid Cisco Service Contract attached to your CCO account.
Alternatively, send an email to [email protected] and give them your CCO account, your PAK license key and ask them to associate the two.

Migrate SSL from iWS4.1 to iWS6.0

I would like to migrate a secure server instance from iWS4.1 to a virtual server in iWS6.0.
For example, on iWS4.1, I have 2 server instances, server1 and server1-secure. I want to setup a single server instance on iWS6.0 and call it server1, with a virtual server for the secure port, but I don't see a way to migrate the certificate to the virtual server.
Any ideas how to do this?
Thanks, Greg

I see no one posted any guidelines!
Do you have any guidelines from your porting experience?

Sap Server movement from physical to virtual(p2v)

Hi all,
We currently have two older versions of R/3 running 4.6c and 4.7ee, both IDES versions.
These versions have been out of support for some time.
We have these instances running for reference purposes. We have new versions of R/3 ECC 5.0, 6.0
also running in our company. All these versions of R/3 are IDES.
Our Windows administrators are of the opinion that servers on which the instances 4.6c and 4.7ee are running are very old,
and spares are hard to find. So they want to move these instances from a physical environment to a virtual environment.
I have read through the Note: 1409608.
It says,
SAP does not support SAP systems that are installed on Windows 32-bit
in a virtualized environment. If you plan to migrate your SAP system that is running
on native hardware on Windows 32-bit to a virtualized environment
on Windows 64-bit, it might be necessary to upgrade the SAP system to a higher release.
For these configurations, SAP recommends to migrate the SAP system to Windows x64 first
and then upgrade the SAP system.
Now, I don't think is it quite possible to upgrade 4.6c and 4.7ee to 64 bit.
License keys on windows are based on SID, Hostname, MAC address of the network card.
If we make sure that the MAC address is the same and
that its at the same place as before(sequence of multiple network cards is the same),
we can still Use the old license.
Our Windows guys say its very hard to retain the MAC address, they can try it.
So with these old versions of R/3, how can we keep them running, if they have to be moved from Physical to virtual,
as license keys and installation software is hard to get.
Regards,
Vishnu.

Hi Markus,
Thanks for your reply. Would open an OSS call.
I have looked at the note mentioned by you, and since our OS is windows, I thought the below statement
holds good in my case. From the note I have also deduced that for Windows, licenses are based only on the Hardware Key.
Am I wrong in assuming this?
Only Windows uses a hardware key that does NOT depend on the hardware.
A new installation of Windows definitely causes the hardware key to change.
I have also looked at note 793649, which says Hardware key changes only when,
1. Formatting the machine and reinstalling Windows.
2. When changing the computer name.
3. When changing the domain (it will not change back when returning to the previous domain).
Regards,
Vishnu.

SCCM 2012 hierarchy from Physical to Virtual

I have an existing standalone SCCM 2012 hierarchy on a physical server with ~ 50K clients reporting with additional servers hosting various site system roles. Now the requirement is to migrate this hierarchy on a virtual environment. Client doesn't want
to do P2V migration and wanted to have the migration done on new infra.
In current hierarchy we have client health compliance at ~90% and we have to maintain the same post migration additionally there are lot of collections, packages and deployments those needs to be successfully migrated.
Please suggest a feasible and most efficient solution for this

Client doesn't want to do P2V migration
Assuming that you have done your homework and are OK that Virtual is the way to go, the easiest way to migrate from Physical to Virtual is to carry out a P2V migration. I don't quite understand this.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Migration Accelerator to migrate machines from one Azure subscription to the Azure subscription

Hi Team,
Can we use Migration accelerator to perform test virtual machines migration from one Azure subscription to the Azure subscription?
Thanks and Regards, Mohd Zaid

No you can't, migration accelerator supports only 6 source platforms:
AWS
Hyper-V
VMware VSphere
VMware VCenter
VMware Vcloud
Physical servers
Look to this blog, i explained all the ways to migrate from anywhere to Hyper-V and Azure.
https://buildwindows.wordpress.com/2015/03/01/the-way-to-migrate-to-hyper-v-azure-introduction/
You can instead use ASR
Regards, Samir Farhat Infrastructure and Virtualization Consultant || Virtualization, Cloud, Azure ? Follow and Ask here https://buildwindows.wordpress.com

Migrate AP from WiSM to Virtual WLC

Similar Messages

Maybe you are looking for