Re: [j-nsp] QFX5110 / EVPN-VXLAN with IPv6 underlay

[Christian Scholz via juniper-nsp]

Also might be worth mentioning that the Router-ID - although it might look like 
one and you would usually use one you already have on your loopback - is 
technically not an IP(v4)-Address. 


See: 
https://www.juniper.net/documentation/us/en/software/junos/static-routing/topics/ref/statement/router-id-edit-routing-options.html

Even if you run only OSPF3 or IPv6 BGP peering in a routing instance, a 32-bit 
router-id must be configured in the instance. This is because IPv6 routing 
protocols use the router-id for handshaking. The router ID must be configured 
as a 4 octet (32 bit) unsigned non-zero integer value. 
It's often convenient to use an IPv4 address as the router ID. However, a valid 
IPv4 address is not required. The RID does not have to be a routable IPv4 
address. You can configure any 32-bit value that is unique within the routing 
domain. If you do not configure the router-id in an IPv6 OSPF or BGP routing 
instance the IPv6 protocols will use an invalid value for the router ID 
(0.0.0.0) and the adjacency and connections will fail

CHS



> Am 28.11.2023 um 16:14 schrieb Roger Wiklund via juniper-nsp 
> :
> 
> For the QFX5110 specifically, MAC-VRF is supported:
> https://apps.juniper.net/feature-explorer/feature-info.html?fKey=9788&fn=MAC+VRF+with+EVPN-VXLAN
> 
> But IPv6 underlay is not:
> https://apps.juniper.net/feature-explorer/feature-info.html?fKey=11165&fn=EVPN-VXLAN+fabric+with+an+IPv6+underlay
> 
> So maybe it's an ASIC limitation as QFX5110 is using Trident 2+ and
> QFX5120/EX4400 is using Trident 3.
> 
> Regards
> Roger
> 
> 
> 
>> On Tue, Nov 28, 2023 at 3:48 PM Roger Wiklund 
>> wrote:
>> 
>> Hey
>> 
>> You're interpreting the default switch limitation incorrectly.
>> 
>> It doesn't mean the QFX5120 can't support MAC-VRFs, it means even if you
>> implement MAC-VRFs you still only have a single switch domain and can't
>> have overlapping VLANs in the different MAC-VRFs. (MX does not have this
>> limitation. It supports 32k VLANs)
>> 
>> IPv6 underlay is supported on QFX5120 in MAC-VRF from Junos 21.2R2:
>> Explore Features by Product | Juniper Networks Pathfinder Feature Explorer
>> 
>> 
>> You can configure an EVPN-VXLAN fabric with an IPv6 underlay. You can use
>> this feature only with MAC-VRF routing instances (all service types). You
>> must configure either an IPv4 or an IPv6 underlay across the EVPN instances
>> in the fabric; you can’t mix IPv4 and IPv6 underlays in the same fabric.
>> To enable this feature, include these steps when you configure the EVPN
>> underlay:
>> • Configure the underlay VXLAN tunnel endpoint (VTEP) source interface as
>> an IPv6 address:
>> • Even though the underlay uses the IPv6 address family, for BGP
>> handshaking to work in the underlay, you must configure the router ID in
>> the routing instance with an IPv4 address:
>> • Enable the Broadcom VXLAN flexible flow feature, release where the
>> feature is not enabled by default:
>> We support the following EVPN-VXLAN features with an IPv6 underlay:
>> • EVPN Type 1, Type 2, Type 3, Type 4, and Type 5 routes(excluding EX9200
>> for type 5).
>> • Shared VTEP tunnels (required with MAC-VRF instances).
>> • All-active multihoming, including Ethernet segment ID (ESI)
>> auto-generation and preferencebased DF (DF) election.
>> • EVPN core isolation.
>> • Bridged overlays.
>> • Layer 3 gateway functions in ERB and CRB overlays with IPv4 or IPv6
>> traffic.
>> • Underlay and overlay load balancing.
>> • Layer 3 protocols over IRB interfaces—BFD, BGP, OSPF.
>> • Data center interconnect (DCI)—over-the-top (OTT) full mesh only.
>> • EVPN proxy ARP and ARP suppression, and proxy NDP and NDP suppression.
>> 
>> Regards
>> Roger
>> 
>> On Mon, Nov 27, 2023 at 11:31 AM Denis Fondras via juniper-nsp <
>> juniper-nsp@puck.nether.net> wrote:
>> 
>>> Hello,
>>> 
>>> Thank you very much everyone for the help.
>>> 
>>> It seems that `netraven` nailed it.
>>> I missed the part where QFX5110 could not support multiple forwarding
>>> instances.
>>> 
>>> I will have to go back to the legacy protocol then :/
>>> Replacing IPv6 addresses with IPv4 addresses, keeping the same config,
>>> worked on
>>> first try.
>>> 
>>> Thank you again !
>>> Denis
>>> 
>>> 
>>> Le Mon, Nov 27, 2023 at 10:52:52AM +0100, netravnen+nspl...@gmail.com a
>>> écrit :
 Dennis,
 
 On Sat, 25 Nov 2023 at 15:26, Denis Fondras via juniper-nsp
  wrote:
