Появляется c NTE-2 CFGFAILED

[DGM]

UPD:
на данный момент на LTE-2X включено 16 абонентов. Во всех случаях, при появлении CFGFAILED двух NTE-2, обязательно присутствует одна и та же NTE-2. Решение проблемы пока одно-реконфиг OLT. Что характерно, графики мощности в этих случаях весьма странны. Сегодня заменим абоненту эту NTE-2 и понаблюдаем за сетью.
Лог:

Код: Выделить всё

Jan 10 23:07:06 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) in REPORTTIMEOUT state
Jan 10 23:07:06 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:03 (desc: vl109-Zakatn-61) in REPORTTIMEOUT state
Jan 10 23:07:06 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:01 (desc: vl109-Zakatn-61) in REPORTTIMEOUT state
Jan 10 23:07:06 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:02 (desc: vl109-Zakatn-61) in REPORTTIMEOUT state
Jan 10 23:07:06 LTE-2X chip-proxy: ONT yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) disconnected (OLT0[0])
Jan 11 00:46:46 LTE-2X telnetd: pam_unix(login:session): session opened for user xxxxx by xxxxx(uid=0)
Jan 11 00:46:46 LTE-2X telnetd: Accepted password for xxxxx from xxx.xxx.xxx.xxx
Jan 11 00:52:23 LTE-2X cli: xxxxx logged out
Jan 11 07:27:22 LTE-2X telnetd: pam_unix(login:session): session opened for user xxxxx by xxxxx(uid=0)
Jan 11 07:27:22 LTE-2X telnetd: Accepted password for xxxxx from xxx.xxx.xxx.xxx
Jan 11 07:30:40 LTE-2X cli: xxxxx logged out
Jan 11 08:44:46 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:0B (desc: vl110-Znakom-177-3) in REPORTTIMEOUT state
Jan 11 08:44:46 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) in REPORTTIMEOUT state
Jan 11 08:44:46 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:09 (desc: vl110-Znakom-177-3) in REPORTTIMEOUT state
Jan 11 08:44:46 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:0A (desc: vl110-Znakom-177-3) in REPORTTIMEOUT state
Jan 11 08:44:47 LTE-2X chip-proxy: ONT yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) disconnected (OLT0[0])
Jan 11 08:45:17 LTE-2X chip-proxy: ONT yy:yy:yy:yy:2A:08 is allocated by link yy:yy:yy:yy:2A:08
Jan 11 08:45:22 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:2A:08 create new path(8352) failed(response->header.rcode 4)
Jan 11 08:45:22 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) link 0 failed
Jan 11 08:45:22 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) configure failed
Jan 11 08:50:34 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:2A:08 in state (CFGFAILED) force rediscovery by timeout started
Jan 11 08:50:34 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:2A:08 reconfiguration initialized
Jan 11 08:50:35 LTE-2X chip-proxy: ONT yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) disconnected (OLT0[0])
Jan 11 08:50:37 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:08 (desc: none) in REPORTTIMEOUT state
Jan 11 08:50:37 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:09 (desc: none) in REPORTTIMEOUT state
Jan 11 08:50:37 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:0A (desc: none) in REPORTTIMEOUT state
Jan 11 08:50:37 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:0B (desc: none) in REPORTTIMEOUT state
Jan 11 08:50:49 LTE-2X chip-proxy: ONT yy:yy:yy:yy:2A:08 is allocated by link yy:yy:yy:yy:2A:08
Jan 11 08:50:53 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:2A:08 create new path(8352) failed(response->header.rcode 4)
Jan 11 08:50:53 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) link 0 failed
Jan 11 08:50:53 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) configure failed
Jan 11 08:55:03 LTE-2X chip-proxy: ONT yy:yy:yy:yy:52:00 is allocated by link yy:yy:yy:yy:52:00
Jan 11 08:55:07 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:52:00 create new path(8354) failed(response->header.rcode 4)
Jan 11 08:55:07 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) link 0 failed
Jan 11 08:55:07 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) configure failed
Jan 11 08:56:04 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:2A:08 in state (CFGFAILED) force rediscovery by timeout started
Jan 11 08:56:04 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:2A:08 reconfiguration initialized
Jan 11 08:56:05 LTE-2X chip-proxy: ONT yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) disconnected (OLT0[0])
Jan 11 08:56:07 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:08 (desc: none) in REPORTTIMEOUT state
Jan 11 08:56:07 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:09 (desc: none) in REPORTTIMEOUT state
Jan 11 08:56:07 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:0A (desc: none) in REPORTTIMEOUT state
Jan 11 08:56:07 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:0B (desc: none) in REPORTTIMEOUT state
Jan 11 08:56:19 LTE-2X chip-proxy: ONT yy:yy:yy:yy:2A:08 is allocated by link yy:yy:yy:yy:2A:08
Jan 11 08:56:23 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:2A:08 create new path(8352) failed(response->header.rcode 4)
Jan 11 08:56:23 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) link 0 failed
Jan 11 08:56:23 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) configure failed
Jan 11 09:00:19 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:52:00 in state (CFGFAILED) force rediscovery by timeout started
Jan 11 09:00:19 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:52:00 reconfiguration initialized
Jan 11 09:00:20 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) in REPORTTIMEOUT state
Jan 11 09:00:20 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:01 (desc: vl109-Zakatn-61) in REPORTTIMEOUT state
Jan 11 09:00:20 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:02 (desc: vl109-Zakatn-61) in REPORTTIMEOUT state
Jan 11 09:00:20 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:03 (desc: vl109-Zakatn-61) in REPORTTIMEOUT state
Jan 11 09:00:20 LTE-2X chip-proxy: ONT yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) disconnected (OLT0[0])
Jan 11 09:00:54 LTE-2X chip-proxy: ONT yy:yy:yy:yy:52:00 is allocated by link yy:yy:yy:yy:52:00
Jan 11 09:00:58 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:52:00 create new path(8354) failed(response->header.rcode 4)
Jan 11 09:00:58 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) link 0 failed
Jan 11 09:00:58 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) configure failed
Jan 11 09:01:35 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:2A:08 in state (CFGFAILED) force rediscovery by timeout started
Jan 11 09:01:35 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:2A:08 reconfiguration initialized
Jan 11 09:01:36 LTE-2X chip-proxy: ONT yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) disconnected (OLT0[0])
Jan 11 09:01:37 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:08 (desc: none) in REPORTTIMEOUT state
Jan 11 09:01:37 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:09 (desc: none) in REPORTTIMEOUT state
Jan 11 09:01:37 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:0A (desc: none) in REPORTTIMEOUT state
Jan 11 09:01:37 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:0B (desc: none) in REPORTTIMEOUT state
Jan 11 09:01:49 LTE-2X chip-proxy: ONT yy:yy:yy:yy:2A:08 is allocated by link yy:yy:yy:yy:2A:08
Jan 11 09:01:54 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:2A:08 create new path(8352) failed(response->header.rcode 4)
Jan 11 09:01:54 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) link 0 failed
Jan 11 09:01:54 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) configure failed
Jan 11 09:06:10 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:52:00 in state (CFGFAILED) force rediscovery by timeout started
Jan 11 09:06:10 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:52:00 reconfiguration initialized
Jan 11 09:06:11 LTE-2X chip-proxy: ONT yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) disconnected (OLT0[0])
Jan 11 09:06:12 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:00 (desc: none) in REPORTTIMEOUT state
Jan 11 09:06:12 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:01 (desc: none) in REPORTTIMEOUT state
Jan 11 09:06:12 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:02 (desc: none) in REPORTTIMEOUT state
Jan 11 09:06:12 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:03 (desc: none) in REPORTTIMEOUT state
Jan 11 09:06:24 LTE-2X chip-proxy: ONT yy:yy:yy:yy:52:00 is allocated by link yy:yy:yy:yy:52:00
Jan 11 09:06:27 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:52:00 create new path(8354) failed(response->header.rcode 4)
Jan 11 09:06:27 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) link 0 failed
Jan 11 09:06:28 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) configure failed
Jan 11 09:07:06 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:2A:08 in state (CFGFAILED) force rediscovery by timeout started
Jan 11 09:07:06 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:2A:08 reconfiguration initialized
Jan 11 09:07:07 LTE-2X chip-proxy: ONT yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) disconnected (OLT0[0])
Jan 11 09:07:08 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:08 (desc: none) in REPORTTIMEOUT state
Jan 11 09:07:08 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:09 (desc: none) in REPORTTIMEOUT state
Jan 11 09:07:08 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:0A (desc: none) in REPORTTIMEOUT state
Jan 11 09:07:08 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:0B (desc: none) in REPORTTIMEOUT state
Jan 11 09:07:20 LTE-2X chip-proxy: ONT yy:yy:yy:yy:2A:08 is allocated by link yy:yy:yy:yy:2A:08
Jan 11 09:07:24 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:2A:08 create new path(8352) failed(response->header.rcode 4)
Jan 11 09:07:24 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) link 0 failed
Jan 11 09:07:24 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) configure failed
Jan 11 09:09:39 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) in REPORTTIMEOUT state
Jan 11 09:09:39 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:03 (desc: vl109-Zakatn-61) in REPORTTIMEOUT state
Jan 11 09:09:39 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:01 (desc: vl109-Zakatn-61) in REPORTTIMEOUT state
Jan 11 09:09:39 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:02 (desc: vl109-Zakatn-61) in REPORTTIMEOUT state
Jan 11 09:09:40 LTE-2X chip-proxy: ONT yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) disconnected (OLT0[0])
Jan 11 09:10:11 LTE-2X chip-proxy: ONT yy:yy:yy:yy:52:00 is allocated by link yy:yy:yy:yy:52:00
Jan 11 09:10:15 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:52:00 create new path(8354) failed(response->header.rcode 4)
Jan 11 09:10:15 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) link 0 failed
Jan 11 09:10:15 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) configure failed
Jan 11 09:12:37 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:2A:08 in state (CFGFAILED) force rediscovery by timeout started
Jan 11 09:12:37 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:2A:08 reconfiguration initialized
Jan 11 09:12:38 LTE-2X chip-proxy: ONT yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) disconnected (OLT0[0])
Jan 11 09:12:39 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:08 (desc: none) in REPORTTIMEOUT state
Jan 11 09:12:39 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:09 (desc: none) in REPORTTIMEOUT state
Jan 11 09:12:39 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:0A (desc: none) in REPORTTIMEOUT state
Jan 11 09:12:39 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:0B (desc: none) in REPORTTIMEOUT state
Jan 11 09:12:51 LTE-2X chip-proxy: ONT yy:yy:yy:yy:2A:08 is allocated by link yy:yy:yy:yy:2A:08
Jan 11 09:12:55 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:2A:08 create new path(8352) failed(response->header.rcode 4)
Jan 11 09:12:55 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) link 0 failed
Jan 11 09:12:55 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) configure failed
Jan 11 09:15:26 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:52:00 in state (CFGFAILED) force rediscovery by timeout started
Jan 11 09:15:26 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:52:00 reconfiguration initialized
Jan 11 09:15:27 LTE-2X chip-proxy: ONT yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) disconnected (OLT0[0])
Jan 11 09:15:28 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:00 (desc: none) in REPORTTIMEOUT state
Jan 11 09:15:28 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:01 (desc: none) in REPORTTIMEOUT state
Jan 11 09:15:28 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:02 (desc: none) in REPORTTIMEOUT state
Jan 11 09:15:28 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:03 (desc: none) in REPORTTIMEOUT state
Jan 11 09:15:40 LTE-2X chip-proxy: ONT yy:yy:yy:yy:52:00 is allocated by link yy:yy:yy:yy:52:00
Jan 11 09:15:44 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:52:00 create new path(8354) failed(response->header.rcode 4)
Jan 11 09:15:44 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) link 0 failed
Jan 11 09:15:44 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) configure failed
Jan 11 09:18:07 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:2A:08 in state (CFGFAILED) force rediscovery by timeout started
Jan 11 09:18:07 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:2A:08 reconfiguration initialized
Jan 11 09:18:08 LTE-2X chip-proxy: ONT yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) disconnected (OLT0[0])
Jan 11 09:18:08 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:08 (desc: none) in REPORTTIMEOUT state
Jan 11 09:18:08 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:09 (desc: none) in REPORTTIMEOUT state
Jan 11 09:18:08 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:0A (desc: none) in REPORTTIMEOUT state
Jan 11 09:18:08 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:0B (desc: none) in REPORTTIMEOUT state
Jan 11 09:18:21 LTE-2X chip-proxy: ONT yy:yy:yy:yy:2A:08 is allocated by link yy:yy:yy:yy:2A:08
Jan 11 09:18:24 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:2A:08 create new path(8352) failed(response->header.rcode 4)
Jan 11 09:18:24 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) link 0 failed
Jan 11 09:18:24 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) configure failed
Jan 11 09:20:56 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:52:00 in state (CFGFAILED) force rediscovery by timeout started
Jan 11 09:20:56 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:52:00 reconfiguration initialized
Jan 11 09:20:57 LTE-2X chip-proxy: ONT yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) disconnected (OLT0[0])
Jan 11 09:20:57 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:00 (desc: none) in REPORTTIMEOUT state
Jan 11 09:20:57 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:01 (desc: none) in REPORTTIMEOUT state
Jan 11 09:20:57 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:02 (desc: none) in REPORTTIMEOUT state
Jan 11 09:20:57 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:03 (desc: none) in REPORTTIMEOUT state
Jan 11 09:21:10 LTE-2X chip-proxy: ONT yy:yy:yy:yy:52:00 is allocated by link yy:yy:yy:yy:52:00
Jan 11 09:21:13 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:52:00 create new path(8354) failed(response->header.rcode 4)
Jan 11 09:21:13 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) link 0 failed
Jan 11 09:21:13 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) configure failed
Jan 11 09:23:36 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:2A:08 in state (CFGFAILED) force rediscovery by timeout started
Jan 11 09:23:36 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:2A:08 reconfiguration initialized
Jan 11 09:23:37 LTE-2X chip-proxy: ONT yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) disconnected (OLT0[0])
Jan 11 09:23:38 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:08 (desc: none) in REPORTTIMEOUT state
Jan 11 09:23:38 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:09 (desc: none) in REPORTTIMEOUT state
Jan 11 09:23:38 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:0A (desc: none) in REPORTTIMEOUT state
Jan 11 09:23:38 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:0B (desc: none) in REPORTTIMEOUT state
Jan 11 09:23:51 LTE-2X chip-proxy: ONT yy:yy:yy:yy:2A:08 is allocated by link yy:yy:yy:yy:2A:08
Jan 11 09:23:54 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:2A:08 create new path(8352) failed(response->header.rcode 4)
Jan 11 09:23:54 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) link 0 failed
Jan 11 09:23:54 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) configure failed
Jan 11 09:26:14 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) in REPORTTIMEOUT state
Jan 11 09:26:14 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:01 (desc: vl109-Zakatn-61) in REPORTTIMEOUT state
Jan 11 09:26:14 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:02 (desc: vl109-Zakatn-61) in REPORTTIMEOUT state
Jan 11 09:26:14 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:03 (desc: vl109-Zakatn-61) in REPORTTIMEOUT state
Jan 11 09:26:15 LTE-2X chip-proxy: ONT yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) disconnected (OLT0[0])
Jan 11 09:28:43 LTE-2X chip-proxy: ONT yy:yy:yy:yy:52:00 is allocated by link yy:yy:yy:yy:52:00
Jan 11 09:28:46 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:52:00 create new path(8354) failed(response->header.rcode 4)
Jan 11 09:28:46 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) link 0 failed
Jan 11 09:28:46 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) configure failed
Jan 11 09:29:06 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:2A:08 in state (CFGFAILED) force rediscovery by timeout started
Jan 11 09:29:06 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:2A:08 reconfiguration initialized
Jan 11 09:29:07 LTE-2X chip-proxy: ONT yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) disconnected (OLT0[0])
Jan 11 09:29:08 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:08 (desc: none) in REPORTTIMEOUT state
Jan 11 09:29:08 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:09 (desc: none) in REPORTTIMEOUT state
Jan 11 09:29:08 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:0A (desc: none) in REPORTTIMEOUT state
Jan 11 09:29:08 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:0B (desc: none) in REPORTTIMEOUT state
Jan 11 09:29:20 LTE-2X chip-proxy: ONT yy:yy:yy:yy:2A:08 is allocated by link yy:yy:yy:yy:2A:08
Jan 11 09:29:24 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:2A:08 create new path(8352) failed(response->header.rcode 4)
Jan 11 09:29:24 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) link 0 failed
Jan 11 09:29:24 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) configure failed
Jan 11 09:33:58 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:52:00 in state (CFGFAILED) force rediscovery by timeout started
Jan 11 09:33:58 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:52:00 reconfiguration initialized
Jan 11 09:33:59 LTE-2X chip-proxy: ONT yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) disconnected (OLT0[0])
Jan 11 09:34:00 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:00 (desc: none) in REPORTTIMEOUT state
Jan 11 09:34:00 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:01 (desc: none) in REPORTTIMEOUT state
Jan 11 09:34:00 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:02 (desc: none) in REPORTTIMEOUT state
Jan 11 09:34:00 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:03 (desc: none) in REPORTTIMEOUT state
Jan 11 09:34:12 LTE-2X chip-proxy: ONT yy:yy:yy:yy:52:00 is allocated by link yy:yy:yy:yy:52:00
Jan 11 09:34:16 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:52:00 create new path(8354) failed(response->header.rcode 4)
Jan 11 09:34:16 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) link 0 failed
Jan 11 09:34:16 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) configure failed
Jan 11 09:34:36 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:2A:08 in state (CFGFAILED) force rediscovery by timeout started
Jan 11 09:34:36 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:2A:08 reconfiguration initialized
Jan 11 09:34:37 LTE-2X chip-proxy: ONT yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) disconnected (OLT0[0])
Jan 11 09:34:37 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:08 (desc: none) in REPORTTIMEOUT state
Jan 11 09:34:37 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:09 (desc: none) in REPORTTIMEOUT state
Jan 11 09:34:37 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:0A (desc: none) in REPORTTIMEOUT state
Jan 11 09:34:37 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:0B (desc: none) in REPORTTIMEOUT state
Jan 11 09:34:50 LTE-2X chip-proxy: ONT yy:yy:yy:yy:2A:08 is allocated by link yy:yy:yy:yy:2A:08
Jan 11 09:34:53 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:2A:08 create new path(8352) failed(response->header.rcode 4)
Jan 11 09:34:53 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) link 0 failed
Jan 11 09:34:53 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) configure failed
Jan 11 09:39:28 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:52:00 in state (CFGFAILED) force rediscovery by timeout started
Jan 11 09:39:28 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:52:00 reconfiguration initialized
Jan 11 09:39:29 LTE-2X chip-proxy: ONT yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) disconnected (OLT0[0])
Jan 11 09:39:30 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:00 (desc: none) in REPORTTIMEOUT state
Jan 11 09:39:30 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:01 (desc: none) in REPORTTIMEOUT state
Jan 11 09:39:30 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:02 (desc: none) in REPORTTIMEOUT state
Jan 11 09:39:30 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:03 (desc: none) in REPORTTIMEOUT state
Jan 11 09:39:42 LTE-2X chip-proxy: ONT yy:yy:yy:yy:52:00 is allocated by link yy:yy:yy:yy:52:00
Jan 11 09:39:46 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:52:00 create new path(8354) failed(response->header.rcode 4)
Jan 11 09:39:46 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) link 0 failed
Jan 11 09:39:46 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) configure failed
Jan 11 09:40:05 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:2A:08 in state (CFGFAILED) force rediscovery by timeout started
Jan 11 09:40:05 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:2A:08 reconfiguration initialized
Jan 11 09:40:06 LTE-2X chip-proxy: ONT yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) disconnected (OLT0[0])
Jan 11 09:40:07 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:08 (desc: none) in REPORTTIMEOUT state
Jan 11 09:40:07 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:09 (desc: none) in REPORTTIMEOUT state
Jan 11 09:40:07 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:0A (desc: none) in REPORTTIMEOUT state
Jan 11 09:40:07 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:0B (desc: none) in REPORTTIMEOUT state
Jan 11 09:40:19 LTE-2X chip-proxy: ONT yy:yy:yy:yy:2A:08 is allocated by link yy:yy:yy:yy:2A:08
Jan 11 09:40:23 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:2A:08 create new path(8352) failed(response->header.rcode 4)
Jan 11 09:40:23 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) link 0 failed
Jan 11 09:40:23 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) configure failed
Jan 11 09:44:58 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:52:00 in state (CFGFAILED) force rediscovery by timeout started
Jan 11 09:44:58 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:52:00 reconfiguration initialized
Jan 11 09:44:59 LTE-2X chip-proxy: ONT yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) disconnected (OLT0[0])
Jan 11 09:44:59 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:00 (desc: none) in REPORTTIMEOUT state
Jan 11 09:44:59 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:01 (desc: none) in REPORTTIMEOUT state
Jan 11 09:44:59 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:02 (desc: none) in REPORTTIMEOUT state
Jan 11 09:44:59 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:03 (desc: none) in REPORTTIMEOUT state
Jan 11 09:45:12 LTE-2X chip-proxy: ONT yy:yy:yy:yy:52:00 is allocated by link yy:yy:yy:yy:52:00
Jan 11 09:45:22 LTE-2X chip-proxy: eapframe_handler: ONU yy:yy:yy:yy:52:00 are in AUTHFAILED state
Jan 11 09:45:35 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:2A:08 in state (CFGFAILED) force rediscovery by timeout started
Jan 11 09:45:35 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:2A:08 reconfiguration initialized
Jan 11 09:45:36 LTE-2X chip-proxy: ONT yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) disconnected (OLT0[0])
Jan 11 09:45:37 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:08 (desc: none) in REPORTTIMEOUT state
Jan 11 09:45:37 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:09 (desc: none) in REPORTTIMEOUT state
Jan 11 09:45:37 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:0A (desc: none) in REPORTTIMEOUT state
Jan 11 09:45:37 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:0B (desc: none) in REPORTTIMEOUT state
Jan 11 09:45:49 LTE-2X chip-proxy: ONT yy:yy:yy:yy:2A:08 is allocated by link yy:yy:yy:yy:2A:08
Jan 11 09:45:53 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:2A:08 create new path(8352) failed(response->header.rcode 4)
Jan 11 09:45:53 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) link 0 failed
Jan 11 09:45:53 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) configure failed
Jan 11 09:50:33 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:52:00 in state (AUTHFAILED) force rediscovery by timeout started
Jan 11 09:50:33 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:52:00 reconfiguration initialized
Jan 11 09:50:34 LTE-2X chip-proxy: ONT yy:yy:yy:yy:52:00 (desc: ) disconnected (OLT0[0])
Jan 11 09:50:35 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:00 (desc: none) in REPORTTIMEOUT state
Jan 11 09:50:35 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:01 (desc: none) in REPORTTIMEOUT state
Jan 11 09:50:35 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:02 (desc: none) in REPORTTIMEOUT state
Jan 11 09:50:35 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:03 (desc: none) in REPORTTIMEOUT state
Jan 11 09:50:48 LTE-2X chip-proxy: ONT yy:yy:yy:yy:52:00 is allocated by link yy:yy:yy:yy:52:00
Jan 11 09:50:51 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:52:00 create new path(8354) failed(response->header.rcode 4)
Jan 11 09:50:51 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) link 0 failed
Jan 11 09:50:51 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) configure failed
Jan 11 09:51:05 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:2A:08 in state (CFGFAILED) force rediscovery by timeout started
Jan 11 09:51:05 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:2A:08 reconfiguration initialized
Jan 11 09:51:06 LTE-2X chip-proxy: ONT yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) disconnected (OLT0[0])
Jan 11 09:51:07 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:08 (desc: none) in REPORTTIMEOUT state
Jan 11 09:51:07 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:09 (desc: none) in REPORTTIMEOUT state
Jan 11 09:51:07 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:0A (desc: none) in REPORTTIMEOUT state
Jan 11 09:51:07 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:0B (desc: none) in REPORTTIMEOUT state
Jan 11 09:51:19 LTE-2X chip-proxy: ONT yy:yy:yy:yy:2A:08 is allocated by link yy:yy:yy:yy:2A:08
Jan 11 09:51:23 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:2A:08 create new path(8352) failed(response->header.rcode 4)
Jan 11 09:51:23 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) link 0 failed
Jan 11 09:51:23 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) configure failed
Jan 11 09:56:03 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:52:00 in state (CFGFAILED) force rediscovery by timeout started
Jan 11 09:56:03 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:52:00 reconfiguration initialized
Jan 11 09:56:04 LTE-2X chip-proxy: ONT yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) disconnected (OLT0[0])
Jan 11 09:56:05 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:00 (desc: none) in REPORTTIMEOUT state
Jan 11 09:56:05 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:01 (desc: none) in REPORTTIMEOUT state
Jan 11 09:56:05 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:02 (desc: none) in REPORTTIMEOUT state
Jan 11 09:56:05 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:03 (desc: none) in REPORTTIMEOUT state
Jan 11 09:56:17 LTE-2X chip-proxy: ONT yy:yy:yy:yy:52:00 is allocated by link yy:yy:yy:yy:52:00
Jan 11 09:56:21 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:52:00 create new path(8354) failed(response->header.rcode 4)
Jan 11 09:56:21 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) link 0 failed
Jan 11 09:56:21 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) configure failed
Jan 11 09:56:35 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:2A:08 in state (CFGFAILED) force rediscovery by timeout started
Jan 11 09:56:35 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:2A:08 reconfiguration initialized
Jan 11 09:56:36 LTE-2X chip-proxy: ONT yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) disconnected (OLT0[0])
Jan 11 09:56:37 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:08 (desc: none) in REPORTTIMEOUT state
Jan 11 09:56:37 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:09 (desc: none) in REPORTTIMEOUT state
Jan 11 09:56:37 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:0A (desc: none) in REPORTTIMEOUT state
Jan 11 09:56:37 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:0B (desc: none) in REPORTTIMEOUT state
Jan 11 09:56:50 LTE-2X chip-proxy: ONT yy:yy:yy:yy:2A:08 is allocated by link yy:yy:yy:yy:2A:08
Jan 11 09:56:54 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:2A:08 create new path(8352) failed(response->header.rcode 4)
Jan 11 09:56:54 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) link 0 failed
Jan 11 09:56:54 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) configure failed
Jan 11 10:01:33 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:52:00 in state (CFGFAILED) force rediscovery by timeout started
Jan 11 10:01:33 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:52:00 reconfiguration initialized
Jan 11 10:01:34 LTE-2X chip-proxy: ONT yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) disconnected (OLT0[0])
Jan 11 10:01:35 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:00 (desc: none) in REPORTTIMEOUT state
Jan 11 10:01:35 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:01 (desc: none) in REPORTTIMEOUT state
Jan 11 10:01:35 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:02 (desc: none) in REPORTTIMEOUT state
Jan 11 10:01:35 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:03 (desc: none) in REPORTTIMEOUT state
Jan 11 10:01:47 LTE-2X telnetd: pam_unix(login:session): session opened for user xxxxx by xxxxx(uid=0)
Jan 11 10:01:47 LTE-2X telnetd: Accepted password for xxxxx from xxx.xxx.xxx.xxx
Jan 11 10:01:47 LTE-2X chip-proxy: ONT yy:yy:yy:yy:52:00 is allocated by link yy:yy:yy:yy:52:00
Jan 11 10:01:51 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:52:00 create new path(8354) failed(response->header.rcode 4)
Jan 11 10:01:51 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) link 0 failed
Jan 11 10:01:51 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) configure failed
Jan 11 10:02:06 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:2A:08 in state (CFGFAILED) force rediscovery by timeout started
Jan 11 10:02:06 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:2A:08 reconfiguration initialized
Jan 11 10:02:07 LTE-2X chip-proxy: ONT yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) disconnected (OLT0[0])
Jan 11 10:02:08 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:08 (desc: none) in REPORTTIMEOUT state
Jan 11 10:02:08 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:09 (desc: none) in REPORTTIMEOUT state
Jan 11 10:02:08 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:0A (desc: none) in REPORTTIMEOUT state
Jan 11 10:02:08 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:2A:0B (desc: none) in REPORTTIMEOUT state
Jan 11 10:02:10 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) in REPORTTIMEOUT state
Jan 11 10:02:10 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:03 (desc: vl109-Zakatn-61) in REPORTTIMEOUT state
Jan 11 10:02:10 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:01 (desc: vl109-Zakatn-61) in REPORTTIMEOUT state
Jan 11 10:02:10 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:52:02 (desc: vl109-Zakatn-61) in REPORTTIMEOUT state
Jan 11 10:02:10 LTE-2X chip-proxy: ONT yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) disconnected (OLT0[0])
Jan 11 10:02:21 LTE-2X chip-proxy: ONT yy:yy:yy:yy:2A:08 is allocated by link yy:yy:yy:yy:2A:08
Jan 11 10:02:26 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:2A:08 create new path(8352) failed(response->header.rcode 4)
Jan 11 10:02:26 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) link 0 failed
Jan 11 10:02:26 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) configure failed
Jan 11 10:02:40 LTE-2X chip-proxy: ONT yy:yy:yy:yy:52:00 is allocated by link yy:yy:yy:yy:52:00
Jan 11 10:02:44 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:52:00 create new path(8354) failed(response->header.rcode 4)
Jan 11 10:02:44 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) link 0 failed
Jan 11 10:02:44 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) configure failed
Jan 11 10:02:59 LTE-2X switchd: %DISPATCH-EVT: Transmit event <18> to service SERVICE PSTATE CHECK
Jan 11 10:02:59 LTE-2X switchd: %LINK-UPDOWN: Port mgmt-pon-port 0: link down
Jan 11 10:02:59 LTE-2X switchd: %LINK-UPDOWN: Port mgmt-pon-port 0: link down
Jan 11 10:02:59 LTE-2X switchd: %DISPATCH-EVT: Transmit event <17> to service SERVICE_LACP
Jan 11 10:03:01 LTE-2X switchd: %DISPATCH-EVT: Transmit event <18> to service SERVICE PSTATE CHECK
Jan 11 10:03:01 LTE-2X switchd: %LINK-UPDOWN: Port mgmt-pon-port 0: link up, speed 100M, full-duplex
Jan 11 10:03:01 LTE-2X switchd: %LINK-UPDOWN: Port mgmt-pon-port 0: link up, speed 100M, full-duplex
Jan 11 10:03:01 LTE-2X switchd: %DISPATCH-EVT: Transmit event <17> to service SERVICE_LACP
Jan 11 10:03:10 LTE-2X chip-proxy: oltfwupdate_handler: OLT[0] in RESETINPROGRESS state
Jan 11 10:03:11 LTE-2X chip-proxy: profiler_olt_reconfigure: config received
Jan 11 10:03:11 LTE-2X chip-proxy: OLT0[0] DRSSI feature enabled. SFP tranceiver LTE3680M-BC   
Jan 11 10:03:12 LTE-2X chip-proxy: OLT0[1] DRSSI feature enabled. SFP tranceiver LTE3680M-BC   
Jan 11 10:03:12 LTE-2X chip-proxy: profiler_olt_reconfigure: OLT[0] in OK state
Jan 11 10:03:18 LTE-2X chip-proxy: ONT yy:yy:yy:yy:19:3C is allocated by link yy:yy:yy:yy:19:3C
Jan 11 10:03:18 LTE-2X chip-proxy: ONT yy:yy:yy:yy:52:00 is allocated by link yy:yy:yy:yy:52:00
Jan 11 10:03:18 LTE-2X chip-proxy: ONT yy:yy:yy:yy:57:34 is allocated by link yy:yy:yy:yy:57:34
Jan 11 10:03:18 LTE-2X chip-proxy: ONT yy:yy:yy:yy:53:28 is allocated by link yy:yy:yy:yy:53:28
Jan 11 10:03:18 LTE-2X chip-proxy: ONT yy:yy:yy:yy:33:D4 is allocated by link yy:yy:yy:yy:33:D4
Jan 11 10:03:18 LTE-2X chip-proxy: ONT yy:yy:yy:yy:2A:08 is allocated by link yy:yy:yy:yy:2A:08
Jan 11 10:03:18 LTE-2X chip-proxy: ONT yy:yy:yy:yy:4C:9C is allocated by link yy:yy:yy:yy:4C:9C
Jan 11 10:03:18 LTE-2X chip-proxy: ONT yy:yy:yy:yy:4E:54 is allocated by link yy:yy:yy:yy:4E:54
Jan 11 10:03:18 LTE-2X chip-proxy: ONT yy:yy:yy:yy:1B:8C is allocated by link yy:yy:yy:yy:1B:8C
Jan 11 10:03:19 LTE-2X chip-proxy: ONT yy:yy:yy:yy:4D:44 is allocated by link yy:yy:yy:yy:4D:44
Jan 11 10:03:20 LTE-2X chip-proxy: ONT yy:yy:yy:yy:55:2C is allocated by link yy:yy:yy:yy:55:2C
Jan 11 10:03:20 LTE-2X chip-proxy: ONT yy:yy:yy:yy:1A:1C is allocated by link yy:yy:yy:yy:1A:1C
Jan 11 10:03:20 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC is allocated by link yy:yy:yy:yy:34:AC
Jan 11 10:03:20 LTE-2X chip-proxy: ONT yy:yy:yy:yy:4D:6C is allocated by link yy:yy:yy:yy:4D:6C
Jan 11 10:03:20 LTE-2X chip-proxy: ONT yy:yy:yy:yy:39:6C is allocated by link yy:yy:yy:yy:39:6C
Jan 11 10:03:20 LTE-2X chip-proxy: ONT yy:yy:yy:yy:3A:A8 is allocated by link yy:yy:yy:yy:3A:A8
Jan 11 10:03:20 LTE-2X chip-proxy: ONT yy:yy:yy:yy:53:30 is allocated by link yy:yy:yy:yy:53:30
Jan 11 10:03:23 LTE-2X chip-proxy: ONT yy:yy:yy:yy:4E:54 (desc: vl113-Znakom-192-5) configure ok (OLT0[1])
Jan 11 10:03:26 LTE-2X chip-proxy: ONT yy:yy:yy:yy:4D:44 (desc: vl106-Znakom-162) configure ok (OLT0[0])
Jan 11 10:03:28 LTE-2X chip-proxy: ONT yy:yy:yy:yy:2A:08 (desc: vl110-Znakom-177-3) configure ok (OLT0[0])
Jan 11 10:03:31 LTE-2X chip-proxy: ONT yy:yy:yy:yy:19:3C (desc: vl112-Zapoved-156-9) configure ok (OLT0[1])
Jan 11 10:03:33 LTE-2X chip-proxy: ONT yy:yy:yy:yy:57:34 (desc: vl104-Biolog-11-49) configure ok (OLT0[0])
Jan 11 10:03:36 LTE-2X chip-proxy: ONT yy:yy:yy:yy:4C:9C (desc: vl115-Pestr-696) configure ok (OLT0[0])
Jan 11 10:03:38 LTE-2X chip-proxy: ONT yy:yy:yy:yy:33:D4 (desc: vl108-Lazurn-7-9) configure ok (OLT0[0])
Jan 11 10:03:41 LTE-2X chip-proxy: ONT yy:yy:yy:yy:39:6C (desc: vl111-Zakatn-954) configure ok (OLT0[0])
Jan 11 10:03:43 LTE-2X chip-proxy: ONT yy:yy:yy:yy:3A:A8 (desc: vl101-Lazurn-28-58) configure ok (OLT0[0])
Jan 11 10:03:46 LTE-2X chip-proxy: ONT yy:yy:yy:yy:52:00 (desc: vl109-Zakatn-61) configure ok (OLT0[0])
Jan 11 10:03:48 LTE-2X chip-proxy: ONT yy:yy:yy:yy:4D:6C (desc: vl103-Biolog-16) configure ok (OLT0[0])
Jan 11 10:03:51 LTE-2X chip-proxy: ONT yy:yy:yy:yy:1A:1C (desc: vl102-Zakatn-13a) configure ok (OLT0[0])
Jan 11 10:03:53 LTE-2X chip-proxy: ONT yy:yy:yy:yy:1B:8C (desc: vl105-Biolog-10) configure ok (OLT0[0])
Jan 11 10:03:56 LTE-2X chip-proxy: ONT yy:yy:yy:yy:53:28 (desc: vl116-Pestr-1091) configure ok (OLT0[0])
Jan 11 10:03:58 LTE-2X switchd: %DHCP-RELAY: parse error 1
Jan 11 10:03:58 LTE-2X switchd: %DHCP-RELAY: parse error 1
Jan 11 10:03:58 LTE-2X chip-proxy: ONT yy:yy:yy:yy:53:30 (desc: vl114-Zakatn-925) configure ok (OLT0[0])
Jan 11 10:04:01 LTE-2X chip-proxy: ONT yy:yy:yy:yy:55:2C (desc: vl100-Zakatn-60) configure ok (OLT0[0])
Jan 11 10:04:02 LTE-2X switchd: %DHCP-RELAY: parse error 1
Jan 11 10:04:02 LTE-2X switchd: %DHCP-RELAY: parse error 1
Jan 11 10:04:04 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) configure ok (OLT0[0])
Jan 11 10:04:15 LTE-2X switchd: %DHCP-RELAY: parse error 1
Jan 11 10:05:04 LTE-2X last message repeated 10 times

