PIX 501 SNMP trap messages

May 03, 2007 7 Replies

Hi,



Why do I get these messages? It comes continously and there is no information in it (for me). The UDP packets comes from a Linux fail over cluster interface and remains inside so PIX why complains about it?



My NMS is full of these traps. How can I disable this? Or how do I have to config PIX I'm not interested in this specifiy SNMP trap? I don't want disable all SNMP messages.



received trap community=xxxx enterprise=ciscoSyslogMIBNotificationPrefix agent=192.168.1.21 generic=6 specific=1 sysuptime=7677 trap=ciscoSyslogMIBNotifications.1 time=08:46:04 argument 1 clogHistFacility.0 => 20 argument 2 clogHistSeverity.0 => 8 argument 3 clogHistMsgName.0 => Syslog Trap argument 4 clogHistMsgText.0 => 710005: UDP request discarded from



192.168.1.18/1026 to inside:192.168.1.255/694 argument 5 clogHistTimestamp.0 => 0:01:16

TIA, Ruzsi



UDP port 694 is used for high-availability (heartbeat).

So it looks like 192.168.1.18 is sending a UDP heartbeat to

192.168.1.255 (broadcast).

Double check the configuration of the 192.168.1.18 on heartbeat

OK. I know it is HA packet but why complains about it PIX?

I checked the traps and found many other packets which the PIX "hate".

I don't want to disable "enable traps".

TIA, Ruzsi

The PIX complains about all broadcast UDP traffic that it receives.

Try

no message logging 71005

Will it disable traps, too? I know this trick for syslog. Tomorrow I make a test.

TIA, Ruzsi

pix(config)# no logg message 71005 syslog 71005 not found

:-(((

TIA, Ruzsi

710005 -- same as the number reported in the SNMP trap.

It seems good!

I copyied mechanically your command line. That was the problem with 71005.

Thank you very much for your help!

Best regards: Ruzsi

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required