Network Management

Aruba technology and support in general frustrates me and I accept a lot of that is probably my misunderstanding**, and lack of training which my company is unwilling to pay for! With that said...

I am looking to understand:

• • best practice for monitoring the AMP box itself and
  • what we could reasonably expect to see

Prior to version 8 of ArubaOS we could monitor (physical and virtual AMPs) interfaces, memory, CPU, etc after we have raised a TAC case to get the underlying OS "edited" to allow this. As an aside it's never been clear to me why it requires a TAC case to enable SNMP monitoring of the AMP - this should be baked into the GUI. My understanding** is that Aruba want us to use the AMP as an NMS, but then how do you actually monitor the AMP? Seems very restrictive!!!

Since v8 and up, it seems even the TAC folk can't get it to work as I would expect. Either that, or they are misunderstanding our request, which I feel is quite simple. That being:

TLDR: We'd like to see, via a third party tool of our choice, all the stats you can see via the GUI: > System > Perfomance - as well as being able to see the general state of health of any AMP we manage. Clearly the stats are being pulled from somewhere on the box ...!

Is this too unreasonable a request when literally every other vendor I have ever dealt with in 30yrs of networking, has always allowed for a 3rd party tool to monitor their devices via SNMP. Not just SNMP Traps.

** For the record. I am not trying to be inflammatory, and I accept my understanding might be wrong. However my experience is very much aligned to the above. I am genuinely wanting to know from those out there that use other monitoring tools i.e. SolarWinds, WhatsUp Gold, Zabbix, etc, etc how you monitor your AMPs, and what your expectation is (/was) and what your experience actually is?

Diolch yn fawr.

The reason is the same as you have said - AMP itself is a NMS platform. The ask is not unreasonable. However, there are triggers to configure for AMP health and alert if there's high disI/O or CPU or memory or services like VisualRF. Additionally, the system > Performance page provides real time AMP status for monitoring the box. So, the request never took priority. 

Aruba technology and support in general frustrates me and I accept a lot of that is probably my misunderstanding**, and lack of training which my company is unwilling to pay for! With that said...

I am looking to understand:

• • best practice for monitoring the AMP box itself and
  • what we could reasonably expect to see

Prior to version 8 of ArubaOS we could monitor (physical and virtual AMPs) interfaces, memory, CPU, etc after we have raised a TAC case to get the underlying OS "edited" to allow this. As an aside it's never been clear to me why it requires a TAC case to enable SNMP monitoring of the AMP - this should be baked into the GUI. My understanding** is that Aruba want us to use the AMP as an NMS, but then how do you actually monitor the AMP? Seems very restrictive!!!

Since v8 and up, it seems even the TAC folk can't get it to work as I would expect. Either that, or they are misunderstanding our request, which I feel is quite simple. That being:

TLDR: We'd like to see, via a third party tool of our choice, all the stats you can see via the GUI: > System > Perfomance - as well as being able to see the general state of health of any AMP we manage. Clearly the stats are being pulled from somewhere on the box ...!

Is this too unreasonable a request when literally every other vendor I have ever dealt with in 30yrs of networking, has always allowed for a 3rd party tool to monitor their devices via SNMP. Not just SNMP Traps.

** For the record. I am not trying to be inflammatory, and I accept my understanding might be wrong. However my experience is very much aligned to the above. I am genuinely wanting to know from those out there that use other monitoring tools i.e. SolarWinds, WhatsUp Gold, Zabbix, etc, etc how you monitor your AMPs, and what your expectation is (/was) and what your experience actually is?

Diolch yn fawr.

You haven't really answered my base question, which if it was missed was: How should I monitor the AMP platform?

>> The ask is not unreasonable. 

I'm not sure what you mean by this.

>> there are triggers to configure for AMP health and alert if there's high disI/O or CPU or memory or services like VisualRF.

Are these are internal triggers on the AMP? If so, how does that work when the box is struggling due to high CPU or Memory use and can't communicate this or you can't log on to see that?