> Can you give a clue ? I haven't found any information on wether it
>>> could work on
> QFX5110.
 
 Looking at the two pages below.
 1. The QFX5120 (assuming this also applies to the QFX5120-32C model)
 *only* supports the default-switch forwarding instance.
 2. And IPv6 underlays seem to be *exactly not* supported for the
 default-switch forwarding instance.
 
 If I 

Re: [j-nsp] How to pick JUNOS Version

[Christian Scholz via juniper-nsp]

--- Begin Message ---
If you face issues, you have JTAC, ATAC, and Engineering - and also a local SE.
I would never wait and "hope" that a fix will be out there because it has been 
reported, "by someone else."
Observe, Pinpoint, Report and if needed Escalate - works very good with Juniper 
and they help you; unlike other vendors who "build bridges" and tell you to 
deploy your software while Saturn is in line with Mars and while offering a 
goat as a token of appreciation at the same time 😉
If there is a nasty issue that is not fixed in any release, Engineering 
provides "Special Customer Releases" to have a fix for your particular 
environment and issue to help you.
Therefore if you report the Bug, you might not have a fix tomorrow, but in the 
next 2-3 months.
And if it takes longer, there's an "escalate this case" button that works very 
well - I never had to wait longer than six weeks for a particular fix after it 
had been confirmed. Your local SE can also assist you if you have trouble.


Back to the topic:
If you start fresh, follow the "JTAC versions to consider" (as stated earlier, 
it's no longer called recommended for various reasons) and ask your local SE - 
that's the "official" way. 
In 9/10 Cases, this is an excellent version to start with if you have no idea 
where to start at all.
If you need a specific feature that's not yet in the "version to consider," or 
there's a bug in this version affecting you, your local SE can tell you what to 
do and what version to try.
This way, you get a working version or the correct pointers on what to do to 
get the right version.

Tom's approach is also an excellent idea - the important part is that you test 
everything for your environment yourself before deploying it to prod. Most of 
the time, "shit hits the fan" because folks don't check appropriately for 
themselves or have no testing environment at all because "it's expensive."
In my personal opinion, it's not the vendor's responsibility to test every 
customer topology in existence with every tiny feature.
It's your job at the end of the day to make sure that you deploy code that 
works. 
The vendor can assist you as best as possible, but it's simply not possible for 
them to test EVERY scenario out there.
Again: Observe, Pinpoint, Report.

Yes - there are often multiple bugs involved, and yes it can be a "Minesweeper 
Game" to find the one that has "everything" fixed (however, such thing does not 
exist per definition because humans are not perfect) - but it's not as 
complicated as with other vendors with 27.000 Releases and Sub-Releases out 
there that have to be "qualified" in order to get support 😉

Just my 2ct

-- Christian






-Ursprüngliche Nachricht-
Von: juniper-nsp  Im Auftrag von Alexandre 
Guimaraes
Gesendet: Donnerstag, 20. August 2020 15:34
An: Tom Beecher ; Colton Conor 
Cc: Juniper List 
Betreff: Re: [j-nsp] How to pick JUNOS Version

The best answer ever!

Go to Vegas, in a Cassino, play some roulette.  Wait for a number between 10 
and 20, if black, normal Junos, if red, SR Junos...  if you lose all money 
before get a code similar a release, follow Tom Beecher schemas.

IT'S A LOTTERY to pick a junos release. 

One of my case
I have deployed some QFX5120 32C and 48Y units a year ago, exactly Aug/2019, 
until today, those units are offline and waiting a code that’s fix 
RSVP/ISIS/MPLS signalization until there, wasted money, etc



Em 19/08/2020 13:32, "juniper-nsp em nome de Tom Beecher" 
 escreveu:

Start with the highest code version supported on the hardware that has all
the features you need.
Subtract 2 from the major revision number.
Pick a .3 version of that major revision.
Work towards current from there depending on test results, security needs,
etc.

On Wed, Aug 19, 2020 at 10:47 AM Colton Conor 

wrote:

> How do you plan which JUNOS version to deploy on your network? Do you 
stick
> to the KB21476 - JTAC Recommended Junos Software Versions or go a 
different
> route? Some of the JTAC recommended code seems to be very dated, but that
> is probably by design for stability.
>
> 
https://urldefense.proofpoint.com/v2/url?u=https-3A__kb.juniper.net_InfoCenter_index-3Fpage-3Dcontent-26id-3DKB21476-26actp-3DMETADATA&d=DwICAg&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=d3qAF5t8mugacLDeGpoAguKDWyMVANad_HfrWBCDH1s&m=a6BNdZOtIAqYpPvwVFnIF4E-D-PQw3QGn-NmT5hFQag&s=CQxemDO4grDS8J_BXAGPC3akSwvKhy2DBPt6JlKN3nI&e=
>
> Just wondering if JUNOS will ever go to a unified code model like Arista
> does? The amount of PR's and bug issues in JUNOS seems overwhelming. Is
> this standard across vendors? I am impressed that Juni

Re: [j-nsp] Juniper support offline?

[Christian Scholz]

Looks like a Maintenance Window - a bit early here but this was planned.



Best Regards
 
Christian Scholz





-Ursprüngliche Nachricht-
Von: juniper-nsp  Im Auftrag von Nathan 
Ward
Gesendet: Donnerstag, 13. Februar 2020 22:42
An: Juniper NSP 
Betreff: Re: [j-nsp] Juniper support offline?

And again.. this time the whole my.juniper.net <http://my.juniper.net/> is 
down, not just the login system. Downloads are also not working, and 
www.juniper.net <http://www.juniper.net/> is really slow to load.. Weirdly, 
support.juniper.net <http://support.juniper.net/> seems to work.

This is not wildly confidence inspiring, eh?

Don’t get me wrong, this is one of those “I’m complaining because I like your 
gear and it pains me to see you mess up so bad” situations.

> On 26/01/2020, at 8:16 PM, Nathan Ward  wrote:
> 
> Hi,
> 
> Looks to me and colleagues of mine like Juniper support is offline.
> 
> Last night, I was able to log in but trying to download an image got to some 
> stage of the redirect process and hung, then a please try again later 
> message. It persisted for the next few hours of me trying every now and then.
> 
> Today, I can’t log in at all - Invalid user/password.
> Password reset process works, but, still doesn’t let me in. Different 
> browsers, cleared cache, all the usual “is it on at the wall sir” debugging.
> 
> Hearing the same story for others.
> 
> I’ve called both the NZ 00800 (international 800) and the US +1888 number. 
> The former says “call cannot be completed”. The US number says “high volume 
> of calls please leave a message”.
> 
> We’re in New Zealand - unsure if that’s relevant.
> 
> 
> Are others having these same issues?
> 
> Any insight in to what’s going on? 
> It’s a long weekend here, so the local sales/SE/etc. folks I usually deal 
> with are likely not anywhere near their phones.
> 
> --
> Nathan Ward
> 

