Controllerless Networks

Hello All, Thank you for checking my post here. I am very new to the Aruba space and recently inherited a previously installed Aruba controllerless wifi infrastructure. I am working to repair the issues in our Airwave server, and was hoping someone might be able to help us.

On the dashboard, we see 65 AP's showing as "Down"

But when we click on the page, most AP's are in a "Verifying" or "Good" Status.
Im confused as to why the AP's show as Good, but are in the Down status.




------------------------------
Rick Reyes
------------------------------

Some general answers to your questions:

APs will show "good" if they received the last configuration, even though they are down.

For the "new" devices, you can add it to a folder designated for that site, or create a folder for that site and then go back and add them to that folder.  Make sure you have the "monitor only" option checked, otherwise Airwave will push a configuration to those devices.

There is a procedure to add a cluster to airwave.  The Airwave/Instant configuration guide is here:  https://support.hpe.com/hpesc/public/docDisplay?docId=a00099169en_us.  Look at the section under "Setting up Instant Manually".

If you are only monitoring APs, that means Airwave is not pushing configuration to those instant APs, and the configuration will always be "mismatched".  You can ignore that for now.  It is only important when you are managing the configuration from airwave.

When you navigate to the ip address of any  AP in a cluster., it will redirect to the cluster ip address, which is what you need to monitor and manage a cluster.

Good luck and I hope any of this helps.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
------------------------------

Thank you very much! Yes this helped!
Ive gone through the training videos on this site, and read through some of the documentation. I feel I am grasping the concepts, now to Test in PROD!!!

From what I understand, the Airwave Server is not necessarily required. Our airwave server is currently set to monitor only, so it's not pushing any configs, just monitoring, which is why I say not necessarily required. 
Instead of being concerned with Airwave, I will first focus on the IAP Cluster. 

Our district contains 5 subnets-
10.10.0.0
10.20.0.0
10.30.0.0
10.40.0.0
10.50.0.0

I have the 10.50.x.x AP's on the correct subnet. The master receives a dhcp address in the correct subnet. I am unable to access the VC using the 10.50 subnet address. I can however access an AP on the 10.50 network, which reroutes me to the master AP. The master AP shows as, what seems to me, to be a duplicate name and address of another site/subnet. 

Here is the VC Gui on the 10.30 Subnet. This looks to be configured correctly.



We usually have issues trying to access the web gui of our 10.30.x.x Virtual Controller. I'm assuming the reason is because the IAP's have created a cluster on the 10.50.x.x subnet, but has a duplicate address for another subnet's VC IP address.

What I would think to do is get into the master AP on the 10.50 subnet, change to the correct site name, and change the Virtual Conroller IP to the 10.50 subnet.  

Once these settings are corrected. I should now be able to reliably access our 10.30 VC, and have a new VC on the 10.50 subnet. Would this be correct? Thank you for the help!!!

------------------------------
Rick Reyes
------------------------------

Original Message:
Sent: Apr 01, 2022 09:16 PM
From: Colin Joseph
Subject: Inherited Wireless Infrastructure - Please Help

Some general answers to your questions:

APs will show "good" if they received the last configuration, even though they are down.

For the "new" devices, you can add it to a folder designated for that site, or create a folder for that site and then go back and add them to that folder.  Make sure you have the "monitor only" option checked, otherwise Airwave will push a configuration to those devices.

There is a procedure to add a cluster to airwave.  The Airwave/Instant configuration guide is here:  https://support.hpe.com/hpesc/public/docDisplay?docId=a00099169en_us.  Look at the section under "Setting up Instant Manually".

If you are only monitoring APs, that means Airwave is not pushing configuration to those instant APs, and the configuration will always be "mismatched".  You can ignore that for now.  It is only important when you are managing the configuration from airwave.

When you navigate to the ip address of any  AP in a cluster., it will redirect to the cluster ip address, which is what you need to monitor and manage a cluster.

Good luck and I hope any of this helps.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
------------------------------

That does look correct.  Make sure the virtual AP ip address is on the same subnet as the APs.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
------------------------------

Original Message:
Sent: Apr 03, 2022 01:24 PM
From: Rick Reyes
Subject: Inherited Wireless Infrastructure - Please Help

Thank you very much! Yes this helped!
Ive gone through the training videos on this site, and read through some of the documentation. I feel I am grasping the concepts, now to Test in PROD!!!