>>Additionally, the system > Performance page provides real time AMP status for monitoring the box. 

Again, if I can't logon due to "issues" then how does one determine this?

What about historical access?

What about reporting on these metrics from a unified platform?

>>So, the request never took priority. 

I have certainly witnessed enough people in here alone asking for this that it ought to have a priority.

Let me ask a slightly different question then - how does AMP monitor itself and alert on itself when it is having issues?

To quote some of my schoolboy Latin ... Quis custodiet ipsos custodes?

The reason is the same as you have said - AMP itself is a NMS platform. The ask is not unreasonable. However, there are triggers to configure for AMP health and alert if there's high disI/O or CPU or memory or services like VisualRF. Additionally, the system > Performance page provides real time AMP status for monitoring the box. So, the request never took priority. 

Aruba technology and support in general frustrates me and I accept a lot of that is probably my misunderstanding**, and lack of training which my company is unwilling to pay for! With that said...

I am looking to understand:

• • best practice for monitoring the AMP box itself and
  • what we could reasonably expect to see

Prior to version 8 of ArubaOS we could monitor (physical and virtual AMPs) interfaces, memory, CPU, etc after we have raised a TAC case to get the underlying OS "edited" to allow this. As an aside it's never been clear to me why it requires a TAC case to enable SNMP monitoring of the AMP - this should be baked into the GUI. My understanding** is that Aruba want us to use the AMP as an NMS, but then how do you actually monitor the AMP? Seems very restrictive!!!

Since v8 and up, it seems even the TAC folk can't get it to work as I would expect. Either that, or they are misunderstanding our request, which I feel is quite simple. That being:

TLDR: We'd like to see, via a third party tool of our choice, all the stats you can see via the GUI: > System > Perfomance - as well as being able to see the general state of health of any AMP we manage. Clearly the stats are being pulled from somewhere on the box ...!

Is this too unreasonable a request when literally every other vendor I have ever dealt with in 30yrs of networking, has always allowed for a 3rd party tool to monitor their devices via SNMP. Not just SNMP Traps.

** For the record. I am not trying to be inflammatory, and I accept my understanding might be wrong. However my experience is very much aligned to the above. I am genuinely wanting to know from those out there that use other monitoring tools i.e. SolarWinds, WhatsUp Gold, Zabbix, etc, etc how you monitor your AMPs, and what your expectation is (/was) and what your experience actually is?

Diolch yn fawr.

These triggers set on AMP can be sent to External Email/NMS server.

If AMP (or any network device) has issues with Disk or CPU, it is unlikely they respond to SNMP queries or send SNMP traps as SNMP is lower priority.

There are SNMP alerts that can be sent from AMP to external NMS system for the generated ones.

AMP health can be monitored (with historical info) under System > Performance page.

AMP has AirWave Glass which can monitor one or more AirWave servers to monitor AMP health along with providing consolidating data from multiple AMPs.

w.r.t to ask, I suggest working with your Accounts team to work with Product management.

You haven't really answered my base question, which if it was missed was: How should I monitor the AMP platform?

>> The ask is not unreasonable. 

I'm not sure what you mean by this.

>> there are triggers to configure for AMP health and alert if there's high disI/O or CPU or memory or services like VisualRF.

Are these are internal triggers on the AMP? If so, how does that work when the box is struggling due to high CPU or Memory use and can't communicate this or you can't log on to see that?

>>Additionally, the system > Performance page provides real time AMP status for monitoring the box. 

Again, if I can't logon due to "issues" then how does one determine this?

What about historical access?

What about reporting on these metrics from a unified platform?

>>So, the request never took priority. 

I have certainly witnessed enough people in here alone asking for this that it ought to have a priority.

Let me ask a slightly different question then - how does AMP monitor itself and alert on itself when it is having issues?

To quote some of my schoolboy Latin ... Quis custodiet ipsos custodes?

