Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

%IP-4-DUPADDR: not showed on the gestion platform

HI all,

The thing is... our gestion platform (which receiveds the SNMP traps) don´t shows dupplicated ip addresses in the network, I mean... ie. we have a 6500 box and we can see the following line in the log: May 30 20:03:35: %IP-4-DUPADDR: Duplicate address 10.9.0.124 on Vlan3003, sourced by 0015.2bb4.fa45

I understand this box has detected a device in the network with an ip which is already configured on itself, but we don´t know the way to tell the 6500 box about sending a trap to the gestion platform...

Has anyone any idea about it?

Thanks in advance.

Regards,

2 REPLIES
Silver

Re: %IP-4-DUPADDR: not showed on the gestion platform

Hi Enrique,

do you have logging to a syslog server enabled?

For IOS: logging trap

and for CATOS: set logging server

If a IOS "logging trap errors" is set the warnings the the Dup_IP are not sent to the syslog server.

Only messages from Level 3 down to 0 are sent (emergencies, alerts, critical and errors)

You will find a list of levels here:

http://www.cisco.com/en/US/products/hw/switches/ps628/products_configuration_guide_chapter09186a00801cde77.html#58814

(Note: This is for another switch, but the levels are accurate)

If you want the level 4 messages sent to a syslog server you have to issue the command

IOS: logging trap warnings

CATOS: set logging server 4

And be sure logging is enabled.

Hope that helps

Best regards,

Frank

New Member

Re: %IP-4-DUPADDR: not showed on the gestion platform

HI Frank,

We have a login level informational, so, it includes from level 6 to 0, Am I right? then... the ip dupplicated address alarm should be sent to the syslog server...

SWPE01#sh logging

Syslog logging: enabled (0 messages dropped, 2 messages rate-limited, 0 flushes, 0 overruns)

Console logging: level debugging, 635 messages logged

Monitor logging: level debugging, 303 messages logged

Buffer logging: level debugging, 637 messages logged

Exception Logging: size (4096 bytes)

Count and timestamp logging messages: disabled

Trap logging: level informational, 352 message lines logged

Logging to 172.26.26.98, 352 message lines logged

Logging to 172.26.26.99, 352 message lines logged

186
Views
0
Helpful
2
Replies
CreatePlease login to create content