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

Cisco 1900 config downloads?

Hello all,

I'm hoping someone can give me a clue. I've got loads of old cisco 1900, yes I can hear the groans, we are part way through replacing them all! I've just installed Cirrus V4 and trying to download configs. Did ok on all until I got to the 1900. If I try telnet it tells me it can't connect to the router, if I use snmp with tftp it tells me the credentials do not have write access to the device. In both cases the credentials are right. I've checked this a number of times and tried a number of our 1900.

Anyone have a clue as to how I can download the 1900 configs?

Thanks in advance

Iain

Find more posts tagged with

cirrus

cisco

backup_configuration

Accepted answers

vhcato

OK... I'm now working on installing and configuring Cirrus on our production server, and I just went through the whole 1900 "exercise" again. In our particular environment, we have 3 models of 1900's (1900, 1900c, and 1900 Lite FX). In the attached zip file, you will find a device template file that I modified to work for each specific type, and below is a brief description of the changes.

Device name and OID - Makes the name accurate in the "Device Command Template" list, as well as allowing the app to recognize each device type automatically by OID.

The "DownloadConfigIndirect" command - Modified to match the command line syntax for the 1900's.

Added the "PreCommand" line - This takes you to the command line interface (sends a "K" before looking for the username prompt).

You should be able to place these into your "DeviceTypes" directory and have Cirrus automatically recognize the devices as being one of these three types (if indeed they are). If you have any 1900 models other than these, you should be able to use these as a guide to create templates for them as well.

Along with these command templates, you will also want to set your devices such that the "Enable Level" = "enable", "Request Configs Using" = "Telnet", "Transfer Configs Using" = "TFTP", and "Allow Intermediary Device Support" = "Yes".

The only thing with which I'm concerned at the moment is that I can login and get the configs, so you may also want to alter other portions of the templates as needed.

Hope this helps...

Cisco Catalyst 1900 Command Templates.zip

All comments

iainskwatt

Just another note on this, the 1900 have that stupid menu where you can press M for a menu driven system or K for the command line. I think that's what is stopping me from using telnet to pull down the configs because I can't get past that option.

I've been looking at the snmp side of things more and now I get an error saying Unable to determine MIB type, TFTP Host:<ipaddress>DeviceIP: <ipaddress>

I can however view MIB tables!

iainskwatt

I've just received an answer from my supplier and found that downloading configs is not possible from the menu driven 1900. thought I'd better update in case anyone tried to find the answer.

chris.conway

When I was at my old job I actually had Haley from SolarWinds sat with me trying to figure this out. In the end we came to the conclusion that the first menu where you press either M or K was the problem.

If there was a way to enter the 'K' option, you'd be there.

Maybe some dev work needed on the SolarWinds side of things to allow for this kind of thing?

iainskwatt

Yeah that's what my supplier said too. Thought that might be the case that's why I was trying the SNMP side of things. But it doesn't like that either. Oh well, we hope to get the rest of the 1900's replaced with 2960's by the end of the year.

Thanks for your comment Chris.