Support Center > Search Results > SecureKnowledge Details
Troubleshooting problem when cannot create SAM rule via CLI
Symptoms
  • Adding Suspicious Activity Monitoring (SAM) rules via CLI fails with error:
    [Expert@MyHost:0]# fw sam -f MyHost -t 600 -l long_noalert -J src 1.1.1.1
    sam: MyHost (0/1) failed 'Inhibit Drop Close src ip 1.1.1.1 on MyHost' processing
    
  • The output of "fw sam -M -nji all" does not show the new SAM rule.
Solution
Note: To view this solution you need to Sign In .