Wireless Access

I would like to know the differences between an architecture with virtual controllers onboard the APs and a bare-metal controller. Is it only the number of manageable controllers that changes? When using bare-metal controllers, is it possible to create and manage an arbitrary number of clusters, or is AirWave still required, with each controller managing only one cluster?

Airwave is a good valueadd for Historical data logs, Monitoring and in some cases management. But since airwave is moving gradually to Central, in that case you can have Central or Central OnPrem.

As for the controllers, depends what you want to achieve, what type of deployment will you do, cost, etc.

For virtual, you need to have Server + Hypervisor in order to have controllers running and also a lot of additional work to do connectivity, port configuration of server infrastructure etc. 

For Baremetal Controllers, you have everything in a box with less headache and simplified to be up & running with less headache.

Performance wise and numbers you can find on here:
https://www.hpe.com/psnow/doc/a00059064enw?jumpid=in_pdfviewer-psnow

https://www.hpe.com/psnow/doc/a00059063enw?jumpid=in_pdfviewer-psnow

https://www.hpe.com/psnow/doc/a00059069enw?jumpid=in_pdfviewer-psnow

https://www.hpe.com/psnow/doc/a00059060enw?jumpid=in_pdfviewer-psnow

https://www.hpe.com/psnow/doc/a00121209enw?jumpid=in_pdfviewer-psnow

https://www.hpe.com/psnow/doc/a00134298enw?jumpid=in_pdfviewer-psnow

https://www.hpe.com/psnow/doc/a00067608enw?jumpid=in_pdfviewer-psnow

Personally, for customers who have well established Server infrastructure, i recommend to purchase Virtual. For end customers who don't have a well structured Datacenter, Redundancy, Licensing of Hypervisors, etc. i recommend bare metals. But there are other things which have to be taken into consideration as well.

I would like to know the differences between an architecture with virtual controllers onboard the APs and a bare-metal controller. Is it only the number of manageable controllers that changes? When using bare-metal controllers, is it possible to create and manage an arbitrary number of clusters, or is AirWave still required, with each controller managing only one cluster?

Sorry, I didn't explain myself well. Today, I have various architectures with different types of IAPs managed by AirWave and multiple clusters centrally managed by AirWave, where I use the same APs as virtual controllers for each cluster. If I were to integrate virtual controllers like the 8360, could I eliminate AirWave since they are capable of managing multiple clusters, or can a physical controller manage only one cluster, meaning I would still need to use AirWave?

Airwave is a good valueadd for Historical data logs, Monitoring and in some cases management. But since airwave is moving gradually to Central, in that case you can have Central or Central OnPrem.

As for the controllers, depends what you want to achieve, what type of deployment will you do, cost, etc.

For virtual, you need to have Server + Hypervisor in order to have controllers running and also a lot of additional work to do connectivity, port configuration of server infrastructure etc. 

For Baremetal Controllers, you have everything in a box with less headache and simplified to be up & running with less headache.

Performance wise and numbers you can find on here:
https://www.hpe.com/psnow/doc/a00059064enw?jumpid=in_pdfviewer-psnow

https://www.hpe.com/psnow/doc/a00059063enw?jumpid=in_pdfviewer-psnow

https://www.hpe.com/psnow/doc/a00059069enw?jumpid=in_pdfviewer-psnow

https://www.hpe.com/psnow/doc/a00059060enw?jumpid=in_pdfviewer-psnow

https://www.hpe.com/psnow/doc/a00121209enw?jumpid=in_pdfviewer-psnow

https://www.hpe.com/psnow/doc/a00134298enw?jumpid=in_pdfviewer-psnow

https://www.hpe.com/psnow/doc/a00067608enw?jumpid=in_pdfviewer-psnow

Personally, for customers who have well established Server infrastructure, i recommend to purchase Virtual. For end customers who don't have a well structured Datacenter, Redundancy, Licensing of Hypervisors, etc. i recommend bare metals. But there are other things which have to be taken into consideration as well.

I would like to know the differences between an architecture with virtual controllers onboard the APs and a bare-metal controller. Is it only the number of manageable controllers that changes? When using bare-metal controllers, is it possible to create and manage an arbitrary number of clusters, or is AirWave still required, with each controller managing only one cluster?

Hi.

I believe you are mixing terms here. Instant only has Virtual Controller hosted on one of the APs. Mobility HW/Virtual controllers/gateways are completely different beasts and can't manage Instant APs virtual controllers. MDs (Managed Device) controllers/gateways can be configured in clusters that are managed ba MM (Mobility Conductor). Mobility Conductor can manage many MD clusters. APs are connected to MDs via tunnels and use different FW downloaded from controllers than Instant APs.

