[45088] in North American Network Operators' Group
Re: router startup behavior
daemon@ATHENA.MIT.EDU (Havard Eidnes)
Wed Jan 16 06:07:15 2002
Date: Wed, 16 Jan 2002 12:05:43 +0100 (CET)
Message-Id: <20020116.120543.52175343.he@uninett.no>
To: mborchers@splitrock.net
Cc: ltd@interlink.com.au, ratul@cs.washington.edu, nanog@merit.edu
From: Havard Eidnes <he@nordu.net>
In-Reply-To: <CA47B6D616C0D211B92E0008C7C5657C16F5FF42@hscmpxsrvcl01>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Errors-To: owner-nanog-outgoing@merit.edu
> Just guessing - you're seeing these events between midnight =
> and 5 am?
Hm, couldn't reist this one: "which time zone"?
Just hinting that even though it's that time interval in the US, local
time is different in other places around the world, so if this is
causing disturbance, others are probably being hit in their working
hours.
Besides, I was under the impression that to activate a new outbound
roting policy on a Cisco, you could just modify / replace it, but that
you would still have to do
router#clear ip bgp xxx soft out
to activate it. This means that the policy for an existing peer can
be modified without having to remove the peering and reenable it
shortly thereafter (something which would cause needless route
flapping).
Regards,
- H=E5vard