The reason is the same as you have said - AMP itself is a NMS platform. The ask is not unreasonable. However, there are triggers to configure for AMP health and alert if there's high disI/O or CPU or memory or services like VisualRF. Additionally, the system > Performance page provides real time AMP status for monitoring the box. So, the request never took priority. 

Aruba technology and support in general frustrates me and I accept a lot of that is probably my misunderstanding**, and lack of training which my company is unwilling to pay for! With that said...

I am looking to understand:

• • best practice for monitoring the AMP box itself and
  • what we could reasonably expect to see

Prior to version 8 of ArubaOS we could monitor (physical and virtual AMPs) interfaces, memory, CPU, etc after we have raised a TAC case to get the underlying OS "edited" to allow this. As an aside it's never been clear to me why it requires a TAC case to enable SNMP monitoring of the AMP - this should be baked into the GUI. My understanding** is that Aruba want us to use the AMP as an NMS, but then how do you actually monitor the AMP? Seems very restrictive!!!

Since v8 and up, it seems even the TAC folk can't get it to work as I would expect. Either that, or they are misunderstanding our request, which I feel is quite simple. That being:

TLDR: We'd like to see, via a third party tool of our choice, all the stats you can see via the GUI: > System > Perfomance - as well as being able to see the general state of health of any AMP we manage. Clearly the stats are being pulled from somewhere on the box ...!

Is this too unreasonable a request when literally every other vendor I have ever dealt with in 30yrs of networking, has always allowed for a 3rd party tool to monitor their devices via SNMP. Not just SNMP Traps.

** For the record. I am not trying to be inflammatory, and I accept my understanding might be wrong. However my experience is very much aligned to the above. I am genuinely wanting to know from those out there that use other monitoring tools i.e. SolarWinds, WhatsUp Gold, Zabbix, etc, etc how you monitor your AMPs, and what your expectation is (/was) and what your experience actually is?

Diolch yn fawr.

This is endemic of the replies and help I get.

I am not high enough up the food chain to be able to liaise with anybody in an 'accounts team' and why should I need to work with anybody to have something that should be present, and I repeat from earlier, in every networking kit I have ever dealt with with the exception of Aruba.

What makes Aruba consider themselves above normal methodologies for management and reporting. 

We don't have, and don't use Glass but we do have a vendor agnostic NMS. It's about time Aruba got up to speed and allowed other NMS's to "see" into their products.

These triggers set on AMP can be sent to External Email/NMS server.

If AMP (or any network device) has issues with Disk or CPU, it is unlikely they respond to SNMP queries or send SNMP traps as SNMP is lower priority.

There are SNMP alerts that can be sent from AMP to external NMS system for the generated ones.

AMP health can be monitored (with historical info) under System > Performance page.

AMP has AirWave Glass which can monitor one or more AirWave servers to monitor AMP health along with providing consolidating data from multiple AMPs.

w.r.t to ask, I suggest working with your Accounts team to work with Product management.

You haven't really answered my base question, which if it was missed was: How should I monitor the AMP platform?

>> The ask is not unreasonable. 

I'm not sure what you mean by this.

>> there are triggers to configure for AMP health and alert if there's high disI/O or CPU or memory or services like VisualRF.

Are these are internal triggers on the AMP? If so, how does that work when the box is struggling due to high CPU or Memory use and can't communicate this or you can't log on to see that?

>>Additionally, the system > Performance page provides real time AMP status for monitoring the box. 

Again, if I can't logon due to "issues" then how does one determine this?

What about historical access?

What about reporting on these metrics from a unified platform?

>>So, the request never took priority. 

I have certainly witnessed enough people in here alone asking for this that it ought to have a priority.

Let me ask a slightly different question then - how does AMP monitor itself and alert on itself when it is having issues?

To quote some of my schoolboy Latin ... Quis custodiet ipsos custodes?

The reason is the same as you have said - AMP itself is a NMS platform. The ask is not unreasonable. However, there are triggers to configure for AMP health and alert if there's high disI/O or CPU or memory or services like VisualRF. Additionally, the system > Performance page provides real time AMP status for monitoring the box. So, the request never took priority. 

