blob: d90fc88e901bd80b6bca268c173c56343ace3c31 [file] [log] [blame]
Nick Gordon221531c2017-06-08 11:44:45 -05001\section{LSDB Status Dataset}
2\label{sec:lsdb-status-dataset}
3
4NLSR makes available the entire contents of the LSDB upon request. A
5command can request LSAs of just a specific type, or request the
6collection of all LSAs. Unlike the Prefix Update and NFD RIB command
7processors, the LSDB Status dataset is available over \emph{both} the
8\texttt{/localhost} and regular router prefixes. That is, you can
9request an arbitrary router's LSDB contents.
10
11\subsection{Requesting the dataset}
12\begin{itemize}
13\item To request the local dataset, simply send an Interest of the
14 form \texttt{/localhost/nlsr/lsdb/<dataset type>}.
15\item To request a remote dataset, send an Interest of the form
16 \texttt{/<router name>/lsdb/<dataset type>}, where \texttt{<router
17 name>} is whatever the router's name is. This is usually
18 \texttt{general.network + general.site + general.router} from the
19 configuration file.
20\end{itemize}
21
22Where \texttt{<dataset type>} is one of \texttt{names, adjacencies, coordinates} or \texttt{list}.