SCOM Monitor types - Create Unit Monitor for Monitor Windows Service availability in SCOM 2019

 

SCOM Monitoring

KPI in SCOM – There are four types of KPI in SCOM Processor, Memory, Days and Network.

Using these KPI you can understand or you can find out the overall health of the server.

What is Monitor in SCOM -:  Basically monitor works on state based like healthy, warning and critical and measures the health of some aspects of managed objects.




Unit Monitoring -: So that's basically the most common monitor which is being used in SCOM by your admins to create, monitoring for any specific object or any specific entity.

When we refer to monitors, we usually refer to unit monitors.

Only a unit monitor also measures some aspects of an application.

Dependency rollup monitors -: Dependency monitors let the health of one object be affected 

by the health of another object. This allows for health rollup between specific related instances 

of different classes.


Aggregate rollup Monitor-: Aggregate monitors group multiple monitors to provide a single 

Health aggregated health state. This provides an organization to all of the monitors targeted at 

a particular class and provides a consolidated health state for specific categories of operation.




How to create Unit based Monitor -:

Login to SCOM operation manager Console ->

Click Authoring

Click Monitors -> Right click and select create Monitor -> Select Unit Monitor



You can select from list which types of monitoring do you want to create, here I am selecting Basic service Monitoring to create to monitor print spooler service


Drop down Management Pack and select Custom management pack for overwrite -> Click next



Give the Name for the monitor you are creating



From Monitor target -> click on select and select the appropriate target from the list.


Drop down and select from parent monitor -> select Availability (In my case it’s service availability)



Click browse button for assign service name 



Click Next



Check mark on Generate alerts for this monitor



Then click Create -> Once created search for the created Unit monitor.



Select the newly created Unit monitor and click Enable



Select for the newly created Unit Monitor -> Right click and select Overrides -> Select Override the monitor -> 



Click for all objects of another class  -> below box will open -> check mark on Enabled and apply Ok.


Now Print Spooler Monitoring rule has created ->

Now login to any of the machine and stop Print Spooler service 

Here I have logged in database.ads.com machine


Select the service from list -> Right click and stop the service



Now go to the Monitoring console in SCOM -> Click active alert and you will see one alert has triggered.


Now go back to Database.ads.com and start Print Spooler service.


Again go to the monitoring console and see active alert -> it should auto close and server status should reflect health.



All done!

Thank you.



Install Agent on Windows Using the Discovery Wizard in SCOM 2019

 SCOM Agent-: An SCOM agent is a piece of software which we install on Windows and Linux client to collect alert, availability, performance and send these data to the SCOM management server  for monitoring purpose and further troubleshooting.




How to install SCOM Agent from Operation manager Console

Connect with SCOM Operation Manager Console.



Click Administration -> Go to device management -> under device management click Agent Manage.



Right click on Agent Managed -> Click Discovery Wizard



Click Windows Computers




Select Automatic computer discovery -: If you are using AD integrated SCOM else select Advanced Discovery.


Click Next 

Select Account for execute discovery


Click Discover



Once Discovery will complete you will see a list of the computers.

Select all or one of them and click and click next



You can change Agent installation Directory.

Specify Credentials for Agent installation, Here I am selecting domain Administrator account

 because I have added this account into the local admin group in all member servers.


Click finish

Now Agent push installation has started on all 3 servers.

Wait for 5-10 minutes and check the status

Now all 3 servers are reflecting under SCOM Agent Managed – Agent will take some time to replicate with SCOM server.


Now all the Agents are showing correctly in SCOM console under Agent Managed.


In Case if Agents are not reflecting properly under the Agent managed, just logged into to any of the failed server and open Event Viewer

Under Applications and services log click Operations Manager and check the log. In my case everything is fine so not giving any alert.



SCOM 2019 installation failing with error code, Product check for 2016RTMServer failed.

 


SCOM installation is failing with error code  Product check for 2016RTMServer failed.



If you are getting an error then first you need to check the installed SQL version – it seems the correct version is not installed.


Note that SCOM 2019 only supports SQL Server 2019 with CU7 or later, it does not support the RTM version.
If you use CU7 or later, you also need to ensure that you use ODBC 17.3 or later, and MSOLEDBSQL 18.2 or later.


