296 | | Rerun `xorp_log.sh` again at `router-1`, and start `XORP` on `router-2` again to enable `OSPF` routing at `router-2`. We see the `OSPF` routing table updates at `router-1` this time! This is because when the `XORP` processes were started again, it sent `OSPF` `hello` messages to other routers to notify that `router-2` was up, and the `OSPF` routing table was updated at each router afterwards. |
| 296 | Rerun `xorp_log.sh` again at `router-1`, and restart `XORP` on `router-2` to enable `OSPF` routing at `router-2`. |
| 297 | |
| 298 | |
| 299 | Start `XORP` by specifying the routing protocol configuration file. |
| 300 | {{{ |
| 301 | xuanliu@router-2:~$ cd /usr/local/xorp/sbin/ |
| 302 | xuanliu@router-2:/usr/local/xorp/sbin$ sudo ./xorp_rtrmgr -b /etc/xorp/ospfd.conf -l /tmp/xorp_rtrmgr_log -d |
| 303 | }}} |
| 304 | |
| 305 | Verify the `XORP` process is running |
| 306 | {{{ |
| 307 | xuanliu@router-1:/usr/local/xorp/sbin$ ps -ef | grep xorp |
| 308 | root 1972 1 0 13:30 ? 00:00:02 xorp_fea |
| 309 | root 1973 1 0 13:30 ? 00:00:00 xorp_rib |
| 310 | root 1974 1 0 13:30 ? 00:00:00 xorp_policy |
| 311 | root 1975 1 0 13:30 ? 00:00:01 xorp_ospfv2 |
| 312 | root 1976 1 0 13:30 ? 00:00:00 ./xorp_rtrmgr -b /etc/xorp/ospfd.conf -l /tmp/xorp_rtrmgr_log -d |
| 313 | }}} |
| 314 | |
| 315 | We see the `OSPF` routing table updates at `router-1` this time! This is because when the `XORP` processes were started again, it sent `OSPF` `hello` messages to other routers to notify that `router-2` was up, and the `OSPF` routing table was updated at each router afterwards. |