Working with Windows failover cluster

×

Prerequisites

• OpsRamp Classic Gateway 14.0.0 and above.
• OpsRamp Nextgen Gateway 14.0.0 and above.
  Note: OpsRamp recommends using the latest Gateway version for full coverage of recent bug fixes, enhancements, etc.
• PS Remoting and WMI remoting to be enabled on each cluster node. If the configured user is non-administrator, then the below user should have privileges on WMI remoting and on Windows Services.
• Add OpsrampGatewayIp to the TrustedHosts list on the target machine to allow the powershell connection from gateway to the target machine.
  • To add TrustedHosts use the following command:
    • To allow any host:
      *Set-Item WSMan:\localhost\Client\TrustedHosts -Force -Value **
    • To allow a specific host:
      Set-Item WSMan:\localhost\Client\TrustedHosts -Force -Concatenate -Value
• Setup and restart the WinRM service for the changes to reflect
  • To set up: Set-Service WinRM -StartMode Automatic
  • Restart using: Restart-Service -Force WinRM**

Following are the specific prerequisites for non-administrator/operator level users:

• Enable WMI Remoting**

  To enable WMI remoting:

  1. Click Start and select Run.
  2. Enter wmimgmt.msc and click OK.
  3. Right click WMI control (Local) and select Properties.
  4. Click Security tab.
  5. Expand Root.
  6. Select WMI and Click Security.
  7. Add user and select the following permissions:
     
     • Execute methods
       
     • Enable account
       
     • Enable remoting
       
     • Read security

• Enable WMI Remoting – CPU, Disk, Network

  1. Click Start and select Run.
  2. Enter lusrmgr.msc and click OK.
  3. In the Groups folder, right click Performance Monitor Users and select Properties.
  4. Click Members of tab, and click Add.
  5. Add users.

• Enable Windows Service Monitoring

  1. Retrieve the user SID of the User Account from the monitored device.
     
  2. Open Command Prompt in Administrator mode.
     
  3. Run the below command to retrieve the user SID.
     Note: Replace UserName with the user name for the User account.
     

      wmic useraccount where name="UserName" get name,sid
  
      Example:
      wmic useraccount where name="apiuser" get name,sid
      

  4. Note down the SID.
     

  (Ex. S-1-0-10-200000-30000000000-4000000000-500)

  5. Retrieve the current SDDL for the SC Manager.
  6. Run the below command which will save the current SDDL for the SC Manager to CurrentSDDL.txt.

      sc sdshow clussvc > CurrentSDDL.txt
      

  7. Edit the CurrentSDDL.txt and copy the entire content.
     The SDDL will look like below:

      D:(A;;CC;;;AU)(A;;CCLCRPRC;;;IU)(A;;CCLCRPRC;;;SU)(A;;CCLCRPWPRC;;;SY)(A;;KA;;;BA)(A;;CC;;;AC)S:(AU;FA;KA;;;WD)(AU;OIIOFA;GA;;;WD)
      

  8. Update the SDDL:
     Frame new SDDL snippet for above SID
     

      (A;;CCLCRPWPRC;;; <SID of User> )
  
      Example:
      (A;;CCLCRPWPRC;;;S-1-0-10-200000-30000000000-4000000000-500)
      

  9. Place this snippet before “S:” of original SDDL.
     Updated SDDL will be like this:
     

      D:(A;;CC;;;AU)(A;;CCLCRPRC;;;IU)(A;;CCLCRPRC;;;SU)(A;;CCLCRPWPRC;;;SY)(A;;KA;;;BA)(A;;CC;;;AC)(A;;CCLCRPWPRC;;;S-1-0-10-200000-30000000000-4000000000-500)S:(AU;FA;KA;;;WD)(AU;OIIOFA;GA;;;WD)
  
      

  10. Execute the below command with the updated SDDL:

      sc sdset clussvc D:(A;;CC;;;AU)(A;;CCLCRPRC;;;IU)(A;;CCLCRPRC;;;SU)(A;;CCLCRPWPRC;;;SY)(A;;KA;;;BA)(A;;CC;;;AC)(A;;CCLCRPWPRC;;;S-1-0-10-200000-30000000000-4000000000-500)S:(AU;FA;KA;;;WD)(AU;OIIOFA;GA;;;WD)
  
      

• Open ports and add user in all nodes and cluster

  • Opsramp gateway should be able to access cluster and nodes.
    
  • Ports to be opened are 5985 and 5986.
    Note: By default, WS-Man and PowerShell remoting use port 5985 and 5986 for connections over HTTP and HTTPS, users should be present in nodes and cluster.

Configure Windows failover cluster monitoring Integration

Modify Windows failover cluster Integration

Discover Resources in Windows failover cluster Integration