[c-nsp] EEM Track Configuration

[Mohammad Khalil]

Hi all 
Maybe the IOS image I was using caused some issues
ACS already in place , but my customer wants to try it via scripting and see the mail arrive at his inbox when a change is made on the device
Can you please share your configuration?
I have done the below but as I told earlier am facing a lot of log messages and error messages 

archive
 log config
 logging enable
 notify syslog 
 hidekeys

event manager scheduler applet thread class default number 10

But My question still if I accessed one of the interfaces , for example
interface Fa0/0
and exit from the configuration mode to the privileged mode , the parser logs that as a change even though , no changes were made 

Thanks in advance

BR,
Mohammad


> Date: Mon, 27 Jul 2015 13:39:06 +0100
> From: p.mayers at imperial.ac.uk
> To: cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] EEM Track Configuration
> 
> On 27/07/15 13:12, Mohammad Khalil wrote:
> > Hi all
> > Am sure the below has been asked a lot , but till now am finding people arguing about this
> >
> > Am trying to track any configuration changes done on my device
> 
> You might want to consider TACACS.
> 
> > If i used parser
> >
> > archive
> >   log config
> >    logging enable
> >    notify syslog contenttype plaintext
> >    hidekeys
> >
> > I am getting not enough TTY lines , so I have configured
> > event manager scheduler applet thread class default number 10
> 
> I don't know what this means.
> 
> We use the archive "log config" without problems. It works fine.
> 
> Where did EEM come into things?
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/