doc/wrs_failures: update before release v5.0

Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

doc/wrs_failures/fail.tex

@@ -245,7 +245,7 @@ WR network.
 			\item [] \underline{Description}:\\
 				In this case, \emph{PTP/PPSi} will fail to stay synchronized and provide
 				synchronization. Even if the WR servo is in the \texttt{TRACK\_PHASE}
-        state, it calculates a new phase shift based on the Master-to-Slave delay
+				state, it calculates a new phase shift based on the Master-to-Slave delay
 				variations. To calculate these variations, it still needs timestamped
 				PTP frames flowing. There could be several causes of such fault:
 				\begin{itemize}
@@ -261,7 +261,10 @@ WR network.
 				\snmpadd{WR-SWITCH-MIB::wrsPortStatusConfiguredMode.<n>}\\
 				\snmpadd{WR-SWITCH-MIB::wrsPTPFramesFlowing}\\
 				\snmpadd{WR-SWITCH-MIB::wrsTimingStatus}\\
-        \snmpadd{WR-SWITCH-MIB::wrsMainSystemStatus} }
+				\snmpadd{WR-SWITCH-MIB::wrsVlansSetStatus}\\
+				\snmpadd{WR-SWITCH-MIB::wrsBootSuccessful}\\
+				\snmpadd{WR-SWITCH-MIB::wrsOSStatusGroup}\\
+				\snmpadd{WR-SWITCH-MIB::wrsMainSystemStatus} }
 			\item [] \underline{Note}: If the kernel driver crashes, there is not much
 				we can do. We end up with either our system frozen or a reboot. For
 				wrong VLAN configuration and HDL problems we can monitor if PTP frames

doc/wrs_failures/snmp_exports.tex

@@ -23,12 +23,6 @@ particular object reports an error. These repair procedures don't require any
 in-depth knowledge about White Rabbit. Independently of an error reported, there
 are some common remarks that apply to all situations:
 \begin{itemize}
-  \item Linux inside the WR Switch enumerates WR interfaces starting from 0.
-    This means we have to use internally port indexes 0..17. However, the
-    port numbers printed on the front panel are 1..18. Syslog messages
-    generated from the switch use the Linux port numbering. The consequence is
-    that every time Syslog says there is a problem on port X, this refers to
-    port index X+1 on the front panel of the switch.
   \item If a procedure given for a specific SNMP object does not solve the
     problem, please contact WR experts to perform a more in-depth analysis of
     the network. For this, you should provide a complete dump of the WRS status
@@ -45,6 +39,14 @@ are some common remarks that apply to all situations:
   \item If a procedure requires replacing a switch with a new unit, the broken
     one should be handled to WR experts or the switch manufacturer to
     investigate the problem.
+  \item Until version 5.0 of the switch firmware
+    Linux inside the WR Switch enumerated WR interfaces starting from 0.
+    This means we have to use internally port indexes 0..17. However, the
+    port numbers printed on the front panel were 1..18. Syslog messages
+    generated from the switch used the Linux port numbering. The consequence
+    was that every time Syslog says there is a problem on port X, this refered
+    to port index X+1 on the front panel of the switch. From the v5.0 ports are
+    numbered wri1 to wri18.
 \end{itemize}
 
 \subsection{General status objects for operators}