Aruba technology and support in general frustrates me and I accept a lot of that is probably my misunderstanding**, and lack of training which my company is unwilling to pay for! With that said...

I am looking to understand:

• • best practice for monitoring the AMP box itself and
  • what we could reasonably expect to see

Prior to version 8 of ArubaOS we could monitor (physical and virtual AMPs) interfaces, memory, CPU, etc after we have raised a TAC case to get the underlying OS "edited" to allow this. As an aside it's never been clear to me why it requires a TAC case to enable SNMP monitoring of the AMP - this should be baked into the GUI. My understanding** is that Aruba want us to use the AMP as an NMS, but then how do you actually monitor the AMP? Seems very restrictive!!!

Since v8 and up, it seems even the TAC folk can't get it to work as I would expect. Either that, or they are misunderstanding our request, which I feel is quite simple. That being:

TLDR: We'd like to see, via a third party tool of our choice, all the stats you can see via the GUI: > System > Perfomance - as well as being able to see the general state of health of any AMP we manage. Clearly the stats are being pulled from somewhere on the box ...!

Is this too unreasonable a request when literally every other vendor I have ever dealt with in 30yrs of networking, has always allowed for a 3rd party tool to monitor their devices via SNMP. Not just SNMP Traps.

** For the record. I am not trying to be inflammatory, and I accept my understanding might be wrong. However my experience is very much aligned to the above. I am genuinely wanting to know from those out there that use other monitoring tools i.e. SolarWinds, WhatsUp Gold, Zabbix, etc, etc how you monitor your AMPs, and what your expectation is (/was) and what your experience actually is?

Diolch yn fawr.

AMP, like most NMS server's (including Cisco DNAC, Junipers Juno Space NMS, SolarWinds etc) are monitoring tools and highly unlikely they can be monitored by another NMS system. They only send SNMP alerts to external NMS server. This is norm for NMS servers.

All Aruba Networking devices can be monitored using NMS servers (AirWave or SNMP based NMS servers). But AMP itself is an NMS server and it has options to send SNMP alerts and monitor performance pages for its health.

Is the NMS system in your network can be monitored by another NMS server?

w.r.t to the feature, unfortunately this forum is not right place. Please work with your Aruba sales team (Account team) to work with Product management.

This is endemic of the replies and help I get.

I am not high enough up the food chain to be able to liaise with anybody in an 'accounts team' and why should I need to work with anybody to have something that should be present, and I repeat from earlier, in every networking kit I have ever dealt with with the exception of Aruba.

What makes Aruba consider themselves above normal methodologies for management and reporting. 

We don't have, and don't use Glass but we do have a vendor agnostic NMS. It's about time Aruba got up to speed and allowed other NMS's to "see" into their products.

These triggers set on AMP can be sent to External Email/NMS server.

If AMP (or any network device) has issues with Disk or CPU, it is unlikely they respond to SNMP queries or send SNMP traps as SNMP is lower priority.

There are SNMP alerts that can be sent from AMP to external NMS system for the generated ones.

AMP health can be monitored (with historical info) under System > Performance page.

AMP has AirWave Glass which can monitor one or more AirWave servers to monitor AMP health along with providing consolidating data from multiple AMPs.

w.r.t to ask, I suggest working with your Accounts team to work with Product management.

You haven't really answered my base question, which if it was missed was: How should I monitor the AMP platform?

>> The ask is not unreasonable. 

I'm not sure what you mean by this.

>> there are triggers to configure for AMP health and alert if there's high disI/O or CPU or memory or services like VisualRF.

Are these are internal triggers on the AMP? If so, how does that work when the box is struggling due to high CPU or Memory use and can't communicate this or you can't log on to see that?

>>Additionally, the system > Performance page provides real time AMP status for monitoring the box. 

Again, if I can't logon due to "issues" then how does one determine this?

What about historical access?

What about reporting on these metrics from a unified platform?

