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

Connectivity issues discarding config file

BryanBecker

I've been having this issue with V3.5.1 for quite some time now. Every night my config backups run I get a failed login report should different devices each night with a failure of "Connectivity issues discarding config file".

If I go into the device details and use the validate login cirrus is able to get in just fine. Again...this is random on which device reports the error but the validation works every time I try it. My case is 7314 and has been open since May. The latest is its sitting in development...

Denny/Mark...can you guys look into this and find out when this will get fixed?

Thanks,

BB

Find more posts tagged with

Accepted answers

All comments

kindbro

I just noticed this happened to me as well, since upgrading to the new version.

Things that make you say Hmmmmm.

Bret

Haley

The error message you are seeing was created in Cirrus 3.5. Cirrus products this error message when it has issues communicating with a device via ssh. To help us better understand your setup, can you please provide answers to the following questions: 1. Are you managing all devices within the job via ssh? Or are some devices managed via ssh and some via telnet?2. Do all ssh managed devices have a username?

3. Within the backup job, which of the following options is selected?

a. Backup Running Configs

b. Backup Startup Configs

c. Backup Running and Startup Configs

BryanBecker

1. Yes - SSH
2. Yes - we have TACACS enabled so all device access from Cirrus uses a specific TACACS username/password.
3. Since day 1 I have been unable to get 1 job to backup both running and starting configs. I'm not sure which job is causing the problem. I have a separate Failed Login Report that runs every night.

BB

jedi755

i am also seeing this error now on a device as well, ssh and never had any problems until now.

dz0

I have the had the same problem.

In order to resolve it I had to reduce the concurrent TFTP sessions to 1. so, I just quit using TFTP altogether and now use telnet/ssh for all of my config downloads.

Oh, and I also had to break up my list of devices into smaller groups - but now one of those groups had grown tom more than I originally started with... go figure.

I wish this app was more consistent and stable - it would be great if it were.

rdeprez

I had this issue when I was running NPM/Cirrus in a VMware environment. At the time I couldn't tell if my network devices were being fickle or if it was something with the virtualization or the constant 60% to 80% load the server was reporting. I moved to a real server with more resources and haven't had a problem since. For the people seeing this issue are you running Cirrus in a virtualized environment or a highly utilized server?

BryanBecker

I had this issue when I was running NPM/Cirrus in a VMware environment. At the time I couldn't tell if my network devices were being fickle or if it was something with the virtualization or the constant 60% to 80% load the server was reporting. I moved to a real server with more resources and haven't had a problem since. For the people seeing this issue are you running Cirrus in a virtualized environment or a highly utilized server?

I have a dedicated server with plenty of horsepower. It never goes over 30% on CPU, memory is good etc. It's happening on 2 different Cirrus servers and the devices in question is very random in nature. SW has been working on this for months but doesn't seem its getting anywhere.

BB

Haley

Support and development have been unable to duplicate the scenario when there are not connectivity issues. You should be hearing from our support team over the next day or two, if you have a case with support, with additional information requests to help isolate the issue. If you do not have a case open, please submit one at https://forms.netsuite.com/app/site/crm/externalcasepage.nl?compid=638609&formid=12&h=3d0552f20b2e9bd6580b.

BryanBecker

My case on this is 7787.

BB

kclark

I'm testing Cirrus now using the eval version, and have the same problem for a subset of my equipment. I have about 80 HP Procurve switches at one location. If I set the Connectivity Profile to "HP Switch", my config backup fails with the error message you specified. If I set the profile to "Generic", it works. I don't know if it will solve your problem, but from my perspective the issue is the Connectivity Profile.

rdeprez

For those who are experiencing this problem, do you have session tracing turned on and if you do what is it showing? If it reveals an error would you post the session trace here for review? (I know it goes without saying but ,please be sure to remove anything that may be sensitive to your environment.)

jonchill

I had this same issue and had to change my concurrent downloaded configs from 20 to 10 and the problem went away.

HTH

bleearg13

I had this same issue and had to change my concurrent downloaded configs from 20 to 10 and the problem went away.
HTH

I wish it were this easy with some of us. I have mine throttled down to 3 simultaneous downloads, but I still experience this problem.

jedi755

has anyone solved this problem? i still have 1 device that all of the sudden started doing this via SSH.

kbenton

Is there anything new on this? I've got v5 sp2 now, and am still getting the same error on catos switches.

kbenton

I'll answer my own question... In the customer portal, I see v5 sp2 is the latest NCM, but when I contacted support about this issue, they gave me the link to download 5.1. Not sure why 5.1 isn't shown on the customer portal...? I upgraded to 5.1 and the problem is now resolved. woohoo!

apscherz

So for me, when I experienced this on my HP switches, I had to change the device command template to auto determine instead of telling it to use HP Switch's template. Not sure if that'll work for anyone else but it did for me.