smartd

I think one of the best things Solarwinds could do is to move away from being Cisco centric. Support for Juniper would be awesome. I currently have 210 Junos nodes, 48 Netscreen, 114 Trapeze (now Juniper) and 5 Neotoris (Juniper IVE) nodes in my database. -=Dan=-

Bump!

Add support for Juniper/Trapeze wireless controllers. Also Ubiquity networks, however they are in need of a MIB update.

Instead of buying another company, just integrate the open source "Simple Event Correlator" into all alerting products. See SEC - open source and platform independent event correlation tool

Totally agree on the need for address de-duplication,, but there is more needed: 1. For routers we have a WAN IP address and a LAN IP address (and possibly a loopback). We manage the LAN IP address in Orion, since that keeps the router address in the same subnet as the plant devices. Our WAN IP is assigned by our carrier,…

This should be available in any product that has MAC addresses, like IPAM.

Did you compare this product to Sunview Changegear Service Desk? I'd be interested in understanding the pros and cons.

In NPM 12 (Note: I filter with a parameter from the Nodes.Custom table) SELECT NodesData.Caption, NodesData.IP_Address, NetObjectDowntime.DateTimeFrom, (CAST((DateDiff(MINUTE, NetObjectDowntime.DateTimeFrom, SYSUTCDATETIME()) / 1440) AS nvarchar(200)) + ':' + CAST(((DateDiff(MINUTE, NetObjectDowntime.DateTimeFrom,…

Totally agree that this needs to be done. I'd love to fix my database, and allow my updates to go to Solarwinds as additions to a master database. The whole MIB and MachineType update process is totally broken. Use posts to a thread to manage updates? Really? I'd like to use something like a bugzilla to track these updates.

Search from the summary module screen should work JUST AS FAST and as simply as the search from Manage Nodes. Search Node Names and IP addresses by default.

Check to see if the SysObjectID is different between devices.

I've migrated to monitoring BOTH nodes and interfaces. Monitoring interfaces is important for detecting the problem with one circuit in an NxT1(E1) solution, and I monitor tunnels (st0 logical interfaces) and sometimes VLAN logicals. As we know, the ability to ping and whether an interface is up is two different things…

Yes. Very frustrating. 

How bout an alert when the machine type or device description changes? (assuming the community stays the same) How bout Orion trying to fix itself when the device pings but SNMP can't connect. Try all the communities in the community store, and then alert that SNMP Community changed.

The main problem for us is that NCCM is Cisco-centric. Things like HP Procurve and Juniper are hardly supported.

24hr, Zulu time that is different than my local timezone. And support the timezone on the Orion server to be different than the database server.

My thinking was like Peter's. Use the SEC concepts: Currently Advanced Alerts only have Single and SingleWithSuppress. The SEC language includes SingleWithThreshold which COUNTS to number of occurances over a time windows. And there are Pair and PairWithThreshold which trigger when two conditions occur, such as interface…

That's actually the intent: The only thing staying the same is the IP and Node-Name. So this option would remove the device and interfaces and then run a discovery on the IP using the community credential store. Only other stats to keep is the event history and audit history for the device. I would like this to be done…

Agree

My use case is in IPAM or NPM to determine what a device is when it does not have SNMP. The best thing would be to do a NMAP service version and OS detection scan and record the results. Determining the MAC and doing a Manuf lookup would be helpful. nmap -sC -sS -sU -sV -T3 -O -F --version-light

Check out this sec rule base for Cisco and think of the possibilities... http://simple-evcorr.sourceforge.net/rulesets/cisco-syslog.sec

The whole MIB/Machine Type functionality is broken. Requests for Machine Type updates go into the black hole. Updates should be automatic, and users should be able to submit changes using a form in a system similar to adding a support case. -=Dan=-

So my strategy is to setup a Linux server with Syslog-NG. The problem is handling traps. I found some code that will convert a trap into a syslog message and pump it into Syslog-NG. In Syslog-NG I can filter noise messages to avoid further processing. Then I can deliver the syslog message to Simple Event Correlator…

This would be GREAT functionality, and much more manageable than trying to create compliance policies. You would need to be able to specify the items to ignore. Our templates have search and replace "keywords" for things like IP addresses, gateways, hostnames, etc.

Adding machine types should not be such a complex issue. Why aren't these stored in the database so they can be easily and dynamically updated? -=Dan=-

Gob: Only issue with your suggestion is that both Down Nodes and your Module have the exact same filter query. ========================================== vumc-swdbrowns-1332073 RTR Plant vumc-mwddekalb-1332103 RTR Plant vumc-medwestpo-1331951 RTR Plant vumc-swdgroesb-1332085 RTR Plant vumc-swdbrowns-1332073 RTR Plant…

I've given this example to the PMs several times. We use Yammer internally for out-of-band trouble discussions in the NOC. They have a feature voting system run by uservoice.com. You can see it at http://yammer.uservoice.com. Its absolutely ideal. ctopaloglu was right on the money about the multiple IP problem. I built a…

Here's what I see in Orion. Note, I use a filter to get rid of alot of non-critical devices (same in both resources) NodeType = 'RTR' OR Category = 'CORE'

I find this a pain. I found I'm better off sending syslog to Splunk. Kiwi could hold thinks in variables allowing you to count events. Very useful. The Syslog and Traps in Orion are rudimentary. I'm still looking for a complete event correlation tool set in these products. I suggest the commands available in the opensource…

Name units minimum maximum currentvalue defaultvalue ---------------------- ----- ------------- ------------- ------------- ------------- Events Retention days 1365 30 30 (1 row(s) affected) =============================================== Caption status severity statusdescription…