___
juniper-nsp mailing list juniper-nsp@puck.nether.net 
https://puck.nether.net/mailman/listinfo/juniper-nsp

___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] Juniper support offline?

[Christian Scholz]

Everything works here again - without resetting.
Looks like it’s recovering



Von meinem iPhone gesendet

> Am 26.01.2020 um 17:08 schrieb Ross Halliday 
> :
> 
> Seems to be back albeit a bit rocky - I could not get in with my previous 
> password and had to reset. SRM and Downloads appear to be functioning
> 
> Ross
> 
> 
> -Original Message-
> From: juniper-nsp  On Behalf Of Thomas 
> Scott
> Sent: January 26, 2020 6:14 AM
> To: Nathan Ward 
> Cc: Juniper NSP 
> Subject: Re: [j-nsp] Juniper support offline?
> 
> Just got off the phone with JTAC and was informed the website was down for
> "maintenance". We managed to open a case last night, but were unable to
> this morning... I'm hoping that the "issue" doesn't last too long..
> 
> Phone number I called was 1-888-314-5822.
> 
> - Thomas Scott | mr.thomas.sc...@gmail.com  
> 
> 
 On Sun, Jan 26, 2020 at 5:28 AM Nathan Ward  wrote:
>> Hi,
>> The published number on the Juniper website - 0080025864737 doesn’t work,
>> and the +1888 US number went to Juniper, but to voicemail.
>> I’ve called the number Liam has posted here (same as above but with +
>> rather than 00), which worked - the agent had told me that there was
>> maintenance yesterday and now there is no way to get copies of images
>> apparently, even JTAC.
>> I was told that there is no ETA for login being restored. All they can do
>> is open a case so I get notified if and when it’s fixed. (Yeah, the agent
>> really said “if and when”).
>> Prsearch disappeared what, Jan 2019.. this year will it be case management
>> and download access we lose for almost a year?
>> On the off chance someone has them and is able to share, I need packages
>> for 18.2R3-S1 for MX204 (so, VMHost), and 18.4R2-S2 for QFX5120.
>> Those are the JTAC recommended versions, so I imagine they’ll be knocking
>> about on plenty of hard drives..
>> Luckily, checksums are still visible on the public site :-)
 On 26/01/2020, at 8:22 PM, Liam Farr  wrote:
>>> I just messaged some local at Juniper NZ and they advised that
>> +80025864737 is working for support.
>>> Seems to work from my 2D mobile here too.
>>> Cheers
>>> Liam
>>> On Sun, 26 Jan 2020 at 8:16 PM, Nathan Ward > > wrote:
>>> Hi,
>>> Looks to me and colleagues of mine like Juniper support is offline.
>>> Last night, I was able to log in but trying to download an image got to
>> some stage of the redirect process and hung, then a please try again later
>> message. It persisted for the next few hours of me trying every now and
>> then.
>>> Today, I can’t log in at all - Invalid user/password.
>>> Password reset process works, but, still doesn’t let me in. Different
>> browsers, cleared cache, all the usual “is it on at the wall sir” debugging.
>>> Hearing the same story for others.
>>> I’ve called both the NZ 00800 (international 800) and the US +1888
>> number. The former says “call cannot be completed”. The US number says
>> “high volume of calls please leave a message”.
>>> We’re in New Zealand - unsure if that’s relevant.
>>> Are others having these same issues?
>>> Any insight in to what’s going on?
>>> It’s a long weekend here, so the local sales/SE/etc. folks I usually
>> deal with are likely not anywhere near their phones.
>>> --
>>> Nathan Ward
>>> ___
>>> juniper-nsp mailing list juniper-nsp@puck.nether.net > juniper-nsp@puck.nether.net>
>>> https://puck.nether.net/mailman/listinfo/juniper-nsp <
>> https://puck.nether.net/mailman/listinfo/juniper-nsp>
>>> --
>>> Kind Regards
>>> Liam Farr
>>> Maxum Data
>>> +64-9-950-5302
>> ___
>> juniper-nsp mailing list juniper-nsp@puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
> ___
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
> ___
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp

