Skip to content
Guides & References

Extreme Networks connection templates

The Extreme templates in rconfig/rConfig-templates v2.2.2: EXOS and NOS over SSH, and why sending the wrong paging command truncates the backup.

Connection TemplatesUpdated
Platform
Extreme Networks
On this page

Extreme Networks connection templates

The extreme/ folder holds two SSH templates, one per Extreme CLI family. Both are Core and Pro, and neither uses enable mode. This page covers release v2.2.2.

Which template

Template Use for
extreme-exos-ssh-noenable EXOS devices, such as Summit and X series switches
extreme-nos-ssh-noenable NOS and SLX-OS devices, the Brocade-derived VDX and SLX lines

The two families take different paging commands. EXOS uses disable clipaging; NOS and SLX-OS accept the Cisco-style terminal length 0. Send the wrong one and paging stays on: the session stalls at the pager prompt and the saved config stops after the first page.

If you’re not sure which family a device runs, log in by hand and run show version. EXOS reports an EXOS image; NOS and SLX-OS report a Network OS or SLX-OS version. Start with the EXOS template for anything running EXOS, and switch to NOS if the session log shows an invalid command error on disable clipaging or the config ends after roughly one screen.

The templates

rConfig-templates / extreme /extreme-exos-ssh-noenable.ymlView on GitHub
Protocol
SSH, port 22
Enable
off
Paging
disable clipaging
Status
community-tested
rConfig-templates / extreme /extreme-nos-ssh-noenable.ymlView on GitHub
Protocol
SSH, port 22
Enable
off
Paging
terminal length 0
Status
untested-starter

What to put in the command group

The folder’s README suggests:

Command group
show running-config

Type to search.