Description

An ACX7100 is seeing an RPD core when a commit is executed. The ACX is configured with a prefix-list tied to IPv4 bogus addresses:

 

set policy-options prefix-list IPV4-BOGONS 0.0.0.0/8

set policy-options prefix-list IPV4-BOGONS 10.0.0.0/8

set policy-options prefix-list IPV4-BOGONS 100.64.0.0/10

set policy-options prefix-list IPV4-BOGONS 127.0.0.0/8

set policy-options prefix-list IPV4-BOGONS 169.254.0.0/16

set policy-options prefix-list IPV4-BOGONS 172.16.0.0/12

set policy-options prefix-list IPV4-BOGONS 192.0.0.0/24

set policy-options prefix-list IPV4-BOGONS 192.0.2.0/24

set policy-options prefix-list IPV4-BOGONS 192.168.0.0/16

set policy-options prefix-list IPV4-BOGONS 198.18.0.0/15

set policy-options prefix-list IPV4-BOGONS 198.51.100.0/24

set policy-options prefix-list IPV4-BOGONS 203.0.113.0/24

set policy-options prefix-list IPV4-BOGONS 224.0.0.0/4

set policy-options prefix-list IPV4-BOGONS 240.0.0.0/4

set policy-options prefix-list IPV4-BOGONS 255.255.255.255/32

 

The prefix is referenced by policies:

 

set policy-options policy-statement IPV4-UCAST-SANITY-OUT term IPV4-BOGONS from prefix-list-filter IPV4-BOGONS orlonger

set policy-options policy-statement IPV4-UCAST-SANITY-OUT term IPV4-BOGONS then reject

 

That are associated with an active BGP peer:

 

set protocols bgp group i1 export IPV4-UCAST-SANITY-OUT

 

labroot@h10-47> show bgp summary 

Aug 02 11:20:05

Threading mode: BGP sharding

Thread counts: Update-io: 4 Shards: 4

Default eBGP mode: advertise - accept, receive - accept

Groups: 2 Peers: 2 Down peers: 0

Table     Tot Paths Act Paths Suppressed  History Damp State  Pending

bgp.rtarget.0     

            0     0     0     0     0     0

inet.0        

            1     1     0     0     0     0

inetflow.0      

            0     0     0     0     0     0

inet6.0        

            0     0     0     0     0     0

inet6flow.0      

            0     0     0     0     0     0

bgp.l3vpn.0      

            0     0     0     0     0     0

bgp.invpnflow.0    

            0     0     0     0     0     0

bgp.l3vpn-inet6.0   

            0     0     0     0     0     0

bgp.in6vpnflow.0   

            0     0     0     0     0     0

Peer           AS   InPkt   OutPkt  OutQ  Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped...

20.72.224.1      65001    13     11    0    0    4:21 Establ

 inet.0: 1/1/1/0

 

A configuration file is then applied. The file is a 'no-op' with a replace action for the same prefix-list:

 

labroot@h10-47> file show /var/tmp/maybe.conf 

policy-options {

  replace: prefix-list IPV4-BOGONS {

   0.0.0.0/8;

   10.0.0.0/8;

   100.64.0.0/10;

   127.0.0.0/8;

   169.254.0.0/16;

   172.16.0.0/12;

   192.0.0.0/24;

   192.0.2.0/24;

   192.168.0.0/16;

   198.18.0.0/15;

   198.51.100.0/24;

   203.0.113.0/24;

   224.0.0.0/4;

   240.0.0.0/4;

   255.255.255.255/32;

  }

}

 

When that file is applied and commited:

 

labroot@h10-47> configure 

Entering configuration mode

 

[edit]

labroot@h10-47# load replace /var/tmp/maybe.conf 

load complete

 

[edit]

labroot@h10-47# run set cli timestamp 

Aug 02 11:15:24

CLI timestamp set to: %b %d %T

 

[edit]

labroot@h10-47# commit and-quit 

Aug 02 11:15:25

commit complete

Exiting configuration mode

 

RPD will core:

 

labroot@h10-47> show system core-dumps 

Aug 02 11:15:54

re0:

--------------------------------------------------------------------------

-rw-r--r-- 1 root root  14736348 Aug 2 11:15 /var/core/re0/rpd.re.re0.1136.2024_08_02.11_15_27.tar.gz

total files: 1

 

Solution

Problem is tracked via PR1827751:

https://prsearch.juniper.net/PR1827751

Modification History

2024-08-02 : Article Created