Commit 6e13b5e5 authored by Adam Wujek's avatar Adam Wujek

presentations/WR_Switch_TC_2015: add slides about management

Signed-off-by: Adam Wujek's avatarAdam Wujek <adam.wujek@cern.ch>
parent 1ed11a41
......@@ -159,21 +159,77 @@
\end{columns}
\end{frame}
\section{Configuration and diagnostics}
\section{Configuration and management}
\subsection{}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}<beamer>{Outline}
\tableofcontents [currentsection]
\end{frame}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}{Remote configuration}
dot-config (+ webinterface?)
\end{frame}
\begin{frame}{Remote management}
SNMP, SNMP, and more SNMP
\begin{itemize}
\item<+-> Why do we need management?
\begin{itemize}
\item<+-> check switch status
\item<+-> explore network status
\item<+-> notify about faults
\item<+-> diagnostics
\item<+-> reconfigure it
\end{itemize}
\item<+->Problem is getting bigger when number of devices increase.
\item<+-> How to manage WRS?
\begin{itemize}
\item<+-> console
\item<+-> web-interface
\item<+-> SNMP
\item<+-> .config
\end{itemize}
\end{itemize}
\end{frame}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}[t]{SNMP in a nutshell}
\begin{itemize}\setlength{\itemsep}{-0.0\baselineskip}
\item<+->[] Simple Network Management Protocol
\item<+-> Designed for managing network devices (switches, routers)
\item<+-> Widely used
\item<+-> Client (manager) -- server (agent) architecture\\
\centering\includegraphics<.>[width=.6\textwidth]{management/snmp_client-server_c.pdf}
\includegraphics<+>[width=.6\textwidth]{management/snmp_client-server2_c.pdf}
\item<+-> Poll and interrupt modes\\
\centering\includegraphics<.>[width=.3\textwidth]{management/snmp_poll_trap_c.pdf}
\item<+-> Objects described in hierarchical tree (MIB)\\
\centering\includegraphics<.>[width=.7\textwidth]{management/snmp_tree_c.pdf}
\end{itemize}
\end{frame}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}[fragile]{.config overview}
\begin{itemize}
\item<+-> Kconfig file format
\item<+-> applied at runtime
\item<+-> stored locally or retrieved from network
\item<+-> keep data like:
\begin{itemize}
\item port timing mode
\item port delays
\item temperature thresholds
\end{itemize}
\item<+->[]
\tiny\begin{verbatim}
CONFIG_PORT00_PARAMS="name=wr0,tx=0,rx=160000,role=slave,fiber=0"
CONFIG_PORT01_PARAMS="name=wr1,tx=0,rx=160000,role=slave,fiber=0"
(..)
CONFIG_SFP00_PARAMS="vn=Axcen Photonics,pn=AXGE-1254-0531,tx=10,rx=10,wl_txrx=1310+1490"
CONFIG_SFP01_PARAMS="vn=Axcen Photonics,pn=AXGE-3454-0531,tx=10,rx=10,wl_txrx=1490+1310"
(..)
CONFIG_FIBER00_PARAMS="alpha_1310_1490=2.6787e-04"
CONFIG_FIBER01_PARAMS="alpha_1310_1490=2.6787e-04"
(..)
CONFIG_SNMP_TEMP_THOLD_FPGA=80
CONFIG_SNMP_TEMP_THOLD_PLL=70
\end{verbatim}
\end{itemize}
\end{frame}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{Plans for the future}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\begin{frame}<beamer>{Outline}
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment