HywelBurris
Enthusiast
Enthusiast

vROps Integration

Jump to solution

Hi,

The action in vROps to "Search for logs in vRealize Log Insight" is the URL customisable? We only allow secure protocols in the environment and it's trying to connect on http rather than https.

Thanks

Tags (1)
0 Kudos
1 Solution

Accepted Solutions
sflanders
Commander
Commander

Launch in context should use 443. Even if vR Ops opens LI over port 80, LI will redirect to 443 as everything is over 443 for LI. Note, LI *REQUIRES* port 80 to be open. If you do not have it open then you will experience issues during upgrade. I hope this helps.

Hope this helps! === If you find this information useful, please award points for "correct" or "helpful". ===

View solution in original post

0 Kudos
4 Replies
MichaelRyom
Hot Shot
Hot Shot

No not to my knowledge.

There has been som enhancements in the latest vRops 6.3 and Log Insight 3.6. Maybe that fixes it ?!

Blogging at https://MichaelRyom.dk
0 Kudos
HywelBurris
Enthusiast
Enthusiast

I am on the latest versions Smiley Sad

0 Kudos
sflanders
Commander
Commander

Launch in context should use 443. Even if vR Ops opens LI over port 80, LI will redirect to 443 as everything is over 443 for LI. Note, LI *REQUIRES* port 80 to be open. If you do not have it open then you will experience issues during upgrade. I hope this helps.

Hope this helps! === If you find this information useful, please award points for "correct" or "helpful". ===
0 Kudos
HywelBurris
Enthusiast
Enthusiast

Thanks Steve,

Port 80 "banned" on this network, will have to apply for exception. The launch in context isn't opening 443 its trying 80 first and redirecting.

With regards to the port 80 required for upgrading is that between then nodes?

0 Kudos