Device mode table
This table shows some examples of how NCM treats enable and configure mode equivalents for various device types.
Please note not all device types supported by NCM are present in this table - we hope it should be clear from these examples how enable /configure mode switching behaves.
This table is most useful when you want NCM to bring a device to a certain CLI mode in Mass Config Push before your commands are executed.
Please see this wiki article State of device before Push - require "enable" or "configure" CLI mode for more details on setting the CLI mode before a Config Push.
Device type |
1st mode - "base" mode
|
Command |
2nd mode - "enable" mode
|
Command |
3rd mode - "configure" mode
|
---|---|---|---|---|---|
Cisco IOS |
device>(user-exec mode) |
enable |
device# (priv-exec mode) |
configure terminal |
device(config)# (configure mode) |
3com / HP / H3C / Huawei |
<switch>(base mode) |
system-view |
[switch] (system mode) |
|
|
Arista |
device> |
enable |
device# |
configure |
device(config)# |
Aruba / HP |
switch> |
enable |
switch# |
configure |
switch (config)# |
Cumulus Linux |
cumulus@cumulus:~$ |
sudo su |
root@cumulus:/home/cumulus# |
|
|
F5 TMOS (BigIP, BigIQ, etc.) |
[root@f5:Act:Stdalone] config # |
tmsh |
(cfg-sync Stdalone)(Act)(/Common)(tmos)# |
|
|
HP V1910 / 1920 |
<switch>(base mode) |
_cmdline-mode on system-view |
[switch] (unlocked and in system mode) |
|
|
Juniper JunOS |
root@device:RE:0% (login to FreeBSD) |
cli |
root@device>(base JunOS mode) |
configure |
root@device# (JunOS configure mode) |
OPNsense |
user@OPNsense:~ % |
sudo su |
root@OPNsense:~ # |
|
|
Palo Alto PAN-OS |
user@pa-fw(active)> |
configure |
user@pa-fw(active)# |
|
|
Ruckus SmartOS |
ruckus> |
enable force |
ruckus# |
config |
ruckus(config)# |
Ubiquiti EdgeRouter |
ubnt@ubnt:~$ |
configure |
ubnt@ubnt:~# |
|
|
Vyatta / VyOS |
vyatta@vyatta:~$ |
configure |
vyatta@vyatta:~# |
|
|