Connectivity issues to network devices in NSO sandbox

[nicklas.eriksson]

Hi,

Try to use the Cisco NSO sandbox. But have a lot of issues with the network connectivity from the NSO boxes to the network devices. Tried terminate and reserve a new sandbox but no luck. Same issues if I try with ssh / telnet from cli from the NSO boxes (10.10.20.49/50)

Regards

Nicklas

admin@ncs> request devices connect
connect-result {
device core-rtr01
result false
info Failed to connect to device core-rtr01: connection refused: NEDCOM CONNECT: No route to host (Host unreachable) in new state
}
connect-result {
device core-rtr02
result false
info Failed to connect to device core-rtr02: connection refused: NEDCOM CONNECT: No route to host (Host unreachable) in new state
}
connect-result {
device dist-rtr01
result false
info Failed to connect to device dist-rtr01: connection refused: NEDCOM CONNECT: No route to host (Host unreachable) in new state
}
connect-result {
device dist-rtr02
result true
info (admin) Connected to dist-rtr02 - 10.10.20.176:23
}
connect-result {
device dist-sw01
result false
info Failed to connect to device dist-sw01: connection refused: NEDCOM CONNECT: No route to host (Host unreachable) in new state
}
connect-result {
device dist-sw02
result false
info Failed to connect to device dist-sw02: connection refused: NEDCOM CONNECT: connect timed out in new state
}
connect-result {
device edge-firewall01
result false
info Failed to connect to device edge-firewall01: connection refused: NEDCOM CONNECT: No route to host (Host unreachable) in new state
}
connect-result {
device edge-sw01
result true
info (admin) Connected to edge-sw01 - 10.10.20.172:23
}
connect-result {
device internet-rtr01
result false
info Failed to connect to device internet-rtr01: connection refused: NEDCOM CONNECT: No route to host (Host unreachable) in new state
}

[bigevilbeard]

@nicklas.eriksson has the sandbox been actives for long before you try and access the devices? I know in the past i had to wait a little while for some device to full build (even after reservation set up) before i could access them.

Thanks!

[willkaren023]

My sandbox hadnt been active for long so thanks. I waited a few and it worked. Although i have one more question if i may ask?

Regards,

Team Discordserverlists

[bigevilbeard]

@willkaren023 or @nicklas.eriksson question away!

[nicklas.eriksson]

@bigevilbeard yes I have the same issue also when the sandbox been running for an hour or more. So unfortunately seems to be some other issue. Thanks!

[bigevilbeard]

@nicklas.eriksson are the devices reachable outside of NSO?

[nicklas.eriksson]

@bigevilbeard no, the devices are unreachable also outside of NSO. 

Looks like the "NSO Devbox" in the Sandbox environment is missing ARP entires to the network devices that are unreachable

(py3venv) [developer@devbox ~]$ arp -a

? (10.10.20.176) at <incomplete> on ens160

? (10.10.20.174) at <incomplete> on ens160

gateway (10.10.20.254) at 00:50:56:bf:b1:c1 [ether] on ens160

? (10.10.20.171) at 52:54:00:01:61:90 [ether] on ens160

? (10.10.20.178) at <incomplete> on ens160

? (10.10.20.181) at 52:54:00:0e:31:ad [ether] on ens160

? (10.10.20.173) at 52:54:00:1e:f5:e1 [ether] on ens160

? (10.10.20.172) at 52:54:00:16:65:1d [ether] on ens160

? (10.10.20.177) at <incomplete> on ens160

? (10.10.20.175) at 52:54:00:06:90:63 [ether] on ens160

-----

admin@ncs(config)# devices connect

connect-result {

    device core-rtr01

    result true

    info (admin) Connected to core-rtr01 - 10.10.20.173:23

}

connect-result {

    device core-rtr02

    result false

    info Failed to connect to device core-rtr02: connection refused: NEDCOM CONNECT: No route to host (Host unreachable) in new state

}

connect-result {

    device dist-rtr01

    result true

    info (admin) Connected to dist-rtr01 - 10.10.20.175:23

}

connect-result {

    device dist-rtr02

    result false

    info Failed to connect to device dist-rtr02: connection refused: NEDCOM CONNECT: No route to host (Host unreachable) in new state

}

connect-result {

    device dist-sw01

    result false

    info Failed to connect to device dist-sw01: connection refused: NEDCOM CONNECT: No route to host (Host unreachable) in new state

}

connect-result {

    device dist-sw02

    result false

    info Failed to connect to device dist-sw02: connection refused: NEDCOM CONNECT: No route to host (Host unreachable) in new state

}

connect-result {

    device edge-firewall01

    result true

    info (admin) Connected to edge-firewall01 - 10.10.20.171:23

}

connect-result {

    device edge-sw01

    result true

    info (admin) Connected to edge-sw01 - 10.10.20.172:23

}

connect-result {

    device internet-rtr01

    result true

    info (admin) Connected to internet-rtr01 - 10.10.20.181:23

}

[bigevilbeard]

Thanks @nicklas.eriksson suggest stopping/ending that reservation and spinning a new one up. If this happens again, i will ask ENG to take look with the BU

[nicklas.eriksson]

Thanks for your assistance @bigevilbeard .
I already tried that, one sandbox last week and two today  

I unfortunately don't saved the logs from the previous attempts, but I think it have been issue with different network devices each time. 

[bigevilbeard]

@nicklas.eriksson the ENG team are working on an issue with this sandbox. It has for now been taken out of the catalog. Please check back later and this should be good to go!

[nicklas.eriksson · Accepted solution]

@bigevilbeard thanks for your assistance and feedback!