Sometime ago Microsoft released a MP for monitoring the availability of the Microsoft Azure Stack (MAS), version 1.0.1.0. There are some things you must know however:
- This MP monitors the availability of the MAS infrastructure running MAS TP3;
- Yes, the MAS nodes are totally locked down, so there is no SCOM Agent involved here;
- Instead some MAS APIs are leveraged to remotely discover and collect instrumentation information, such as a Deployments, Regions and Alerts;
- Out of the box, this MP doesn’t do anything. After import additional actions are required;
- Concurrent monitoring of multiple regions has not been tested with this MP;
- For MAS deployments using AAD, the SCOM Management Server requires a connection with Azure. This can also be done from the system running the SCOM Console, used for configuring the MAS MP;
- .NET Framework 4.5 MUST be installed on all SCOM Management Servers and systems running the SCOM Console;
- The SSL certificate provided for the Microsoft Azure Stack deployment of Azure Resource Manager, must be installed in the Trusted Root Certificate Authority Store of all SCOM Management Servers and the computer(s) with the SCOM Console used for configuring the MAS MP;
- When SPN is used for authentication, the same certificate created along the SPN must be installed on all SCOM Management Servers and the computer(s) with the SCOM Console used for configuring the MAS MP;
- The account credentials which have Owner rights to the Default Provider Subscription of MAS (mostly the Azure Stack Service Administrator account) are required when configuring the MAS MP.
The MP and it’s related guide (PLEASE RTFM!!!) can be found here.
No comments:
Post a Comment