From what I understand, the Airwave Server is not necessarily required. Our airwave server is currently set to monitor only, so it's not pushing any configs, just monitoring, which is why I say not necessarily required. 
Instead of being concerned with Airwave, I will first focus on the IAP Cluster. 

Our district contains 5 subnets-
10.10.0.0
10.20.0.0
10.30.0.0
10.40.0.0
10.50.0.0

I have the 10.50.x.x AP's on the correct subnet. The master receives a dhcp address in the correct subnet. I am unable to access the VC using the 10.50 subnet address. I can however access an AP on the 10.50 network, which reroutes me to the master AP. The master AP shows as, what seems to me, to be a duplicate name and address of another site/subnet. 

Here is the VC Gui on the 10.30 Subnet. This looks to be configured correctly.



We usually have issues trying to access the web gui of our 10.30.x.x Virtual Controller. I'm assuming the reason is because the IAP's have created a cluster on the 10.50.x.x subnet, but has a duplicate address for another subnet's VC IP address.

What I would think to do is get into the master AP on the 10.50 subnet, change to the correct site name, and change the Virtual Conroller IP to the 10.50 subnet.  

Once these settings are corrected. I should now be able to reliably access our 10.30 VC, and have a new VC on the 10.50 subnet. Would this be correct? Thank you for the help!!!

------------------------------
Rick Reyes
------------------------------


Original Message:
Sent: Apr 01, 2022 09:16 PM
From: Colin Joseph
Subject: Inherited Wireless Infrastructure - Please Help

Some general answers to your questions:

APs will show "good" if they received the last configuration, even though they are down.

For the "new" devices, you can add it to a folder designated for that site, or create a folder for that site and then go back and add them to that folder.  Make sure you have the "monitor only" option checked, otherwise Airwave will push a configuration to those devices.

There is a procedure to add a cluster to airwave.  The Airwave/Instant configuration guide is here:  https://support.hpe.com/hpesc/public/docDisplay?docId=a00099169en_us.  Look at the section under "Setting up Instant Manually".

If you are only monitoring APs, that means Airwave is not pushing configuration to those instant APs, and the configuration will always be "mismatched".  You can ignore that for now.  It is only important when you are managing the configuration from airwave.

When you navigate to the ip address of any  AP in a cluster., it will redirect to the cluster ip address, which is what you need to monitor and manage a cluster.

Good luck and I hope any of this helps.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

Thank you again cjoseph for all your help! I was able to change the Virtual Controller IP to match the 10.50.x.x subnet. I am now able to access the cluster by VC IP. 

My next question is about adding newer IAP's to the cluster. As I understand it, all AP's must be on the same firmware version. My current firmware version on the cluster is 6.5.2.0_59123 and contains IAP-205 AP's.
I am now adding iap-305 AP's, and their current firmware is 8.7.1.3_79817.

I assume my next step would be to update the firmware on the current IAP-205's to the latest firmware. If the firmware is higher than the new 305 AP's, then I would update the firmware on these to match as well.

Once this is completed, I should be able to plug in my additional IAP-305's, and they should receive the config from the VC, being that auto-join is enabled. I would then assume, the new AP's would show in the Access Points Window

Is there something I may be missing before I commit?

------------------------------
Rick Reyes
------------------------------

Original Message:
Sent: Apr 03, 2022 02:54 PM
From: Colin Joseph
Subject: Inherited Wireless Infrastructure - Please Help

That does look correct.  Make sure the virtual AP ip address is on the same subnet as the APs.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
------------------------------


Original Message:
Sent: Apr 03, 2022 01:24 PM
From: Rick Reyes
Subject: Inherited Wireless Infrastructure - Please Help

Thank you very much! Yes this helped!
Ive gone through the training videos on this site, and read through some of the documentation. I feel I am grasping the concepts, now to Test in PROD!!!

From what I understand, the Airwave Server is not necessarily required. Our airwave server is currently set to monitor only, so it's not pushing any configs, just monitoring, which is why I say not necessarily required. 
Instead of being concerned with Airwave, I will first focus on the IAP Cluster. 

Our district contains 5 subnets-
10.10.0.0
10.20.0.0
10.30.0.0
10.40.0.0
10.50.0.0