You use Instant clusters If I read your post correctly. If you want to manage more than one VC cluster from one place you need AirWave or Central or Central OnPrem to do it.

By 8360 do you mean an ArubaCX 8360 switch or you have a different beast in your mind? HW controllers/gateways are 7xxx (obsolete now) or 9xxx series. switch can't control APs.

Best, Gorazd

Sorry, I didn't explain myself well. Today, I have various architectures with different types of IAPs managed by AirWave and multiple clusters centrally managed by AirWave, where I use the same APs as virtual controllers for each cluster. If I were to integrate virtual controllers like the 8360, could I eliminate AirWave since they are capable of managing multiple clusters, or can a physical controller manage only one cluster, meaning I would still need to use AirWave?

Airwave is a good valueadd for Historical data logs, Monitoring and in some cases management. But since airwave is moving gradually to Central, in that case you can have Central or Central OnPrem.

As for the controllers, depends what you want to achieve, what type of deployment will you do, cost, etc.

For virtual, you need to have Server + Hypervisor in order to have controllers running and also a lot of additional work to do connectivity, port configuration of server infrastructure etc. 

For Baremetal Controllers, you have everything in a box with less headache and simplified to be up & running with less headache.

Performance wise and numbers you can find on here:
https://www.hpe.com/psnow/doc/a00059064enw?jumpid=in_pdfviewer-psnow

https://www.hpe.com/psnow/doc/a00059063enw?jumpid=in_pdfviewer-psnow

https://www.hpe.com/psnow/doc/a00059069enw?jumpid=in_pdfviewer-psnow

https://www.hpe.com/psnow/doc/a00059060enw?jumpid=in_pdfviewer-psnow

https://www.hpe.com/psnow/doc/a00121209enw?jumpid=in_pdfviewer-psnow

https://www.hpe.com/psnow/doc/a00134298enw?jumpid=in_pdfviewer-psnow

https://www.hpe.com/psnow/doc/a00067608enw?jumpid=in_pdfviewer-psnow

Personally, for customers who have well established Server infrastructure, i recommend to purchase Virtual. For end customers who don't have a well structured Datacenter, Redundancy, Licensing of Hypervisors, etc. i recommend bare metals. But there are other things which have to be taken into consideration as well.

I would like to know the differences between an architecture with virtual controllers onboard the APs and a bare-metal controller. Is it only the number of manageable controllers that changes? When using bare-metal controllers, is it possible to create and manage an arbitrary number of clusters, or is AirWave still required, with each controller managing only one cluster?

excuse me not 8360 but 9240. Ok this is the problem: now i've 4 cluster with vc instant controller managed by airwave.  if i buy one  9240 i can remove airwave and manage the 4 cluster via 9240 or 9240 are  only a wifi-controller and can't manage more then 1 cluster?

Hi.

I believe you are mixing terms here. Instant only has Virtual Controller hosted on one of the APs. Mobility HW/Virtual controllers/gateways are completely different beasts and can't manage Instant APs virtual controllers. MDs (Managed Device) controllers/gateways can be configured in clusters that are managed ba MM (Mobility Conductor). Mobility Conductor can manage many MD clusters. APs are connected to MDs via tunnels and use different FW downloaded from controllers than Instant APs.

You use Instant clusters If I read your post correctly. If you want to manage more than one VC cluster from one place you need AirWave or Central or Central OnPrem to do it.

By 8360 do you mean an ArubaCX 8360 switch or you have a different beast in your mind? HW controllers/gateways are 7xxx (obsolete now) or 9xxx series. switch can't control APs.

Best, Gorazd

Sorry, I didn't explain myself well. Today, I have various architectures with different types of IAPs managed by AirWave and multiple clusters centrally managed by AirWave, where I use the same APs as virtual controllers for each cluster. If I were to integrate virtual controllers like the 8360, could I eliminate AirWave since they are capable of managing multiple clusters, or can a physical controller manage only one cluster, meaning I would still need to use AirWave?

Airwave is a good valueadd for Historical data logs, Monitoring and in some cases management. But since airwave is moving gradually to Central, in that case you can have Central or Central OnPrem.

As for the controllers, depends what you want to achieve, what type of deployment will you do, cost, etc.

For virtual, you need to have Server + Hypervisor in order to have controllers running and also a lot of additional work to do connectivity, port configuration of server infrastructure etc. 

For Baremetal Controllers, you have everything in a box with less headache and simplified to be up & running with less headache.

