às 14:03, Cristian Cardoso
escreveu:
>
> I'm configuring two spine switches with Juniper and two leaf switches
> running Nxos 9k to validate EVPN-VXLAN interoperability
> I configured the propagation of the loopbacks via OSPF and then
> OVERLAY, in the spines I configured the cl
I'm configuring two spine switches with Juniper and two leaf switches
running Nxos 9k to validate EVPN-VXLAN interoperability
I configured the propagation of the loopbacks via OSPF and then
OVERLAY, in the spines I configured the cluster-id to function as a
route-reflector of the motes that are lea
e
IRQ problem no longer occurred and in recent system updates there were no
major problems.
Em qui., 12 de nov. de 2020 às 10:20, Cristian Cardoso <
cristian.cardos...@gmail.com> escreveu:
> When there was an exhaustion of IPv4 LPM routes in spine2, I noticed a
> greater increase in
n is EX4650 specific. Do you use the EX4650 platform ?
>
> Thanks
>
> Le 21/03/2023 à 11:38, Cristian Cardoso a écrit :
> > Hi
> >
> > Here I use "from prefix-list", from what I understand from Juniper, when
> > "from destination-prefix-list" is i
Hi
Here I use "from prefix-list", from what I understand from Juniper, when
"from destination-prefix-list" is inserted it is as if it were an IP on the
internal interface of the network and not an IP source IP filter and the
"from prefix-list" is more like source address.
set firewall family inet
blems.
kind regards,
Cristian Cardoso
Em qua., 14 de dez. de 2022 às 12:26, Andrey Kostin
escreveu:
> Cristian Cardoso писал(а) 2021-07-26 21:37:
> > Hi Andrey
> >
> > My idea was to keep only with VRRP to be something simpler for the
> > team to manage.
> >
Hi Johan
I experienced a similar issue in my evpn-vxlan environment on QFX5120-48y
switches. The DDOS alert occurred whenever a large number of VM migrations
occurred simultaneously in my environment, some times there were 20 VM's in
simultaneous migration and the DDOS alarmed.
To solve this, I s
Hi
I had a strange behavior in my environment where I use qfx5120-48y-8c
switches, in spine/leaf topology with EVPN-VXLAN configured.
I transport the VLANs via VXLAN between the servers that are below the
leafs, to my mx routers that are above the spines. To make my life easier,
I use the configu
nd up
happening.
I did several reboots between one MX80 and another and so far there
was no problem with the gateway dying for the network that is in VRRP.
Em sex., 23 de jul. de 2021 às 14:34, Andrey Kostin
escreveu:
>
> Cristian Cardoso via juniper-nsp писал 2021-07-19 14:15:
> > Hi
&
oes the MAC get learnt from the other MX80 properly? Does the EVPN
> > update get generated?
> >
> >
> > On 19/07/2021 13:56, Cristian Cardoso via juniper-nsp wrote:
> > > I had several problems using the virtual gateway via EVPN on the
> > > switches, even the funct
above the VXLAN switches, is just
to let the switches do only the VXLAN and thus remove the functions of
the layer 3 gateway from the qfx.
Using a more "simple" Layer 3 scenario for routing.
Em seg., 19 de jul. de 2021 às 09:41, Nathan Ward
escreveu:
>
> Hi,
>
> > On 20/07/20
I have a scenario here where I use EVPN-VXLAN with qfx5120 switches
and until then I was using the gateways on the switches, but as the
switch does not have the possibility to use any kind of firewall on
the irb interfaces, I had the idea to migrate the networks to two
routers MX80.
But I caught a
s network related IRQs, it
> should be seen during a packet capture.
>
> On Tue, Nov 10, 2020 at 4:40 PM Cristian Cardoso
> wrote:
>>
>> I running 19.1R2.8 version on Junos.
>> Today I was in contact with Juniper support about a route depletion
>> problem and it
CPU utilization ?
>
>
> On Tue, Nov 10, 2020 at 9:07 PM Cristian Cardoso
> wrote:
>>
>> > show configuration protocols evpn
>> vni-options {
>> vni 810 {
>> vrf-target target:888:888;
>> }
>> vni 815 {
>> vrf
address 10.19.11.253/22 {
preferred;
virtual-gateway-address 10.19.8.1;
}
}
Em ter., 10 de nov. de 2020 às 15:16, Nitzan Tzelniker
escreveu:
>
> Can you show your irb and protocols evpn configuration please
>
> Nitzan
>
> On Tue, Nov 10, 2020 at 3:26
Does anyone use EVPN-VXLAN in the Centrally-Routed and Bridging topology?
I have two spine switches and two leaf switches, when I use the
virtual-gateway in active / active mode in the spines, the servers
connected only in leaf1 have a large increase in IRQ's, generating
higher CPU consumption in t
Hello everyone
I am using QFX switches with EVPN-VXLAN and IRB interfaces, when
trying to monitor the IRB interfaces, both via cacti and via zabbix,
only inbound traffic is displayed on the IRB interfaces. Similar
behavior also occurs on interfaces to and that connect from spines to
leafs, where it
routing instances.
> Loopback filters per routing instance (such as lo0.100, lo0.103, lo0.105) are
> not supported and may cause unpredictable behavior. We recommend that you
> apply the loopback filter to the lo0.0 (master routing instance) only.
>
> Regards
> Roger
>
> On
I forgot to mention, that I'm using the QFX5120 equipment in this scenario
Em qui., 17 de set. de 2020 às 10:19, Cristian Cardoso
escreveu:
>
> Hi
> I am trying to create a firewall filter to protect the routing engine
> only in a routing-instance, and with that I apply the fir
Hi
I am trying to create a firewall filter to protect the routing engine
only in a routing-instance, and with that I apply the firewall filter
in the lo0.1 interface.
I noticed that when applying the filter that in theory should only
apply to the routing-instance, it also ends up dropping packets t
tocols evpn
> Do you have ?
> protocols evpn default-gateway no-gateway-community
>
> Nitzan
>
> On Fri, Sep 11, 2020 at 5:52 PM Cristian Cardoso
> wrote:
>>
>> Hi
>> My 4 switches are model QFX-5120 48Y-8C and are in version 18.4R3-S4.2.
>>
>
vlan-id 4018;
vxlan {
vni 4018;
}
}
Em sex., 11 de set. de 2020 às 11:30, Roger Wiklund
escreveu:
>
> Hi
>
> Can I have the configs on spine and leafs? This is not expected behaviour.
> What version are you running?
>
> Regards
> Roger
>
> On Fri,
Hello
Did anyone on the list have the EVPN-VXLAN scenario active with
Centrally-Routed Bridging?
Here in my scenario, I have two spines and 2 leafs and I am testing
this form of configuration, where the IRB interfaces work with the
virtual gateway function, for access redundancy, but I realized tha
23 matches
Mail list logo
