![]() ![]() The view can be found in the Monitoring space under “Operations ManagerNetwork DiscoveryNetwork Discovery Progress Events”. Thankfully, Microsoft created a view (and a rule) to pick-up and show all the relevant events for the network discovery progress right in the console: Once you are sure the MP was configured correctly and was successfully deployed to the managing management server, examine the discover events… 3.2 Events Once you export and open this management pack in a text editor, you’ll see the module configuration for the discovery:įirst thing worth checking is to look into that MP and see if the configuration you’ve done with the wizard is reflected in the MP. After you finished the wizard, start the discovery:Īfter you finished the wizard, an unsealed management pack with the name “” will be modified with your configuration. The discovery schedule was set to manually. Besides, I learned a lot about network discovery which might help in other scenarios… To tell you upfront, selecting only SNMP will successfully add my device but in this case I want to know why ICMP and SNMP is not working – especially since my discovery management server can successfully ping the machine. Note that I selected “ICMP and SNMP” as Access mode. Only the parts necessary for this case will be discussed.īecause I only want to discover one single device, I chose “Explicit discovery” as discovery method. I will not go through all the options, the wizard provides. Let’s have a look how discovery is set up and how it’s working: When you create a network discovery rule you go through a wizard providing a lot of information about discovery methods, accounts, devices, schedule, etc. No response ping?! Needless to say that my management server is able to ping the device and responds just nice to the ping requests. After a while the “Network Devices Pending Management” view shows my device: The actual discovery process runs asynchronously but more on that later in the Discovery section. The task window shows that the discovery job was successfully kicked off but this doesn’t really mean that the discovery is already done. Running the discovery manually showed that the task completed successfully: By the time of RTM, Microsoft should release a complete list of supported network devices… (see Update 2 below)Īs soon as I started the network device discovery I realized that my device couldn’t be discovered. SCOM doesn’t really know much about those devices and are therefore handled as a “generic” device with a very limited set of monitoring rules (mostly availability and response times but no monitoring of ports, CPU, bandwidth etc.). Supported Cisco routers for example are monitored much more detailed than a consumer grade Zyxel Zywall-2. First you should know, that SCOM treats certain devices different as others. My small lab environment doesn’t really have lots of high-end network devices (in fact the number of high-end network devices in my lab is ZERO!) but I thought why not bring in my low-end, consumer grade devices for testing. I thought it’s time to do the same and share some experience I had with network discovery. I guess everyone is testing SCOM 2012 Beta right now and a lot of people are already blogging about their experience. I’ll try to repro the issue in the upcoming releases to see if the behavior changed and provide updates if necessary. The following article applies to SCOM 2012 BETA and may or may not apply to RC or RTM release.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |