If PIM operation causes the same event to occur six more times during the initial log throttle period, there are no
further entries in the Event Log. However, if the event occurs again after the log throttle period has expired, the
switch repeats the message (with an updated counter) and starts a new log throttle period.
Figure 85: Duplicate messages over multiple log throttling periods
Note that if the same type of event occurs under different circumstances, the switch handles these as unrelated
events for the purpose of Event Log messages. For example, if PIM operation simultaneously detects that VLANs
100 and 205 are configured without IP addresses, you see log messages similar to the following:
Figure 86: Example: of log messages generated by unrelated events of the same type
Example: of event counter operation
Suppose the switch detects the following after a reboot:
• Three duplicate instances of the PIM "Send error" during the first log throttle period for this event
• Five more instances of the same Send error during the second log throttle period for this event
• Four instances of the same Send error during the third log throttle period for this event
In this case, the duplicate message appears three times in the Event Log (once for each log throttle period for the
event being described), and the duplicate message counter increments as shown in the following table. (The
same operation applies for messages sent to any configured SNMP trap receivers.)
Table 37: How the duplicate message counter increments
Instances during 1st log
throttle period
Instances during 2nd log
throttle period
Instances during 3rd log
throttle period
Duplicate message
counter
3
1
5
4
4
9
Chapter 13 Troubleshooting
503
