Wireless Access

last person joined: 22 hours ago 

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

U flags while provisioning AP in different groups

This thread has been viewed 6 times

  • 1.  U flags while provisioning AP in different groups

    Posted Feb 15, 2016 12:04 PM

    Hi Folks,

    Today in one site I was doing AP provisioning for some of the new APs, but everytime I am provisioing those new APs to a newly created group its shoing U flags.

    However under default group APs are coming fine.

    Even if I assign these APs to any other group (which are running) its coming fine.

    Screenshot,

    AP unprovisoined.jpg

    Any suggestion ?



  • 2.  RE: U flags while provisioning AP in different groups

    Posted Feb 15, 2016 12:23 PM
    Do you have any Virtual-APs assigned under the AP-GROUP ?

    If you do have Virtual-APs and those have VLANs assigned make sure those VLANs exist on your controller


  • 3.  RE: U flags while provisioning AP in different groups

    Posted Feb 15, 2016 12:31 PM
    Actually the setup is in production, and i am creating a new ap group and sharing the existing vaps.
    So yes same vlan does exists in controller which is being used in vap.

    Sent from Outlook Mail for Windows 10 phone


  • 4.  RE: U flags while provisioning AP in different groups

    EMPLOYEE


  • 5.  RE: U flags while provisioning AP in different groups

    Posted Feb 16, 2016 03:13 AM

    Checked,

    Nothing for that group.



  • 6.  RE: U flags while provisioning AP in different groups

    EMPLOYEE
    Posted Feb 16, 2016 03:37 AM

    Well, I suggest you open a tac case.  Without any information, we are just guessing here.



  • 7.  RE: U flags while provisioning AP in different groups

    Posted Feb 16, 2016 03:44 AM
    Yeah, That would be my next step.


  • 8.  RE: U flags while provisioning AP in different groups
    Best Answer

    Posted Feb 16, 2016 01:51 PM

    Ah,

    Forgot to do 'write mem' on master and the new AP group is assigned to a local controller.

    A write mem on master resolved  the issue. :)