Wireless Access

last person joined: 6 hours ago 

Access network design for branch, remote, outdoor and campus locations with Aruba access points, and mobility controllers.
Expand all | Collapse all

6.3.1 RAP database msg...

Jump to Best Answer
  • 1.  6.3.1 RAP database msg...

    Posted Oct 28, 2013 05:29 AM

    Hi all,

     

    After upgrading to 6.3.1, you of course get the following on the CLI (when logging in)...

     

    "WARNING: This controller has RAP whitelist data stored in pre-6.3 format..."

     

    After commiting the "local-userdb-ap del all" command however, this message persists in the CLI.

     

    Anybody else seeing this?



  • 2.  RE: 6.3.1 RAP database msg...

    Posted Oct 28, 2013 07:58 AM
    I am seeing it as well.
    I ran "local-userdb-ap del all" and it removed all the entries in that database.
    I then saved the config, message was still there.
    I removed all of my APs using the whitelist-db del command and re-added them with the whitelist-db add command
    message still there.
    I exported the gap-db, same thing.



  • 3.  RE: 6.3.1 RAP database msg...

    Posted Oct 28, 2013 08:12 AM

     

    try whitelist-db rap purge and then do a show whitelist-db rap to see if it is there.

     

    If you login and you can still see the message you may have to reboot the controller.

     



  • 4.  RE: 6.3.1 RAP database msg...
    Best Answer

    Posted Oct 28, 2013 08:34 AM
    no need to do the purge. Good thought though.

    Just tested on another controller.
    Simply run "local-userdb-ap del all" and reboot the controller and the message disappears.



  • 5.  RE: 6.3.1 RAP database msg...

    Posted Oct 28, 2013 08:57 AM

    Ahh, reboot fix yes? Cool. Thanks all.



  • 6.  RE: 6.3.1 RAP database msg...

    Posted Oct 28, 2013 09:09 AM
    reboot and it disappears.


  • 7.  RE: 6.3.1 RAP database msg...

    Posted Nov 03, 2013 12:58 PM

    Did you run into any issue where your RAPs no longer came back online?

     

    I'm having an issue with my RAP-2WG APs. After upgrading to 6.3.1.1, they wouldn't come back online.



  • 8.  RE: 6.3.1 RAP database msg...

    Posted Nov 04, 2013 08:15 AM

    I did see this during an upgrade to 6.3.1.0 where some RAPs didn't come back.

     

    The customer logged a TAC case and was told that it was due to bug 88314 which was fixed in 6.3.1.1.

     

    As you upgraded to 6.3.1.1, that can't be the same thing.

     

    I recommend you log it with TAC if not done so already!



  • 9.  RE: 6.3.1 RAP database msg...

    Posted Nov 04, 2013 03:20 PM

    @The.racking.monkey wrote:

    I did see this during an upgrade to 6.3.1.0 where some RAPs didn't come back.

     

    The customer logged a TAC case and was told that it was due to bug 88314 which was fixed in 6.3.1.1.

     

    As you upgraded to 6.3.1.1, that can't be the same thing.

     

    I recommend you log it with TAC if not done so already!


    Thanks.

     

    I have a Ticket with TAC already although he seemed clueless.

     

    Will see what happens.

     



  • 10.  RE: 6.3.1 RAP database msg...

    Posted Nov 04, 2013 04:07 PM

    @eosuorah wrote:

    @The.racking.monkey wrote:

    I did see this during an upgrade to 6.3.1.0 where some RAPs didn't come back.

     

    The customer logged a TAC case and was told that it was due to bug 88314 which was fixed in 6.3.1.1.

     

    As you upgraded to 6.3.1.1, that can't be the same thing.

     

    I recommend you log it with TAC if not done so already!


    Thanks.

     

    I have a Ticket with TAC already although he seemed clueless.

     

    Will see what happens.

     


    eosuorah,

     

    At any point, you can ask to have your case escalated if you feel like you are getting nowhere.