Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Debug cPCE and cPCEP Adaptor

Troubleshooting is a systematic approach to solving a problem. The goal of troubleshooting is to determine why something does not work as expected and how to resolve the problem.

Troubleshooting Container

You can implement various docker commands to monitor and troubleshoot issues at container level when cPCE is deployed as a docker container.

  • docker ps: List out active containers and their state.

  • docker stats: Continuous monitor the resource utilization.

  • docker logs: Extract container logs in case the container terminates unexpectedly.

  • docker stop: Stop the Docker from the current state.

  • docker start: Restart the Docker container.

Verify Docker

To verify docker details:
  1. Verify the installed Docker Engine version by using the docker version command.

    root@ubuntu-vm18:~# docker version

  2. View the software and hardware information in the system.

    root@ubuntu-vm18:~# uname -a

  3. View the version of ubuntu.

    root@ubuntu-vm18:~# lsb_release -a

Verify Reachability of cPCE Bash Shell

To access the cRPD using bash shell:
  1. Run the command to launch the Junos shell.

    root@ubuntu-vm18:~# docker exec -it cRPD-cpce bash

  2. Run the command to ping the host ubuntu VM from cPCE.

    root@cRPD-cpce:/# ping 172.17.0.1 -c 2

Verify Sample outputs from cPCE

  1. Verify route details.

    root@cRPD-cpce> show route

  2. Verify interfaces.

    root@cRPD-cpce> show interfaces terse

  3. Run the command to start shell mode.

    root@cRPD-cpce> start shell

  4. Run the command to ping R1 from cPCE.

    root@cRPD-cpce# ping 10.1.255.1 -c 2

Verify Reachability from R1

  1. Configure host device to connect to R1.

    root@ubuntu-vm18:~# ip link

    root@ubuntu-vm18:~# ip addr add 10.1.1.2/30 dev eth1

    root@ubuntu-vm18:~# ip link set eth1 up

    root@ubuntu-vm18:~# ip route add 10.1.0.0/16 via 10.1.1.1

    root@ubuntu-vm18:~# ip route

  2. Ping R1 from host device.

    root@ubuntu-vm18:~# ping 10.1.1.1 -c 2

Verify Sample Outputs from cPCEPAdaptor

  1. Start shell mode on Adaptor.

    root@CPCE1-pcepAdaptor> start shell

    root@CPCE1-pcepAdaptor# ifconfig

  2. Ping cPCE from Adaptor.

    root@CPCE1-pcepAdaptor# ping 172.17.0.2 -c 2

  3. Ping Ubuntu host VM from Adaptor.

    root@CPCE1-pcepAdaptor# ping 172.17.0.1 -c 2

  4. Ping Router R1 from Adaptor.

    root@CPCE1-pcepAdaptor# ping 10.1.255.1 -c 2

Verify Sample Outputs from R1

  1. Verify that the LSP is up.

    root@R1> show mpls lsp ingress

  2. Verify OSPF neighbor.

    root@R1> show ospf neighbor

  3. Verify BGP summary.

    root@R1> show bgp summary

View Trace Files

  1. Configure the gRPC trace options.

    root@CPCE1-pce# set system services extension-service traceoptions file grpc.log

    root@CPCE1-pce# set system services extension-service traceoptions flag all

  2. Configure the programmable RPD trace options.

    root@CPCE1-pce# set routing-options programmable-rpd traceoptions file grpc-server.log

    root@CPCE1-pce# set routing-options programmable-rpd traceoptions flag te-path-compute

  3. Configure bgp trace options.

    root@CPCE1-pce# set protocols bgp traceoptions file bgp.log

    root@CPCE1-pce# set protocols bgp traceoptions file size 1m

    root@CPCE1-pce# set protocols bgp traceoptions file world-readable

    root@CPCE1-pce# set protocols bgp traceoptions flag all

  4. Configure mpls trace options.

    root@CPCE1-pce# set protocols mpls traceoptions file extctrl.log

    root@CPCE1-pce# set protocols mpls traceoptions file size 1m

    root@CPCE1-pce# set protocols mpls traceoptions file world-readable

    root@CPCE1-pce# set protocols mpls traceoptions flag externally-controlled-lsp

    root@CPCE1-pce# set protocols mpls traceoptions flag all

Restart cPCEPAdaptor

Specify the command to restart if the pcepAdaptor gets disconnected.

root@CPCE1-pcepAdaptor# run restart pceserver