I have the 10.50.x.x AP's on the correct subnet. The master receives a dhcp address in the correct subnet. I am unable to access the VC using the 10.50 subnet address. I can however access an AP on the 10.50 network, which reroutes me to the master AP. The master AP shows as, what seems to me, to be a duplicate name and address of another site/subnet. 

Here is the VC Gui on the 10.30 Subnet. This looks to be configured correctly.



We usually have issues trying to access the web gui of our 10.30.x.x Virtual Controller. I'm assuming the reason is because the IAP's have created a cluster on the 10.50.x.x subnet, but has a duplicate address for another subnet's VC IP address.

What I would think to do is get into the master AP on the 10.50 subnet, change to the correct site name, and change the Virtual Conroller IP to the 10.50 subnet.  

Once these settings are corrected. I should now be able to reliably access our 10.30 VC, and have a new VC on the 10.50 subnet. Would this be correct? Thank you for the help!!!

------------------------------
Rick Reyes


Original Message:
Sent: Apr 01, 2022 09:16 PM
From: Colin Joseph
Subject: Inherited Wireless Infrastructure - Please Help

Some general answers to your questions:

APs will show "good" if they received the last configuration, even though they are down.

For the "new" devices, you can add it to a folder designated for that site, or create a folder for that site and then go back and add them to that folder.  Make sure you have the "monitor only" option checked, otherwise Airwave will push a configuration to those devices.

There is a procedure to add a cluster to airwave.  The Airwave/Instant configuration guide is here:  https://support.hpe.com/hpesc/public/docDisplay?docId=a00099169en_us.  Look at the section under "Setting up Instant Manually".

If you are only monitoring APs, that means Airwave is not pushing configuration to those instant APs, and the configuration will always be "mismatched".  You can ignore that for now.  It is only important when you are managing the configuration from airwave.

When you navigate to the ip address of any  AP in a cluster., it will redirect to the cluster ip address, which is what you need to monitor and manage a cluster.

Good luck and I hope any of this helps.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

One addition to the question. I noticed the firmware name of the 205's is "Taurus", and the firmware name for the 305's is called "Ursa". Can I assume that I would download the Ursa Firmware from the Aruba Support Portal, and upload it to the VC that contains the IAP's with the Taurus firmware? Thanks again!

------------------------------
Rick Reyes
------------------------------

Original Message:
Sent: Apr 04, 2022 02:03 PM
From: Rick Reyes
Subject: Inherited Wireless Infrastructure - Please Help

Thank you again cjoseph for all your help! I was able to change the Virtual Controller IP to match the 10.50.x.x subnet. I am now able to access the cluster by VC IP. 

My next question is about adding newer IAP's to the cluster. As I understand it, all AP's must be on the same firmware version. My current firmware version on the cluster is 6.5.2.0_59123 and contains IAP-205 AP's.
I am now adding iap-305 AP's, and their current firmware is 8.7.1.3_79817.

I assume my next step would be to update the firmware on the current IAP-205's to the latest firmware. If the firmware is higher than the new 305 AP's, then I would update the firmware on these to match as well.

Once this is completed, I should be able to plug in my additional IAP-305's, and they should receive the config from the VC, being that auto-join is enabled. I would then assume, the new AP's would show in the Access Points Window

Is there something I may be missing before I commit?

------------------------------
Rick Reyes
------------------------------


Original Message:
Sent: Apr 03, 2022 02:54 PM
From: Colin Joseph
Subject: Inherited Wireless Infrastructure - Please Help

That does look correct.  Make sure the virtual AP ip address is on the same subnet as the APs.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.


Original Message:
Sent: Apr 03, 2022 01:24 PM
From: Rick Reyes
Subject: Inherited Wireless Infrastructure - Please Help

Thank you very much! Yes this helped!
Ive gone through the training videos on this site, and read through some of the documentation. I feel I am grasping the concepts, now to Test in PROD!!!

From what I understand, the Airwave Server is not necessarily required. Our airwave server is currently set to monitor only, so it's not pushing any configs, just monitoring, which is why I say not necessarily required. 
Instead of being concerned with Airwave, I will first focus on the IAP Cluster. 

Our district contains 5 subnets-
10.10.0.0
10.20.0.0
10.30.0.0
10.40.0.0
10.50.0.0

I have the 10.50.x.x AP's on the correct subnet. The master receives a dhcp address in the correct subnet. I am unable to access the VC using the 10.50 subnet address. I can however access an AP on the 10.50 network, which reroutes me to the master AP. The master AP shows as, what seems to me, to be a duplicate name and address of another site/subnet. 

