As I promised in my previous blog article, I will show you how do you can change vRealize Operation Manager Agent’s log level and file size limit. If you want to debug a problem these two changes are helpful because you can store log information for a longer time than default 5Mb. Ok, let’s go.
The default location of bin files of the agent is “C:\ep-agent\conf\” on Windows environment. Under this folder, you will find “agent.properties” file. Open it by Notepad or your favorite editor.
agent.logLevel=INFO
Search for “agent.logLevel” config, and change from INFO to DEBUG. Save the file and restart agent’s service. Ok, you will see more details in the log file, but the file size will grow fast, and if it will be higher then 5Mb the agent overwrite the old data. You can prevent it, so change the file size limit. The file size setting is very close to log level settings.
Change the value (in KB) end of the line, and save the file, and restart agent’s service.
log4j.appender.R.MaxFileSize=5000KB
If you want to know more about agent property, click the link below:
In Log Insight jump to Content Packs / Veeam Backup & Replication / Alerts menu
Click “vbr – Backup job failed”
The content pack will create a query of failed backups.
Change the name of alert as you wish or leave default
You can edit Description and Recommendation
Fill “Sent to vRealize Operation Manager” checkbox
Hit the “Select…” button and select your Veeam Backup&Replication server (VM or Windows layer)
Set criticality to Critical
Check Auto Cancel option
Click “Send test alert” button
Save to my alerts
If you do everything right you will see the test alert in vRealize Operation Manager (wait 5 minutes before you start troubleshooting)
You can see the alert on VM or Windows layer dash or if you select Alert button, you will see the alert under it.
The alert comes as Notification event so you can create Notification settings under Alerts / Notification settings if you want to receive an e-mail alert.
Datastores is an importent objects in every VMware environtment. Especially free space of Datastore. So I think we need collect information about free space and we want to get alert message when the free space is low or it is getting low on DS.
Fortunetly VMware vROps has a built-in alert message about this topic. Name of this alert is “Datastore is running out of disk space” wich alert send to Us e-mail when “Datastore space usage reaching “ALERT LEVEL” limit” (85/90/95%) and “Datastore space time remaining is low” symptom definitions meet the values.
Default Alert settings of Datastore is running out of disk space
As you remember in vROps Alerts is working different way as other monitoring tools (as I know, like Nagios).
vROps collect metrics from environment, in this case from Datastore through vCenter Server. We can create Symptome Definitions (Alert / Alert Settings / Symptom Definitions/Add (green cross)) from Metrics or Properties.
Alerts consists of symptoms. If symptoms reaching the level wich was seted up and match all conditions (Any / All logical separation) we have got Alert from vROps.
Jump back to subject of this blog article. My problem was with default DS alert that we should have leave huge free spaces on big datastores becouse of this symptoms is watching free space in precent. Eg. I got alert from 8TB datastore despite of I had 700GB free space on this DS.
I created new symptom definitions:
Base Object Type: vCenter Adapter / Datastore Metrics: Capacity / Available Space (GB) Threshold: Static
Name
Level
Condition
Value
Datastore Available Space reaching Warning limit
Warning
is less than or equel to
150
Datastore Available Space reaching Immediate limit
Immediate
is less than or equel to
100
Datastore Available Space reaching Critical limit
Critical
is less than or equel to
50
After I added this tree symptoms to “Datastore is running out of disk space” alert as new Self-Datastore objects by “Any” condition.
This alert mean: The DataStore free space is lower than 85% or 90% or 95% and 150GB or 100GB ot 50GB and Disk space time remaining <= 60 days we are going to get an Alert message from vROps.
I admit, the new UI is brilliant, my colleagues are sharing this opinion. So U can read about new features and integration with VMware Log Insigt and Business Management.
After upgrade process was done we realize in vRealize 🙂 something strange. When we selected a VM we seen a watermarked message in the background, as you can see in the picture below. “License is invalid”
License is invalid watermark
The solution is simple, you can go Administration / Management / Licensing page and select License Groups tab in vROPS.
Check the Licensable Usage column and if you see 0 value in Product Licensing row it will be the problem.
Check Licensable Usage
In this case select Product Licensing row and click pencil icon on top. Under vRealize Operation Manager select your license key or keys depends on your environment and click next.
Select your license key or keys
Define a membership criteria as you wish or use legacy settings. They didn’t change in our environment. If you could advice about filering I would give you, pls. contact me. Click next.
Check Preview then click Finish button.
!! Don’t forget push the refresh button on License Keys page however you can’t see the changes on License Groups page 🙂
Push the Refresh button!!!
When you did everything right on License Groups page you will see a bigger value then 0 in Licensable usege column.
I hope this short article will help for you, when you experience similar problem after your upgrade.
We have investigated our problem with VMware Support and they want run a query in Postgres database. Usually I use Putty for SSH connection, but before I could do this I should on the ssh on vROps:
Open vROps Console and press “Alt+F1” to switch console
Type “root” user
In default vRealize root user hasan’t password
Press enter for Old password and the promt will change New password
Type new password and type again
When we are able to login by root type: “chkconfig sshd on”
Start service: “service sshd start”
Go back to Putty and connect to vRealize Operation Manager by ssh.
We upgraded our Cisco UCS environment, every host got extra memory from 128 to 256GB. Before we did it we had mesured CPU usage by VMware vRealize Operation Manager. It was a great help to this process. We ware able to proof the CPU performance will be ok with this memory size. We would have liked to incrase our VMware environment density.
We had to coolect every memory module serial numbers, and information about that witch chassis consist of witch memory modul.
We used to Cisco PowerShell for this task. Yes, exist PowerShell tool for Cisco UCS 🙂
You can download Cisco UCS Power Too pack (click link) and install your computer.
(You must restart your computer after install process)
Collect memory serial numbers, and UCS chassis information:
