lmconfig control at device/group level
I have raised this numerous times with my CSM, account manager, etc. but it does not seem to be getting traction. It is a lawsuit waiting to happen, so it really deserves attention. Right now, the trigger for LMConfig is entirely arbitrary depending on who wrote which code. Most often it is based on ssh.user and ssh.pass being defined in a device. The problem with this is there are other reasons to have those properties (e.g., Err-Disabled port detection), so you can enable LMConfig across many devices and incur a large cost (especially with the new contract terms) without intent. It should be required to check off an "Enable LMConfig" option at the device or group level, and similarly for any other premium feature. Minimally, all the configsources should be changed to have a"enable_lmconfig" or similar property required in the Applies To logic.2Views0likes0Comments
LMConfig and Reporting on ConfigSources
Hi Guys, Wejust implemented LMConfig and I'm trying to run a report to see what devices do not have the IOS configuration successfully downloaded. We have some legacy equipment still not Configured for SSH and TACACS accounts.soI'm trying to get out of having to manually hunting through all our devices to determine what ones need SSH configured and what ones need the TACACS account added.Even justbeing able to pull a report on all devices and whatones have the ConfigSources - IOS Configs field would be a big help. See attached pic for a visual Cheers and Thanks in advance Joel23Views0likes2Comments
LMConfig View Config rights
Currently, users need Manage rights to access the Config view. We need our junior sys admins to be able to view configurations without having the Manage rights. Please add a View onlyright for Config. The View Config right should only allow viewing of already collected configurations, but not permit Collect Now.7Views0likes1CommentLMConfig - Enhanced config alerting
Currently the only option available is to alert each time a configretrieval fails. I would like to be able to say "only alert if config retrieval fails n number of times in a row". For some of my devices, I'm not so concerned if daily config retrieval fails, but I'd like to know about it if it was failing for 3 or more days in a row.3Views0likes0CommentsLMConfig - More control over config retrieval time
Currently, a ConfigSource only provides a limited choice of options for when to collect a device configuration (1 hour, 4 hours, 8 hours, 1 day). There is not control over when the collection occurs and it appears to automatically happen at or around midnight of each day. We have 1,000+ network devices and we are seeing frequent config retrieval failures, and we suspect it is because the Collector is trying to dotoo much at once. We are distributing the load to a second Collector, but with a couple of hundred, some collections fail. Sometimes it's just one of the four Cisco configs, other times all four fail. The request is to be able to somehow tell the Collectors to stagger their config collections.0Views0likes0Comments