Here is the VC Gui on the 10.30 Subnet. This looks to be configured correctly.



We usually have issues trying to access the web gui of our 10.30.x.x Virtual Controller. I'm assuming the reason is because the IAP's have created a cluster on the 10.50.x.x subnet, but has a duplicate address for another subnet's VC IP address.

What I would think to do is get into the master AP on the 10.50 subnet, change to the correct site name, and change the Virtual Conroller IP to the 10.50 subnet.  

Once these settings are corrected. I should now be able to reliably access our 10.30 VC, and have a new VC on the 10.50 subnet. Would this be correct? Thank you for the help!!!

------------------------------
Rick Reyes


Original Message:
Sent: Apr 01, 2022 09:16 PM
From: Colin Joseph
Subject: Inherited Wireless Infrastructure - Please Help

Some general answers to your questions:

APs will show "good" if they received the last configuration, even though they are down.

For the "new" devices, you can add it to a folder designated for that site, or create a folder for that site and then go back and add them to that folder.  Make sure you have the "monitor only" option checked, otherwise Airwave will push a configuration to those devices.

There is a procedure to add a cluster to airwave.  The Airwave/Instant configuration guide is here:  https://support.hpe.com/hpesc/public/docDisplay?docId=a00099169en_us.  Look at the section under "Setting up Instant Manually".

If you are only monitoring APs, that means Airwave is not pushing configuration to those instant APs, and the configuration will always be "mismatched".  You can ignore that for now.  It is only important when you are managing the configuration from airwave.

When you navigate to the ip address of any  AP in a cluster., it will redirect to the cluster ip address, which is what you need to monitor and manage a cluster.

Good luck and I hope any of this helps.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

I would downgrade the IAP-305 to the software version of the current IAP-205s, because it is less disruptive, and you are new at this.

A multi-AP type upgrade requires a tftp, ftp or http server to put all of the version of software on; it is easier just to downgrade the 305 to the 205s version of InstantOS code.

You are correct about the naming.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
------------------------------

Original Message:
Sent: Apr 04, 2022 02:16 PM
From: Rick Reyes
Subject: Inherited Wireless Infrastructure - Please Help

One addition to the question. I noticed the firmware name of the 205's is "Taurus", and the firmware name for the 305's is called "Ursa". Can I assume that I would download the Ursa Firmware from the Aruba Support Portal, and upload it to the VC that contains the IAP's with the Taurus firmware? Thanks again!

------------------------------
Rick Reyes
------------------------------


Original Message:
Sent: Apr 04, 2022 02:03 PM
From: Rick Reyes
Subject: Inherited Wireless Infrastructure - Please Help

Thank you again cjoseph for all your help! I was able to change the Virtual Controller IP to match the 10.50.x.x subnet. I am now able to access the cluster by VC IP. 

My next question is about adding newer IAP's to the cluster. As I understand it, all AP's must be on the same firmware version. My current firmware version on the cluster is 6.5.2.0_59123 and contains IAP-205 AP's.
I am now adding iap-305 AP's, and their current firmware is 8.7.1.3_79817.

I assume my next step would be to update the firmware on the current IAP-205's to the latest firmware. If the firmware is higher than the new 305 AP's, then I would update the firmware on these to match as well.

Once this is completed, I should be able to plug in my additional IAP-305's, and they should receive the config from the VC, being that auto-join is enabled. I would then assume, the new AP's would show in the Access Points Window

Is there something I may be missing before I commit?

------------------------------
Rick Reyes


Original Message:
Sent: Apr 03, 2022 02:54 PM
From: Colin Joseph
Subject: Inherited Wireless Infrastructure - Please Help

That does look correct.  Make sure the virtual AP ip address is on the same subnet as the APs.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.


Original Message:
Sent: Apr 03, 2022 01:24 PM
From: Rick Reyes
Subject: Inherited Wireless Infrastructure - Please Help

Thank you very much! Yes this helped!
Ive gone through the training videos on this site, and read through some of the documentation. I feel I am grasping the concepts, now to Test in PROD!!!

From what I understand, the Airwave Server is not necessarily required. Our airwave server is currently set to monitor only, so it's not pushing any configs, just monitoring, which is why I say not necessarily required. 
Instead of being concerned with Airwave, I will first focus on the IAP Cluster. 

