Lab 9 NorthStar Controller Troubleshooting Overview
- Jean-luc KRIKER
| Part 1 | Â Analyzing the Topology |
|---|---|
| Part 2 | Loading The Configuration |
lab@student-desktop ~]$ ./lab9-setup.sh | |
[lab@student-desktop ~]$ ssh lab@northstar sudo docker exec -it crpd cli configure load override /home/configs/lab9-start.config commit | |
| Part 3 | Troubleshooting Topology Issues |
operator / admin / lab123 | |
| no Nodes or links | More Options > Administration and SELECT System Settings CLICK:Â Â Reset Network Model |
| check crpd | root@crpd# run show bgp summary show routing-options autonomous-system 100 set routing-options autonomous-system 64512 commit |
| check vmx-2 | [lab@student-desktop ~]$ ssh lab@vmx-2 show route advertising-protocol bgp 192.168.1.100 show policy-options policy-statement TE set protocols bgp group northstar export TE commit show route advertising-protocol bgp 192.168.1.100 |
Refresh the browser | |
| Part 4 | Troubleshooting LSP Provisioning |
show path-computation-client status >> Status = New The NorthStar Controller Topology Server (Toposerver) associates PCEP sessions with the nodes in the topology learned from the network TED. If a PCEP session is established using a node’s management IP address, the Toposerver might not receive that IP address from the TED and the PCEP session will not be allowed to establish. Step | |
lab@vmx-1# set protocols mpls lsp-external-controller pccd | |
More Options > Administration and SELECT Device Profile CLICK:Â "Sync with Live Network" + add Mgt IP and PCEP IP for vmx1 | |
| Part 5 | Debugging Network Model and NorthStar Controller |
| vmx-3 | show ospf neighbor show interface routing show interface routing | match Down show configuration interface ge-0/0/5 |
delete interfaces ge-0/0/5.0 disable commit | |
refresh the "Element panel" >> new LSP tunnel appear | |
| create a 100m Strict Path | vmx1 to vmx2 Provision LSP > Selection: required + Hops: vmx3, vmx5, vmx2 ( all Strict ) |
[lab@northstar-app ~]$ sudo cat /opt/northstar/logs/pcs.log | grep "vmx1-to-vmx2-Strict" 2021 Mar 11 03:38:01.475671 northstar-app PCServer [NorthStar][PCServer][LSPProvisioning] msg=0x000060b2 vmx1-to-vmx2-Strict@172.20.20.1 path=StrictPathName (192.168.1.1), from=172.20.20.1 to=172.20.20.2 lsp add/update event lsp_state=ACTIVE admin_state=UP, delegated=true, setup_type=RSVP, path_type=primary path, priority=7/7 bw=100000000 metric=-1, admin group bits exclude=0 include_any=0 include_all=0, control_type=PCE initiated, ERO=172.20.20.1--172.22.101.2--172.22.105.2--172.22.110.1, RRO=172.20.20.1--172.22.101.2--172.22.105.2–172.22.110.1 | |
sudo cat /opt/northstar/logs/pceserver.log | grep "vmx1-to-vmx2-Strict" 2021 Mar 11 03:38:01.432309 northstar-app pce_server 192.168.1.1:vmx1-to-vmx2-Strict/StrictPathName ADD SENT TO PCC 626810001 2021 Mar 11 03:38:01.466397 northstar-app pce_server 192.168.1.1:vmx1-to-vmx2-Strict/StrictPathName UPD RCVD FROM PCC, ack 626810001 2021 Mar 11 03:38:01.466662 northstar-app pce_server 192.168.1.1:vmx1-to-vmx2-Strict/StrictPathName ADD SENT TO PCS 626810001, UP 2021 Mar 11 03:38:01.469534 northstar-app pce_server 192.168.1.1:vmx1-to-vmx2-Strict/StrictPathName UPD RCVD FROM PCC 2021 Mar 11 03:38:01.470258 northstar-app pce_server 192.168.1.1:vmx1-to-vmx2-Strict/StrictPathName UPD SENT TO PCS 0, ACTIVE [root@northstar-app ~]# | |
| Part 5 | Debugging Network Model and NorthStar Controller |
| generate JTAC recommended debug information | [lab@northstar-app /]$ sudo /u/wandl/bin/system-diagnostic.sh northstar_debug >> /tmp/northstar_debug.tbz2 file |
| Part 6 | Resetting the Lab Topology |
| delete the LSP:  vmx1-to-vmx2-Strict | |
[lab@northstar-app ~]$ sudo docker exec -it crpd cli root@crpd# load override /home/configs/reset.config commit |