FAQ. OLT BDCOM freezes when polling the ONU list: различия между версиями
Нет описания правки |
|||
Строка 1: | Строка 1: | ||
[[FAQ._OLT_BDCOM_freezes_when_polling_the_ONU/ONT_list|en]] | [[FAQ._Зависание_OLT_BDCOM_при_опросе_списка_ONU/ONT|ru]] | [[FAQ._OLT_BDCOM_freezes_when_polling_the_ONU/ONT_list|en]] | [[FAQ._Зависание_OLT_BDCOM_при_опросе_списка_ONU/ONT|ru]] | ||
It has been observed that the OLT BDCOM reacts rather poorly to frequent SNMP requests. Apparently the devices have a rather weak processor and SNMP requests have a low priority. As a result - if OLT is connected to a large number of ONT/ONU, then, when trying to get information on the list of ONT/ONU, the device may stop responding to SNMP-queries altogether. Typically SNMP will start working again on the device after 30-60 minutes. It has been observed that after a reboot the device will often not hang up within a week and will return data without any problems. | |||
The situation is not solved for the 3310 branch models as there is no new firmware available for them. | |||
For the 36** branch the situation is a bit better - in more recent firmware versions the situation is somewhat better, but not ideal. |
Версия от 15:57, 10 марта 2023
It has been observed that the OLT BDCOM reacts rather poorly to frequent SNMP requests. Apparently the devices have a rather weak processor and SNMP requests have a low priority. As a result - if OLT is connected to a large number of ONT/ONU, then, when trying to get information on the list of ONT/ONU, the device may stop responding to SNMP-queries altogether. Typically SNMP will start working again on the device after 30-60 minutes. It has been observed that after a reboot the device will often not hang up within a week and will return data without any problems.
The situation is not solved for the 3310 branch models as there is no new firmware available for them.
For the 36** branch the situation is a bit better - in more recent firmware versions the situation is somewhat better, but not ideal.