EditThe error with connectivity is not related to the system being unresponsive at the other end, it is because parsing stops at config show .... which means onecli will not try a remote XCC address, instead it will try to connect inband, and that fails, since i'm running the code from a VM,
Also, I noticed something "strange".So if I just copy paste the code from CMD - the top level error happens.however if I remove the --bmc and then type it back, it changes color in the PS commandline, like below - and goes through successfully.
I think I have found the issue, the problem was a non UTF-8 character in the string I was pasting into powershell, the 1st "-" from --bmc was a UTF-8 BOM character and that was causing onecli to stop parsing the output after that.
3a8082e126