[Dirks G]

Добрый день.

Каковы результаты наблюдений? Покажите профиль Rules, Path, Ports который назначен на эти NTE.

[DGM]

Проблемную NTE-2 заменил на другую, заодно поменял правила(снятие-добавление тэга локально). Пока норма. Профиль Rules, Path, Ports - дефолтный.

Код: Выделить всё

LTE-2x_1(ONT-x/1010/yy:yy:yy:yy:21:70)# show config
Channel/ID: x/1010   MAC: yy:yy:yy:yy:21:70  Type: NTE-2         
(OLT: x Port: x)
Secret: 1234
Description: vl110-Znakom-177-3
ONU    block: no
UNI0   block: no
UNI1   block: no
RF out block: n/a
Rules profile:        0      Default profile
Shaper profile:       0      Default profile
IP multicast profile: 0      Default profile
Ports profile:        0      Default profile
Paths profile:        0      Default profile
Additional network parameters:
Alternative ethertype: 0x88A8
Use for upstream:  no  Use for downstream:  no
LTE-2x_1(ONT-x/1010/yy:yy:yy:yy:21:70)# rule show pon
 0) 5: if (VID == 110) then DeleteTag *Local*
 1) 14: if (LinkIndex == 0x0) then path = port 0 queue 0; forward *Profile*
 2) 14: if (LinkIndex == 0x1) then path = port 0 queue 1; forward *Profile*
 3) 14: if (LinkIndex == 0x2) then path = port 1 queue 0; forward *Profile*
 4) 14: if (LinkIndex == 0x3) then path = port 1 queue 1; forward *Profile*