___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] EX4300-AFO to AFI

[Christian Scholz]

Make sure to involve JTAC because if you have to RMA this and the Database has 
not been updated you might get the wrong switch back. 

BR
Christian



Von meinem iPhone gesendet

> Am 12.12.2019 um 17:48 schrieb Dovid Bender :
> 
> Just swapping them out seemed to do the trick for us.
> 
>>> On Thu, Dec 12, 2019 at 11:19 AM Colin  wrote:
>> Hi
>> Is it possible, or has anybody successfully tried, to convert an
>> EX4300-AFO to an AFI by just replacing the fan and power supply which
>> are both FRU items  (EX4300-FAN-AFI, JPSU-350-AC-AFI-A) or would changes
>> need to be made to the firmware?  Thanks.
>> Colin McIntyre
>> ___
>> juniper-nsp mailing list juniper-nsp@puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
> ___
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp

___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] DNS Flag Day

[Christian Scholz]

What they told you sounds like bullshit to me. From 10.2 on there are no 
special settings required. Maybe they don’t know how to do it?

So I guess they are just very lazy or don’t know better and blame the 
firewall... I pray for you that they don’t run Code below 10.2...

https://kb.juniper.net/InfoCenter/index?page=content&id=KB23569&cat=SRX_5600_1&actp=LIST


CHS








Von meinem iPhone gesendet

Am 25.01.2019 um 12:53 schrieb sth...@nethelp.no:

>> When doing some investigation for the upcoming DNS Flag Day 
>> (https://dnsflagday.net: February 1st 2019) I got some bad news from one of 
>> the service providers: they use Juniper SRX firewalls, and claim that they 
>> can't properly support EDNS because of a bug in their SRX firewalls. This 
>> seems outrageous to me. Is this just because they haven't upgraded their 
>> JunOS for years, they're running ancient DNS server software, or is there 
>> really a problem?
> 
> See
> 
> https://mailman.nanog.org/pipermail/nanog/2019-January/099180.html
> 
> "Juniper and Checkpoint have newer code that doesn't do this."
> 
> Steinar Haug, Nethelp consulting, sth...@nethelp.no
> ___
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] eve-ng - lab environment

[Christian Scholz]

Welcome to the world of EVE.
I prepped my JNCIE purely with EVE ;)




> Am 16.07.2018 um 14:16 schrieb Aaron Gould :
> 
> Oh my gosh, Eve-ng is awesome!  If you didn't know about it, you gotta try
> it.  It's so cool in its ability to run vSRX and vMX so far in my testing.
> In only a short couple days I've been able to test the following.
> 
> - mpls martini l2circuits using ldp
> - mpls vpls bgp ad/ldp sig (rfc4762)
> - mpls vpls bgp ad/bgp sig (rfc4761)
> - mpls evpn (my first look ever!)
> - mplsogre (my first look ever in junos!)
> 
> I wanted to see it run L2 bridging technologies since I had so much
> unsuccess in my previous GNS3 attempts over the last few years (I may have
> never set up the virtual l2 fwd'ing plane in gns3 like I should have)
> 
> incase you want to take a look.
> 
> http://eve-ng.com 
> 
> 
> 
> I had to take a moment and share about this.  It's so clean and elegant in
> how it runs and works.
> 
> 
> 
> -Aaron 
> 
> ___
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp

___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] juniper login down ?

[Christian Scholz]

Yes - they had planned maintenance today...




 Ursprüngliche Nachricht Von: Aaron Gould  
Datum: 09.02.18  00:32  (GMT+01:00) An: juniper-nsp@puck.nether.net Betreff: 
[j-nsp] juniper login down ? 
iam-sso.juniper.net - is this down ?

 

- Aaron

___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] What is your experience with the EX2200

[Christian Scholz]

