--- Begin Message ---
+1 on the performance of Amsterdam, shocking. MPLS + jumbo frames absolutely
useless. Went with 16.3.6 to get around all said issues and seems stable as a
ibgp RR with the couple of licenses I need to run that contact the cisco smart
system.
On 22 Nov 2021, at 11:43 pm,
On 11/22/21 14:10, Robert Hass wrote:
We will keep our ASR 9001 until support will expire, but for small Edge nodes.
Well it is hard to trust Cisco currently.
I can recall our CSR 1000V story (permament licenses). CSR 1000V
permament licenses are EoL/EoS. But subscription CSR 1000V are not,
On Wed, Nov 10, 2021 at 8:15 AM Mark Tinka wrote:
> Not really that interested in Cisco anymore.
We will keep our ASR 9001 until support will expire, but for small Edge nodes.
Well it is hard to trust Cisco currently.
I can recall our CSR 1000V story (permament licenses). CSR 1000V
permament li
Randy will be presenting draft-ymbk-sidrops-rov-no-rr during RIPE-83, at
around 1530hrs UTC:
https://datatracker.ietf.org/doc/html/draft-ymbk-sidrops-rov-no-rr-02
Most grateful if you can join, and provide some initial feedback. Thanks.
Mark.
___
cis
On Mon, 22 Nov 2021 at 11:14, Gert Doering wrote:
> Haven't tried, but that would be extremely annoying.
>
> The use case I have in mind is using large communities to control
> per-peer-AS exports, as in:
>
> :0: --> "do not announce to $yourasn"
> :1: --> "prepend to $yourasn"
We need to
Hi,
On Mon, Nov 22, 2021 at 10:02:56AM +0100, Sascha E. Pollok wrote:
> I have actually tried to specify a custom community as a parameter and match
> against that
> in the route-policy's condition but that didn't work with match-any
> ($community). The
> parser wouldn't let me commit that.
>
--- Begin Message ---
Moin Gert,
if (neighbor-asn '12731') then
# Announce this one prefix only, if receiving neighbor is in ASN 12731
done
elseif (neighbor-ip '192.168.1.1') then
# Announce this one prefix only, if receiving neighbor is 192.168.1.1
done
endif
Not
Hi,
On Fri, Nov 19, 2021 at 05:48:56PM +0100, Sascha E. Pollok via cisco-nsp wrote:
> So for example if I have a route-policy on a neighbor-group and would like to
> announce a
> specific prefix only to one of these neighbors, I would like to be able to do
> something like:
>
> if (neighbor-