If you are running SQL 2019 CU0 like below, then you need to download the latest CU using the link below and update.

How check version -:

Open SQL management studio -> Connect to server ->

Right click -> properties

General ->





Solution 

Latest CU link

https://docs.microsoft.com/en-us/sql/database-engine/install-windows/latest-updates-for-microsoft-sql-server?view=sql-server-ver15

Direct download link for SQL 2019 CU

https://www.microsoft.com/en-us/download/confirmation.aspx?id=100809


Post Update CU with latest version.



Now attempt for SCOM installation.


Esxcli command to Upgrade ESXI host to VMware ESXi, 7.0.3, 18644231

You can upgrade using VUM, ISO or ESXCLI

Here I am going to do this using ESXCLI

I am using HPE custom ISO, you can download an offline bundle from VMware.

VMware-ESXi-7.0.3-18644231-HPE-703.0.0.10.7.1.16-Oct2021-depot.zip

Before upgrade

Steps to upgrade ESXi-7.0.3-18644231

Download offline bundle in .zip file from VMware portal

Open ESXI using web console

Login to ESXI using root credentials

Browse local Datastore

Upload this file in local datastore

Connect ESXI host using Putty

Run below command to see current Image profile

esxcli software sources profile list -d (Offline bundle path) like below

esxcli software sources profile list -d  /vmfs/volumes/5bafd178-826d6f1a-bfec-00fd4548fbe0/VMware-ESXi-7.0.3-18644231-HPE-703.0.0.10.7.1.16-Oct2021-depot.zip’


Output will be like below



Now run below command to update ESXI host


esxcli software profile update -d /vmfs/volumes/5bafd178-826d6f1a-bfec-00fd4548fbe0/VMware-ESXi-7.0.3-18644231-HPE-703.0.0.10.7.1.16-Oct2021-depot.zip -p HPE-Custom-AddOn_703.0.0.10.7.1-16



Once command will complete you will see Message: The update completed successfully like below



Reboot the host and post reboot you can see the host is updated.

After upgrade



Azure Public IP Address Associate and Dissociate# Create, Modify and Delete

Public IP Address -: Public IP addresses allow Internet resources to communicate inbound to Azure resources. Public IP addresses enable Azure resources to communicate to Internet and public-facing Azure services.

Public IP Address -> Login to Azure Portal -> Search for Public IP Address

Click Create

Public IP Address assignment criteria 

Virtual Machine -> We can assign Public IP in both way either Dynamic or Static

VPN Gateway -> Dynamic Public IP Address assignment is possible on Application Gateway.

Below chart for Public IP Address assignment on applications




Click Create Public IP Address 

Select IPv4

Select SKU Type Standard or Basic.


Note -: If you select Basic SKU then you can assign Static or Dynamic Public IP on VMs,  if you select Standard SKU then you can assign Static public IP address.

Below  chart for Basic and Standard SKU 


Select Tier for Regional and Global.

Give name for Public IP Configuration.

Here I am selecting Basic SKU - You will see both Static and Dynamic IP assignment is highlighted 


Give DNS name label -> Always in small letter

An "A record" that starts with the specified label and resolves to this public IP address will be registered with the Azure-provided DNS servers. Example: mylabel.westus.cloudapp.azure.com.


Select Subscription


Select Resource Group

Select location


Click Create


New Public IP "PublicIP_Raju" has created.


How to assign Public IP address to Network interface or loadbalancer

Click on newly created Public IP -> PublicIP_Raju


Click Associate -> 

Select Load balancer or Network Interface from the drop down


Once you select Network Interface you will see a list of the network interface created in the location, select from one of them.


To delete Created  public IP in Azure

Login to Azure Portal

Search for Created public IP

Open created public IP


Click on Dissociate -> Select Yes


Now it is not Associated to any of the network or load balancer

Now it has successfully Deleted 

Thanks




Featured Post

HPE MSA 2040 configuration step by step

HPE MSA 2040 configuration Default IP range for HP SAN storage MSA 2040 is 10.0.0.1/2 You need to connect your laptop and storage with...