nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Reverse Telnet

ceclark

Our security posture requires us to console into all boundary devices. I've been trying to get Cirrus to work with this, but no luck yet. We have some Avocent ACS boxes that forward to a console port. For example if I want to connect to port 5 at 10.10.10.1, I enter my username, a colon, then the port number (ceclark:1005). Once passed through to the device (Cisco router) prompts for authentication. The problem I am facing is that in Cirrus if I enter the username:port parameter, it passes through the Avocent device OK but fails at login because Cirrus is passing the ${GlobalUsername} variable (set to username:port). If I change it to just the username the login would be successful, however because there is no port number after the username, the Avocent ACS device does not know what port to forward too. Any know of a way to hack Cirrus to use two different variables (ie one for login and one for ${GlobalUsername})?