NNMi monitoring of APs

Question

Hi there.  We are monitoring various Cisco Aps through NNMi.  All was fine till a few days ago, when a threshold was set, and all the APs of a certain model started showing alarms and not clearing.
The model in question is mainly a 1262, and NNMI has started monitoring these OIDs
hajap177-0204:
Policy: Cisco Memory Pool Performance Monitoring
Target: 10.230.4.84
Poller: NnmSnmpPoller, Target Responding: true, Poll Successful: true, Poll Duration: 15 mSec
sysUpTime 520969360
Object    | memoryUtil | freeMemory | ciscoMemoryPoolUsed | ciscoMemoryPoolFree
----------|------------|------------|---------------------|--------------------
I/O.8     | 0.51       | 16300.51   | 85496               | 16691720          
Processor | 39.87      | 40440.8    | 27457288            | 41411380          
I/O.2     | 85.94      | 4608.1     | 28835736            | 4718696    
hajap217-0601:
Policy: Cisco Memory Pool Performance Monitoring
Target: 10.230.4.124
Poller: NnmSnmpPoller, Target Responding: true, Poll Successful: true, Poll Duration: 34 mSec
sysUpTime 1470244695
Object    | memoryUtil | freeMemory | ciscoMemoryPoolUsed | ciscoMemoryPoolFree
----------|------------|------------|---------------------|--------------------
Processor | 39.81      | 40483.46   | 27413604            | 41455064          
I/O.2     | 85.94      | 4608.1     | 28835736            | 4718696           
I/O.8     | 0.51       | 16300.51   | 85496               | 16691720    
Namely it's the I/O.2 that is causing the problem, as the threshold is set at 85%, and its sitting at 85.9.  I've looked at several APs, and the all show the same memory usage, and it doesn't change hour on hour,
which leads me to believe that that's how it's meant to behave, there's nothing to worry about, and we should just set our threshold to 90%.  The problem lies in the fact that we are a big cumbersome company, and the NOC won't change the threshold without documentary evedence that the threshold should be changed (they can't tell me on what information they based the decision to chose 85% for this particular OID.....). 
Can anyone tell me what the difference between the I/O.2 and the I/O.8 is?  and it there a Cisco recommended baseline to monitor against?
Cheers, Al.

Answer 1

My team has
been working a similar issue where our application compliance was slowly changing from success to error using SCCM 2012 (no SP1). After 3 weeks of
working with Microsoft we finally resolved this issue. We are using task sequences to deploy application stacks. There is a known bug that causes issues
when changing the task sequence to update the rev of an application in it (allegedly fixed in SP1). The TS was still referencing an old version of the application despite our updates and from the console you can't tell. When the machine runs its policy evaluation
and hits one of these apps it stops fails the evaluation of all applications. So, App "A" has the issue in the TS, you deploy App "B" and initial compliance looks good until the App Policy runs and hits the issue for App "A" and
report an error for your App "B" deployment
CIAgent.log
(The prod version of this app is "12", below you can see the TS was still using version "10"
CIAgentJob({BB81C59E-0D68-4F80-8C26-F3672FDA6993}): CAgentJob::VersionInfoTimedOut for ModelName
ScopeId_FBAD85CC-8425-4A82-9A2A-A69D6941A909/RequiredApplication_826f927c-b7b4-446b-9767-9e03529677ff,
version 10 not available.
CCIInfo::SetError - Setting CI level error to (0x87d00314). <- this repeated many times
VersionInfo ModelName=ScopeId_FBAD85CC-8425-4A82-9A2A-A69D6941A909/RequiredApplication_826f927c-b7b4-446b-9767-9e03529677ff,
Version=10, IsVersionSpecific=TRUE timed out
The results of this SQL query give you a link to XML to reveal the
friendly name of the offending application.
select
top 10 *
from CI_ConfigurationItems where CI_UniqueID
like '%/Application_826f927c-b7b4-446b-9767-9e03529677ff%'
Once we had this we removed it from the task sequence then added it back in. Once all the clients check in and run the App Policy again they will see the update and magically all the errors
for unrelated applications changed from error to success