Rare project developers

[mc36 <>]

there are better things than a full restart....

"write" followed by a "reload warm" is way more faster and you dont have to 
deal with the 3+ years old systemd bugs....

"write erase" also should work, then re-pasting the good parts...

just one thing, don't trust linux in the rare builds, they're way too old.... 
:(

thanks,

cs

On 3/21/23 02:06, Kaliraj Vairavakkalai wrote:
> Frederic, we did systemct stop/start of freertr. And it helped to some extent.
>
> Current status is:
>
>   * Cleanup up ISIS config from two VRFs. It is only present in eantc-bgp-ct.
>   * and ISIS is stable now. Best effort ping over LU is passing.
>   * RSVP-TE LSPs between PE1->ASBR1 are no-cspf, strict hop EROs.
>   * RSVP-TE from ASBR1->PE1 using eantc-bgp-ct as signaling instance, but 
> using eantc-bgp-ct-gold/bronze for forwarding.
>   * Only problem is: *CT advertised labels are not installed to P4 forwarding*
>
> the following labels advertised ASBR1->ASBR2 are not getting installed to P4.
>
> core#show mpls forwarding | include 661923
>
> 661923 eantc-bgp-ct-bronze:4tunnel3100.1.2.3630
>
> core#show mpls forwarding | include 164692
>
> 164692 eantc-bgp-ct-gold:4tunnel2100.1.1.3630
>
> core#show p4lang p4 done-mpls | include 661923
>
> core#show p4lang p4 done-mpls | include 164692
>
> core#
>
> Can you or Csaba help with debugging and fixing this?
>
> Fyi: Latest free-rtr config is saved at: /rtr-sw-20230320-1800-PDT.txt, also 
> attached to this mail.
>
> And the pings to verify the streams are (from PE2):
>
>      Best-effort: *root@Juniper-34-MX204_5> ping 100.2.0.36 source 100.2.0.34 rapid count 2 *   
>
>    Gold SLA:***root@Juniper-34-MX204_5> ping 100.3.0.36 source 100.3.0.34 rapid count 2 *   
>
> **Bronze SLA:***root@Juniper-34-MX204_5> ping 100.5.0.36 source 100.5.0.34 rapid count 2***   
>
> Ping us if you need anything while debugging this.
>
> Thanks
>
> Kaliraj
>
> *From: *Natrajan Venkataraman <>
> *Date: *Monday, March 20, 2023 at 2:32 PM
> *To: *Fr  d  ric LOUI <>
> *Cc: *Kaliraj Vairavakkalai <>, Anton Elita <>, Reshma Das <>, Simon Leinen <>, Krzysztof Szarkowicz 
> <>, Alexander Gall <>
> *Subject: *Re: RARE/freeRtr status @EANTC
>
> I think we hit it everytime.
>
> *From: *Fr  d  ric LOUI <>
> *Date: *Monday, March 20, 2023 at 2:25 PM
> *To: *Natrajan Venkataraman <>
> *Cc: *Kaliraj Vairavakkalai <>, Anton Elita <>, Reshma Das <>, Simon Leinen <>, Krzysztof Szarkowicz 
> <>, Alexander Gall <>
> *Subject: *Re: RARE/freeRtr status @EANTC
>
> [External Email. Be cautious of content]
>
>
> Does this happen everytime you issue    clear p4lang p4    ?
> Or is it an isolated case ?
>
> In that case I suggest first to issue restart freertr via systemd.
>
> > Le 20 mars 2023    22:20, Natrajan Venkataraman <> a   crit :
> >
> > Hi Frederic,
> >
> > P4 stopped working after we did a    clear p4lang p4   . Need your help to 
> > fix up the dataplane.
> >
> > Thanks,
> > -Nats-
> >
> > From: Frederic LOUI <>
> > Date: Monday, March 20, 2023 at 10:55 AM
> > To: Kaliraj Vairavakkalai <>
> > Cc: Anton Elita <>, Reshma Das <>, Simon Leinen 
> > <>, Natrajan Venkataraman <>, Krzysztof Szarkowicz 
> > <>, Alexander Gall <>
> > Subject: Re: RARE/freeRtr status @EANTC
> <SNIP>
>
> Juniper Business Use Only
>
>
> Juniper Business Use Only