Difference between revisions of "enable or disable a Provider-1 CMA"

From cpwiki.net
Jump to: navigation, search
Check Point Profressional Services
Line 5: Line 5:
 
  2) '''mdsenv <cma|cma_ip>'''
 
  2) '''mdsenv <cma|cma_ip>'''
 
  3) '''chattr +i $FWDIR/tmp/manage.lock'''  
 
  3) '''chattr +i $FWDIR/tmp/manage.lock'''  
        this makes the file undeletable.  Attempts to “disconnect” and forcibly take write access via smartdashboard fail, rm on the file fails too.
+
        this makes the file undeletable.  Attempts to “disconnect” and forcibly take write access via smartdashboard fail, rm on the file fails too.
  
 
to re-enable
 
to re-enable
  
 
  1) '''mdsenv <cma|cma_ip>'''
 
  1) '''mdsenv <cma|cma_ip>'''
  2) '''chattr -i $FWDIR/tmp/manage.lock''', this makes the file deletable again
+
  2) '''chattr -i $FWDIR/tmp/manage.lock'''
 +
          this makes the file deletable again
 
  3) '''rm $FWDIR/tmp/manage.lock'''
 
  3) '''rm $FWDIR/tmp/manage.lock'''
  
 
[[category:provider-1]]
 
[[category:provider-1]]

Revision as of 05:07, 6 August 2014


to disable a cma…

1)	Connect to cma with write privledges, this creates a manage.lock file in $FWDIR/tmp/
2)	mdsenv <cma|cma_ip>
3)	chattr +i $FWDIR/tmp/manage.lock 
        this makes the file undeletable.  Attempts to “disconnect” and forcibly take write access via smartdashboard fail, rm on the file fails too.

to re-enable

1)	mdsenv <cma|cma_ip>
2)	chattr -i $FWDIR/tmp/manage.lock
         this makes the file deletable again
3)	rm $FWDIR/tmp/manage.lock