On SRX Series devices, In Chassis Cluster, when security alg trace options are deactivated together as part of single commit, it causes the entire security hierarchy to get deactivated.
- SRX devices in Chassis Cluster having security alg trace options configured. - Triggered by deactivating the ALG, alg-support-library, alg-manager traceoptions together in single commit.
{primary:node0}user@router# show | display set | match traceoptionsset security alg traceoptions file sip-alg-traceset security alg traceoptions file size 10mset security alg traceoptions file files 5set security alg traceoptions level verboseset security alg alg-manager traceoptions flag allset security alg alg-support-lib traceoptions flag allset security alg <sip|ftp...> traceoptions flag allwhen the above mentioned traceoptions are deactivated together as part of single commit.{primary:node0}user@router# show | display set | match deactivatedeactivate security alg alg-manager traceoptionsdeactivate security alg alg-support-lib traceoptionsdeactivate security alg <sip|ftp...> traceoptionsdeactivate security alg traceoptions
/config/juniper.conf:288:(42) syntax error: traceoptions [edit security alg alg-manager] 'alg-manager inactive: traceoptions flag all;' syntax error[edit security alg] 'alg-manager' warning: statement has no contents; ignored[edit security alg] 'alg-support-lib' warning: statement has no contents; ignoredload complete (1 errors)
{primary:node0}[edit]user@router# commitwarning: You have changed enhanced services mode.You must reboot the system for your change to take effect.If you have deployed a cluster, be sure to reboot all nodes.node0:commit complete
{primary:node0}[edit]user@router# show security#### inactive: security##
commitIt causes the entire security hierarchy to get deactivated.{primary:node0}[edit]user@router# show | display set | match deactivate deactivate chassis cluster redundancy-group 1 interface-monitordeactivate security idpdeactivate security alg traceoptionsdeactivate security alg sip traceoptionsdeactivate security flow traceoptionsdeactivate security nat destination rule-set PAT rule WASPdeactivate security nat proxy-arp interface reth4.0deactivate security zones security-zone Private interfaces reth4.0deactivate security <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<deactivate interfaces reth4
If user deletes the trace options instead of deactivating it, then the deactivation of security stanza is not seen OR if the user follow the commit at every step after running one by one command, like below example then also issue {deactivation of security stanza} not seen.deactivate security alg alg-manager traceoptions------>Commitdeactivate security alg alg-support-lib traceoptions------>Commitdeactivate security alg <sip|ftp...> traceoptions------>Commitdeactivate security alg traceoptions------->CommitNote: This is an expected behavior for now and need to follow workaround solution mentioned to avoid the issue.
PR : 1482426 [single-source-commit] - When deactivating ALG trace options it also deactivates the security stanza