RE: router startup behavior

Mailman List Mirror (Read Only)
1

the most likely cause would be one of:

<items deleted for brevity>

  (c) script used to configure router(s) adds a 'network'
statement prior to trimming route-filters

Yeah, (c) seems most likely to me. Ratul, a script like
this or some variant could cause what you are seeing:

config-router# no neighbor <a>
config-router# no neighbor <b>
config-router# no neighbor <c>
(script to rewrite filters executes)
config-router# neighbor <a> remote-as <x>
config-router# neighbor <a> remote-as <y>
config-router# neighbor <a> remote-as <z>
(sessions start coming up)
config-router# neighbor <a> route-map <A> out
config-router# neighbor <b> route-map <B> out
config-router# neighbor <c> route-map <C> out
config-router# Ctrl-Z
# clear ip bgp external soft out

Just guessing - you're seeing these events between midnight
and 5 am?

2

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�vard