We've encountered the same problem with slip addresses. The way we addressed the
issue was to change the trap to "LOG ONLY". At the end of each day, we have a
script that reads the trapd.log for the duplicate IP messages, filters the one
that contain valid IP addresses, and then emails the report to specific
engineers. If you familiar with Korn Shell, the script looks something like
this.....

#
# Extracts duplicate addess messages & creates a tempfile
grep "Duplicate Address" trapd.log  > tempfile.rpt
#
# Filters messages that have 127.0.0.1 from the tempfile
grep -v "127.0.0.1" tempfile.rpt > dupip.rpt
#
#Sends the report to usr@abc..
mail -s"Duplicate Address" "usr@abc" < dupip.rpt


Brad Martin
Metlife






"BAUDOUX BERNARD" <bernard.baudoux AT FORTISBANK DOT COM> on 10/11/99 02:47:08 
AM

Please respond to "Discussion of IBM NetView and POLYCENTER Manager on NetView"
      <NV-L AT UCSBVM.ucsb DOT edu>

To:   NV-L AT UCSBVM.ucsb DOT edu
cc:    (bcc: Brad Martin/Bsg/MetLife/US)
Subject:  Re: Duplicate Address trap



Hi,

if you use the same IP address for some interfaces, then I guess this
particular address is not of much mean for you.
Have you tried to 'unmanage' the interfaces associated to this address ?

Regards,
Bernard Baudoux
IS/DIS/Telecom/ LAN & Routers Architectures
* : +32 (0)2/56.524.68
* : 66/U
e-mail : bernard.baudoux AT fortisbank DOT com


> -----Original Message-----
> From: Sin Wai Yee, Maggie [SMTP:mwysin AT KCRC DOT COM]
> Sent: Monday, 11 October, 1999 03:32
> To:   NV-L AT UCSBVM.UCSB DOT EDU
> Subject:      Duplicate Address trap
>
> I have received many duplicate address trap. The reason is that we are
> using
> same SLIP address for some switches and same Loopback address for some
> routers. For our existing setting, how should we handle this case ?
>
> Please comment ?