Performance wise and numbers you can find on here:
https://www.hpe.com/psnow/doc/a00059064enw?jumpid=in_pdfviewer-psnow

https://www.hpe.com/psnow/doc/a00059063enw?jumpid=in_pdfviewer-psnow

https://www.hpe.com/psnow/doc/a00059069enw?jumpid=in_pdfviewer-psnow

https://www.hpe.com/psnow/doc/a00059060enw?jumpid=in_pdfviewer-psnow

https://www.hpe.com/psnow/doc/a00121209enw?jumpid=in_pdfviewer-psnow

https://www.hpe.com/psnow/doc/a00134298enw?jumpid=in_pdfviewer-psnow

https://www.hpe.com/psnow/doc/a00067608enw?jumpid=in_pdfviewer-psnow

Personally, for customers who have well established Server infrastructure, i recommend to purchase Virtual. For end customers who don't have a well structured Datacenter, Redundancy, Licensing of Hypervisors, etc. i recommend bare metals. But there are other things which have to be taken into consideration as well.

I would like to know the differences between an architecture with virtual controllers onboard the APs and a bare-metal controller. Is it only the number of manageable controllers that changes? When using bare-metal controllers, is it possible to create and manage an arbitrary number of clusters, or is AirWave still required, with each controller managing only one cluster?

excuse me not 8360 but 9240. Ok this is the problem: now i've 4 cluster with vc instant controller managed by airwave.  if i buy one  9240 i can remove airwave and manage the 4 cluster via 9240 or 9240 are  only a wifi-controller and can't manage more then 1 cluster?

Hi.

I believe you are mixing terms here. Instant only has Virtual Controller hosted on one of the APs. Mobility HW/Virtual controllers/gateways are completely different beasts and can't manage Instant APs virtual controllers. MDs (Managed Device) controllers/gateways can be configured in clusters that are managed ba MM (Mobility Conductor). Mobility Conductor can manage many MD clusters. APs are connected to MDs via tunnels and use different FW downloaded from controllers than Instant APs.

You use Instant clusters If I read your post correctly. If you want to manage more than one VC cluster from one place you need AirWave or Central or Central OnPrem to do it.

By 8360 do you mean an ArubaCX 8360 switch or you have a different beast in your mind? HW controllers/gateways are 7xxx (obsolete now) or 9xxx series. switch can't control APs.

Best, Gorazd

Sorry, I didn't explain myself well. Today, I have various architectures with different types of IAPs managed by AirWave and multiple clusters centrally managed by AirWave, where I use the same APs as virtual controllers for each cluster. If I were to integrate virtual controllers like the 8360, could I eliminate AirWave since they are capable of managing multiple clusters, or can a physical controller manage only one cluster, meaning I would still need to use AirWave?

Airwave is a good valueadd for Historical data logs, Monitoring and in some cases management. But since airwave is moving gradually to Central, in that case you can have Central or Central OnPrem.

As for the controllers, depends what you want to achieve, what type of deployment will you do, cost, etc.

For virtual, you need to have Server + Hypervisor in order to have controllers running and also a lot of additional work to do connectivity, port configuration of server infrastructure etc. 

For Baremetal Controllers, you have everything in a box with less headache and simplified to be up & running with less headache.

Performance wise and numbers you can find on here:
https://www.hpe.com/psnow/doc/a00059064enw?jumpid=in_pdfviewer-psnow

https://www.hpe.com/psnow/doc/a00059063enw?jumpid=in_pdfviewer-psnow

https://www.hpe.com/psnow/doc/a00059069enw?jumpid=in_pdfviewer-psnow

https://www.hpe.com/psnow/doc/a00059060enw?jumpid=in_pdfviewer-psnow

https://www.hpe.com/psnow/doc/a00121209enw?jumpid=in_pdfviewer-psnow

https://www.hpe.com/psnow/doc/a00134298enw?jumpid=in_pdfviewer-psnow

https://www.hpe.com/psnow/doc/a00067608enw?jumpid=in_pdfviewer-psnow

Personally, for customers who have well established Server infrastructure, i recommend to purchase Virtual. For end customers who don't have a well structured Datacenter, Redundancy, Licensing of Hypervisors, etc. i recommend bare metals. But there are other things which have to be taken into consideration as well.

I would like to know the differences between an architecture with virtual controllers onboard the APs and a bare-metal controller. Is it only the number of manageable controllers that changes? When using bare-metal controllers, is it possible to create and manage an arbitrary number of clusters, or is AirWave still required, with each controller managing only one cluster?