We're having trouble getting Network Discovery to work. I've set it up with all of our subnets and also provided the domain name. I've enable searching local domains and have verified that the component is running by reviewing the netdisc.log.
I've got a couple of subnets that I'm trying to discover resources on discovery can't find them.
I don't have anything set for SNMP communities or devices.
To successfully discover and monitor SNMP-enabled devices using Operations Manager, you will defintely need to know the read only community string of the device, and it must be configured to accept communication from Operations Manager. Here are some resources to assist.
Here are some resources to help with SNMP device discovery
Here's a post from an SNMP blog series on what discovery is doing behind the scenes:
http://www.systemcentercentral.com/BlogDetails/tabid/143/IndexId/13018/Default.aspx
How to verify SNMP support in network devices
http://www.systemcentercentral.com/BlogDetails/tabid/143/IndexID/19277/Default.aspx
Here are some resources to help with SNMP device monitoring
How to configure OpsMgr as an SNMP Trap Receiver
http://www.systemcentercentral.com/BlogDetails/tabid/143/IndexId/13020/Default.aspx
Thanks, I'll work with our networking guys and see if I can get the community names and see what I need to do to have them add permissions for our SCCM server.
Any other gotcha's you can think of? Thanks for the fast reply.
From a discovery perspective, the process is relatively straightforward. Bear in mind that Operations Manager only monitors up/down status using an SNMP get on the SysName property. There is no discovery of device components or interfaces.
How to monitor non-Windows devices in Operations Manager
If you want to monitor more specific aspects of an SNMP-enabled device, that will raise a whole new set of questions. Have a look at this document as a start, but I have no doubt we'll have more specific scenarios to discuss. At that point, you may also look into some MS Partner solutions that bring additional functionality to the show, such as Quest and Jalasoft.
Unless you have a need to capture network devices and printers(which has little use in ConfigMgr anyways), leave network discovery disabled, which is the default. Majority of the environments out there use AD systems discovery which is all you'll need to populate systems into your collections. Once you configure the local domain, check the box to run now, wait 5minutes and update the all systems collection. You should see them populated(may need to F5 till the hour glass goes away). Then after boundaries are setup, you can push the client to start managing..
Also, make sure you setup a FSP role and add FSP=mpservername into the client push properties. There are specific reports that help troubleshoot the next part, any client installation problems..