Security

last person joined: 6 days ago 

Ask questions and share experiences with Juniper Connected Security. Discuss Advanced Threat Protection, SecIntel, Secure Analytics, Secure Connect, Security Director, and all things related to Juniper security technologies.
  • 1.  this configuration is not available in central policy mode

    Posted 08-08-2011 09:18

    hello all,

     

    i have nsm with version 2010.4

    i have srx -650 with version 10.4r3.4

     

    i received this error when i try to check the configuration under security-nat-(source, static, destination)

     

    I want to know how i can fix this error.

     

    Thanks

     

    Edgart

     

     



  • 2.  RE: this configuration is not available in central policy mode

    Posted 08-10-2011 08:50

    It looks like you are using Central policy mode. Hence you can not create a in-device nat policy. You need to add you NAT rules in your central policy. Select your firewall policy in NSM and use the plus button in the upper right window corner right below the Juniper logo. Pressing that plus button will reveal options to add a NAT policy to your firewall policy. Use that. The rest will be self-explanatory.

     

    Sascha



  • 3.  RE: this configuration is not available in central policy mode
    Best Answer

    Posted 08-12-2011 09:11

    Cool!

     

    Thanks



  • 4.  RE: this configuration is not available in central policy mode

    Posted 02-07-2012 03:25

    Hello,

    I'm using NSM version 2011.4
    SRX650 Virtual Chasses, OS version 11.4, Central Policy Mode.

    When I click the plus sign, then I see the options:

    Add global Firewall Rulebase
    Add Multicast Rulebase
    Add IDP Rulebase
    Add Application Rulebase
    Add Backdoor Rulebase
    Add SYN Protected Rulebase
    Add Traffic Anomalies Rulebase
    Add Network Honeypot Rulebase

    Where can I find "NAT policy"?

     



  • 5.  RE: this configuration is not available in central policy mode

    Posted 02-07-2012 05:58
    It should be there, you used the right button.

    Can you check if you already had a NAT configuration in your SRX when you first imported it? Because this will be tucked away inside the device config and not the policy, and I wouldn't be surprised if for that reason NSM hides the NAT policy option (which I'd consider a bug).


  • 6.  RE: this configuration is not available in central policy mode

    Posted 02-07-2012 07:10

    Yes, I had configured NAT before import. I'll try to remove device from NSM and then reimport without NAT.



  • 7.  RE: this configuration is not available in central policy mode

    Posted 02-07-2012 23:35

    I was previously in "Domain Admin" role and I got problem solved then my partner added my NSM account to "System Administrator" (full permissions) role.
    I have to mention that without "System Administrator" role I got strange errors then I manipulate with NAT objects.