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

Config backup fails only on Active F5

fraser-sky

I am having issues with backing up config from an F5, comes back with a timeout error.

When testing the ssh connection it comes back as failed but i can see it is on the command prompt.

ANd by session trace it appears solarwinds is not detecting it is on the command prompt so does not send commands.

Strange thing is the standby partner works fine and when I fail them over the issue moves with the Active device.

Also the same device template works on all other F5s, just have issue with 2

I have a case with Solarwinds support and F5 but going round in circles.

Any help will be greatly appreciated

Thanks

Fraser

Find more posts tagged with

Accepted answers

fraser-sky

Found the reason it was not seeing the command prompt.

SSH window length is default (80), the full command prompt is 80 characters so the F5 creates a new line to put the cursor on, NCM sees the new line and not the cmd prompt.

Workaround is to adjust the prompt timeout and use virtual prompt.

If anybody knows where in Solarwinds I can set the SSH terminal size ???

Only thing in settings is CLI timeouts

All comments

fraser-sky

Done some investigation and can see through packet captures on the F5 , Solarwind poller and session trace of the SSH connection.

The F5 is responding with the command prompt, Solarwind poller detects this but does not set the command prompt, just sends another CRLF and the F5 responds with cmd prompt, this pattern continues till it times out.

Because the Solarwind poller is not setting the cmd prompt it does not send the next commands to run.

Anybody seen this issue and resolved it ??

I have updated my case with SW support and waiting on reply.

fraser-sky

Found the reason it was not seeing the command prompt.

SSH window length is default (80), the full command prompt is 80 characters so the F5 creates a new line to put the cursor on, NCM sees the new line and not the cmd prompt.

Workaround is to adjust the prompt timeout and use virtual prompt.

If anybody knows where in Solarwinds I can set the SSH terminal size ???

Only thing in settings is CLI timeouts

fraser-sky

Okay so it is hard coded into Solarwinds/NCM and cannot be changed.