According to HP, the functionality is different in 2003? Didn't make sense to me either, but they supposedly have a workaround coming. The way the Team is registered in WMI I guess? Allowing the SCOM discovery to work? Solution
HP Engineering consulted with Microsoft and was advised that PerfMon only identifies physical adapters and not logical. This prevents Perfmon from displaying NIC team as an available instance to select. Note that this behavior is different than is observed on a server running Windows 2003 Server operating systems, which does enable selection of the NIC team. Regardless, is the best practice to simply collect counters on each physical adapter and massage the #'s from there? From: [email protected] To: [email protected] Subject: RE: [msmom] SCOM 2007 R2 - Teamed NIC - Performance Collection Date: Tue, 6 Aug 2013 22:01:03 +0000 Interesting – I thought this was always broken…. it has to do with how we discover a teamed NIC, and how we pass that information to the perfmon module – these fail because the discovered name doesn’t not match any instance in perfmon. From: [email protected] [mailto:[email protected]] On Behalf Of Bill MacKenzie Sent: Tuesday, August 6, 2013 4:52 PM To: [email protected] Subject: [msmom] SCOM 2007 R2 - Teamed NIC - Performance Collection I've recently ran into the issue where SCOM 2007 R2 is unable to collect Network Adapter Performance Metrics when the NIC's are Teamed on Windows Server 2008. Perfmon is only able to see the Physical adapters as well. HP has slated an upgrade to their Network Configuration Utility later this year (Ver. 10.9) that addresses this issue. But, I'm curious of what everyone else is doing as a workaround? We still need to collect Network Utilization metrics. Cheers, -Bill MacKenzie
