topic Re: Identity Services Engine 3.2 - Can not connect to API on VPN in DevNet Sandbox

Identity Services Engine 3.2 - Can not connect to API on VPN

zachary3 — Fri, 09 Aug 2024 20:46:12 GMT

I recently spun up the lab for ISE 3.2 to test out integrations with the API. I was able to successfully provision the lab and received connection details for the VPN. Using AnyConnect 4.10, I was able to successfuly connect to the VPN with the credentials provided. However, I could not reach the lab environment. The provided ISE nodes at 10.10.20.77 and 10.10.20.78 in my environment were not ping-able. I also tried using Postman to query the API just to confirm that was also not reachable.

Is there any additional guidance for interacting with the Reserved lab environments once connected to the provided VPN?

Re: Identity Services Engine 3.2 - Can not connect to API on VPN

zachary3 — Sat, 10 Aug 2024 00:13:55 GMT

I was able to fix this by enabling a feature in MacOS that was preventing AnyConnect from functioning properly. However, now the username and password for the ISE nodes is incorrect.

Re: Identity Services Engine 3.2 - Can not connect to API on VPN

jeffrbul — Wed, 28 Aug 2024 17:29:00 GMT

Hey @zachary3, Two questions: 1) Are you still having the username/pass issues with the ISE nodes? 2) When you say "Lab" do you mean the DevNet Sandbox?

Re: Identity Services Engine 3.2 - Can not connect to API on VPN

zachary3 — Wed, 28 Aug 2024 17:49:30 GMT

Hi @jeffrbul , yes I am referring to DevNet Sandbox. A few days later I spun up a new instance of the sandbox and was able to query one of the ISE nodes, but not the other (IIRC .77 did not work, .78 did work).

For me, the quickest solution would be if someone could fix the expired password issue for the Always-On sandbox.
https://community.cisco.com/t5/devnet-sandbox/the-ise-always-on-sandbox-is-asking-for-a-new-password/td-p/5158610

Re: Identity Services Engine 3.2 - Can not connect to API on VPN

jokearns1 — Thu, 29 Aug 2024 11:16:33 GMT

Hi,

I tested the Identity Services Engine 3.2 sandbox this morning and both ISE Nodes are reachable in my reservation. Deployment us good.
If you have a problem like this with any reservation, two options:
1. Kill your existing sandbox and wait for it to teardown. Then spin up a new lab
2. If the issue persists, jump on here and reference your reservation URL. We can then check your VMs.

Joe