LTE-2x_1(ONT-x/1010/yy:yy:yy:yy:21:70)# rule show uni0
 0) 5: if (Always) then AddTagVID = 110 *Local*
 1) 14: if (Always) then path = link 0 queue 0; forward *Profile*
LTE-2x_1(ONT-x/1010/yy:yy:yy:yy:21:70)# rule show uni1
 0) 14: if (Always) then path = link 2 queue 0; forward *Profile*

Теперь другая NTE-2 отваливается(снятие-добавление тэга профилем). Профиль Path, Ports - дефолтный.
Конфигурация

Код: Выделить всё

LTE-2x_1(ONT-x/1007/yy:yy:yy:yy:34:AC)# show config
Channel/ID: x/1007   MAC: yy:yy:yy:yy:34:AC  Type: NTE-2         
(OLT: x Port: x)
Secret: 1234
Description: vl107-Zakatn-39
ONU    block: no
UNI0   block: no
UNI1   block: no
RF out block: n/a
Rules profile:        8      vlan107
Shaper profile:       0      Default profile
IP multicast profile: 0      Default profile
Ports profile:        0      Default profile
Paths profile:        0      Default profile
Additional network parameters:
Alternative ethertype: 0x88A8
Use for upstream:  no  Use for downstream:  no
LTE-2x_1(ONT-x/1007/yy:yy:yy:yy:34:AC)# rule show pon
 0) 5: if (VID == 107) then DeleteTag *Profile*
 1) 14: if (LinkIndex == 0x0) then path = port 0 queue 0; forward *Profile*
 2) 14: if (LinkIndex == 0x1) then path = port 0 queue 1; forward *Profile*
 3) 14: if (LinkIndex == 0x2) then path = port 1 queue 0; forward *Profile*
 4) 14: if (LinkIndex == 0x3) then path = port 1 queue 1; forward *Profile*
