Skip to content

W
White Rabbit
Commit 4bc4b141 authored by Adam Wujek's avatar Adam Wujek 💬 Committed by Grzegorz Daniluk
Browse files
Options

docs/specifications/management: update wrs_failures with sfp info 

DONE: "Not supported SFP plugged into the cage (especially non 1-Gb SFP)"
UDATED: "Detected SFP not supported for WR timing"
Signed-off-by: Adam Wujek's avatarAdam Wujek <adam.wujek@cern.ch>
parent e5e122c9
Show whitespace changes
Inline Side-by-side
Showing with 17 additions and 11 deletions
documents/specifications/management/wrs_failures/fail.tex
View file @ 4bc4b141
...@@ -174,7 +174,7 @@ WR network.\\ ...@@ -174,7 +174,7 @@ WR network.\\
\item {\bf Detected SFP not supported for WR timing} \item {\bf Detected SFP not supported for WR timing}
\label{fail:timing:wrong_sfp} \label{fail:timing:wrong_sfp}
\begin{packed_enum} \begin{packed_enum}
\item [] \underline{Status}: TODO \item [] \underline{Status}: TODO \emph{(allow disable checking if not WR-ports)}
\item [] \underline{Severity}: ERROR \item [] \underline{Severity}: ERROR
\item [] \underline{Mode}: \emph{all} \item [] \underline{Mode}: \emph{all}
\item [] \underline{Description}:\\ \item [] \underline{Description}:\\
...@@ -184,17 +184,21 @@ WR network.\\ ...@@ -184,17 +184,21 @@ WR network.\\
\emph{PPSi} not having the right values to estimate link asymmetry. \emph{PPSi} not having the right values to estimate link asymmetry.
Despite \emph{PPSi} offset being close to 0 \emph{ps}, the device won't Despite \emph{PPSi} offset being close to 0 \emph{ps}, the device won't
be properly synchronized. be properly synchronized.
\item [] \underline{SNMP objects}: \emph{(not yet implemented)}\\ \item [] \underline{SNMP objects}:\\
\texttt{WR-SWITCH-MIB::portSfpID.<n>} \emph{(info available via hal shm)}\\ \texttt{WR-SWITCH-MIB::portSfpVN.<n>}\\
\texttt{WR-SWITCH-MIB::portSfpPN.<n>}\\
\texttt{WR-SWITCH-MIB::portSfpVS.<n>}\\
\texttt{WR-SWITCH-MIB::portSfpInDB.<n>}\\ \texttt{WR-SWITCH-MIB::portSfpInDB.<n>}\\
\texttt{WR-SWITCH-MIB::portSfpGbE.<n>} \texttt{WR-SWITCH-MIB::portSfpGbE.<n>}\\
\item [] \underline{Note}: HAL should provide this info to the shared \texttt{WR-SWITCH-MIB::portSfpError.<n>}\emph{(not implemented)}
memory, so in general we should build a per-port structure describing \item [] \underline{Note}: HAL provide this info to the shared
memory, so in general we build a per-port structure describing
SFP info: SFP info:
\begin{packed_items} \begin{packed_items}
\item SFP ID (e.g. AXGE-1254-0531) \emph{(available via halshm)} \item SFP ID (e.g. AXGE-1254-0531) \emph{(available via halshm)}
\item Matched ? (to SFP database entries) \item Matched ? (to SFP database entries)
\item Gigabit ? (based on supported speeds read from i2c eeprom) \item Gigabit ? (based on supported speeds read from i2c eeprom)
\item portSfpError ? (true when port configured as a WR but not in DB or not GbE)
\end{packed_items} \end{packed_items}
\vspace{12pt} \vspace{12pt}
WRS configuration should also allow to disable this check on some ports. WRS configuration should also allow to disable this check on some ports.
...@@ -665,7 +669,7 @@ wrs-192.168.16.242# devmem 0xfffffd04 ...@@ -665,7 +669,7 @@ wrs-192.168.16.242# devmem 0xfffffd04
\item {\bf Not supported SFP plugged into the cage (especially non 1-Gb SFP)} \item {\bf Not supported SFP plugged into the cage (especially non 1-Gb SFP)}
\label{fail:other:sfp} \label{fail:other:sfp}
\begin{packed_enum} \begin{packed_enum}
\item [] \underline{Status}: TODO \item [] \underline{Status}: DONE
\item [] \underline{Severity}: WARNING \item [] \underline{Severity}: WARNING
\item [] \underline{Description}:\\ \item [] \underline{Description}:\\
If not supported Gigabit Fiber SFP is plugged into the cage, then it's a If not supported Gigabit Fiber SFP is plugged into the cage, then it's a
...@@ -673,10 +677,12 @@ wrs-192.168.16.242# devmem 0xfffffd04 ...@@ -673,10 +677,12 @@ wrs-192.168.16.242# devmem 0xfffffd04
used, then no Ethernet traffic would be flowing on that port. It's due used, then no Ethernet traffic would be flowing on that port. It's due
to the fact, that we don't have 10/100Mbit Ethernet implemented inside to the fact, that we don't have 10/100Mbit Ethernet implemented inside
the WRS. the WRS.
\item [] \underline{SNMP objects}: \emph{(not yet implemented)}\\ \item [] \underline{SNMP objects}:\\
\texttt{WR-SWITCH-MIB::portSfpGbE} \texttt{WR-SWITCH-MIB::portSfpVN.<n>}\\
\item [] \underline{Note}: We should get the information about supported \texttt{WR-SWITCH-MIB::portSfpPN.<n>}\\
Ethernet speed through HAL together with the SFP's ID. \texttt{WR-SWITCH-MIB::portSfpVS.<n>}\\
\texttt{WR-SWITCH-MIB::portSfpGbE.<n>}\\
\texttt{WR-SWITCH-MIB::portSfpError.<n>}\emph{(not implemented)}
\end{packed_enum} \end{packed_enum}
\item {\bf File system / Memory corruption} \item {\bf File system / Memory corruption}
......
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