post 1/7: optics test

up-n-atom · Dec 2, 2024 · 0eeb10b · 0eeb10b
1 parent 837dc89
commit 0eeb10b
Show file tree

Hide file tree

Showing 2 changed files with 11 additions and 2 deletions.
diff --git a/docs/posts/install-8311-community-firmware-on-the-bfw-solutions-was-110.md b/docs/posts/install-8311-community-firmware-on-the-bfw-solutions-was-110.md
@@ -381,6 +381,15 @@ configurations based on your network setup:
 
 You should now be able to access the [WAS-110] at `192.168.11.1`.
 
+## Test optics
+
+Before any installation, it's highly recommended to do a simple optics [fault test] on the [WAS-110]. If the signal(s)
+are abnormal, contact the seller immediately to start the RMA process. If you're uncertain, please double-check on the
+[8311 Discord].
+
+[fault test]: https://pon.wiki/guides/troubleshoot-connectivity-issues-with-the-bfw-solutions-was-110/#optical-status
+[8311 Discord]: https://discord.pon.wiki/
+
 ## Dump & backup firmware <small>optional</small> { #dump-and-backup-firmware data-toc-label="Dump & backup firmware" }
 
 1. [Enable SSH] from the web UI by following the steps outlined below in the shell upgrade section.

diff --git a/docs/posts/troubleshoot-connectivity-issues-with-the-bfw-solutions-was-110.md b/docs/posts/troubleshoot-connectivity-issues-with-the-bfw-solutions-was-110.md
@@ -111,11 +111,11 @@ where both __Laser output power__ and __Receiver signal average optical power__
 ethtool -m pon0
 ```
 
-!!! failure "Failure test"
+!!! failure "Optic fault test"
 
     1. Unplug the fiber cable.
     2. Check the [optical status](#optical-status), if the transmit (Tx) and receive (Rx) power (dBm) do not report
-       __No signal__, the optics have failed.
+       __No signal__ or __-40dBm__, the optics have failed.
 
 ### Fake O5