question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

ruijie_os cannot be entered the enable mode

See original GitHub issue

hi,I want to use Netmiko’s ruijie_os module to automate Ruijie S7800 series switches ,However, I found a BUG during the test, and I could not enter the enable mode .

from netmiko import ConnectHandler
ruijie = {
     'device_type' : 'ruijie_os',
     'host' :    '172.16.1.1',
     'username' : 'test',
     'password' : 'test@123',
	 'port' : 22,
     'secret' : 'test@123'
}
net_connect = ConnectHandler(**ruijie)
output = net_connect.send_command('show ip int brief')
print(output)
% User doesn't have sufficient privilege to execute this command.

Log display on the switch

%CLI-5-EXEC_CMD_FAIL: User from vty0(x.x.x.x) doesn't have sufficient privilege to execute command:terminal width 256
%CLI-5-EXEC_CMD_FAIL: User from vty0(x.x.x.x) doesn't have sufficient privilege to execute command:terminal length 0
%CLI-5-EXEC_CMD_FAIL: User from vty0(x.x.x.x) doesn't have sufficient privilege to execute command:show ip int brief

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:13 (7 by maintainers)

github_iconTop GitHub Comments

1reaction
luoxiaodongzx123commented, Oct 28, 2021
  1. Only test with the Netmiko develop branch.
  2. Capture the Netmiko session_log and include it in this issue.

Netmiko automatically calls enable() as part of the session_preparation method before setting the terminal width or terminal length so I don’t see anything wrong with the code. If you see a code issue, let me know what it is and the proposed fix.

But please include your session_log here.

Kirk

I think I found the problem. My switch name had a # sign in it, which caused the code to think I was in enable mode when executing. Now I have changed the switch name and the problem has been fixed

0reactions
ktbyerscommented, Oct 27, 2021
  1. Only test with the Netmiko develop branch.
  2. Capture the Netmiko session_log and include it in this issue.

Netmiko automatically calls enable() as part of the session_preparation method before setting the terminal width or terminal length so I don’t see anything wrong with the code. If you see a code issue, let me know what it is and the proposed fix.

But please include your session_log here.

Kirk

Read more comments on GitHub >

github_iconTop Results From Across the Web

Ruijie Cloud Troubleshooting Cookbook (V1.0)
1) There are several steps needed to be checked, the contents are shown as below: l Network Connectivity. l Device Running Mode(Wireless only)....
Read more >
ruijie-rg-is2700g-series-switches-rgos-command-reference ...
You must enter an entire alias; otherwise it cannot be recognized. ... Show the configuration of all aliases if no command mode is...
Read more >
22. How to Configure a Switch IP Address - YouTube
CCNA BOOST3. LAN Switching.
Read more >
A User Cannot Enter the System View After Logging In to the ...
Version:V200R011C10.This document describes the working mechanisms, configuration procedures, and configuration examples of User Access and Authentication ...
Read more >
Ruijie Reyee Series Access Points Web-Based Configuration ...
The AP mode refers to fit AP mode. All WAN ports are enabled with DHCP by default. You can configure a WAN port...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found