Hi,

Thanks, now it works with your help!

I noticed that using command c:\progra~1\CSCOpx\bin\cwcli config compare -u admin -p admin -device %~1 -m elbe@telindus.fr give me as result difference between n and n-1 archive config.

But, I would like to compare running/startup and runing/last archive.

How is it possible with compare command or everything else ?

Elisabeth

Comparing startup to running is not easily doable from the command line. It would involve traversing the NMSROOT\files\rme\dcma\devicefiles directory to find the matching device. However, assuming that you are using syslog messages to trigger a config archive sync, simply comparing the latest archive to n-1 would suffice. If not, you could do:

cwcli config get -u admin -p admin -device %~1

Once that job completes, then run your compare command.

In fact I prefer to generate an automated action with change audit. But is seems that %~1 is not defined as device but something like "Syslog triggered Config Collection : VLAN-RUNNING".

Do you think that it exists a variable for device IP or name ?

If not, I will get the config like you mentioned then I will compare in aumomated action with syslog

-----Message d'origine-----

De : lms-marseille@telindus.fr [mailto:lms-marseille@telindus.fr]

Envoyé : vendredi 5 décembre 2008 16:15

À : Elisabeth Bezombes

Objet : RME CLI Results

Hello,

The following is the details of the command execution on "LMS".

Command Executed : cwcli config compare -u admin -p -device Syslog triggered Config Collection : VLAN-RUNNING -m elbe@telindus.fr

Details :

FATAL - DCR Error occurred. Recommended Action:Check whether DCRServer is up and running.

ERROR - Invalid device(s) specified. Recommended Action: 1.Check whether the correct device-name is used. 2.Ensure that the devices are not in suspended/conflicting states. 3.Ensure that the user is authorized to use the devices.

SUMMARY

========

Failed: compare: Failed to obtain any device(s) to work on.

You're doing a change audit automated action? I had assumed syslog. You are seeing CSCsr93354, then. I filed this bug requesting more arguments (e.g. the device name) get passed to change audit automated actions. I wrote some code to implement this, but it has not yet been committed to a release. I'm hoping to get it into LMS 3.2 due out next summer.

In the meantime, the only argument passed to a Change Audit automated action is the change description.

Hi,

You are right, at the begining I worked with syslog. After, I saw that it was possible to generate a script with change audit, so I try ...

Thanks for the bug you have given, I will work with syslog automated action until next LMS version.

I have a last question, tell me if you think I need to create an other thread.

We can't configure security device (firewall) to forward informationnal syslog (config modification)to LMS because thoses devices generate many informationnal syslogs.

Those device can generate a trap (config change) which is send to DFM.

Do you think that we can configure DFM to generate a syslog to lms which is analysed by RME which launch the script diff.bat for sending a mail with conf difference ?

Many thanks, Elisabeth

What you want to do is not possible. RME will have to receive the syslog message directly from the device or from a transparent forwarding source. Going through DFM will not work.

What do you mean by transparent forwarding source ?

Is it possible to use a soft which receive the trap and forward a syslog similar to a config change syslog to rme ?