Hi Leslie,

I've had this problem before when migrating from rsrb to dlsw.  The source of
the problem was a leftover source-bridge remote-peer statement in the cisco
config (with no matching peer statement on the remote router).

If you query the mib2 tcpConnTable for the routers in question, you should see
the ip addresses that are the source of the trouble.  (You may need to issue
the query several times to see which connections keep opening and closing.)

Hope that helps...

Mike Flood
Lands' End
Dodgeville, WI



Leslie Clark wrote:

> Anybody had trouble with lots and lots of these? The customer can't see
> what would cause
> a couple of 2500 routers to send these out at the rate of up to 1/sec.
> There was a half-baked
> install of Ciscoworks on the system, but I killed all of those daemons and
> moved the
> registration file out of sight in case somehow the application was
> generating them, to no
> avail. The only other place I've seen this was when a customer had a script
> running that
> repeatedly connected to the router to run something. I can filter them out
> but we really want
> to stop them. Besides the traffic (if there is any real traffic), they are
> filling up the event log,
> so we have no useful history. I appreciate any suggestions...
>
> Cordially,
>
> Leslie A. Clark
> IBM Global Services - Systems Mgmt & Networking
> (248) 552-4968 Voicemail, Fax, Pager