cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2561
Views
2
Helpful
12
Replies

CML Response Time

T.Golbach
Level 1
Level 1

Hi,

there are too long response times from the CML Server (10.10.20.50, 10.10.20.161). Can you fix the problem please?

Kind regards, Thomas

12 Replies 12

AntonioGabor
Frequent Visitor
Frequent Visitor

Something is happening on the back end for sure. Beyond massive lags.
I tried changing the ISP link on my side to verify it is not my device. Definitely something on Devnet backend. 

Pinging 10.10.20.50 with 32 bytes of data:
Reply from 10.10.20.50: bytes=32 time=174ms TTL=64
Request timed out.
Request timed out.
Request timed out.

I saw this thread https://community.cisco.com/t5/devnet-sandbox/sandbox-doesn-t-work/m-p/5281452#M11116 looks like latency issues over the VPN. I am sure the team is investigating. Would check back later.

Please mark this as helpful or solution accepted to help others
Connect with me https://bigevilbeard.github.io

AntonioGabor
Frequent Visitor
Frequent Visitor

If I ping from 10.10.20.50 to 10.10.20.161 also unusually high latency over 400ms so that would indicate issue that is not vpn related.

I see, so this could be an internal issue the team is having.

Please mark this as helpful or solution accepted to help others
Connect with me https://bigevilbeard.github.io

AntonioGabor
Frequent Visitor
Frequent Visitor

I did a trace just there:

 

Tracing route to devnetsandboxiosxe.cisco.com [131.226.217.181]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.10.254
2 12 ms 11 ms 13 ms 089-100-020001.ntlworld.ie [89.100.20.1]
3 12 ms 12 ms 11 ms 109.255.255.254
4 25 ms 23 ms 23 ms ie-dub01a-rc1-ae-31-0.aorta.net [84.116.238.42]
5 * * * Request timed out.
6 26 ms 33 ms 25 ms uk-lon01b-ri1-ae-25-0.aorta.net [84.116.136.102]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * 156 ms ae0.cs2.den5.us.eth.zayo.com [64.125.31.1]
16 * * * Request timed out.
17 * * 158 ms ae0.cs3.slc2.us.eth.zayo.com [64.125.23.178]
18 * 153 ms * ae5.cs3.sjc7.us.eth.zayo.com [64.125.23.220]
19 156 ms 155 ms 155 ms ae6.er1.sjc5.us.zip.zayo.com [64.125.30.17]
20 153 ms 153 ms 152 ms 208.185.154.181.IPYX-234918-ZYO.zip.zayo.com [208.185.154.181]
21 * * * Request timed out.
22 * * * Request timed out.
23

Also now there is now following warning:

WairissonGomes
Frequent Visitor
Frequent Visitor

Definetely something is wrong, I have been trying to access Cat Center Reserved Lab there is a huge packet loss, I tried to use a VM in the USA, near Cisco DC but the result is the same, can't get access to CML, ISE or CatCenter. 

@WairissonGomes I see there is unplanned maintenance on the sandbox right now.

Please mark this as helpful or solution accepted to help others
Connect with me https://bigevilbeard.github.io

Thanks for your response, now the maintenance message is gone but I am still experiencing 50% packet loss to cml node via sandbox.

Still not working 😕

Team could be working on clearing the issues still. I have not seen any updates.

Please mark this as helpful or solution accepted to help others
Connect with me https://bigevilbeard.github.io

Please let us know if there is any update on it ?

I am also facing the problem as well

WairissonGomes
Frequent Visitor
Frequent Visitor

It seems they have fixed the issue, now it is ok, no packet loss.