Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

ACE - SNMP Monitoring

ACE - SNMP Monitoring

To monitor the ACE's Rserver status, one can poll the following OID:


However, a topic I am not familiar with; is the SNMP method for storing the ascii values of those Rserver names.
Whereby the table values of Rserver are respresented by what I understand as variable-length OID string index (If that's even a proper name).

So unless your SNMP application/vendor is willing to write code to convert those values; your SNMP table output is useless; with the exception of the right hand column, showing values for its OperStatus.

An easy way to transform these results, as I had on the CSS, is to use the OID for the Server Names (Services on the CSS)

The RserverName equivelant OID for the ACE is as follows:


However, for some odd reason (does anyone know why?); Cisco decided to mark its permission as 'not accessible'

Had it been set to 'read-only' so I could poll that data; then my SNMP application, Solarwinds Orion, would have been able to transform those results properly and without any further development support.

I did open a TAC case to clarify; most specificaly to ask why they restricted the use of the RserverName OID...but he had no answers; just that the OperStatus OID was enough and it was up to my SNMP application read the OID index out as ascii.

Currently, I am waiting and hoping the Solarwinds development team will release a MIB update that will satisfy my needs.

Any information as to why Cisco restricts Rserver name OID or why one often finds these ascii values hidden in the OID index would be appreciated.

Thank You,


Below, is an example of the output of OperStatus:

Left Column is the OID format of the ascii Rserver Name