Thanks, we're going to try these steps out and I will let you know.
El 05/05/2010 4:30, Ihsan Junaidi Ibrahim escribió:
without studying your topology in detail, i think the best reason that
can be explained by your rtsockmon output is there is spurious routing
updates in your topology. these
Hi,
In this router, we have configured 2 logical router. In the 'physical'
we have only one provider (one full-routing) and in the logical one we
are connected to 2 providers (2 full-routing). Are these events for both
logical routers? They are differents providers, why should I configure
alw
Looks like there's a persistent oscillation in your routing topology. If you
see routes i.e. 195.240.208.0 that comes from different peer ASes, you might
want to configure always-compare-med in your bgp path-selection statement.
By default, it will only compare routes that come from the same peer A
Hello,
I've just executed this comand on the shell and it appeared a lot of routes:
r...@eg01% rtsockmon -t rpd
sender flagtype op
[17:30:29] rpd Proute add inet6 2401:ee00:: tid=2
plen=32 type=user flags=0x10 nh=indr nhflags=0x4 nhidx=262144 filtidx=0
[17:
Hello there,
This message has appeared in the log of our M20. It is not the first
time it occurs and we are quite worried. The average CPU consumption is
4% and just at the time the message appeared on the log, we found
increases up to 100% and an increase in temperature of 6 º in the
routing
5 matches
Mail list logo