Import MIBs to monitor network devices
A way to import MIB's into SCOM to monitor network devices. This would open a new way to monitor network capabilities from third parties who delivers MIB's.
With the release of System Center 2016 Operations Manager, you now have access to the new Network Monitoring Management Pack generator tool which provides you with extended monitoring for your SNMP-enabled devices by generating your own custom Management Pack. Till tool also has an inbuilt MIB browser which allows you to import MIBs.
More information is available here: https://blogs.technet.microsoft.com/momteam/2016/10/20/system-center-operations-manager-extensible-network-monitoring/
Will 2019 support v3 Trap? It is a huge requirement in our organisation with 7000+ network devices, and in-house security is setting standards that devices must be configured with SNMP v3 but we can't monitor v3 Traps with SCOM??? Frustrating we can't provide this monitoring capability to our customers of their devices, and makes the monitoring team look bad.
This is no practical tool for snmpv3. You can only edit snmpv2 - so the issue about snmpv3 Traps will not be solved by this. where will be the solution for snmpv3 traps...
have you actually tested your own tool? its not a practical solution for production (eg. you cant edit a created mp, no support for overrides of monitored parameters etc ...)
in my opionin its far from completed...
Blog on the availability of this capability - https://blogs.technet.microsoft.com/momteam/2016/10/20/system-center-operations-manager-extensible-network-monitoring/
As suggested by Gerald, will mark this idea as closed and included in SCOM 2016.
Gerald Versluis commented
Would it be possible to mark this idea as "closed and included in SCOM 2016" so people can have their votes back?
Stefan Roth commented
Awesome! When will SCOM TP 5 available?
Thanks for all the feedback. We (SCOM team) are excited to share with you that we would have our first version of “Network Monitoring Management Pack Generation Tool” as part SCOM 2016 Technical Preview 5.
The Network Monitoring Management Pack generation tool would help the user generate Management Pack to add extended monitoring support for new network devices, without the need of Microsoft device certification. It would be a command line tool with an input XML file in which customers would need to define SNMP based monitors and rules for the network device. In addition to the current extended monitoring support for Network devices (Processor and Memory monitoring), this tool would enable the customers to add monitoring for additional device components such as fan, temperature sensor, voltage sensor and power supply.
Albert Neef commented
Yes a must have.. Via importing the MIBs SCOM is always up to date with supporting the new networkdevices. 3+ votes for me. On this moment I have problems with monitor the new Cisco Nexus model. Only port and inferfaces are only monitored.
Im in the process in purchasing a MIB to MP third party tool. Would be great if Microsoft can create a tool within SCOM. I am not sure why they don't have it, looks like a simple tool.
The most important problem the lack of MIB-support causes is that you need to turn directly to the OEM or to third parties. Each and one of them have implemented their own ways to deal with this. It´s not just an easy Network discovery plus a native management pack.. no no! For example, we now have "plugins" from DELL, NetAPP, Comtrade, HP and EMC. They are all different. Some need dedicated servers, some need extra services running on the management servers, some does not use normal discovery, most need some license management and even license servers and databases for storing the license. Some does not support this and some does not support that, the list goes on.
You end up in quite a complex and brittle environment, were you need to spend a lot of time(=money) just to keep up with new versions. Not to mention that the plugins all cost money compared to a freely distributed MIB.
However, I don´t think SCOM should be equipped with another, new technology to support MIBs. That could also lead to more complex management. Instead you probably have to build on the management pack idea and make some sort of import-feature that translates a MIB to a MP. But what do I know :)
I will spend an extra vote on this one!
Ricardo Carvalho commented
This is a must, all other monitoring tools do it
Tero Ilenius commented
Has been a need since the first release of network monitoring and how many years is that... Starts to be just about the right time to add it quickly.
I agree, plus V3 traps need to be supported to better place SCOM in the SNMP trap management space.
Patrick Uschold commented
+3 votes. This is a must-have and would simplify SCOM SNMP monitoring a lot!
jean vjan commented
Yes! That would make SNMP monitoring so much more convenient!
Or at least do something about discovering/monitoring snmp tables!