Posts Tagged ‘Network’

What’s New in SCOM 2012 Network Device Monitoring

25/08/2011 Leave a comment

In the old days Winking smile when we used Operations Manager 2007 R2 to monitor network device we ware limited to network device availability (online or offline). if we wish to know more, we could used the xSNMP management pack .this MP helped us monitor the availability of ports and interfaces and performance related issues. But xSNMP MP covers only few devices like Cisco, HP ProCurve , Juniper etc. moreover discovery of network devices is limited to SNMP V1 & V2 only. if we wish to monitor SNMP V3 we must use third party applications that extend OM2007 (like JalaSoft).

So what changes have been made to network monitoring in OM2012 ?

  • Extended device monitoring
  • Multi vendor support and multi protocol support.
  • Resource pools
  • Discovery
  • Server to network dependency
  • Dashboards and reporting

Extended Device monitoring

Unlike Operations Manager 2007, Operations Manager 2012 is a game-changer with a new network device monitoring engine. OM2012 extend those capabilities to a large number of vendors and devices (provide port monitoring for devices that implement interface MIB (RFC 2863) and MIB-II (RFC 1213) standards.)
OM2012 provides the ability to discover and monitor network routers and switches, including the network interfaces and ports on those devices and the virtual LAN (VLAN) and Hot Standby Router Protocol (HSRP) groups that they participate in. further more, OM2012 can monitor Firewalls and load balancers.

Multi vendor support and multi protocol support

Microsoft published an Excel spreadsheet that lists the devices, vendors, model names, and versions of network devices that have extended monitoring capability. The Devices worksheet includes processor and memory columns for each device to indicate whether Operations Manager can provide extended monitoring for either or both aspects for each device.

Resource Pools

Resource Pool is a feature in OM2012 which gives us the ability to monitor non-windows devices in a high availability mode. The concept behind this feature is that we can select management servers and group them in a pool, and then assign network devices to be monitored by the pool. If a server goes down from that pool, it will automatically failover any monitoring that is occurring on that management server to the other members of the pool.


The network discovery process is a great change compared to SCOM2007, it allows us to discover multiple devices using discovery rules. the discovery deals with different community names just like run as account and allows us to discover sets of devices and individual network devices in the same rule.
There are 2 types of discovery:
Explicit – OM will discover specific network device that was specified in the rule.
Recursive – OM will discover the devices specified as well devices found in the ARP table of those devices.
I preferred explicit rather then recursive discovery, because recursive will discover devices that we don’t need to monitor and as a result, will increase the administrative workload and the management server workload.

Server to network dependency

Server and network dependency is part of the vicinity dashboard, and it’s actually a dynamic map that show us contextual network map. we can choose whether to display computers that connected to the network devices. the map can be scoped to number of hopes from the selected network node.

Dashboards and reporting

Well, how can one explain this ? I thought that a a picture is worth a thousand words…








Useful links :

Categories: OpsMgr2012 Tags: ,