Our district contains 5 subnets-
10.10.0.0
10.20.0.0
10.30.0.0
10.40.0.0
10.50.0.0

I have the 10.50.x.x AP's on the correct subnet. The master receives a dhcp address in the correct subnet. I am unable to access the VC using the 10.50 subnet address. I can however access an AP on the 10.50 network, which reroutes me to the master AP. The master AP shows as, what seems to me, to be a duplicate name and address of another site/subnet. 

Here is the VC Gui on the 10.30 Subnet. This looks to be configured correctly.



We usually have issues trying to access the web gui of our 10.30.x.x Virtual Controller. I'm assuming the reason is because the IAP's have created a cluster on the 10.50.x.x subnet, but has a duplicate address for another subnet's VC IP address.

What I would think to do is get into the master AP on the 10.50 subnet, change to the correct site name, and change the Virtual Conroller IP to the 10.50 subnet.  

Once these settings are corrected. I should now be able to reliably access our 10.30 VC, and have a new VC on the 10.50 subnet. Would this be correct? Thank you for the help!!!

------------------------------
Rick Reyes


Original Message:
Sent: Apr 01, 2022 09:16 PM
From: Colin Joseph
Subject: Inherited Wireless Infrastructure - Please Help

Some general answers to your questions:

APs will show "good" if they received the last configuration, even though they are down.

For the "new" devices, you can add it to a folder designated for that site, or create a folder for that site and then go back and add them to that folder.  Make sure you have the "monitor only" option checked, otherwise Airwave will push a configuration to those devices.

There is a procedure to add a cluster to airwave.  The Airwave/Instant configuration guide is here:  https://support.hpe.com/hpesc/public/docDisplay?docId=a00099169en_us.  Look at the section under "Setting up Instant Manually".

If you are only monitoring APs, that means Airwave is not pushing configuration to those instant APs, and the configuration will always be "mismatched".  You can ignore that for now.  It is only important when you are managing the configuration from airwave.

When you navigate to the ip address of any  AP in a cluster., it will redirect to the cluster ip address, which is what you need to monitor and manage a cluster.

Good luck and I hope any of this helps.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

Got it, I'll look into setting up a tftp server, being that I also have some new 505's. For now, I like the idea of downgrading to the current cluster. next problem though... I'm unable to access any downloads on the ASP site. I recieve a 404 error. I tried with additional firmware files, but I receive the same error on all. I tried accessing the file download from home, but receive the same results. Is there another way of obtaining the firmware file?


------------------------------
Rick Reyes
------------------------------

Original Message:
Sent: Apr 04, 2022 02:55 PM
From: Colin Joseph
Subject: Inherited Wireless Infrastructure - Please Help

I would downgrade the IAP-305 to the software version of the current IAP-205s, because it is less disruptive, and you are new at this.

A multi-AP type upgrade requires a tftp, ftp or http server to put all of the version of software on; it is easier just to downgrade the 305 to the 205s version of InstantOS code.

You are correct about the naming.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
------------------------------


Original Message:
Sent: Apr 04, 2022 02:16 PM
From: Rick Reyes
Subject: Inherited Wireless Infrastructure - Please Help

One addition to the question. I noticed the firmware name of the 205's is "Taurus", and the firmware name for the 305's is called "Ursa". Can I assume that I would download the Ursa Firmware from the Aruba Support Portal, and upload it to the VC that contains the IAP's with the Taurus firmware? Thanks again!

------------------------------
Rick Reyes


Original Message:
Sent: Apr 04, 2022 02:03 PM
From: Rick Reyes
Subject: Inherited Wireless Infrastructure - Please Help

Thank you again cjoseph for all your help! I was able to change the Virtual Controller IP to match the 10.50.x.x subnet. I am now able to access the cluster by VC IP. 

My next question is about adding newer IAP's to the cluster. As I understand it, all AP's must be on the same firmware version. My current firmware version on the cluster is 6.5.2.0_59123 and contains IAP-205 AP's.
I am now adding iap-305 AP's, and their current firmware is 8.7.1.3_79817.

I assume my next step would be to update the firmware on the current IAP-205's to the latest firmware. If the firmware is higher than the new 305 AP's, then I would update the firmware on these to match as well.

Once this is completed, I should be able to plug in my additional IAP-305's, and they should receive the config from the VC, being that auto-join is enabled. I would then assume, the new AP's would show in the Access Points Window