>>So, the request never took priority. 

I have certainly witnessed enough people in here alone asking for this that it ought to have a priority.

Let me ask a slightly different question then - how does AMP monitor itself and alert on itself when it is having issues?

To quote some of my schoolboy Latin ... Quis custodiet ipsos custodes?

The reason is the same as you have said - AMP itself is a NMS platform. The ask is not unreasonable. However, there are triggers to configure for AMP health and alert if there's high disI/O or CPU or memory or services like VisualRF. Additionally, the system > Performance page provides real time AMP status for monitoring the box. So, the request never took priority. 

Aruba technology and support in general frustrates me and I accept a lot of that is probably my misunderstanding**, and lack of training which my company is unwilling to pay for! With that said...

I am looking to understand:

• • best practice for monitoring the AMP box itself and
  • what we could reasonably expect to see

Prior to version 8 of ArubaOS we could monitor (physical and virtual AMPs) interfaces, memory, CPU, etc after we have raised a TAC case to get the underlying OS "edited" to allow this. As an aside it's never been clear to me why it requires a TAC case to enable SNMP monitoring of the AMP - this should be baked into the GUI. My understanding** is that Aruba want us to use the AMP as an NMS, but then how do you actually monitor the AMP? Seems very restrictive!!!

Since v8 and up, it seems even the TAC folk can't get it to work as I would expect. Either that, or they are misunderstanding our request, which I feel is quite simple. That being:

TLDR: We'd like to see, via a third party tool of our choice, all the stats you can see via the GUI: > System > Perfomance - as well as being able to see the general state of health of any AMP we manage. Clearly the stats are being pulled from somewhere on the box ...!

Is this too unreasonable a request when literally every other vendor I have ever dealt with in 30yrs of networking, has always allowed for a 3rd party tool to monitor their devices via SNMP. Not just SNMP Traps.

** For the record. I am not trying to be inflammatory, and I accept my understanding might be wrong. However my experience is very much aligned to the above. I am genuinely wanting to know from those out there that use other monitoring tools i.e. SolarWinds, WhatsUp Gold, Zabbix, etc, etc how you monitor your AMPs, and what your expectation is (/was) and what your experience actually is?

Diolch yn fawr.

Respectfully, you are wrong.  As already mentioned I do not have access to an account team and this is the perfect place to discuss a vendor specific issue. 

If, as you insist, AMP can't be monitored then why was it previously monitorable on AOS v7 and down? It's only since Aruba moved to v8 and up that the functionality that was there has disappeared.

So to return this thread back to the point where I started it...and hopefully you won't side-track it again.

HOW do we monitor AMP(s) now that they are running AOS v8 and up?

------------------------------
Stuart D

Original Message:
Sent: Oct 18, 2023 10:52 AM
From: Gowri Amujuri
Subject: Monitoring the Aruba Mgmt Platform (AMP) - how?

AMP, like most NMS server's (including Cisco DNAC, Junipers Juno Space NMS, SolarWinds etc) are monitoring tools and highly unlikely they can be monitored by another NMS system. They only send SNMP alerts to external NMS server. This is norm for NMS servers.

All Aruba Networking devices can be monitored using NMS servers (AirWave or SNMP based NMS servers). But AMP itself is an NMS server and it has options to send SNMP alerts and monitor performance pages for its health.

Is the NMS system in your network can be monitored by another NMS server?

w.r.t to the feature, unfortunately this forum is not right place. Please work with your Aruba sales team (Account team) to work with Product management.

------------------------------
Regards
Gowri Amujuri

Original Message:
Sent: Oct 18, 2023 10:29 AM
From: stuart_d1
Subject: Monitoring the Aruba Mgmt Platform (AMP) - how?

This is endemic of the replies and help I get.

I am not high enough up the food chain to be able to liaise with anybody in an 'accounts team' and why should I need to work with anybody to have something that should be present, and I repeat from earlier, in every networking kit I have ever dealt with with the exception of Aruba.

