Acme Packet (MOSC)

MOSC Banner

Acme Packet SBC and SNMP authentication failure traps strange behavior

edited Oct 26, 2021 10:45AM in Acme Packet (MOSC) 2 commentsAnswered

Using ESBC 3900 running SCZ8.4.

Under system-config, the parameter enable-snmp-auth-traps is set to enabled.

1) It seems that the SBC is sending out a SNMP trap with trap type apSysMgmtAuthenticationFailedTrap (OID 1.3.6.1.4.1.9148.3.2.6.0.16) EVERY TIME that an SSH user logs out of the system. Furthermore, the SBC is not sending this trap when a user fails SSH authentication; instead the trap is sent every time a user closes an SSH session, whether the user was autheticated or failed authentication.

2) The generic SNMP authenticationFailure trap (OID 1.3.6.1.6.3.1.1.5.5) should be sent when "The SNMPv2 agent received a protocol message that was not properly authenticated" - for example if someone sends an SNMP GET request with the wrong community string. However, this trap is never sent out.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center