LTE-2x_1(ONT-x/1007/yy:yy:yy:yy:34:AC)# rule show uni0
 0) 5: if (Always) then AddTagVID = 107 *Profile*
 1) 14: if (Always) then path = link 0 queue 0; forward *Profile*
LTE-2x_1(ONT-x/1007/yy:yy:yy:yy:34:AC)# rule show uni1
 0) 14: if (Always) then path = link 2 queue 0; forward *Profile*
LTE-2x_1(profile-rules)# show information
Index:   8
Description: vlan107
LTE-2x_1(profile-rules)# rule show pon
 0) 5: if (VID == 107) then DeleteTag
 1) 14: if (LinkIndex == 0x0) then path = port 0 queue 0; forward
 2) 14: if (LinkIndex == 0x1) then path = port 0 queue 1; forward
 3) 14: if (LinkIndex == 0x2) then path = port 1 queue 0; forward
 4) 14: if (LinkIndex == 0x3) then path = port 1 queue 1; forward
LTE-2x_1(profile-rules)# rule show uni0
 0) 5: if (Always) then AddTagVID = 107
 1) 14: if (Always) then path = link 0 queue 0; forward
LTE-2x_1(profile-rules)# rule show uni1
 0) 14: if (Always) then path = link 2 queue 0; forward

