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

Problem with Config Download

I had this same problem in v3 and still have it in v4.

When I get the e-mail to tell me which devices failed downloading there configs there are at least a dozen (I would be good to just get a list of the failed devices and not all devices). So when I try and sort these out in Cirrus and try manually logging in and downloading the config it works everytime for every device that failed the previous night

I've checked ACS for failed TACACS login but there are none during the time of the downloads so much so that checking the passed authentications the so called failed devices logged in successfully.

I'm now confused as to how to resolve the problem ACS and TACACS is saying the device was logged nto successfully but Cirrus says that the download failed due to bad password and done manually it works fine.

Any help would be much appreciated.

Thanks

Find more posts tagged with

Accepted answers

All comments

jodros

Are the devices that are failing connected via low-speed links, i.e. fractional T1 frame-relay? I have the same issue, but I believe it to be either the device was down at the time, which of course would not show a TACACS+ passed authentication, or it is taking too long for Cirrus to get the reply back from the log in. You might want to tweak some of the settings that will allow Cirrus to wait a bit longer for a reply. If these devices are on your LAN, then I have no idea why it is doing this, unless there is some major congestion on the network at the time.

jonchill

The devices are on a LAN and connected to Cirrus via a 1gig WAN.

jodros

So if I am understanding you correctly, the devices that are having the issue are geographically in another location from Cirrus, and a Gig WAN connection is used to communicate. Is this correct? What sort of WAN connection is it? I would assume possibly Metro E if it is a gig connection. Is there any bottlenecking on this gig connection?

jonchill

It a switched fibre LES circuit.

Just checked the report from lastnight and while there are some of the same switch that failed yesterday there are others that were all right yesterday and have failed today.

The WAN typically runs at around 10Mbps during the day and spikes between 00:00 and 02:00 when it runs at around 100Mbps so its not strained.

chris.lapoint

I had this same problem in v3 and still have it in v4.
When I get the e-mail to tell me which devices failed downloading there configs there are at least a dozen (I would be good to just get a list of the failed devices and not all devices). So when I try and sort these out in Cirrus and try manually logging in and downloading the config it works everytime for every device that failed the previous night
I've checked ACS for failed TACACS login but there are none during the time of the downloads so much so that checking the passed authentications the so called failed devices logged in successfully.
I'm now confused as to how to resolve the problem ACS and TACACS is saying the device was logged nto successfully but Cirrus says that the download failed due to bad password and done manually it works fine.
Any help would be much appreciated.

Jon, if you're still experiencing this issue, can you please open a support ticket against this and reference internal dev tracking #1179? It seems now we have several folks experiencing this issue so we'd like to leverage your help to get to the bottom of it. We're not able to reproduce in house, so we're going to need to enable special logging and/or sessions traces in your environment to help us troubleshoot.

jonchill

I did have a call open but then went on leave and the call was closed and I'm now up to my eye balls in work and not on site most of next week so will log a call when I get a chance.

chris.lapoint

Thanks Jon, we appreciate the help. I definitely hear you on the leave for a week, come back to 2 weeks worth of work. Let me know when you do and I'll make sure the case gets assigned to this issue in dev.

FJS

We have the same issue and we noticed it started after we implemented TACACS. It looks like Cirrus is trying to backup the configs too quick and the devices don't have enough time to contact TACACS for authentication therefore authentication failure. When you execute a manual backup through Cirrus, no problems. Please let us know when this is fixed. Our backups are only randomly working now...

Not sure if this helps but our TACACS server is using Active Directory for authentication.

Thanks.