[c-nsp] Scheduling daily reload

[Roland Dobbins]

On Jan 2, 2008, at 10:27 AM, Tom Storey wrote:

> Perhaps it is an issue with ARP at the ISP end. If you dont send any  
> traffic for a period of time and your ARP entry times out, this  
> would cause data flow on a bridged service to stop, however, the ARP  
> entry should return at their end once you start generating a bit of  
> traffic, so that should be easily fixed.

GMTA.

;>

I've run into this several times in the past, and sending some traffic  
generally seemed to fix it, though in a couple of cases, I had to  
bounce the interface.

> In the case above, something like an SLA monitor which simply pings  
> an IP address accross the link, say, once a minute, should ensure  
> that ARP stays "fresh" at the ISP end. It is always possible that  
> the firmware their DSLAMs or hardware at their PoP runs has a bug  
> and doesnt properly re-establish an ARP entry for your service

Something of this sort should work, or just bouncing the interface.   
But, as you say, this is an issue which should be probably taken up  
with the upstream provider in order to determine the root cause, so  
that the workarounds won't be necessary in future.

-----------------------------------------------------------------------
Roland Dobbins <rdobbins at cisco.com> // 408.527.6376 voice

	Culture eats strategy for breakfast.

            -- Ford Motor Company