Unfortunately no pattern yet - all areas have problems - but if I have to
name one that has very "hard" Problems it will be dot1x...
Thing is, that we installed a lot of them in production, they were just fine
but after a while we noticed, that whenever we changed the config (even
changing a single VLAN) the Device crashes - no pattern - no Clue. 
Core-Dump does not tell anything good.
JTAC is on this but didn't come up with a Solution yet - we replaced all of
them with the good old EX2200 and now the Production Network runs fine again
(Version 12.3R12-S6 I think).
We will test 17.4 or maybe even better 18.1 or 18.2 - the EX2300 needs to
become more mature before we trust it again.

By the way:
My earlier Mail was not meant to "bully" anyone - it was just my Opinion. I
love Juniper but the Software 15.1 is only a Joke - but enough said ;)



-Ursprüngliche Nachricht-
Von: Dan White [mailto:dwh...@olp.net] 
Gesendet: Montag, 11. Dezember 2017 16:53
An: Christian Scholz 
Cc: juniper-nsp@puck.nether.net
Betreff: Re: What is your experience with the EX2200

Thank you all for your feedback. This is invaluable advice as we don't have
much operational experience with Juniper switches to work with.

Christian,

Is there a common theme among the issues you've encountered? Are they
aligned with a particularly feature set?

On 12/09/17 20:29 +0100, Christian Scholz wrote:
>I would only buy the EX2300 if somebody points a Gun in my Face -
seriously!
>Anyone recommending a Device that purely relies on 15.1 Software does 
>not even closely know what he is talking about...
>
>The 2300 is a Joke so far - We have 7 PR's open and weekly Core-Dumps...
>Stick with the EX2200 since the EX2200 is not EOL and the EX2300 is 
>unusable until a fine Release (17.3 onwards) is available, fixing all 
>the critical things.
>15.1 is the new Windows Vista - unstable, unreliable and just a big 
>joke - never ever ever ever use a 15.X in Production until you want to 
>watch the World burn...
>
>Just my 2 cents...

--
Dan White
BTC Broadband
Network Admin Lead
Ph  918.366.0248 (direct)   main: (918)366-8000
Fax 918.366.6610email: dwh...@olp.net
http://www.btcbroadband.com


___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] What is your experience with the EX2200

[Christian Scholz]

I would only buy the EX2300 if somebody points a Gun in my Face - seriously!
Anyone recommending a Device that purely relies on 15.1 Software does not
even closely know what he is talking about...

The 2300 is a Joke so far - We have 7 PR's open and weekly Core-Dumps...
Stick with the EX2200 since the EX2200 is not EOL and the EX2300 is unusable
until a fine Release (17.3 onwards) is available, fixing all the critical
things.
15.1 is the new Windows Vista - unstable, unreliable and just a big joke -
never ever ever ever use a 15.X in Production until you want to watch the
World burn...

Just my 2 cents...


___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] It is about cisco command

[Christian Scholz]

There is no such way to "test before apply " in Cisco. Thats one reason to 
choose Juniper ;)
You could Create a Lab-Environment to test such things or test this virtually 
with Cisco VIRL. Besides that there is no way because as you wrote - Cisco will 
take everything and fires it live...
RegardsChris


 Ursprüngliche Nachricht Von: Brijesh Patel 
 Datum: 21.03.17  22:13  (GMT+01:00) An: Saku Ytti 
 Cc: juniper-nsp@puck.nether.net Betreff: Re: [j-nsp] It is about 
cisco command 
Hi Saku,

Thanks for your response.

In juniper* test *command will test before apply to neighbour

Where in cisco , once you implement command go into nvram so bit not give
answer.

Regards,

Brijesh Patel


On Tue, Mar 21, 2017 at 8:00 PM, Saku Ytti  wrote:

> Hey,
>
> > *Juniper>test policy CUSTOMER-BGP-ABC-Consultancy-V4 192.168.x.y/24 *
> >
> > *Is there any command in cisco to test roue-map and prefix-list. *
>
> Pretty sure best you get is 'show ip bgp route-map XYZ'
>
> --
>   ++ytti
>
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp