Objectives
The simulator ticks each one as soon as the network meets it.
On both routers enable ports 1/1/1 and 1/1/2 (admin-state enable).
Create router interface "to-R2" / "to-R1" on port 1/1/1 (10.0.12.1/30 and .2/30) and "to-LAN" on port 1/1/2 (192.168.1.1/24 and 192.168.2.1/24).
Add a static route to the far LAN; its next hop needs admin-state enable.
Commit, then check show router route-table for the Static route.
Ping PC2 from PC1.
Before you start
Work in a candidate: edit-config private, make the changes, compare, then commit. On SR OS a router interface is bound to a port, and both the port and a static next hop start disabled. The route table lists the static route with preference 5.
Concept
Model-driven CLI: candidate, compare, commit
Nokia SR OS MD-CLI (and SR Linux) edit a candidate copy of the configuration. Nothing you type changes the router until you commit, and commit applies every change together after checking it, so a half-finished change never reaches the network.
Concept
Static routes and the routing table
A static route is an entry you type yourself: “to reach this network, send to this next hop”. Routers know only their directly connected subnets until you add routes or run a routing protocol.