What makes Aruba consider themselves above normal methodologies for management and reporting. 

We don't have, and don't use Glass but we do have a vendor agnostic NMS. It's about time Aruba got up to speed and allowed other NMS's to "see" into their products.

------------------------------
Stuart D

Original Message:
Sent: Oct 18, 2023 10:21 AM
From: Gowri Amujuri
Subject: Monitoring the Aruba Mgmt Platform (AMP) - how?

These triggers set on AMP can be sent to External Email/NMS server.

If AMP (or any network device) has issues with Disk or CPU, it is unlikely they respond to SNMP queries or send SNMP traps as SNMP is lower priority.

There are SNMP alerts that can be sent from AMP to external NMS system for the generated ones.

AMP health can be monitored (with historical info) under System > Performance page.

AMP has AirWave Glass which can monitor one or more AirWave servers to monitor AMP health along with providing consolidating data from multiple AMPs.

w.r.t to ask, I suggest working with your Accounts team to work with Product management.

------------------------------
Regards
Gowri Amujuri

Original Message:
Sent: Oct 18, 2023 10:06 AM
From: stuart_d1
Subject: Monitoring the Aruba Mgmt Platform (AMP) - how?

You haven't really answered my base question, which if it was missed was: How should I monitor the AMP platform?

>> The ask is not unreasonable. 

I'm not sure what you mean by this.

>> there are triggers to configure for AMP health and alert if there's high disI/O or CPU or memory or services like VisualRF.

Are these are internal triggers on the AMP? If so, how does that work when the box is struggling due to high CPU or Memory use and can't communicate this or you can't log on to see that?

>>Additionally, the system > Performance page provides real time AMP status for monitoring the box. 

Again, if I can't logon due to "issues" then how does one determine this?

What about historical access?

What about reporting on these metrics from a unified platform?

>>So, the request never took priority. 

I have certainly witnessed enough people in here alone asking for this that it ought to have a priority.

Let me ask a slightly different question then - how does AMP monitor itself and alert on itself when it is having issues?

To quote some of my schoolboy Latin ... Quis custodiet ipsos custodes?

------------------------------
Stuart D

Original Message:
Sent: Oct 18, 2023 09:40 AM
From: Gowri Amujuri
Subject: Monitoring the Aruba Mgmt Platform (AMP) - how?

The reason is the same as you have said - AMP itself is a NMS platform. The ask is not unreasonable. However, there are triggers to configure for AMP health and alert if there's high disI/O or CPU or memory or services like VisualRF. Additionally, the system > Performance page provides real time AMP status for monitoring the box. So, the request never took priority. 

------------------------------
Regards
Gowri Amujuri

Original Message:
Sent: Oct 18, 2023 05:44 AM
From: stuart_d1
Subject: Monitoring the Aruba Mgmt Platform (AMP) - how?

Aruba technology and support in general frustrates me and I accept a lot of that is probably my misunderstanding**, and lack of training which my company is unwilling to pay for! With that said...

I am looking to understand:

• • best practice for monitoring the AMP box itself and
  • what we could reasonably expect to see

Prior to version 8 of ArubaOS we could monitor (physical and virtual AMPs) interfaces, memory, CPU, etc after we have raised a TAC case to get the underlying OS "edited" to allow this. As an aside it's never been clear to me why it requires a TAC case to enable SNMP monitoring of the AMP - this should be baked into the GUI. My understanding** is that Aruba want us to use the AMP as an NMS, but then how do you actually monitor the AMP? Seems very restrictive!!!

Since v8 and up, it seems even the TAC folk can't get it to work as I would expect. Either that, or they are misunderstanding our request, which I feel is quite simple. That being:

TLDR: We'd like to see, via a third party tool of our choice, all the stats you can see via the GUI: > System > Perfomance - as well as being able to see the general state of health of any AMP we manage. Clearly the stats are being pulled from somewhere on the box ...!

Is this too unreasonable a request when literally every other vendor I have ever dealt with in 30yrs of networking, has always allowed for a 3rd party tool to monitor their devices via SNMP. Not just SNMP Traps.