Лог (возникновение проблемы-решение реконфигом OLT):

Код: Выделить всё

LTE-2x_1# log search Jan 12
Jan 12 10:49:43 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) configure ok (OLT0[0])
Jan 12 10:49:06 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC is allocated by link yy:yy:yy:yy:34:AC
Jan 12 10:48:59 LTE-2X chip-proxy: profiler_olt_reconfigure: OLT[0] in OK state
Jan 12 10:48:58 LTE-2X chip-proxy: OLT0[1] DRSSI feature enabled. SFP tranceiver LTE3680M-BC   
Jan 12 10:48:57 LTE-2X chip-proxy: OLT0[0] DRSSI feature enabled. SFP tranceiver LTE3680M-BC   
Jan 12 10:48:56 LTE-2X chip-proxy: profiler_olt_reconfigure: config received
Jan 12 10:48:56 LTE-2X chip-proxy: oltfwupdate_handler: OLT[0] in RESETINPROGRESS state
Jan 12 10:48:47 LTE-2X switchd: %DISPATCH-EVT: Transmit event <17> to service SERVICE_LACP
Jan 12 10:48:47 LTE-2X switchd: %LINK-UPDOWN: Port mgmt-pon-port 0: link up, speed 100M, full-duplex
Jan 12 10:48:47 LTE-2X switchd: %LINK-UPDOWN: Port mgmt-pon-port 0: link up, speed 100M, full-duplex
Jan 12 10:48:47 LTE-2X switchd: %DISPATCH-EVT: Transmit event <18> to service SERVICE PSTATE CHECK
Jan 12 10:48:45 LTE-2X switchd: %DISPATCH-EVT: Transmit event <17> to service SERVICE_LACP
Jan 12 10:48:45 LTE-2X switchd: %LINK-UPDOWN: Port mgmt-pon-port 0: link down
Jan 12 10:48:45 LTE-2X switchd: %LINK-UPDOWN: Port mgmt-pon-port 0: link down
Jan 12 10:48:45 LTE-2X switchd: %DISPATCH-EVT: Transmit event <18> to service SERVICE PSTATE CHECK
Jan 12 10:48:30 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) configure failed
Jan 12 10:48:30 LTE-2X chip-proxy: profiler_onu_path_internal: create ONT yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) path 0 failed
Jan 12 10:48:26 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC is allocated by link yy:yy:yy:yy:34:AC
Jan 12 10:48:14 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AF (desc: none) in REPORTTIMEOUT state
Jan 12 10:48:14 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AE (desc: none) in REPORTTIMEOUT state
Jan 12 10:48:14 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AD (desc: none) in REPORTTIMEOUT state
Jan 12 10:48:14 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AC (desc: none) in REPORTTIMEOUT state
Jan 12 10:48:13 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) disconnected (OLT0[0])
Jan 12 10:48:12 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:34:AC reconfiguration initialized
Jan 12 10:48:12 LTE-2X chip-proxy: Got signal for reconfigure ONT-yy:yy:yy:yy:34:AC
Jan 12 10:48:08 LTE-2X chip-proxy: ONT yy:yy:yy:yy:39:6C (desc: vl111-Zakatn-954) configure ok (OLT0[0])
Jan 12 10:48:04 LTE-2X chip-proxy: ONT yy:yy:yy:yy:39:6C is allocated by link yy:yy:yy:yy:39:6C
Jan 12 10:47:09 LTE-2X chip-proxy: ONT yy:yy:yy:yy:39:6C (desc: vl111-Zakatn-954) disconnected (OLT0[0])
Jan 12 10:47:09 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:39:6F (desc: vl111-Zakatn-954) in REPORTTIMEOUT state
Jan 12 10:47:09 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:39:6E (desc: vl111-Zakatn-954) in REPORTTIMEOUT state
Jan 12 10:47:09 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:39:6C (desc: vl111-Zakatn-954) in REPORTTIMEOUT state
Jan 12 10:47:09 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:39:6D (desc: vl111-Zakatn-954) in REPORTTIMEOUT state
Jan 12 10:46:03 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) configure failed
Jan 12 10:46:03 LTE-2X chip-proxy: profiler_onu_path_internal: create ONT yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) path 0 failed 
Jan 12 10:07:40 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) configure failed
Jan 12 10:07:40 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) link 0 failed
Jan 12 10:07:40 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:34:AC create new path(8448) failed(response->header.rcode 4)
Jan 12 10:07:36 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC is allocated by link yy:yy:yy:yy:34:AC
Jan 12 10:07:24 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AF (desc: none) in REPORTTIMEOUT state
Jan 12 10:07:24 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AE (desc: none) in REPORTTIMEOUT state
Jan 12 10:07:24 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AD (desc: none) in REPORTTIMEOUT state
Jan 12 10:07:24 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AC (desc: none) in REPORTTIMEOUT state
Jan 12 10:07:23 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) disconnected (OLT0[0])
Jan 12 10:07:22 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:34:AC reconfiguration initialized
Jan 12 10:07:22 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:34:AC in state (CFGFAILED) force rediscovery by timeout started
Jan 12 10:02:10 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) configure failed
Jan 12 10:02:10 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) link 0 failed
Jan 12 10:02:10 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:34:AC create new path(8448) failed(response->header.rcode 4)
Jan 12 10:02:06 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC is allocated by link yy:yy:yy:yy:34:AC
Jan 12 10:01:54 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AF (desc: none) in REPORTTIMEOUT state
Jan 12 10:01:54 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AE (desc: none) in REPORTTIMEOUT state
Jan 12 10:01:54 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AD (desc: none) in REPORTTIMEOUT state
Jan 12 10:01:54 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AC (desc: none) in REPORTTIMEOUT state
Jan 12 10:01:53 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) disconnected (OLT0[0])
Jan 12 10:01:52 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:34:AC reconfiguration initialized
Jan 12 10:01:52 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:34:AC in state (CFGFAILED) force rediscovery by timeout started
Jan 12 09:56:41 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) configure failed
Jan 12 09:56:41 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) link 0 failed
Jan 12 09:56:41 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:34:AC create new path(8448) failed(response->header.rcode 4)
Jan 12 09:56:37 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC is allocated by link yy:yy:yy:yy:34:AC
Jan 12 09:56:24 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AF (desc: none) in REPORTTIMEOUT state
Jan 12 09:56:24 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AE (desc: none) in REPORTTIMEOUT state
Jan 12 09:56:24 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AD (desc: none) in REPORTTIMEOUT state
Jan 12 09:56:24 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AC (desc: none) in REPORTTIMEOUT state
Jan 12 09:56:24 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) disconnected (OLT0[0])
Jan 12 09:56:22 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:34:AC reconfiguration initialized
Jan 12 09:56:22 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:34:AC in state (CFGFAILED) force rediscovery by timeout started
Jan 12 09:51:10 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) configure failed
Jan 12 09:51:10 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) link 0 failed
Jan 12 09:51:10 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:34:AC create new path(8448) failed(response->header.rcode 4)
Jan 12 09:51:06 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC is allocated by link yy:yy:yy:yy:34:AC
Jan 12 09:50:54 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AF (desc: none) in REPORTTIMEOUT state
Jan 12 09:50:54 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AE (desc: none) in REPORTTIMEOUT state
Jan 12 09:50:54 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AD (desc: none) in REPORTTIMEOUT state
Jan 12 09:50:54 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AC (desc: none) in REPORTTIMEOUT state
Jan 12 09:50:53 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) disconnected (OLT0[0])
Jan 12 09:50:52 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:34:AC reconfiguration initialized
Jan 12 09:50:52 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:34:AC in state (CFGFAILED) force rediscovery by timeout started
Jan 12 09:45:39 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) configure failed
Jan 12 09:45:39 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) link 0 failed
Jan 12 09:45:39 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:34:AC create new path(8448) failed(response->header.rcode 4)
Jan 12 09:45:35 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC is allocated by link yy:yy:yy:yy:34:AC
Jan 12 09:45:23 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AF (desc: none) in REPORTTIMEOUT state
Jan 12 09:45:23 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AE (desc: none) in REPORTTIMEOUT state
Jan 12 09:45:23 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AD (desc: none) in REPORTTIMEOUT state
Jan 12 09:45:23 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AC (desc: none) in REPORTTIMEOUT state
Jan 12 09:45:22 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) disconnected (OLT0[0])
Jan 12 09:45:21 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:34:AC reconfiguration initialized
Jan 12 09:45:21 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:34:AC in state (CFGFAILED) force rediscovery by timeout started
Jan 12 09:40:08 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) configure failed
Jan 12 09:40:08 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) link 0 failed
Jan 12 09:40:08 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:34:AC create new path(8448) failed(response->header.rcode 4)
Jan 12 09:40:04 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC is allocated by link yy:yy:yy:yy:34:AC
Jan 12 09:39:52 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AF (desc: none) in REPORTTIMEOUT state
Jan 12 09:39:52 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AE (desc: none) in REPORTTIMEOUT state
Jan 12 09:39:52 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AD (desc: none) in REPORTTIMEOUT state
Jan 12 09:39:52 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AC (desc: none) in REPORTTIMEOUT state
Jan 12 09:39:51 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) disconnected (OLT0[0])
Jan 12 09:39:50 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:34:AC reconfiguration initialized
Jan 12 09:39:50 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:34:AC in state (CFGFAILED) force rediscovery by timeout started
Jan 12 09:34:38 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) configure failed
Jan 12 09:34:38 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) link 0 failed
Jan 12 09:34:38 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:34:AC create new path(8448) failed(response->header.rcode 4)
Jan 12 09:34:35 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC is allocated by link yy:yy:yy:yy:34:AC
Jan 12 09:34:22 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AF (desc: none) in REPORTTIMEOUT state
Jan 12 09:34:22 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AE (desc: none) in REPORTTIMEOUT state
Jan 12 09:34:22 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AD (desc: none) in REPORTTIMEOUT state
Jan 12 09:34:22 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AC (desc: none) in REPORTTIMEOUT state
Jan 12 09:34:21 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) disconnected (OLT0[0])
Jan 12 09:34:20 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:34:AC reconfiguration initialized
Jan 12 09:34:20 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:34:AC in state (CFGFAILED) force rediscovery by timeout started
Jan 12 09:29:09 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) configure failed
Jan 12 09:29:09 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) link 0 failed
Jan 12 09:29:09 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:34:AC create new path(8448) failed(response->header.rcode 4)
Jan 12 09:29:05 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC is allocated by link yy:yy:yy:yy:34:AC
Jan 12 09:28:53 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AF (desc: none) in REPORTTIMEOUT state
Jan 12 09:28:53 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AE (desc: none) in REPORTTIMEOUT state
Jan 12 09:28:53 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AD (desc: none) in REPORTTIMEOUT state
Jan 12 09:28:53 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AC (desc: none) in REPORTTIMEOUT state
Jan 12 09:28:52 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) disconnected (OLT0[0])
Jan 12 09:28:51 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:34:AC reconfiguration initialized
Jan 12 09:28:51 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:34:AC in state (CFGFAILED) force rediscovery by timeout started
Jan 12 09:23:39 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) configure failed
Jan 12 09:23:39 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) link 0 failed
Jan 12 09:23:39 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:34:AC create new path(8448) failed(response->header.rcode 4)
Jan 12 09:23:35 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC is allocated by link yy:yy:yy:yy:34:AC
Jan 12 09:23:23 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AF (desc: none) in REPORTTIMEOUT state
Jan 12 09:23:23 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AE (desc: none) in REPORTTIMEOUT state
Jan 12 09:23:23 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AD (desc: none) in REPORTTIMEOUT state
Jan 12 09:23:23 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AC (desc: none) in REPORTTIMEOUT state
Jan 12 09:23:22 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) disconnected (OLT0[0])
Jan 12 09:23:21 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:34:AC reconfiguration initialized
Jan 12 09:23:21 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:34:AC in state (CFGFAILED) force rediscovery by timeout started
Jan 12 09:18:09 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) configure failed
Jan 12 09:18:09 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) link 0 failed
Jan 12 09:18:09 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:34:AC create new path(8448) failed(response->header.rcode 4)
Jan 12 09:18:06 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC is allocated by link yy:yy:yy:yy:34:AC
Jan 12 09:17:53 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AF (desc: none) in REPORTTIMEOUT state
Jan 12 09:17:53 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AE (desc: none) in REPORTTIMEOUT state
Jan 12 09:17:53 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AD (desc: none) in REPORTTIMEOUT state
Jan 12 09:17:53 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AC (desc: none) in REPORTTIMEOUT state
Jan 12 09:17:52 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) disconnected (OLT0[0])
Jan 12 09:17:51 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:34:AC reconfiguration initialized
Jan 12 09:17:51 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:34:AC in state (CFGFAILED) force rediscovery by timeout started
Jan 12 09:12:40 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) configure failed
Jan 12 09:12:40 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) link 0 failed
Jan 12 09:12:40 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:34:AC create new path(8448) failed(response->header.rcode 4)
Jan 12 09:12:36 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC is allocated by link yy:yy:yy:yy:34:AC
Jan 12 09:12:24 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AF (desc: none) in REPORTTIMEOUT state
Jan 12 09:12:24 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AE (desc: none) in REPORTTIMEOUT state
Jan 12 09:12:24 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AD (desc: none) in REPORTTIMEOUT state
Jan 12 09:12:24 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AC (desc: none) in REPORTTIMEOUT state
Jan 12 09:12:23 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) disconnected (OLT0[0])
Jan 12 09:12:22 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:34:AC reconfiguration initialized
Jan 12 09:12:22 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:34:AC in state (CFGFAILED) force rediscovery by timeout started
Jan 12 09:07:10 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) configure failed
Jan 12 09:07:10 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) link 0 failed
Jan 12 09:07:10 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:34:AC create new path(8448) failed(response->header.rcode 4)
Jan 12 09:07:06 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC is allocated by link yy:yy:yy:yy:34:AC
Jan 12 09:06:54 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AF (desc: none) in REPORTTIMEOUT state
Jan 12 09:06:54 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AE (desc: none) in REPORTTIMEOUT state
Jan 12 09:06:54 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AD (desc: none) in REPORTTIMEOUT state
Jan 12 09:06:54 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AC (desc: none) in REPORTTIMEOUT state
Jan 12 09:06:53 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) disconnected (OLT0[0])
Jan 12 09:06:52 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:34:AC reconfiguration initialized
Jan 12 09:06:52 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:34:AC in state (CFGFAILED) force rediscovery by timeout started
Jan 12 09:01:41 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) configure failed
Jan 12 09:01:41 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) link 0 failed
Jan 12 09:01:41 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:34:AC create new path(8448) failed(response->header.rcode 4)
Jan 12 09:01:36 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC is allocated by link yy:yy:yy:yy:34:AC
Jan 12 09:01:24 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AF (desc: none) in REPORTTIMEOUT state
Jan 12 09:01:24 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AE (desc: none) in REPORTTIMEOUT state
Jan 12 09:01:24 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AD (desc: none) in REPORTTIMEOUT state
Jan 12 09:01:24 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AC (desc: none) in REPORTTIMEOUT state
Jan 12 09:01:23 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) disconnected (OLT0[0])
Jan 12 09:01:22 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:34:AC reconfiguration initialized
Jan 12 09:01:22 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:34:AC in state (CFGFAILED) force rediscovery by timeout started
Jan 12 08:56:09 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) configure failed
Jan 12 08:56:09 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) link 0 failed
Jan 12 08:56:09 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:34:AC create new path(8448) failed(response->header.rcode 4)
Jan 12 08:56:06 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC is allocated by link yy:yy:yy:yy:34:AC
Jan 12 08:55:53 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AF (desc: none) in REPORTTIMEOUT state
Jan 12 08:55:53 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AE (desc: none) in REPORTTIMEOUT state
Jan 12 08:55:53 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AD (desc: none) in REPORTTIMEOUT state
Jan 12 08:55:53 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AC (desc: none) in REPORTTIMEOUT state
Jan 12 08:55:53 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) disconnected (OLT0[0])
Jan 12 08:55:52 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:34:AC reconfiguration initialized
Jan 12 08:55:52 LTE-2X chip-proxy: ONT-yy:yy:yy:yy:34:AC in state (CFGFAILED) force rediscovery by timeout started
Jan 12 08:50:40 LTE-2X chip-proxy: profiler_onu_reconfigure: ONU yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) configure failed
Jan 12 08:50:40 LTE-2X chip-proxy: profiler_link_reconfigure_internal: create ONT yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) link 0 failed
Jan 12 08:50:40 LTE-2X chip-proxy: profiler_onu_link_create_path_internal: link yy:yy:yy:yy:34:AC create new path(8448) failed(response->header.rcode 4)
Jan 12 08:50:36 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC is allocated by link yy:yy:yy:yy:34:AC
Jan 12 08:50:06 LTE-2X chip-proxy: ONT yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) disconnected (OLT0[0])
Jan 12 08:50:05 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AF (desc: vl107-Zakatn-39) in REPORTTIMEOUT state
Jan 12 08:50:05 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AE (desc: vl107-Zakatn-39) in REPORTTIMEOUT state
Jan 12 08:50:05 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AD (desc: vl107-Zakatn-39) in REPORTTIMEOUT state
Jan 12 08:50:05 LTE-2X chip-proxy: alarm_oltlink: yy:yy:yy:yy:34:AC (desc: vl107-Zakatn-39) in REPORTTIMEOUT state

