topic Re: Cisco ISE 3.2 sandbox lab active, but Lab Network Address: None in DevNet Sandbox

Cisco ISE 3.2 sandbox lab active, but Lab Network Address: None

xorxe7 — Wed, 27 Dec 2023 21:24:30 GMT

Hi all,

Today [27.12.2023] I tried to launch a Cisco ISE 3.2 sandbox lab five times. I succeeded twice, but missing "Lab Network Address: None" [via email] or "vpn_address: None" [in GUI Quick Access section] info prevented me from making a VPN connection to the sandbox and use this lab. Other three attempts to launch/create the lab failed within 1-2 minutes from the beginning.

I noticed that some changes are taking place in the sandbox infra. I would like to know when the automated provisioning will be functional or whether there is a way how to I can obtain the correct vpn_address from otherwise active lab sandbox. Thanks in advance.

Irgo

Re: Cisco ISE 3.2 sandbox lab active, but Lab Network Address: None

Ruben Cocheno — Wed, 27 Dec 2023 22:18:45 GMT

@xorxe7

The instability might be related to the migration of the sandboxes to another platform as per below

https://community.cisco.com/t5/devnet-sandbox/active-environments-launched-from-this-blueprint-reached/td-p/4976470

Re: Cisco ISE 3.2 sandbox lab active, but Lab Network Address: None

xorxe7 — Wed, 27 Dec 2023 22:38:39 GMT

@Ruben Cocheno Ruben, thanks for the info.

I am still hoping for more specific replies to my questions. The provided URL is of 12-Dec-2023 ("We have just switched to a new sandbox platform and it will take a few days for us to reach a steady state") A few days have already passed and still the sandbox for ISE 3.2 is unusable. I understand that such a migrations is a complex deal, but fixing a missing vpn_address piece of info should not be so complicated.

Thanks a bunch, Irgo

Re: Cisco ISE 3.2 sandbox lab active, but Lab Network Address: None

xorxe7 — Thu, 28 Dec 2023 09:11:55 GMT

Update: The aforementioned issue was fixed by the sandbox team, vpn_address info is now available.

Thanks.