Not able to connect to a VA

Team,

We have internal servers which have sample DB data and we want to integrate that with our sailpoint simeio partnet instance.

We installed the VA ( followed the document process) on vSphere in our servers but when we try to connect via the partnet sailpoint instance, getting check your connection configurations failure message.

Could anyone please guide us on what could be the configuration miss or any config that needs to be enabled.?

Thanks.

If your “partner” instance is xxxxx.identitynow-demo.com (vs. xxxxx.identitynow.com) then there’s a specific VA image that you have to use vs. the standard image. Please see @colin_mckibben 's post below for the downloads.

I’d also suggest reviewing the Virtual Appliance Troubleshooting Guide which will help you test connectivity directly from the VA to the source to ensure you’re not hitting firewall issues, port issues, etc.

Hey Ed,

Thanks for the information and yes our partner instance is [xxxxx.identitynow-demo.com].
Could you please help me where i can find the document to download the VA image for it?

And also we checked the connectivity from our servers to the partner instance and it looks good!

@PratithShetty - See this article here in the DEV forums. It applies to the ambassador developer tenants AND the partner tenants.
https://developer.sailpoint.com/discuss/t/guide-adding-a-va-to-ambassador-sandbox-tenants/14774

Hi @edmarks - Looks like the URL is private…getting this error .

Hi Pratith,

Please fellow the below link for adding VA into SailPoint.

Add the stunt file in the Virtual appliance server of " /home/sailpoint/" path.
I am sharing shunt file to upload into VA.
Note:
Make sure same keypassphrase password of config.yaml file which you have to use if you already have connected 1VA to SailPoint.
Once you add shunt file run the below comment

  • Open stunt file by using “cd stunt”

  • open list of stunt files by using “ls” commend

  • run ./stunt.sh(It will run the shunt file)

  • Check the “stuntlog.txt” file if you see any errors or not once the file executed

  • If no errors run “sudo systemctl disable esx_dhcp_bump” commend

  • wait for some time and perform the test connection.

Fellow below link for more troubleshooting steps:

“https://community.sailpoint.com/t5/IdentityNow-Connectors/Virtual-Appliance-Troubleshooting-Guide/ta-p/78735”

Thanks,
Siva.K

Sorry i forget to share stunt file
stunt.zip (1.6 KB)

Hi @Sivakrishna1993 - I have followed your steps and did the changes you mentioned. Still from the UI getting Connection failed.

Not sure what i am missing here.

When I was doing IDN setup which was partner tenant not a client one, so I learn that there are different VA softwares, it’s not same for every tenant. Guess that might be a possibility.

1 Like

Hi Pratith,

From VA run stunt.sh file and check any errors in the file. You may observe some wrong observe instead of sailpoint → sharepoint change the sharepoint name with sailpoint then reboot the VA and then start the VA give for 5min and then perform test connection.

Thanks,
Siva.K

Hi Siva,

As you mentioned, on the stunt.sh file I see the below

intro “Getting jobs list” “ls -l /opt/sharepoint/share/jobs/”
ls -l /opt/sharepoint/share/jobs/ >> $LOGFILE

Could this be causing the issue?

Thanks
Divya

Hi Divya,

Yes please correct the path in place of sharepaint add sailpoint

I also am looking for the demo tenant VA image, and the above link is not available to me. How do I find the VA file that I need for the demo tenant, please?
Thanks

https://developer.sailpoint.com/discuss/t/identitynow-development-tenants/11153

https://developer.sailpoint.com/discuss/uploads/short-url/v1QFiWCkRMwyU693wfaawdW3LSI.7z

https://developer.sailpoint.com/discuss/uploads/short-url/uPkb7A7z6YIw6mq2123dSB4Ma1h.7z

Sorry everyone. Better late than never :smile:

Here is the VA image for demo tenants.

vavm.7z

If you need to deploy to Azure or Hyper-v, use this one.

vavm_microsoft-vhd.7z

2 Likes

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.