labroot@vsrx> show security screen ids-option screen1

Screen object status:

Name value

TCP SYN flood attack threshold 20000

TCP SYN flood alarm threshold 5000

TCP SYN flood source threshold 5000

TCP SYN flood destination threshold 1000

TCP SYN flood timeout 30

TCP SYN fragment enabled

TCP SYN FIN enabled

TCP SYN-ACK-ACK proxy threshold 1000

However at the cacti side there is problem with the OIDs.

- When we go with those overly long OIDs , we get a problem in Cacti, the objects are listed in the verbose scan result, but are not detected properly and hence not all added to Cacti

root@vSRX1-Branch> show snmp mib walk 1.3.6.1.4.1.2636.3.39.1.8.1.1.1.1.3 

jnxJsScreenMonSynAttk.84.82.85.83.84.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0 = 0

jnxJsScreenMonSynAttk.117.110.116.114.117.115.116.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0 = 0

- String "85.78.84.82.85.83.84.0.0.0..." after the OID means the value of "jnxJsScreenZoneName".

It means the security zone name which screen is used for.

- The index string type is ASCII and length is fixed 64.

- "85.78.84.82.85.83.84.0.0.0..." =》 UNTRUST.0.0.0... <<< security zone name is UNTRUST

For example, 85 = U, 78=Un...