Commit 27d80ac8 authored by Adam Wujek's avatar Adam Wujek Committed by Grzegorz Daniluk

docs/specifications/management: remove portSfpCopper

As agreed with Greg portSfpCopper is not needed because portSfpError will
notify about not valid SFP configuration.
Signed-off-by: Adam Wujek's avatarAdam Wujek <adam.wujek@cern.ch>
parent aef29c3c
......@@ -233,8 +233,6 @@ operators.
database with fixed delays and alpha ? (timing: \ref{fail:timing:wrong_sfp})
\item [] \texttt{WR-SWITCH-MIB::portSfpGbE.<n>}\\ - is there Gigabit Ethernet
SFP plugged ? (other: \ref{fail:other:sfp})
\item [] \texttt{WR-SWITCH-MIB::portSfpCopper.<n>}\\ - is there a copper Gigabit
Ethernet SFP plugged ?
\item [] \texttt{WR-SWITCH-MIB::portNoTiming.<n>}\\ - port is used only for data
transfer, no timing, or non-WR timing; timing-unsupported SFP may be used
there (it's a signal for NMS not to raise an alarm if
......
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