** For the record. I am not trying to be inflammatory, and I accept my understanding might be wrong. However my experience is very much aligned to the above. I am genuinely wanting to know from those out there that use other monitoring tools i.e. SolarWinds, WhatsUp Gold, Zabbix, etc, etc how you monitor your AMPs, and what your expectation is (/was) and what your experience actually is?

Diolch yn fawr.

------------------------------
Stuart D
------------------------------

Aruba technology and support in general frustrates me and I accept a lot of that is probably my misunderstanding**, and lack of training which my company is unwilling to pay for! With that said...

I am looking to understand:

• • best practice for monitoring the AMP box itself and
  • what we could reasonably expect to see

Prior to version 8 of ArubaOS we could monitor (physical and virtual AMPs) interfaces, memory, CPU, etc after we have raised a TAC case to get the underlying OS "edited" to allow this. As an aside it's never been clear to me why it requires a TAC case to enable SNMP monitoring of the AMP - this should be baked into the GUI. My understanding** is that Aruba want us to use the AMP as an NMS, but then how do you actually monitor the AMP? Seems very restrictive!!!

Since v8 and up, it seems even the TAC folk can't get it to work as I would expect. Either that, or they are misunderstanding our request, which I feel is quite simple. That being:

TLDR: We'd like to see, via a third party tool of our choice, all the stats you can see via the GUI: > System > Perfomance - as well as being able to see the general state of health of any AMP we manage. Clearly the stats are being pulled from somewhere on the box ...!

Is this too unreasonable a request when literally every other vendor I have ever dealt with in 30yrs of networking, has always allowed for a 3rd party tool to monitor their devices via SNMP. Not just SNMP Traps.

** For the record. I am not trying to be inflammatory, and I accept my understanding might be wrong. However my experience is very much aligned to the above. I am genuinely wanting to know from those out there that use other monitoring tools i.e. SolarWinds, WhatsUp Gold, Zabbix, etc, etc how you monitor your AMPs, and what your expectation is (/was) and what your experience actually is?

Diolch yn fawr.

Sort of disappointed that nobody else other than a staff member has responded to this! I know, from conversations elsewhere, I'm not the only one that believes their approach to monitoring, etc is right. 

And as such I really wanted others (i.e. not staff) input.

Aruba technology and support in general frustrates me and I accept a lot of that is probably my misunderstanding**, and lack of training which my company is unwilling to pay for! With that said...

I am looking to understand:

• • best practice for monitoring the AMP box itself and
  • what we could reasonably expect to see

Prior to version 8 of ArubaOS we could monitor (physical and virtual AMPs) interfaces, memory, CPU, etc after we have raised a TAC case to get the underlying OS "edited" to allow this. As an aside it's never been clear to me why it requires a TAC case to enable SNMP monitoring of the AMP - this should be baked into the GUI. My understanding** is that Aruba want us to use the AMP as an NMS, but then how do you actually monitor the AMP? Seems very restrictive!!!

Since v8 and up, it seems even the TAC folk can't get it to work as I would expect. Either that, or they are misunderstanding our request, which I feel is quite simple. That being:

TLDR: We'd like to see, via a third party tool of our choice, all the stats you can see via the GUI: > System > Perfomance - as well as being able to see the general state of health of any AMP we manage. Clearly the stats are being pulled from somewhere on the box ...!

Is this too unreasonable a request when literally every other vendor I have ever dealt with in 30yrs of networking, has always allowed for a 3rd party tool to monitor their devices via SNMP. Not just SNMP Traps.

** For the record. I am not trying to be inflammatory, and I accept my understanding might be wrong. However my experience is very much aligned to the above. I am genuinely wanting to know from those out there that use other monitoring tools i.e. SolarWinds, WhatsUp Gold, Zabbix, etc, etc how you monitor your AMPs, and what your expectation is (/was) and what your experience actually is?

Diolch yn fawr.