Is there something I may be missing before I commit?

------------------------------
Rick Reyes


Original Message:
Sent: Apr 03, 2022 02:54 PM
From: Colin Joseph
Subject: Inherited Wireless Infrastructure - Please Help

That does look correct.  Make sure the virtual AP ip address is on the same subnet as the APs.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.


Original Message:
Sent: Apr 03, 2022 01:24 PM
From: Rick Reyes
Subject: Inherited Wireless Infrastructure - Please Help

Thank you very much! Yes this helped!
Ive gone through the training videos on this site, and read through some of the documentation. I feel I am grasping the concepts, now to Test in PROD!!!

From what I understand, the Airwave Server is not necessarily required. Our airwave server is currently set to monitor only, so it's not pushing any configs, just monitoring, which is why I say not necessarily required. 
Instead of being concerned with Airwave, I will first focus on the IAP Cluster. 

Our district contains 5 subnets-
10.10.0.0
10.20.0.0
10.30.0.0
10.40.0.0
10.50.0.0

I have the 10.50.x.x AP's on the correct subnet. The master receives a dhcp address in the correct subnet. I am unable to access the VC using the 10.50 subnet address. I can however access an AP on the 10.50 network, which reroutes me to the master AP. The master AP shows as, what seems to me, to be a duplicate name and address of another site/subnet. 

Here is the VC Gui on the 10.30 Subnet. This looks to be configured correctly.



We usually have issues trying to access the web gui of our 10.30.x.x Virtual Controller. I'm assuming the reason is because the IAP's have created a cluster on the 10.50.x.x subnet, but has a duplicate address for another subnet's VC IP address.

What I would think to do is get into the master AP on the 10.50 subnet, change to the correct site name, and change the Virtual Conroller IP to the 10.50 subnet.  

Once these settings are corrected. I should now be able to reliably access our 10.30 VC, and have a new VC on the 10.50 subnet. Would this be correct? Thank you for the help!!!

------------------------------
Rick Reyes


Original Message:
Sent: Apr 01, 2022 09:16 PM
From: Colin Joseph
Subject: Inherited Wireless Infrastructure - Please Help

Some general answers to your questions:

APs will show "good" if they received the last configuration, even though they are down.

For the "new" devices, you can add it to a folder designated for that site, or create a folder for that site and then go back and add them to that folder.  Make sure you have the "monitor only" option checked, otherwise Airwave will push a configuration to those devices.

There is a procedure to add a cluster to airwave.  The Airwave/Instant configuration guide is here:  https://support.hpe.com/hpesc/public/docDisplay?docId=a00099169en_us.  Look at the section under "Setting up Instant Manually".

If you are only monitoring APs, that means Airwave is not pushing configuration to those instant APs, and the configuration will always be "mismatched".  You can ignore that for now.  It is only important when you are managing the configuration from airwave.

When you navigate to the ip address of any  AP in a cluster., it will redirect to the cluster ip address, which is what you need to monitor and manage a cluster.

Good luck and I hope any of this helps.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

Ok, I recieved the file after calling ASP Phone#. They were able to provide me with the file directly. I will now try to downgrade an AP and will report back. Thank you!

------------------------------
Rick Reyes
------------------------------

Original Message:
Sent: Apr 04, 2022 04:42 PM
From: Rick Reyes
Subject: Inherited Wireless Infrastructure - Please Help

Got it, I'll look into setting up a tftp server, being that I also have some new 505's. For now, I like the idea of downgrading to the current cluster. next problem though... I'm unable to access any downloads on the ASP site. I recieve a 404 error. I tried with additional firmware files, but I receive the same error on all. I tried accessing the file download from home, but receive the same results. Is there another way of obtaining the firmware file?


------------------------------
Rick Reyes
------------------------------


Original Message:
Sent: Apr 04, 2022 02:55 PM
From: Colin Joseph
Subject: Inherited Wireless Infrastructure - Please Help

I would downgrade the IAP-305 to the software version of the current IAP-205s, because it is less disruptive, and you are new at this.

A multi-AP type upgrade requires a tftp, ftp or http server to put all of the version of software on; it is easier just to downgrade the 305 to the 205s version of InstantOS code.

You are correct about the naming.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.


