You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 6, 2022. It is now read-only.
1, Query the actual router VRP database and compare the content to that of the Routinator.
2. Repeat the comparison after the data has changed in the Routinator. Does the router pick up the changes and does its database match the Routinator data?
This probably requires that I know the serial number of the Routinator data and the router data.
For the Routinator getting the serial number depends on NLnetLabs/routinator#73, though it might be possible to get the serial number from the Routinator logs.
For the router, at least Alcatel/Lucent/Nokia SROS 16.0.R6 exposes the serial via the console:
A:vSIM>show router origin-validation rpki-session detail
...
Serial ID : 53149 Session ID : 0
Use environment no more (otherwise the interface prompts for the next page) and show router origin-validation database to get the actual VRPs.
I'm not sure if I can get it via NETCONF or if doing so would be any more standard across routers than using the proprietary console.
The text was updated successfully, but these errors were encountered:
1, Query the actual router VRP database and compare the content to that of the Routinator.
2. Repeat the comparison after the data has changed in the Routinator. Does the router pick up the changes and does its database match the Routinator data?
This probably requires that I know the serial number of the Routinator data and the router data.
For the Routinator getting the serial number depends on NLnetLabs/routinator#73, though it might be possible to get the serial number from the Routinator logs.
For the router, at least Alcatel/Lucent/Nokia SROS 16.0.R6 exposes the serial via the console:
Use
environment no more
(otherwise the interface prompts for the next page) andshow router origin-validation database
to get the actual VRPs.I'm not sure if I can get it via NETCONF or if doing so would be any more standard across routers than using the proprietary console.
The text was updated successfully, but these errors were encountered: