Wireless Access

Reply
Contributor II

Instant AP mismatched, but VC is not?

Seeing weird behavior in Airwave. 

The customer has 30 Instant AP's that are being deployed like RAP's - 1 IAP per remote location.  So in Airwave, we have 30 AP's and 30 VC's.

 

The weird thing is that in each case, the VC shows up as "good' but the AP itself shows as "mismatched".  The audit of the device shows this:

 

 

Device Settings
Template:
        
        per-ap-settings 00:0b:86:ff:ff:ff
          g-channel 0 0
          g-external-antenna 0
          hostname 00:0b:86:ff:ff:ff
Actual    ip-address 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 ""
Desired   ip-address 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 foo.com
          swarm-mode cluster
          uplink-vlan 0
          wifi0-mode access

 

But I can not find the line "ip-address 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0 foo.com" anywhere in the template.  Where is this "foo.com" coming from?

 

Moderator

Re: Instant AP mismatched, but VC is not?

What version of AirWave are you running?  I've seen this before and foo.com is related to DE14268 which was fixed for 7.7.  I'll have to double check to see if the AOS defect is still there, but the issue is that if DHCP is used, then the foo.com appears.


Rob Gin
Senior QA Engineer - Network Services
Aruba Networks, a Hewlett Packard Enterprise Company

Re: Instant AP mismatched, but VC is not?

That is still there in 7.7.  Please open a case for tracking and resolution.  

Seth R. Fiermonti
Consulting Systems Engineer - ACCX, ACDX, ACMX
Email: seth@hpe.com
-----
If you found my post helpful, please give kudos
Moderator

Re: Instant AP mismatched, but VC is not?

It was an AOS side bug (82804) that's fixed in IAP firmware 3.4 code.  What's the current firmware of the IAPs?

 

Note on AirWave side, AirWave supports up to 3.3 for templates in 7.7 (with plans to support 3.4), and only 3.2 in the Instant GUI Config Beta.


Rob Gin
Senior QA Engineer - Network Services
Aruba Networks, a Hewlett Packard Enterprise Company
Contributor II

Re: Instant AP mismatched, but VC is not?

The IAPs are running 3.4.  Would that be the issue then, that Airwave only supports up to 3.3?

Moderator

Re: Instant AP mismatched, but VC is not?

We sould still have gotten the correct domain if the IAPs is on 3.4.  Was DHCP done while on 3.4?  Or was the IAP on a previous version when it got it's IP?  I'm double checking to see what the fix actually was.


Rob Gin
Senior QA Engineer - Network Services
Aruba Networks, a Hewlett Packard Enterprise Company
Moderator

Re: Instant AP mismatched, but VC is not?

Update:

 

The IAP 3.4 fix committed merely makes it so that APs on 3.4 that DHCP don't pre-fill domain with foo.com.

 

On the AirWave side, if you have a new IAP that's already on 3.4, then domain name will be empty / null.  But if you already had the AP monitored / managed in AirWave before upgrading to 3.4, then you'll need to perform an import settings on the AP.

 

Steps to update individual AP:

1.  Navigate to IAP (AP entry, not VC)

2.  Go to manage page

3.  Select 'import settings' at the bottom right

4.  Confirm

5.  Wait a few minutes, then the foo.com should be gone

 

Steps to update bulk APs:

1.  Navigate to a group or folder view (if folder view, you can expand top and then filter for just the non VC devices

2.  Select the 'modify devices' wrench above the list table (checkboxes will appear next to devices)

3.  Check all devices that are currently showing foo.com as domain

4.  Below the list table -> find and select 'import settings'

5.  Confirm

6.  Wait a few minutes, then the foo.com should be gone


Rob Gin
Senior QA Engineer - Network Services
Aruba Networks, a Hewlett Packard Enterprise Company
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: