Hi,
wanted to know if there's any support for Acme's Session Boarder Controller.
It's CLI based, although, there is 2 levels of password in order to get into basic mode, then enable to get to exec mode.
Thanks
Can you post the exact series of commands necessary to show the config on the command line? Are there 2 password prompts or are there 3?
when you login via SSH there is 2 sets of password, here is what it look likeL:
Using username "pipsadmin".pipsadmin@10.98.5.100's password: ****** (the password is not actualy echoed back)
PIPSSBC1Please be sure to type in your commands wiselyAnd remember, with great power comes great responsibilityPassword: ****** (the password is not actualy echoed back)SBC1>SBC1>SBC1>SBC1> enablePassword:SBC1#SBC1# show configuration
We just purchased one of these too, so backing it up would be great.
The issue here is that using ssh, there is 2 login prompts.
you ssh to the box, enter a username, then a password.
Then it asks you for another password.
then you type enable
then you get the enable password
then your in...
this is what the NCM is lacking, is the ability to change how many password prompts there is.
Any feedback on this?
NCM 5 resolves this issue. Are you in the Beta group? If so you may want to try the RC to see if it has resolved the issue for you.
Resolves the issue?
Yes I am in the beta, and yes I have RC installed, but how is RC fixing this issue?
In the RC we added the capability for SSH based interactive login. Looking at the session traces, it seems that the device you are connected to is requesting an interactive login.
If RC is not working for you, please post the session trace from that so we can diagnose what could be going on here.
where is this SSH interactive login?
I cannot seem to find this...
SSH Interactive login capability was added for the SSH sessions that Cirrus establishes with the devices. The users should not have to do anything as Cirrus will detect the interactive login mode on the device and send username and password to the device.
Until now Cirrus would only pass the credentials to the device during the SSH connection handshake. So if the device required an interactive login after the SSH session was established it would fail to connect to the device. WIth the interactive login support we now look for user name prompt and then send the credentials in as needed.
the problem here, is that there is 2 password.
NCM failes to login with SSH all the time to this device.
How can I debug this and see what NCM actualy sees and sends in response?
Cirrus provides Session Traces to debug these sort of issues. To turn on session tracing
log into the win32 console
Click on File > Settings > Session Tracing
Check the box to collect Session traces
Now when you perform the download operation, Cirrus will generate a session trace. This trace will allow us to see the interaction between Cirrus and the device. Once you have the trace you may want to post it here so we can try and assist with the diagnosis.