> I scanned up some routers that fit the profile of my custom device > 'Cisco3600' - that template includes the Interface service. My newly > discovered device gets modeled but quickly goes magenta, > indicating service down.
Ah, I see where your original issue came from. We added something to services in 7.0 that you are missing out on, and it happens that the auto discovery is filling it in for you. Let me explain. When you add a service manually to a host (by clicking ADD in the Services list for that host), you now get a dialog that has three input boxes. Two of these are new. One is a "comment" field that lets you record why you are monitoring that service. No explanation needed there. But the other (the middle one on the dialog) is marked "Arguments". This is a new capability in WUG 7.0 that allows a special customization value be passed to each service to match it to particulars of that host. (The fact that you used a custom host type to put Interface on your hosts helped hide this from you, since you didn't get to see the Add dialog from there). In previous versions of WUG, if you wanted to use the SNMP Threshold service to monitor interfaces, you would have had to set up a separate custom service for each possible interface number on the target. I.e. one to monitor "Interface 1", another to monitor "Interface 2" and so on. It was very tedious. In WUG 7 this new argument field allows us to have a single custom service definition called Interface, and store the interface numbers with the host, where they belong. The flip side of this is that if you create an "Interface" service definition on a host manually, and you leave the Argument blank, it will fail! The argument is essential because of the way "Interface" is defined. That's why you were seeing a down result. If you open Logs | Debug Log..., and then right click the affected host and choose Check Now (or waited for a poll), you would have seen something like this: Checking 192.168.0.1 : 00 : Interface No argument SNMPMON [Interface] OID:1.3.6.1.2.1.2.2.1.8 on IP:192.168.0.1 SNMPMON ERROR: SNMP GET failed! Check Complete (-2) 192.168.0.1 : 00 : Interface No argument That would have showed you why it was failing - because there was no argument present. The MIB-II OID 1.3.6.1.2.1.2.2.1.8 is not a valid one to fetch, you need at least one more element on there to specify which interface number you are requesting. That's what the (missing) argument supplies. When you use Auto Discover to fill in the Interfaces, these arguments get filled in for you automatically, based on what the host actually has. I recommend you use Auto Discover (or Discover Devices / New Map Wizard, which do the same thing) to populate your Interface services, rather than doing it manually. The argument field is actually generically useful for any custom service you build that is based on the "SNMP Monitoring" monitor. It always gets appended to the OID that is in the custom service at poll time. So you can build your own SNMP checks that behave the way Interface does in this respect (minus the auto-discovery part). Currently there aren't any other service monitors (besides "SNMP Monitoring") that use the custom argument, but it is exposed through the API so third parties can use it if needed. (Indeed, in WUG 7 all the service monitoring uses the very same API we publish to the outside world). Hope that makes sense. --Tim Farley IPSWITCH Please visit http://www.ipswitch.com/support/mailing-lists.html to be removed from this list. An Archive of this list is available at: http://www.mail-archive.com/whatsup_forum%40list.ipswitch.com/
