Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »


Part 1 Analyzing the Topology




Part 2Loading 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 3Troubleshooting Topology Issues

https://172.25.11.100:8443 

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 4Troubleshooting 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 5Debugging 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

Part 6Resetting the Lab Topology










  • No labels