Original Message:
Sent: Apr 04, 2022 02:16 PM
From: Rick Reyes
Subject: Inherited Wireless Infrastructure - Please Help

One addition to the question. I noticed the firmware name of the 205's is "Taurus", and the firmware name for the 305's is called "Ursa". Can I assume that I would download the Ursa Firmware from the Aruba Support Portal, and upload it to the VC that contains the IAP's with the Taurus firmware? Thanks again!

------------------------------
Rick Reyes


Original Message:
Sent: Apr 04, 2022 02:03 PM
From: Rick Reyes
Subject: Inherited Wireless Infrastructure - Please Help

Thank you again cjoseph for all your help! I was able to change the Virtual Controller IP to match the 10.50.x.x subnet. I am now able to access the cluster by VC IP. 

My next question is about adding newer IAP's to the cluster. As I understand it, all AP's must be on the same firmware version. My current firmware version on the cluster is 6.5.2.0_59123 and contains IAP-205 AP's.
I am now adding iap-305 AP's, and their current firmware is 8.7.1.3_79817.

I assume my next step would be to update the firmware on the current IAP-205's to the latest firmware. If the firmware is higher than the new 305 AP's, then I would update the firmware on these to match as well.

Once this is completed, I should be able to plug in my additional IAP-305's, and they should receive the config from the VC, being that auto-join is enabled. I would then assume, the new AP's would show in the Access Points Window

Is there something I may be missing before I commit?

------------------------------
Rick Reyes


Original Message:
Sent: Apr 03, 2022 02:54 PM
From: Colin Joseph
Subject: Inherited Wireless Infrastructure - Please Help

That does look correct.  Make sure the virtual AP ip address is on the same subnet as the APs.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.


Original Message:
Sent: Apr 03, 2022 01:24 PM
From: Rick Reyes
Subject: Inherited Wireless Infrastructure - Please Help

Thank you very much! Yes this helped!
Ive gone through the training videos on this site, and read through some of the documentation. I feel I am grasping the concepts, now to Test in PROD!!!

From what I understand, the Airwave Server is not necessarily required. Our airwave server is currently set to monitor only, so it's not pushing any configs, just monitoring, which is why I say not necessarily required. 
Instead of being concerned with Airwave, I will first focus on the IAP Cluster. 

Our district contains 5 subnets-
10.10.0.0
10.20.0.0
10.30.0.0
10.40.0.0
10.50.0.0

I have the 10.50.x.x AP's on the correct subnet. The master receives a dhcp address in the correct subnet. I am unable to access the VC using the 10.50 subnet address. I can however access an AP on the 10.50 network, which reroutes me to the master AP. The master AP shows as, what seems to me, to be a duplicate name and address of another site/subnet. 

Here is the VC Gui on the 10.30 Subnet. This looks to be configured correctly.



We usually have issues trying to access the web gui of our 10.30.x.x Virtual Controller. I'm assuming the reason is because the IAP's have created a cluster on the 10.50.x.x subnet, but has a duplicate address for another subnet's VC IP address.

What I would think to do is get into the master AP on the 10.50 subnet, change to the correct site name, and change the Virtual Conroller IP to the 10.50 subnet.  

Once these settings are corrected. I should now be able to reliably access our 10.30 VC, and have a new VC on the 10.50 subnet. Would this be correct? Thank you for the help!!!

------------------------------
Rick Reyes


Original Message:
Sent: Apr 01, 2022 09:16 PM
From: Colin Joseph
Subject: Inherited Wireless Infrastructure - Please Help

Some general answers to your questions:

APs will show "good" if they received the last configuration, even though they are down.

For the "new" devices, you can add it to a folder designated for that site, or create a folder for that site and then go back and add them to that folder.  Make sure you have the "monitor only" option checked, otherwise Airwave will push a configuration to those devices.

There is a procedure to add a cluster to airwave.  The Airwave/Instant configuration guide is here:  https://support.hpe.com/hpesc/public/docDisplay?docId=a00099169en_us.  Look at the section under "Setting up Instant Manually".

If you are only monitoring APs, that means Airwave is not pushing configuration to those instant APs, and the configuration will always be "mismatched".  You can ignore that for now.  It is only important when you are managing the configuration from airwave.

When you navigate to the ip address of any  AP in a cluster., it will redirect to the cluster ip address, which is what you need to monitor and manage a cluster.

Good luck and I hope any of this helps.

------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.