VMware Cloud Community
lolo31
Enthusiast
Enthusiast
Jump to solution

vRLI Integration - "vidm-fqdn" Refused to connect.

Hello guys,

I integrated the vROPS instance in vRLI, and activate the integration of vRLI in vROPS :

The 2 « TEST » button work and give me back a « Test successful. »

But when I go to vROPS and click on Home > Troubleshoot > Using Logs

The vRLI home page appears inside vROPS UI, but after entering my credentials :

with vIDM credential : I get a grey page : "MY-VIDM-FQDN" refused to connect.

with vRLI local default (built-in) credential : Failed

If i try to login directly from vRLI with vIDM or Local default (built-in) account, the connection work.

Do you have any idea what's going on?

Products :

vROPS Version 8.0.1.15331180

vRLI Version 8.0.0-14870409

vIDM Version 3.3.1.0 Build 14635482

Thanks.

Reply
0 Kudos
1 Solution

Accepted Solutions
lolo31
Enthusiast
Enthusiast
Jump to solution

Ok, i just found the issue.

That's a bug with Chrome Browser... errrrr...

Everything (vRLI/vROPS Integration w/ local or vIDM account) works perfectly on Firefox or IE...

View solution in original post

Reply
0 Kudos
7 Replies
RickVerstegen
Expert
Expert
Jump to solution

Did you configure the Loginsight adapter in vRealize Operations with FQDN or hostname?

Was I helpful? Give a kudo for appreciation!
Blog: https://rickverstegen84.wordpress.com/
Twitter: https://twitter.com/verstegenrick
Reply
0 Kudos
lolo31
Enthusiast
Enthusiast
Jump to solution

The vRLI adapter in vROPS is configure with the vRLI FQDN.

The Test connection is successful.

Thanks

Edit : I justed Edit my first topic with more information :

But when I go to vROPS and click on Home > Troubleshoot > Using Logs

The vRLI home page appears inside vROPS UI, but after entering my credentials :

with vIDM credential : I get a grey page : "MY-VIDM-FQDN" refused to connect.

with vRLI local default (built-in) credential : Failed

If i try to login directly from vRLI with vIDM or Local default (built-in) account, the connection work.

Reply
0 Kudos
RickVerstegen
Expert
Expert
Jump to solution

Is there any firewall between those components? Did you configure launch in context properly in vRLI for integration with vRealize Operations and used test connection to verify?

Was I helpful? Give a kudo for appreciation!
Blog: https://rickverstegen84.wordpress.com/
Twitter: https://twitter.com/verstegenrick
Reply
0 Kudos
lolo31
Enthusiast
Enthusiast
Jump to solution

vROPS and vRLI appliances are on the same VLAN / Subnet (w/o micro-seg),

I use the default setting for FW inside vROPS and vRLI Appliances, cf : i didn't touch anything.

Yes the "Enable launch in context" box in vRLI for vROPS integration is marked and the connection is sucessful

Thanks.

Reply
0 Kudos
RickVerstegen
Expert
Expert
Jump to solution

Does vRLI have a valid certificate? I suggest to open a case at VMware support.

Was I helpful? Give a kudo for appreciation!
Blog: https://rickverstegen84.wordpress.com/
Twitter: https://twitter.com/verstegenrick
Reply
0 Kudos
lolo31
Enthusiast
Enthusiast
Jump to solution

In fact, I work on a test lab before implementing for my client the complete suite of vRealize (with vRLCM).

So I am not able to open a VMware case right now.

Well, the certificates for vRLI / vROPS and vIDM are approved by my CA and it works great when I connect directly on vROPS or vRLI with or w/o vIDM authentication.

I will still try to resolve the issue, be sure that I will update the topic if I find something.

Thanks for your help Rick.

Reply
0 Kudos
lolo31
Enthusiast
Enthusiast
Jump to solution

Ok, i just found the issue.

That's a bug with Chrome Browser... errrrr...

Everything (vRLI/vROPS Integration w/ local or vIDM account) works perfectly on Firefox or IE...

Reply
0 Kudos