На графике мощности те же симптомы:резкое увеличение уровня.

[Dirks G]

Скажите вашу почту, можно в личку.

[Lucky SB]

Это не увеличение уровня - это НОЛЬ.
т.е. информация об уровне недоступна

[DGM]

Да, я как-то не подумал об этом. В этот момент действительно ONT отваливается, поэтому уровень-0.

[Lucky SB]

Нда. вот и до меня эта проблема докатилась

Прошивка.

Version: 3.14.4
Build: 0
Compile Date: 09.12.2014
Compile Time: 17:21:24

Сварщик в магистральной муфте работал - в результате загиба волокон дерево кусками отваливалось и приваливалось.

Много висело в состоноянии AUTHOK, некоторые в состоянии CFGFAILED - но через некоторое время они переподключались.

[DGM]

Подниму тему: проблему с CFGFAILED решили?
Новых прошивок на сайте не появилось, проблема периодически возникает, абоненты жалуются.

[churin]

Подниму тему: проблему с CFGFAILED решили?
Новых прошивок на сайте не появилось, проблема периодически возникает, абоненты жалуются.

Проблема с CfgFailed решена. На завершающей стадии тестирования было решено добавить в текущий релиз дополнительный функционал (незначительный).
После закрытия этого вопроса версия будет опубликова на сайте.
Версию с правками по CfgFailed можем направить вам для установки на сети.

