↧
MINUTEMAN SNMP-NV6.UnDP
↧
Monitoring Feature-Function Matrix (XLS)
↧
↧
What We're Working on for NPM (Updated July 28, 2015)
Since the release on NPM 11.5 we've been hard at working building the next round of exciting functionality and improvements in existing functionality. I'm excited to share the following list of items we're working on:
- Updated UI Look and Feel - The UI is receiving some love this release, spanning across NPM, SAM, VMAN, and the other Orion based products.
- Deep Visibility into F5 load balancers - Covering things like connection counts by VIP and server. NPM F5 info FEATURE REQUEST - F5 Load Balancers - Show Wide IP status, GTM Server List, etc - Case #448234
- Monitoring for Cisco Switch Stacks (3750, 3850, 2960S) - Covering things like stack master, stack ring health, enumerating members, tracking member changes, per member hardware health, and so on. Cisco Stack monitoring
- Syslog / Traps / search improvements - Search Enhancements
- Unmanage behavior improvements - Unmanage reason (like shutdown tracker in Windows 2008)Silence Alerts While Still MonitoringUnmanage reason (like shutdown tracker in Windows 2008)Show 'Unmanaged' durationSilence Alerts While Still Monitoring
- Manage Pollers improvements - map sysoid values to arbitrary text for node details properties. Unknown Devices: admin mapping of sysObjectID to Vendor and MachineType
- Enhancements to view restrictions
- QoE Transport-Layer Metrics
Ongoing Initiatives:
- Increased scalability per SolarWinds instance (target of 250k elements / instance)
- Improved performance and decreased resource load times via analysis with SolarWinds DPA
- Increased number of pollers possible per instance
↧
Trap to Event List using Custom SQL Alert
Hi
The image above shows the trap i need to get into the Event list on Orion NPM.
"spSensorValue = 1" should be the Trigger Condition, and "spSensorValue = 0" is the Reset Condition.
I have tried to make a custom sql alert, but can't get it right.
Can someone help me on this one?
Thanks,
Simon
UPDATE:
Case is closed, this is the solution:
Trigger Condition:
INNER JOIN traps a
ON a.nodeid = nodes.nodeid
INNER JOIN trapvarbinds b
ON a.trapid = b.trapid
AND b.oidname = 'spSensorValue'
WHERE a.traptype = 'HHMSAGENT-MIB:spUnknownStatus.301'
AND a.datetime >= Dateadd(second, -15, Getdate())
AND b.oidvalue = '1'
Reset Condition:
INNER JOIN traps a
ON a.nodeid = nodes.nodeid
INNER JOIN trapvarbinds b
ON a.trapid = b.trapid
AND b.oidname = 'spSensorValue'
WHERE a.traptype = 'HHMSAGENT-MIB:spUnknownStatus.301'
AND a.datetime >= Dateadd(second, -15, Getdate())
AND b.oidvalue = '0'
Big thanks to RichardLetts.
when developing these I start with a database query that returns the set of nodes that match the criteria:
SELECTnodeid,
traptype,
oidvalue
FROM trapsa
INNERJOINtrapvarbindsb
ONa.trapid=b.trapid
ANDb.oidname='spSensorValue'
WHERE a.acknowledged=0
ANDtraptype='HHMSAGENT-MIB:spUnknownStatus.301'
ORDER BY a.datetime
This is much faster at developing and testing that trying to use the alert manager to do this. Then convert this into the bit I paste into the 'alert' ; I like to put a time-bound on traps and allow then to be 'acknowledged'
INNERJOIN trapsa
ONa.nodeid=nodes.nodeid
INNERJOINtrapvarbindsb
ONa.trapid=b.trapid
ANDb.oidname='spSensorValue'
WHERE a.acknowledged=0
AND a.traptype='HHMSAGENT-MIB:spUnknownStatus.301'
ANDa.datetime>=Dateadd(hour,-4,Getdate())
ANDb.oidvalue='1'
INNERJOIN trapsa
ONa.nodeid=nodes.nodeid
INNERJOINtrapvarbindsb
ONa.trapid=b.trapid
ANDb.oidname='spSensorValue'
WHERE a.traptype='HHMSAGENT-MIB:spUnknownStatus.301'
ANDa.datetime>=Dateadd(hour,-4,Getdate())
ANDb.oidvalue='0'
Hopefully that is enough to get you started in the right direction
[SOAPBOX]
I have prefer putting the restrictions into the join criteria because they get evaluated how most people expect them to do when you have an outer join.
I like putting the table restrictions in the join criteria when it makes sense, because if you ever need an outer join they work more like you expect them to
Note: the Orion trap receiver incorrectly decoded the trap type. if that ever gets fixed you may have to update your clause.
[/SOAPBOX]
You are going to need some more complex SQL, because you have to check that the last trap received trap for the oidvalue:
INNERJOINtrapsa
ONa.nodeid=nodes.nodeid
ANDa.traptype='HHMSAGENT-MIB:spUnknownStatus.301'
INNERJOINtrapvarbindsb
ONa.trapid=b.trapid
ANDb.oidname='spSensorValue'
WHERE a.acknowledged=0
ANDa.datetime>=Dateadd(hour,-4,Getdate())
ANDa.datetime=(SELECTMax(datetime)
FROM trapst
WHERE t.nodeid=a.nodeid
ANDT.traptype=
'HHMSAGENT-MIB:spUnknownStatus.301')
ANDb.oidvalue='1'
Thanks alot, Richard!
I did some customization of your examples, and now it works perfect for our use.
Trigger Condition:
INNER JOIN traps a
ON a.nodeid = nodes.nodeid
INNER JOIN trapvarbinds b
ON a.trapid = b.trapid
AND b.oidname = 'spSensorValue'
WHERE a.traptype = 'HHMSAGENT-MIB:spUnknownStatus.301'
AND a.datetime >= Dateadd(second, -15, Getdate())
AND b.oidvalue = '1'
Reset Condition:
INNER JOIN traps a
ON a.nodeid = nodes.nodeid
INNER JOIN trapvarbinds b
ON a.trapid = b.trapid
AND b.oidname = 'spSensorValue'
WHERE a.traptype = 'HHMSAGENT-MIB:spUnknownStatus.301'
AND a.datetime >= Dateadd(second, -15, Getdate())
AND b.oidvalue = '0'
This document was generated from the following discussion: Trap to Event List using Custom SQL Alert
↧
Barracuda Web Filter Universal Device Poller
↧
↧
downloadmib.exe
↧
Server Report
↧
linuxatemyram
↧
Checkpoint Firewalls Universal Device Pollers
↧
↧
Cisco ASR Showing 95% 98% Memory Used.
Since we are seeing very frequent issue with ASR Memory Consumption . Let me try to explain in a little details.
Issue: Cisco ASR Showing 95 % / 98 % Memory Consumed.
Troubleshooting :-
When we checked with PollerChecker Tool we found no other Memory Poller are been responded by the Device.
SolarWinds Knowledge Base :: How to Use the Poller Checker Tool
ONLY Responded Memory Poller is CiscoGen3
We then checked from the CiscoGen3 Memory poller i found following .
EXPLANATION OF EACH OID TABLE FUNCTION
cisco MemoryPoolName 1.3.6.1.4.1.9.9.48.1.1.1.2
Cisco ciscoMemoryPoolUsed 1.3.6.1.4.1.9.9.48.1.1.1.5
Cisco CiscoMemoryPoolFree 1.3.6.1.4.1.9.9.48.1.1.1.6
NAME OF MEMORY
.1.3.6.1.4.1.9.9.48.1.1.1.2.1 = STRING: "processor"
.1.3.6.1.4.1.9.9.48.1.1.1.2.6 = STRING: "reserved"
.1.3.6.1.4.1.9.9.48.1.1.1.2.7 = STRING: "image"
TOTAL MEMORY USED BY EACH NAME
.1.3.6.1.4.1.9.9.48.1.1.1.5.1 = GAUGE32: 1791774344
.1.3.6.1.4.1.9.9.48.1.1.1.5.6 = GAUGE32: 134217728
.1.3.6.1.4.1.9.9.48.1.1.1.5.7 = GAUGE32: 66994200
TOTAL PORTION OF MEMORY FREE
.1.3.6.1.4.1.9.9.48.1.1.1.6.1 = GAUGE32: 86892544
.1.3.6.1.4.1.9.9.48.1.1.1.6.6 = GAUGE32: 0
.1.3.6.1.4.1.9.9.48.1.1.1.6.7 = GAUGE32: 0
CALCULATION :
TOTAL USED MEMORY
1791774344 + 134217728 + 66994200 = 1992386272
TOTAL FREE MEMORY
0+0+86892544 = 86892544
TOTAL MEMORY
1992386272 + 86892544 = 2079278816
% MEMORY UTILIZATION
1992386272 % 2079278816 = 95.8 %
/// <summary>
/// Memory poller for devices which support CISCO-MEMORY-POOL MIB (various Cisco devices)
/// <support pollertype="N.Memory.SNMP.CiscoGen3">
/// Poller utilizes GetSubtree request to gather used memory using OID:
/// ciscoMemoryPoolUsed = 1.3.6.1.4.1.9.9.48.1.1.1.5
/// Poller utilizes GetSubtree request to gather free memory using OID:
/// ciscoMemoryPoolFree = 1.3.6.1.4.1.9.9.48.1.1.1.6
/// Used memory is computed as SUM of all ciscoMemoryPoolUsed returned values.
/// Free memory is computed as SUM of all ciscoMemoryPoolFree returned values.
/// Total memory is computed as SUM of used and free memory.
Conclusion:-
By calculation above provided by the Node OID tables values .
Orion is marked the memory correctly by consuming 95% .
However We found the device is responded to following Poller for memory calculation other then the standard Cisco .CISCO-ENHANCED-MEMPOOL-MIB
CISCO-ENHANCED-MEMPOOL-MIB |
|
Memory Free | Memory Used |
.1.3.6.1.4.1.9.9.221.1.1.1.1.20.18788073.1 = COUNTER64: 6196785152 | .1.3.6.1.4.1.9.9.221.1.1.1.1.18.18788073.1 = COUNTER64: 2198077384 |
.1.3.6.1.4.1.9.9.221.1.1.1.1.20.18788073.2 = COUNTER64: 0 | .1.3.6.1.4.1.9.9.221.1.1.1.1.18.18788073.2 = COUNTER64: 134217728 |
.1.3.6.1.4.1.9.9.221.1.1.1.1.20.18788073.3 = COUNTER64: 0 | .1.3.6.1.4.1.9.9.221.1.1.1.1.18.18788073.3 = COUNTER64: 60565808 |
.1.3.6.1.4.1.9.9.221.1.1.1.1.20.26932192.1 = COUNTER64: 4756275200 | .1.3.6.1.4.1.9.9.221.1.1.1.1.18.26932192.1 = COUNTER64: 1417358984 |
.1.3.6.1.4.1.9.9.221.1.1.1.1.20.26932192.2 = COUNTER64: 0 | .1.3.6.1.4.1.9.9.221.1.1.1.1.18.26932192.2 = COUNTER64: 134217728 |
.1.3.6.1.4.1.9.9.221.1.1.1.1.20.26932192.3 = COUNTER64: 0 | .1.3.6.1.4.1.9.9.221.1.1.1.1.18.26932192.3 = COUNTER64: 66994200 |
.1.3.6.1.4.1.9.9.221.1.1.1.1.20.51614490.1 = COUNTER64: 6160363520 | .1.3.6.1.4.1.9.9.221.1.1.1.1.18.51614490.1 = COUNTER64: 2234499016 |
.1.3.6.1.4.1.9.9.221.1.1.1.1.20.51614490.2 = COUNTER64: 0 | .1.3.6.1.4.1.9.9.221.1.1.1.1.18.51614490.2 = COUNTER64: 134217728 |
.1.3.6.1.4.1.9.9.221.1.1.1.1.20.51614490.3 = COUNTER64: 0 | .1.3.6.1.4.1.9.9.221.1.1.1.1.18.51614490.3 = COUNTER64: 60565808 |
.1.3.6.1.4.1.9.9.221.1.1.1.1.20.52690955.1 = COUNTER64: 4381138944 | .1.3.6.1.4.1.9.9.221.1.1.1.1.18.52690955.1 = COUNTER64: 1792495240 |
.1.3.6.1.4.1.9.9.221.1.1.1.1.20.52690955.2 = COUNTER64: 0 | .1.3.6.1.4.1.9.9.221.1.1.1.1.18.52690955.2 = COUNTER64: 134217728 |
.1.3.6.1.4.1.9.9.221.1.1.1.1.20.52690955.3 = COUNTER64: 0 | .1.3.6.1.4.1.9.9.221.1.1.1.1.18.52690955.3 = COUNTER64: 66994200 |
Resolution
We have created Device Poller for such devices (attached )
Cisco ASR Memory Poller is attached .
Download .
Go to Orion Web page > Settings > Manage Nodes >
Import the Poller
You will Notice "Cisco ASR Devices" poller will be included
Now go to the Node and do "List Resources "
Select the "Cisco ASR Devices" Poller
> Submit
Leave the System running for 10 ~ 15 min for the polling .
confirmed the system is now showing correct memory .
↧
Cisco ASR9K
↧
Credentials Used By APM Component Monitors
↧
CPU Utilization Baseline Statistics
↧
↧
Memory Utilization Baseline Statistics
↧
Receive Interface Utilization Baseline Statistics
↧
Transmit Interface Utilization Baseline Statistics
↧
What We're Working on for NPM (Updated July 28, 2015)
Since the release on NPM 11.5 we've been hard at working building the next round of exciting functionality and improvements in existing functionality. I'm excited to share the following list of items we're working on:
- Updated UI Look and Feel - The UI is receiving some love this release, spanning across NPM, SAM, VMAN, and the other Orion based products.
- Deep Visibility into F5 load balancers - Covering things like connection counts by VIP and server. NPM F5 info FEATURE REQUEST - F5 Load Balancers - Show Wide IP status, GTM Server List, etc - Case #448234
- Monitoring for Cisco Switch Stacks (3750, 3850, 2960S) - Covering things like stack master, stack ring health, enumerating members, tracking member changes, per member hardware health, and so on. Cisco Stack monitoring
- Syslog / Traps / search improvements - Search Enhancements
- Unmanage behavior improvements - Unmanage reason (like shutdown tracker in Windows 2008)Silence Alerts While Still MonitoringUnmanage reason (like shutdown tracker in Windows 2008)Show 'Unmanaged' durationSilence Alerts While Still Monitoring
- Manage Pollers improvements - map sysoid values to arbitrary text for node details properties. Unknown Devices: admin mapping of sysObjectID to Vendor and MachineType
- Enhancements to view restrictions
- QoE Transport-Layer Metrics
Ongoing Initiatives:
- Increased scalability per SolarWinds instance (target of 250k elements / instance)
- Improved performance and decreased resource load times via analysis with SolarWinds DPA
- Increased number of pollers possible per instance
↧
↧
Cisco UCS Chassis Slot Information.UnDP
↧
GNS3 to SolarWinds NPM Integration Guide
↧
Monitoring 101 ebook
↧