- CheckMates
- :
- Products
- :
- Quantum
- :
- Management
- :
- Re: CLI access denied through serial
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
CLI access denied through serial
Hello there,
i have a gateway, that all users can connect through webUI & ssh on clish and expert mode. But we cannot connect to clish through console(serial).
So, the problem is that we are going to do some big changes and we want to make sure that we have console access if we have a problem. We can connect to expert mode, if we change the user's default shell to bash, but from expert when we execute "clish" we get "User: admin denied access via CLI" error for every user we tried.
After researching the knowledge base, i found the sk102828 which needs fail-over and this gateway is not clustered.
Does anyone had this issue before? Any ideas?
Thank you!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
cpinfo -y all please
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
also try this from any user clish available:
set user admin shell /etc/cli.sh
add rba user admin roles adminRole
unless those lines are already in place?
> show configuration user
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Jerry,
the admin user has already default shell the /etc/cli.sh and by default has the adminRole.
Please be advice that when you ssh into the machine everything works fine, only when you try serial connection the issue occurs.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
fine. gotcha.
please provide output from following commands:
1. cpinfo -y all
2. uname -a
3. ntpq -pn
4. date
Let's see though what you really run there, before that it is extremely difficult to say why "console" connection behave as described.
On a side note, are you doing the "console hook-up" by Console Port or mini-USB one? is it done by Mac or PC? have you tried that on more than one computer?
