| |
|
1 |
Log in to the router via CLI.
|
2 |
Configure traffic-engineering on OSPF, IS-IS, or both via CLI since it cannot be done through NSP via an ICM pre-defined intent:
Classic:
/configure router ospf traffic-engineering
/configure router isis traffic-engineering
MD:
/configure router ospf traffic-engineering
/configure router isis traffic-engineering
/commit
|
3 |
Log in to NSP.
|
4 |
Import the intent type icm-te-tunnel into Device Management, Configuration Intent Types.
|
5 |
Navigate to Device Management, Configuration Templates.
|
6 |
Create a configuration template and associate the icm-te-tunnel intent type.
For example, the configuration template created below is named as icm-te-tunnel-template.
|
7 |
Navigate to Device Management, Configuration Deployments.
|
8 |
Create a logical deployment and select the TE tunnel (LSP) template.
|
9 |
Click on VIEW/EDIT TEMPLATE CONFIG and enter the LSP and LSP path parameters (source, destination, signaling-type (RSVP vs. SR-TE) path-computation method, primary and secondary paths, hop limits and conditions, etc.).
|
10 |
Click UPDATE.
|
11 |
Give LSP Tunnel a name and click DEPLOY.
End of steps |
