Use with caution in live environment as I'm going off of some testing I was
recently doing in my lab and I'm pretty sure I saw this same issue.
Sounds like something I saw with my internet boundary pe's, would add my AS
on routes were learned from internet and send as vpnv4 routes into my
Grettings
I'm setting up this VRF that hosts the full routing table. I have other
peerings or remote PEs that import IX routes through eBGP as well.
The problem resides on something TAC tells me is Juniper specific, which is
to add my own internal ASN to the as-path when using vrf-import to get
No, things changed there as well. Lookup merchant sillicon, and revise this
post every 6 months. have you heard of Barefoot networks? The days of ASICs
from Cisco are gone and we are glad, we tested the P4 DSL (cisco never got
that right with mantel) on Nexus and its wonderful.
The asics you
I've been doing it for years with no ill effects. The only thing I do
is change the backup/master designations in chassis redundancy to
clear the alarm about running on the backup RE:
mx960> show configuration chassis redundancy |display set
set chassis redundancy routing-engine 0 backup
set
Probably also good for us as engineers to gain confidence in our equipment
knowing that it's purring along just fine on the re1 as master, makes us
feel better that both re's work :)
-Aaron
-Original Message-
From: juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of
In my testing I haven't seen an issue with leaving it like this, however,
that is my lab testing I only turned up my dual re, (5) node 100 gig
ring of mx960's about 2 months ago with live traffic, and haven't had to do
any issu upgrades or anything ... so I can only speak from my lab test thus
I almost always leave it running as master on the former backup. It is good to
exercise both REs periodically. I haven't bothered with ISSU in a long time
since I have node/path redundancy.
On Thu, Jun 28, 2018 at 09:12:14AM -0500, Chris Adams wrote:
> It's been a bit since I upgraded JUNOS
It's been a bit since I upgraded JUNOS on a dual-RE router, and I was
refreshing my memory from the documentation. I noticed at the end they
list switching RE mastership back to the first RE (which of course would
cause a second network outage)... is that really needed? Do you do
that, or do you
remote site logs are also shared below:
Jun 28 17:23:20 rpd[1398]: EVENT st0.0 index 79
Jun 28 17:23:20 kmd[1403]: KMD_VPN_DOWN_ALARM_USER: VPN VPN-SOORTY from
123.123.123.123 is down. Local-ip: 50.50.50.50, gateway name: gw-soortybd,
vpn name: VPN-SOORTY, tunnel-id: 131073, local
Gentlemans,
anyone help me on this issue?
On Mon, Jun 25, 2018 at 10:37 PM, sameer mughal
wrote:
> Dear Alexandre,
> Please guide how can I fix this issue? It raise suddenly before this on
> same configuration ipsec tunnel was working fine for more than 5 to 6
> months.
>
> On Mon, Jun 25,
10 matches
Mail list logo
