Hi ​@harishchandras 

where are you seeing the timeout error, in the benchmark? Can you please test with the Tune option in Shared Device Settings?

Or it may be a true timeout that NB experiences but not CLI SSH test. Please experiment with timeout settings in Advanced Device Settings.

regards
Carsten

Hi ​@harishchandras ,

You can adjust CLI Connection Timeout value from 10 to 60 secs for a try. If you are still experiencing 301 error code, this issue could be network issue. you can use Wireshark tool to capture TCP packet for further analysis.

Packet Flow Summary

1. Client → Server: TCP handshake, version exchange, authentication.
2. Server → Client: Public key, authentication request.
3. Client → Server: Authentication response, encrypted command.
4. Server → Client: Encrypted command output.
5. Client/Server → Disconnect: Session termination.