RARE user and assistance email list

[mc36 <>]

i saw no reply to this in the lists so jumping in...

we had our weekly call this friday and simon said that we cannot have fee 
waiver,
instead the girl at eantc suggested us to ask for a juniper sticker and be 
get added
for a much cheaper price as juniper's 10th box on the venue... what's your 
opinion? :)

thanks,
cs


On 2/16/23 11:46, Krzysztof Szarkowicz wrote:
> Simon,
>
> Did you contacted Carsten from EANTC?
>
> Thanks,
>
> --
>
> Krzysztof Grzegorz Szarkowicz, JAWS PLM, Solutions Architect | Phone: +49 89 
> 203 012 127
>
> Please consider my current time zone, when calling: CET (UTC+01:00)
>
> https://easylink.juniper.net/slicing
>
> *From: *mc36 <>
> *Date: *Wednesday, 2023-02-15:We at 18:36
> *To: *Krzysztof Szarkowicz <>, Kaliraj Vairavakkalai <>,  <>, Simon Leinen <>, 
> Ivana Golub <>, Fr  d  ric LOUI <>, Rafal Szmidt <>, Anton Elita <>
> *Cc: *Natrajan Venkataraman <>, Reshma Das <>, 
>  <>
> *Subject: *Re: [RARE-users] test topology for -ct interop ---- ex: EANTC - 
> BGP CT - Juniper-FreeRTR
>
> [External Email. Be cautious of content]
>
>
> hi,
>
> sorry for the long delay, i needed a new knob plus i hit 1 bug, but finally 
> we're here....
> the fixed builds should be out at freertr.org in 1-2 hours as ci-cd finishes 
> everything...
> at the bottom of the webpage, it now tells you 23.2.14, it'll be bumped to 
> 23.2.15 when it's done...
> until that, you cannot run the topology from the attached .tar as it needs 
> all the stuff from today...
>
> howto run it:
>
> tar xvf zzz.tar
> ./topo.sh                           !optionally capture r3 eth3 capture r3 
> eth2
> telnet localhost 20001 !to access r1
> telnet localhost 20002 !to access r2
> telnet localhost 20003 !to access r3
> ..
> telnet localhost 20007 !to access r7
>
> r1, r2, r6, r7 are just cpe routers, plain endpoints without routing 
> protocols enabled yet...
>
> if you ping flood from r2->r6 then it uses vlan 111 in between r3-r4...
> if you ping flood from r1->r7 then it uses vlan 222 in between r3-r4...
> (it's just my shame that i cannot have 2 rsvp-te over a single link, or at 
> least
> never tried, that's why the vlans, maybe it could work with a single link 
> here... :)
>
> if you "display interface traffic" on r3 or r4 while performing the ping 
> flood, you'll see that it works...
>
> to do the flood, use the topo.tst's last two pings,
> one is for red, the other is for blue,
> simply add "size 1111 repeat 11111111" :)
>
> also check out how hackish the import became on r3's and r4's rpl ibgp-in... 
> ugly as hell! :)
>
> any comment welcomed!
> thanks,
> cs
>
>
>
>
> On 2/15/23 10:24, mc36 wrote:
>  > my bad, noted! :)
>  >
>  > On 2/15/23 10:21, Krzysztof Szarkowicz wrote:
>  >> Sorry, wrong Anton(i)                 .
>  >>
>  >> +Anton,
>  >>
>  >> BCC: Antoni
>  >>
>  >> --
>  >>
>  >> Krzysztof Grzegorz Szarkowicz, JAWS PLM, Solutions Architect | Phone: +49 
> 89 203 012 127
>  >>
>  >> Please consider my current time zone, when calling: CET (UTC+01:00)
>  >>
>  >> https://easylink.juniper.net/slicing 
> <https://easylink.juniper.net/slicing>
>  >>
>  >> *From: *mc36 <>
>  >> *Date: *Wednesday, 2023-02-15:We at 10:19
>  >> *To: *Kaliraj Vairavakkalai <>,  
> <>, Krzysztof Szarkowicz <>, Simon Leinen 
> <>,
>  >> Ivana Golub <>, Fr     d     ric LOUI 
> <>, Rafal Szmidt <>, Antoni Przygienda 
> <>
>  >> *Cc: *Natrajan Venkataraman <>, Reshma Das 
> <>,  <>
>  >> *Subject: *Re: test topology for -ct interop ---- ex: EANTC - BGP CT - 
> Juniper-FreeRTR
>  >>
>  >> [External Email. Be cautious of content]
>  >>
>  >>
>  >> +Rafal, +Anton
>  >>
>  >> please note we're on-list here, archive to see what i'm labbing right now:
>  >> 
> https://urldefense.com/v3/__https://lists.geant.org/sympa/arc/rare-users/2023-02/msg00068.html__;!!NEt6yMaO-gk!DpsKIctYFQ6G_Li0nUoU3Qppgy6gHxGcx2v4nPVlyZqCjKMhWJR4Zq2zzlk5-lWRt5i8GB8ASP09$ <https://urldefense.com/v3/__https:/lists.geant.org/sympa/arc/rare-users/2023-02/msg00068.html__;!!NEt6yMaO-gk!DpsKIctYFQ6G_Li0nUoU3Qppgy6gHxGcx2v4nPVlyZqCjKMhWJR4Zq2zzlk5-lWRt5i8GB8ASP09$> <https://urldefense.com/v3/__https:/lists.geant.org/sympa/arc/rare-users/2023-02/msg00068.html__;!!NEt6yMaO-gk!DpsKIctYFQ6G_Li0nUoU3Qppgy6gHxGcx2v4nPVlyZqCjKMhWJR4Zq2zzlk5-lWRt5i8GB8ASP09$ <https://urldefense.com/v3/__https:/lists.geant.org/sympa/arc/rare-users/2023-02/msg00068.html__;!!NEt6yMaO-gk!DpsKIctYFQ6G_Li0nUoU3Qppgy6gHxGcx2v4nPVlyZqCjKMhWJR4Zq2zzlk5-lWRt5i8GB8ASP09$>>
>  >>
>  >> i'll get back to you all when i have something that works and we can 
> discuss further...
>  >>
>  >> tbh never tested such a complex topology beforehand, just piece-by-piece 
> integration tests on the topic...
>  >>
>  >> br,
>  >> cs
>  >>
>  >>
>  >> On 2/15/23 08:40, Kaliraj Vairavakkalai wrote:
>  >>     > Sure, Thanks :)
>  >>     >
>  >>     > *From: *mc36 <>
>  >>     > *Date: *Tuesday, February 14, 2023 at 11:31 PM
>  >>     > *To: *Kaliraj Vairavakkalai <>,  
> <>, Krzysztof Szarkowicz <>, Simon Leinen 
> <>,
>  >>     > Ivana Golub <>, Fr         d         ric LOUI 
> <>
>  >>     > *Cc: *Natrajan Venkataraman <>, Reshma Das 
> <>,  <>
>  >>     > *Subject: *Re: [freertr] [RARE-users] EANTC - BGP CT - 
> Juniper-FreeRTR
>  >>     >
>  >>     > [External Email. Be cautious of content]
>  >>     >
>  >>     >
>  >>     > hi,
>  >>     >
>  >>     > On 2/15/23 08:28, Kaliraj Vairavakkalai wrote:
>  >>     >>>so r3-r4 will be in isis, vpnv4 ibgp, and have 2 rsvp-te for the 2 
> colors,
>  >>     >>>i'll place the tunnel-te to the two colored vrfs
>  >>     >>
>  >>     >> Ok. Will the vpnv4 ibgp routes put traffic on the rsvp-te tunnels 
> in the colored-vrfs?
>  >>     >>
>  >>     >> What is the release we should use, to play around. Can you point 
> us to the link?
>  >>     >>
>  >>     >
>  >>     > it should be out, and tested piece-by-piece, but first let me craft
>  >>     > the whole topology we're talking here with all the configs in place,
>  >>     > first, for your reference, second, to see if we're hitting any 
> bugs...
>  >>     >
>  >>     > i'll keep you posted... :)
>  >>     >
>  >>     > br,
>  >>     > cs
>  >>     >
>  >>     >
>  >>     > Juniper Business Use Only
>  >>     >
>  >>
>  >>
>  >> Juniper Business Use Only
>  >>
>
>
> Juniper Business Use Only