Forum Discussion
ChetanAr_315803
Cirrus
CirrusSSL handshake Failures and Fatal Errors through MIB
How can i capture SSL handshake Failures and Fatal Errors through MIB? If not through MIB, is there any other way through which i could capture them and see their trends in monitoring tool?
Got it sorted. Manual SNMP OIDs can be used to capture specific kind of profiles like Handshake error, Fatal Errors, etc. Format of SNMP OID (For SSL Client side Handshake Failures - ltmClientSslStatHandshakeFailures): snmpwalk -v 2c -c public <F5 IP> 1.3.6.1.4.1.3375.2.2.6.2.2.3.1.29.<Length of the profile name in decimal>.<Name of the profile in decimal>. For example, profile name called "/common/test_profile" has SNMP OID for ltmClientSslStatHandshakeFailures as below:
snmpwalk -v 2c -c public <F5 IP> 1.3.6.1.4.1.3375.2.2.6.2.2.3.1.29.20.47.67.111.109.109.111.110.47.116.101.115.116.95.112.114.111.102.105.108.101
Accordingly based on the name, SNMP OID can be configured. If below command is executed, it will list all the profiles with the value of Handshake errors: snmpwalk -v 2c -c public <F5 IP> 1.3.6.1.4.1.3375.2.2.6.2.2.3.1.29
ChetanAr_315803Got it sorted. Manual SNMP OIDs can be used to capture specific kind of profiles like Handshake error, Fatal Errors, etc. Format of SNMP OID (For SSL Client side Handshake Failures - ltmClientSslStatHandshakeFailures): snmpwalk -v 2c -c public <F5 IP> 1.3.6.1.4.1.3375.2.2.6.2.2.3.1.29.<Length of the profile name in decimal>.<Name of the profile in decimal>. For example, profile name called "/common/test_profile" has SNMP OID for ltmClientSslStatHandshakeFailures as below:
snmpwalk -v 2c -c public <F5 IP> 1.3.6.1.4.1.3375.2.2.6.2.2.3.1.29.20.47.67.111.109.109.111.110.47.116.101.115.116.95.112.114.111.102.105.108.101
Accordingly based on the name, SNMP OID can be configured. If below command is executed, it will list all the profiles with the value of Handshake errors: snmpwalk -v 2c -c public <F5 IP> 1.3.6.1.4.1.3375.2.2.6.2.2.3.1.29