Rare project developers

[Frédéric LOUI <>]

Hi,

As per previous discussion. 

Now bf_forwarder will send a notification back to the control plane whenever 
an entry cannot be programmed.
https://bitbucket.software.geant.org/projects/RARE/repos/rare/commits/cc36f4fb97c5c5173445972a3f97bc763ba8720d

Before starting bf_forrwarder:

DAV0001#show p4lang p4                             
category    value                                  
peer        null                                   
closed      null                                   
capability  null                                   
platform    null                                   
since       1970-01-01 01:00:00                    
for         never                                  

After having started bf_forwarder
                                                   
DAV0001#show p4lang p4                             
category    value                                  
peer        127.0.0.1                              
closed      0                                      
capability  mpls mcast acl_in acl_out tun bier gre 
platform    tna/bfforwarder                        
since       2022-02-08 09:44:12                    
for         00:00:02                               

As you can see I configured a NAT basic rule:

DAV0001#sh run | i nat                                                        
 
ipv4 nat inet sequence 10 srclist ACL_NAT4 interface sdn15                    
 
                                                                              
 
DAV0001#ah ACL_NAT4                                                           
 
invalid command, try  ?                                                       
 
                                                                              
 
DAV0001#show access-list ACL_NAT4                                             
 
 sequence 10 permit 17 any all 4.4.4.4 255.255.255.255 all                    
 
  match=tx=0(0) rx=0(0) drp=0(0) accessed=never ago, 00:00:00 timeout         
 
 sequence 20 permit 6 any all 4.4.4.4 255.255.255.255 all                     
 
  match=tx=0(0) rx=0(0) drp=0(0) accessed=never ago, 00:00:00 timeout         
 
 sequence 30 deny all any all any all                                         
 
  match=tx=0(0) rx=13764(188) drp=0(0) accessed=00:00:00 ago, 00:00:00 
timeout 

After having issue:
debug p4lang server rx
term monitor

DAV0001#term mon                                                              
                                                  
DAV0001#warning servP4lang.srvAccept:servP4lang.java:641 neighbor 127.0.0.1 
up                                                  
info servP4langConn.doRound:servP4lang.java:2033 dataplane said: entry failed 
to prepare entry for table ig_ctl.ig_ctl_ipv4b.tbl_ipv4_fib_host with 
Key[hdr.ipv4b.dst_addr 10.1.14.4 None None None None None,ig_md.vrf 1 None 
None None None None] Data[nexthop_id 51154 None None None None None None]     
                                                                              
     
info servP4langConn.doRound:servP4lang.java:2033 dataplane said: entry failed 
to prepare entry for table ig_ctl.ig_ctl_ipv4b.tbl_ipv4_fib_host with 
Key[hdr.ipv4b.dst_addr 10.1.12.2 None None None None None,ig_md.vrf 1 None 
None None None None] Data[nexthop_id 42506 None None None None None None]     
                                                                              
     
info servP4langConn.doRound:servP4lang.java:2033 dataplane said: entry failed 
to prepare entry for table ig_ctl.ig_ctl_ipv4b.tbl_ipv4_fib_host with 
Key[hdr.ipv4b.dst_addr 10.1.13.3 None None None None None,ig_md.vrf 1 None 
None None None None] Data[nexthop_id 16671 None None None None None None]     
                                                                              
     
…


The important point here is to see that p4lang server reported a P4 dataplane 
that does not have NAT.
 Hence, the errors we can observe in debug mode.

All the best
fl