Why 3rd-Party ONUs is in config status failed after OLT upgraded?

This article will share with you a case about the customer upgraded Huawei GPON OLT MA5800 X7 X15 X17  from V100R019C10SPH217 to V100R020C00SPC201. After upgrade was done all 3rd-Party ONUs (even from different vendors) are in config status failed.

Issue description

Customer upgraded the OLT from V100R019C10SPH217 to V100R020C00SPC201. After upgrade was done all 3rd-Party ONUs (even from different vendors) are in config status failed.

ONU examples:

0/1/0/5

0/1/0/6

0/1/3/0

0/1/3/1

0/18/1/8

0/18/1/9

ONTs on R19 version device do not have such issue.

Handling Process

We re-registed ONTs and collected lastword log. we saw that when OLT send OMCI message(MIB upload message) to ONT, but ONT didn’t reply, caused timeout, so the configure state is failed.

From the lastword, we can see that on version R20, OLT received mibuppload next message from ONT, but these message was failed on security verification, so MA5800 discard these message, caused this issue. MA5800 add these security verification on R20 version, to enhanced security.

We analyzed the mibupload next message and saw that ONT report huawei private protocol 0xff7a, but the content is different(we doubt that it is ONT vendor private protocol), so caused failed on security verification, message be discard.

Root cause

ONT report mibupload next message with unknown content. R20 use new security check than R19 version and could not recognize the message. So, OLT dropped the message.

Solution

We suggest using this workaround:

(config)#xpon ont-interoperability-mode gpon vendor ADTN itu-t g984 //ADTN is the vendor ID, if you use other vendor ONT, they can change it to other vendor ID.