We are an MSP using SCOM 2012 R2 UR4 for server and network device monitoring. We deploy Cisco ASA5505's at all of our customers locations. Since we moved to SCOM 2012 R2 (fresh install) we've been unable to monitor most of these ASA's. The reason is that Cisco has shipped a massive batch of ASA that have the same MAC address on a virtual interface called Internal-Data0/1. Normally this wouldn't be a problem but it's also the lowest mac-address on the device, so SCOM uses this MAC address as the unique device-key. Adding another one of these ASA's into SCOM results in them replacing each other. So we can only have 1 of these ASA's in at a time. I have created a support case with Microsoft to no avail, they just pointed the finger at Cisco. I'm currently working with Cisco TAC to see if they can come up with a solution.
Has anyone else had this problem? How have you solved it? I noticed a bunch of config files on the management server under C:\Program Files\Microsoft System Center 2012 R2\Operations Manager\Server\NetworkMonitoring\. I was wondering if these are editable to block SCOM from looking for that interface name or MAC address.
Here's a copy of the interface that is causing the issues:
9: Int: Internal-Data0/1 : address is 0000.0003.0002, irq 255
Thank you!