[DGM]

Проблема с CFGFAILED в новых прошивках для LTE-2X, LTE-8X не решена.
ONU NTE-2(B+), конфигурация OLT - 128 ONU на PON порт.
UPD! на LTE-8X был старый софт, поменял-буду наблюдать. Логи с LTE-2X с новым софтом отправил на анализ.

[Lucky SB]

как успехи ?

[DGM]

На
LTE-2x# show version
Eltex LTE software version 3.14.4 build 5 on 19.05.2015 13:13:58
и
LTE-8X# show version
Eltex LTE software version 3.14.4 build 133 on 19.05.2015 13:16:15
проблемы с CFGFAILED нет, на сайте появился новый софт http://eltex.nsk.ru/pressroom/news/obno ... lte-2x.php
Этот софт еще не пробовал. Есть отзывы?

[DGM]

Сменил софт на последний. Пока норма.

[Lucky SB]

Код: Выделить всё

Uplink ports:    4
PON ports:    2
Version:    3.14.4
Build:    9
Compile Date:    10.07.2015
Compile Time:    15:36:27
Current Date:    17.11.2015
Current Time:    13:29:13
System uptime:    47 days, 13:37
CPU load average (1m, 5m, 15m):    0.09 0.16 0.10
Free RAM/Total RAM (Mbytes):    126/243
Temperature (PON ports / PON chips):    14 / 23
Fan state (fan0/fan1):    127 rps / 127 rps
 
Factory settings
Device type:    LTE-2X
Hardware revision:    1v2
Serial number:    TG1A000035
MAC:    A8:F9:4B:80:42:EA


Вот такая голова.
У меня имеется периодический глюк с отваливанием трафика через одну из приставок NTE-2, за приставкой находится коммутатор, поэтому профиль на приставке равный дефолтному стоит.

так вот. периодически трафик перестает ходить сквозь ONT. по резулттатам разбирательства на форуме и в ТП
меняли нам голову, прошивку и ONU, но глюк остался. Хотя гораздо реже происходит - раз в пару-тройку месяцев.


Сегодня после olt0 reconfigure появилась ONU в позе CFGFAILED
реконфиг ону не помогает.