Forum Discussion

nprts_142504's avatar
nprts_142504
Icon for Nimbostratus rankNimbostratus
Feb 11, 2014

OSPF warnings on F5 BIG-IP 11.4.1

Hello,

I have an issue with F5 BIG-IP LTM 11.4.1.

I am getting numerous warning messages from OSPF process in logs. OSPF seems to work fine, but I don't know what these messages mean. Should I ignore them? Their OSPF neighbors are Cisco Catalyst 4900 switches. Please give me a clue. Thank you!

Tue Feb 11 04:15:43 MSK 2014 warning m1-rt-f5-1 OSPF[12267] OSPF: AgentX: process_packet, unhandled PDU, Operational state
Tue Feb 11 04:15:43 MSK 2014 warning m1-rt-f5-1 OSPF[12267] OSPF: AgentX: process_packet (Operational state), Response-PDU, 78966:78965
Tue Feb 11 04:15:43 MSK 2014 warning m1-rt-f5-1 OSPF[12267] OSPF: AgentX: requested pdu : 1
Tue Feb 11 04:15:43 MSK 2014 warning m1-rt-f5-1 OSPF[12267] OSPF: AgentX: process_packet, unhandled PDU, Operational state
Tue Feb 11 04:21:57 MSK 2014 warning m1-rt-f5-1 OSPF[12267] OSPF: AgentX: process_packet (Operational state), Response-PDU, 78995:78994
Tue Feb 11 04:21:57 MSK 2014 warning m1-rt-f5-1 OSPF[12267] OSPF: AgentX: requested pdu : 1
Tue Feb 11 04:21:57 MSK 2014 warning m1-rt-f5-1 OSPF[12267] OSPF: AgentX: process_packet, unhandled PDU, operational state
Tue Feb 11 04:28:07 MSK 2014 warning m1-rt-f5-1 OSPF[12267] OSPF: AgentX: process_packet (Operational state), Response-PDU, 79025:79021
Tue Feb 11 04:28:07 MSK 2014 warning m1-rt-f5-1 OSPF[12267] OSPF: AgentX: requested pdu : 1
Tue Feb 11 04:28:07 MSK 2014 warning m1-rt-f5-1 OSPF[12267] OSPF: AgentX: process_packet, unhandled PDU, Operational state
Tue Feb 11 04:28:07 MSK 2014 warning m1-rt-f5-1 OSPF[12267] OSPF: AgentX: process_packet (Operational state), Response-PDU, 79025:79022
Tue Feb 11 04:28:07 MSK 2014 warning m1-rt-f5-1 OSPF[12267] OSPF: AgentX: requested pdu : 1

  • This really does need to be fixed.

     

    i understand it is fixed in 11.6.0.

     

    sol15572: The BIG-IP system logs AgentX error messages every ten seconds

     

    https://support.f5.com/kb/en-us/solutions/public/15000/500/sol15572.html

     

    Not certain why F5 thinks it is not an issue to fill the logs with garbage

     

    can syslog-ng filter it?

     

    LTM 9.4.2+: Custom Syslog Configuration by Deb Allen

    https://devcentral.f5.com/s/articles/LTM-9-4-2-Custom-Syslog-Configuration

     

  • did you enable the routing module? have you enabled logging with a higher level?

     

  • F5 answer for this problem

     

    The OSPF error messages that you are seeing are due to bug ID 380290. It's a cosmetic warning message. If a BIG-IP is configured for SNMP traps, then when a ZebOS routing protocol requests to send a trap, it will get back an internal response confirming the trap is being sent, but the calling protocol stack fails to match the trap confirmation to the trap request and logs the warning message. There is no definite fix for it at this time.

     

    For me, this exist at least on 11.3 & 11.4.1, and there was no workarround, because it's not possible to unconfigure SNMP traps.

     

  • This really does need to be fixed. Not certain why F5 thinks it is not an issue to fill the logs with garbage....ggrrrr