VIAVI TestCenter: Session Manager can't connect to a new virtual LabServer VM

Symptoms and Troubleshooting • The old virtual LabServer (vLS) was 5.35. • A new vLS VM was built, using the VIAVI_TestCenter_LabServer-5.45.2586.ova, and powered on. • But when trying to connect to it using the Session Manager, a "Connection to Server failed." message is thrown.       • The new vLS looked to be alive because: • it responded to pings; • when SSH'ing to it and logging in as admin/VIAVI: • the "[3] System Information" looks good; and • the "[4] System Status" -> "[2] Networking" looked properly configured. • But... • From the SSH login as admin, from "[6] Shell Access," we could not gain Docker access. When we tried the command      docker exec -ti $(docker ps -q) /bin/bash we'd see          docker: "exec" requires a minimum of 2 arguments.         See 'docker exec --help'.         Usage:  docker exec [OPTIONS] CONTAINER COMMAND [ARG...]         Run a command in a running container • Also, when we telneted to port 40006, it did not show "STC" as expected (see pic below).       This made it seem like it might be a firewall issue. • The new vLS VM was powered off and the old vLS VM was powered on (they both had the same IP address) and  • the 5.45 Session Manager would show that the connection failed because of a version mismatch; and      • the 5.35 Session Manager could connect to it. So, this showed that it wasn't a firewall issue, per se, since the firewall was allowing the TCP ports that any vLS would use.

N/A