Modify cRPD Configuration

During the installation of Paragon Automation, you can configure the address of the BGP-LS routers that will peer with cRPD to provide topology information to Paragon Pathfinder. You can also modify the cRPD configuration after installation, in the following ways:

• You can edit the BGP Monitoring Protocol (BMP) configuration file (kube-cfg.yml) located in the Paragon Automation primary node /etc/kubernetes/po/bmp/ directory, and then apply the new configuration.

  To edit the BMP configuration file and add a new neighbor:

  1. Edit the kube-cfg.yml file.

     content_copy zoom_out_map

     root@primary-node:~# vi /etc/kubernetes/po/bmp/kube-cfg.yml
     
     ---
     apiVersion: v1
     kind: ConfigMap
     metadata:
       namespace: northstar
       name: crpd-config
     data:
       config: |
         protocols {
           bgp {
             group northstar {
               neighbor 10.xx.43.1;
               neighbor 10.xx.43.2;   <= make sure you include the “;”
               }
           }
         }
     

  2. Apply the changes in the kube-cfg.yml file.

     content_copy zoom_out_map

     root@primary-node:~# kubectl apply -f /etc/kubernetes/po/bmp/kube-cfg.yml
     deployment.apps/bmp configured
     configmap/crpd-config configured
     service/bmp-grpc unchanged
     service/crpd unchanged
     service/bgp unchanged
     persistentvolumeclaim/crpd-data unchanged
     

  3. Connect to the cRPD container.

     content_copy zoom_out_map

     root@primary-node:/# cd usr/local/bin/
     
     root@primary-node:/usr/local/bin# ./pf-crpd 
     

  4. Verify that the changes are applied.

     content_copy zoom_out_map

     root@bmp-5888bb7dfd-72v9t> show configuration protocols bgp | display inheritance 
     group northstar {
     ---more--
         ##
         ## '10.xx.43.1' was inherited from group 'extra'
         ##
         neighbor 10.xx.43.1;
         ##
         ## '10.xx.43.2' was inherited from group 'extra'
         ##
         neighbor 10.xx.43.2;
     

     Note:

     Any additional neighbor will be added under a configuration group named extra. Use the | display inheritance command to see the new neighbor.

• Connect to the cRPD container and edit the configuration like you would on any Junos device.

  To connect to cRPD and add a new neighbor or change the autonomous system (AS) number:

  1. Connect to the cRPD container and enter configuration mode.

     content_copy zoom_out_map

     root@primary-node:/# cd usr/local/bin/
     
     root@primary-node:/usr/local/bin# ./pf-crpd 
     
     root@ bmp-5888bb7dfd-72v9 > edit
     
     [edit]
     root@ bmp-5888bb7dfd-72v9t#
     

  2. Review the current BGP configuration and AS number.

     content_copy zoom_out_map

     [edit]
     root@bmp-5888bb7dfd-72v9t# show protocols bgp | display inheritance 
     group northstar {
     ---more--
         ##
         ## '10.xx.43.1' was inherited from group 'extra'
         ##
         neighbor 10.xx.43.1;
         ##
         ## '10.xx.43.2' was inherited from group 'extra'
         ##
         neighbor 10.xx.43.2;
     
     [edit]
     root@bmp-5888bb7dfd-72v9t# show routing-options autonomous-system 
     11;
     

  3. Change the AS number.

     content_copy zoom_out_map

     [edit]
     root@bmp-5888bb7dfd-72v9t# set routing-options autonomous-system 64500
     

  4. Add a new neighbor.

     content_copy zoom_out_map

     [edit]
     root@bmp-5f78448d69-f84q7# edit protocols bgp 
     
     [edit protocols bgp]
     root@bmp-5888bb7dfd-72v9t# set group northstar neighbor 10.xx.43.3
     
     [edit protocols bgp group northstar]
     root@bmp-5888bb7dfd-72v9t# show | display inheritance 
     ---more---
     neighbor 10.xx.43.3;
         ##
         ## '10.xx.43.1' was inherited from group 'extra'
         ##
         neighbor 10.xx.43.1;
         ##
         ## '10.xx.43.2' was inherited from group 'extra'
         ##
         neighbor 10.xx.43.2;
     

     Note:

     You could also add the neighbor under the configuration group extra. However, if the pod is restarted, this change will be overwritten by the configuration in the kube-cfg.yml file.

  5. Commit your configuration changes.

     content_copy zoom_out_map

     [edit]
     root@bmp-5f78448d69-f84q7# commit