{"id":903,"date":"2014-08-08T14:59:35","date_gmt":"2014-08-08T06:59:35","guid":{"rendered":"http:\/\/www.thunder-link.com\/blog\/?p=903"},"modified":"2023-04-12T14:00:52","modified_gmt":"2023-04-12T06:00:52","slug":"alarm-of-optical-modules-on-ssn1pex2-ssn2pex1-and-tnn1ex2-boards-on-h-mstp-equipment","status":"publish","type":"post","link":"https:\/\/www.thunder-link.com\/blog\/alarm-of-optical-modules-on-ssn1pex2-ssn2pex1-and-tnn1ex2-boards-on-h-mstp-equipment\/","title":{"rendered":"Alarm of Optical Module’s on PEX2&PEX1 and EX2 Boards on H-MSTP Equipment"},"content":{"rendered":"

Summary:<\/strong><\/em>
\nThe LASER_MOD_ERR alarm is reported when some vendors’ optical modules are used on different PCB versions on SSN1PEX2<\/a>, SSN2PEX1, and TNN1EX2 boards.<\/p>\n

\"Huawei<\/p>\n

[Problem Description]<\/strong><\/em>
\nTrigger condition:<\/strong>
\nScenario 1: The optical modules of specific models report the LASER_MOD_ERR alarm.
\nIf the equipment <\/a>version is V200R012C01SPH102 (board software version 6.04) or earlier and the board is fitted with FINISAR FTLX1413M3BCL-HW optical modules, the LASER_MOD_ERR alarm will be reported.
\nScenario 2: Specific PCB versions report the LASER_MOD_ERR alarm.
\nThe following attachment lists the combinations that will report the LASER_MOD_ERR alarm.
\nSymptom:<\/strong><\/em>
\nThe NMS displays the LASER_MOD_ERR alarm.
\nThe query result on the Navigator displays the LASER_MOD_ERR alarm.
\nIdentification method:
\n1. Method to identify the trigger condition for scenario 1:
\nUse the NMS or Navigator to query the board manufacturing information. If the optical module model is FTLX1413M3BCL-HW and the software version is V200R012C01SPH102
\n(board software 6.04) or earlier, the LASER_MOD_ERR alarm will be reported<\/p>\n

Figure 1 Querying the board manufacturing information on the NMS<\/p>\n

Figure 2 Querying the board manufacturing information on the Navigator<\/p>\n

Figure 3 Querying the board software version on the Navigator<\/p>\n

2. Method to identify the trigger condition for scenario 2:<\/p>\n

Use the Navigator to query the PCB version and software version of the board. If the combination triggering scenario 2 is present (see the attachment), the LASER_MOD_ERR alarm. Figure 4 shows the method to query the software version. Figure 4 shows the method to query the PCB version.<\/p>\n

[Root Cause]<\/strong><\/em>
\nDifferent PCB versions correspond to different optical module models. However, the optical modules and boards on some live network offices have been separately quoted and purchased. If the combination can trigger scenario 2, as listed in the attachment, the LASER_MOD_ERR alarm will be reported.
\n[Impact and Risk]
\nThe LASER_MOD_ERR alarm will be reported on live networks. It does not affect services but affects customer feeling.<\/p>\n

[Measures and Solutions]<\/strong><\/em>
\nWorkarounds:
\nScenario 1: The optical modules of specific models report the LASER_MOD_ERR alarm.
\nReplace the FTLX1413M3BCL-HW model with an appropriate one.
\nScenario 2: Specific PCB versions report the LASER_MOD_ERR alarm.
\nReplace the incorrect optical module models with the ones corresponding to the PCB versions.
\nPreventive measures:
\nScenario 1: The optical modules of specific models report the LASER_MOD_ERR alarm.
\nUpgrade to V200R012C01SPH102 (board software 6.04) or later.
\nScenario 2: Specific PCB versions report the LASER_MOD_ERR alarm.
\nUpgrade to a software version that does not trigger the scenario.<\/p>\n","protected":false},"excerpt":{"rendered":"

Summary: The LASER_MOD_ERR alarm is reported when some vendors’ optical modules are used on different PCB versions on SSN1PEX2, SSN2PEX1, and TNN1EX2 boards. [Problem Description] Trigger condition: Scenario 1: The optical modules of specific models report the LASER_MOD_ERR alarm. If the equipment version is V200R012C01SPH102 (board software version 6.04) or earlier and the board is […]<\/p>\n","protected":false},"author":1,"featured_media":1029,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[128],"tags":[253,249,250,251,252],"_links":{"self":[{"href":"https:\/\/www.thunder-link.com\/blog\/wp-json\/wp\/v2\/posts\/903"}],"collection":[{"href":"https:\/\/www.thunder-link.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.thunder-link.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.thunder-link.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.thunder-link.com\/blog\/wp-json\/wp\/v2\/comments?post=903"}],"version-history":[{"count":0,"href":"https:\/\/www.thunder-link.com\/blog\/wp-json\/wp\/v2\/posts\/903\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.thunder-link.com\/blog\/wp-json\/wp\/v2\/media\/1029"}],"wp:attachment":[{"href":"https:\/\/www.thunder-link.com\/blog\/wp-json\/wp\/v2\/media?parent=903"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.thunder-link.com\/blog\/wp-json\/wp\/v2\/categories?post=903"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.thunder-link.com\/blog\/wp-json\/wp\/v2\/tags?post=903"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}