Alerts for server with DRS enabled

[dermott]

Hi,
We're currently trialling veeam and are getting the alerts below when servers are powered down by DRS

Monitor object: 'Veeam.LicenseServer.InfrastructureMonitor', Error: 'Soap login to to 'cheryl.xxxxxxxx.ie' failed, port 443, user 'root', proxy srv:, proxy port: 0, proxy user: '''.

Is it possible to get veeam to recognise that the server in question is powered down via drs and not raise this alert?

Thanks!
Dermot

[Alec King]

hi Dermot,

Are you referring to ESX host put in Standby Mode by vCenter DPM?

If you have a vCenter connection, then we should track the vCenter events that notify of "DPM-Standby", and therefore we would not alert on the host being down.

However if you have direct-to-ESX-Host connections, then you would get an alert. This is one reason that a single vCenter connection is the preferred method.

Can you confirm how you have set up your VMware servers in Connected Servers in the nworks UI?
Please also confirm your nworks Management Center version, Collector version and MP version.

Thanks!

[dermott]

Hi Alec,
Sorry meant to say DPM, I'd say you could be right with the connections, they are direct to host. Just reconfigured it there so we'll see how it goes

Thanks again,

Dermot

[dermott]

No luck with this, still getting the same error for one host when DPM has it powered off

[dermott]

Has anyone got any ideas on this?????????

[vBPav]

Hi Dermott,

It would be best to open up a case with our support team to take a look at your environment. When you get a moment please contact support@veeam.com with your issue. Please reference this forum and any other information you can provide in the initial e-mail to support.

Thanks!

-Brian

[dermott]

Thanks Brian, just logged a call there now
Dermot

[vBPav]

Awesome Dermot!

I will follow-up with this case. Thanks for using Veeam Support!

Regards,

Brian Pavnick
Veeam Solutions Architect for nworks MP!

[bradje]

Hi, Did this get resolved? What was the fix?
Thx,
John Bradshaw

[Vitaliy S.]

Hello John,

Unfortunately, I'm not sure about the resolution since previous poster has not mentioned his support case number. Please contact our support team directly for assistance. By the way what version of MP are you running?

Thanks!

[Airat]

Hello!

We have the same issue. But our servers are not powered down.

I registered a case #528762.
Version is 5.0.3.248

Am I right,that the list of prereq-s should be met:

- port 443 listening on monitored server
- account with special rights(what rights should be?)
- license..

any ideas?

Thanks in advance!

[sameerdave]

Did anyone get a solution to this?

I am seeing the same error from one of our vcenter servers.
Our environment - 3 collector servers, one management server. and we are on 5.5.2.533 version.
And this error is only from one of the vcenter servers.. all others are fine..

EDIT* -
I found that the server showing error is the only vcenter server that has no opsmgr agent installed.
Do we need to install opsmgr agent to the vcenter server and enable proxing for nworks? How would it benefit for having an opsmgr agent installed on the vcenter server?

[Irina Simkina]

Hi Sameer,

this error appears in case the connection to the VC cannot be established. Please check credentials you use to connect to VC (at least read-only access) and the firewall settings on a VC to have 443 port open for incoming connections.

With best regards,
Irina