I'm working on a provider-1 R65 system with two CMAs.   One CMA
switches logs every night just fine.  The other one is not working for
some reason even though the schedule is set up correctly. 

On the one that isn't working properly; I set mdsenv to the correct
cma, then do a 'fw logswitch'.  It eventually times out with a "Failed
to Connect" message.  What's interesting is, if I stop then start the
CMA the fw logswitch will work fine - but only once or twice.  I've
also tried from the SmartView Tracker.  To get the logswitch to work
again temporarily I have to stop and start the CMA. 

Has anyone else had this problem before? 

Matt

Scanned by Check Point Total Security Gateway.

=================================================
To set vacation, Out-Of-Office, or away messages,
send an email to [EMAIL PROTECTED]
in the BODY of the email add:
set fw-1-mailinglist nomail
=================================================
To unsubscribe from this mailing list,
please see the instructions at
http://www.checkpoint.com/services/mailing.html
=================================================
If you have any questions on how to change your
subscription options, email
[EMAIL PROTECTED]
=================================================

Reply via email to