This blog I had prepared a long time ago but never published it. So now it’s the time to do it. Since we all know that SCOM 2012 has build in network device monitoring we of course want to use it. This works perfectly , except I you are using devices that are not certified by SCOM. In that case you will not get the CPU and memory counter and Fan/PSU states. For example most of the Procurve network devices from HP are left in the dark. So..
We want to monitor also CPU and Memory usages from HP network devices.
I will keep it simple and clear. I will demonstrate the steps using VSAE and give you as bonus the MP at the end. I will use VSAE management pack templates just to illustrate the power of it.
The steps will be:
1. [Classes] create the memory and CPU classes
We just simple make use of on the memory and processor classes that are already present in the system center network library. So we create 2 classes based on that:
2. [Datasources] create the memory and CPU discovery datasources
Now we have to create the datasources for the discovery of the CPU and memory targets
The most important is that you set the device key correctly to the parent node. Otherwise the relationship between the new CPU / memory class and the network device node will not be set. And you will not see any CPU / Memory targets. This can sometime be a ‘error and retry’ process.
3. [Discovery's] create discovery’s for the CPU and Memory targets
Now we have the discovery datasource we can create the 2 discovery rules for the CPU and Memory targets. We will use the VSAE discovery templates for this. Just simple add new ‘Discovery’ template and you add the 2 rules below.
Create the 2 new discovery’s and specify the correct datasources.
You specify the datasources we created above to the correct discovery rule. Fill in the correct OID to match the HP processor and Memory OIDs.
If you now import the MP will will see at a HP node the CPU and Memory classes created. So continue the the next step.
4) [Rules] create the memory and CPU collection rules
So now we can make the stuff we wanted to see. The Memory and CPU counters. So we just simple use the add new item ‘Rule (Performance Collection)’ template and make the 2 new rules. We are going to use the already build in performance collection rules for the network nodes.
The most important is to specify the correct OID for the Memory and CPU counters at the datasource configuration. See below:
Memory: .18.104.22.168.22.214.171.124.126.96.36.199.188.8.131.52.1.7 and .184.108.40.206.220.127.116.11.18.104.22.168.22.214.171.124.1.5
I am not going to do a deep dive on this. You can just simple reference to the downloadable project source at the end of this post to check the details out.
Now you import the MP and you will see you most wanted performance counters !! Open the Network Summary Dashboards and Node dashboard for the CPU Usage to check it out.
And the ‘free Memory (Percent)’ performance view for the memory usage.
And below the relation ship diagram.
The next step could be to add monitors to alert on high Memory or CU usages. I am not going to give you this bonus because its better to get some VSAE practice you self’s… You can do this the same way you did with the collection rules. There is a template for monitors also.
Download VSAE project (for the diehards): http://sdrv.ms/11mkq9j
Download Management Pack example: http://sdrv.ms/11mku8S