Hi. Im testing ESI integration with SCOM innot yet supported environment. SCOM is 2012 R2 and Windows Server OS 2012 R2 as well.
When i will workaroud all warnings about unsupported OS and so on everything seems to be fine. Our VNX5100 for testing purposes is shown in SCOM. Inventory is taken, alerts are generated and so on.
What is not working is Overall Topology view. There is only root container. No service connection and storage system is shown here - and EMC SI Service Connection Group is empty. Dynamic members (Object is EMC SI Service Connection AND True) - enabled...
Can anyone help me debug this... discovery? Im not sure, why i see correct healt monitor information (memory, disks, luns, ....) and cant use Topology view.
SCOM 2012 R2 is natively supporting new Windows Server 2012 R2 OS.
Unfortunately it is working now correctly without any interaction from my side. Topology is discovered after more than 24 hours.
The thing i dont understand is why i see HW info and not topology view. The only information for ESI is where is SI windows service located and how to connect to it. And why if SCOM can connect to my storage trough ESI is not this service added to "EMC SI Service Connection Group". Shouldn't all of the services be located there (EMC SI Service Connection Group)? All information about topology view and HW inventory are taken just from this services. Am I right?
Anyway, i dont know if it is SCOM internal or some ESI MP problem. But like i said, after more hours Overall Topology view is working.
Actually im looking for EMC ESI support :). Because installer dont have support for Server 2012 R2 OS and MP are in ESI version 3.0 only for SCOM 2012 non R2.
fangycz
4 Posts
1632
0
Posted November 6th, 2013 00:00
Hi Scott. Thank you for reply to my thread.
SCOM 2012 R2 is natively supporting new Windows Server 2012 R2 OS.
Unfortunately it is working now correctly without any interaction from my side. Topology is discovered after more than 24 hours.
The thing i dont understand is why i see HW info and not topology view. The only information for ESI is where is SI windows service located and how to connect to it. And why if SCOM can connect to my storage trough ESI is not this service added to "EMC SI Service Connection Group". Shouldn't all of the services be located there (EMC SI Service Connection Group)? All information about topology view and HW inventory are taken just from this services. Am I right?
Anyway, i dont know if it is SCOM internal or some ESI MP problem. But like i said, after more hours Overall Topology view is working.