Cisco connection templates
The cisco/ folder is the largest in the library. It holds eight CLI templates that run on Core and Pro, and two TL1 templates for ONS 15454 optical nodes that need Pro. This page covers the CLI templates at release v2.2.2. The ONS templates are covered in the Optical (TL1) guides.
Which template
| Template | Use for |
|---|---|
cisco-ios-ssh-enable |
IOS and IOS-XE over SSH, where the account needs an enable password |
cisco-ios-ssh-noenable |
IOS and IOS-XE over SSH, where the account already lands at privilege 15 |
cisco-ios-telnet-enable |
IOS and IOS-XE over telnet, with enable |
cisco-ios-telnet-noenable |
IOS and IOS-XE over telnet, account at privilege 15 |
cisco-ios-telnet-enable-nousername |
Telnet lines that ask for a password only, with no username prompt |
cisco-asa-ssh-enable |
ASA firewalls over SSH |
cisco-smb-telnet-noenable |
Small Business switches (SG and SF series) over telnet |
cisco-wlc-ssh-noenable |
Wireless LAN Controllers. The only template that works with them |
For most IOS estates the choice is between the two SSH templates, and it comes down to how the account is set up on the device. If AAA puts the backup account straight into privilege 15, use noenable: there is no enable password to store, and nothing to fail. If the account lands at privilege 1, use enable and give the device record an enable password.
Firepower Threat Defense appliances (the 1120 and similar) have no template of their own. Use an IOS SSH template and set the device’s main prompt to '>' (a single quote, a greater-than sign and a single quote). Without that prompt, the backup is truncated.
The templates
rConfig-templates / cisco /cisco-ios-ssh-enable.ymlView on GitHub- Protocol
- SSH, port 22
- Enable
- on
- Paging
- terminal length 0
- Status
- community-tested
- Protocol
- SSH, port 22
- Enable
- off
- Paging
- terminal length 0
- Status
- community-tested
- Protocol
- Telnet, port 23
- Enable
- on
- Paging
- terminal length 0
- Status
- community-tested
- Protocol
- Telnet, port 23
- Enable
- off
- Paging
- terminal length 0
- Status
- community-tested
- Protocol
- Telnet, port 23
- Enable
- on
- Username prompt
- empty (skipped)
- Status
- community-tested
- Protocol
- SSH, port 22
- Enable
- on
- Paging
- terminal pager 0
- Status
- community-tested
- Protocol
- Telnet, port 23
- Enable
- off
- Paging
- terminal length 0
- Status
- community-tested
- Protocol
- SSH, port 22
- Login
- sshInteractive, User: prompt
- Paging
- config paging disable
- Status
- community-tested
Snippet error checking
The two IOS SSH templates carry a snippet_errors section. On rConfig Pro V8.4.1 and later, a snippet line that IOS answers with % Invalid input detected, % Incomplete command, % Ambiguous command or % Unknown command fails the send, and a reply starting % Warning marks it as a warning. Core and earlier versions ignore the section. The telnet templates leave it out because telnet snippet sends aren’t checked, and the ASA, SMB and WLC templates leave it out until their error output has been checked against real devices. See snippet error detection.
What to put in the command group
For IOS and IOS-XE, the repository’s annotated session uses show running-config. For a WLC, use show run-config commands: plain show run-config takes far too long to print.