Страница 1 из 1
NTE-RG-1421G-Wac разрывы через 20мин
Добавлено: 12 окт 2017 23:24
alex-xxi
Каждые 20 минут пропадает связь до NTE-RG-1421G-Wac. Уровень сигнала нормальный, стенд собран на столе.
LTE-8X настроен на 128 ONU на ветку.
Код: Выделить всё
LTE-8X(profile-rules)# rule show pon
0) 14: if (LinkIndex == 0x0) then path = port 0 queue 1; forward
1) 14: if (LinkIndex == 0x1) then path = port 0 queue 2; forward
LTE-8X(profile-rules)# rule show uni0
0) 14: if (Always) then path = link 0 queue 0; forwardПО на LTE-8X - 3.16.0.120, NTE-RG-1421G-Wac - 3.16.0.2422
В чем может быть проблема?
Лог с LTE-8X:
Код: Выделить всё
Jan 14 23:52:18 LTE-8X chip-proxy: alarm_oltlink: 02:00:6B:00:17:8C (desc: 1421) in REPORTTIMEOUT state
Jan 14 23:52:18 LTE-8X chip-proxy: alarm_oltlink: 02:00:6B:00:17:8D (desc: 1421) in REPORTTIMEOUT state
Jan 14 23:52:18 LTE-8X chip-proxy: alarm_oltlink: 02:00:6B:00:17:8E (desc: none) in REPORTTIMEOUT state
Jan 14 23:52:18 LTE-8X chip-proxy: alarm_oltlink: 02:00:6B:00:17:8F (desc: none) in REPORTTIMEOUT state
Jan 14 23:52:19 LTE-8X chip-proxy: ONT 02:00:6B:00:17:8C (desc: 1421) disconnected (OLT0[0])
Jan 14 23:53:17 LTE-8X chip-proxy: ONT 02:00:6B:00:17:8C is allocated by link 02:00:6B:00:17:8C
Jan 14 23:53:18 LTE-8X chip-proxy: ONT 02:00:6B:00:17:8C (desc: 1421) configure ok (OLT0[0])
Jan 14 23:58:01 LTE-8X chip-proxy: alarm_oltlink: 02:00:6B:00:17:8E (desc: none) in REPORTTIMEOUT state
Jan 14 23:58:02 LTE-8X chip-proxy: alarm_oltlink: 02:00:6B:00:17:8F (desc: none) in REPORTTIMEOUT state
Jan 15 00:18:55 LTE-8X chip-proxy: alarm_oltlink: 02:00:6B:00:17:8E (desc: none) in REPORTTIMEOUT state
Jan 15 00:18:55 LTE-8X chip-proxy: alarm_oltlink: 02:00:6B:00:17:8F (desc: none) in REPORTTIMEOUT state
Jan 15 00:39:48 LTE-8X chip-proxy: alarm_oltlink: 02:00:6B:00:17:8E (desc: none) in REPORTTIMEOUT state
Jan 15 00:39:48 LTE-8X chip-proxy: alarm_oltlink: 02:00:6B:00:17:8F (desc: none) in REPORTTIMEOUT state
Jan 15 00:53:51 LTE-8X chip-proxy: alarm_oltlink: 02:00:6B:00:17:8C (desc: 1421) in REPORTTIMEOUT state
Jan 15 00:53:51 LTE-8X chip-proxy: alarm_oltlink: 02:00:6B:00:17:8D (desc: 1421) in REPORTTIMEOUT state
Jan 15 00:53:51 LTE-8X chip-proxy: alarm_oltlink: 02:00:6B:00:17:8E (desc: none) in REPORTTIMEOUT state
Jan 15 00:53:52 LTE-8X chip-proxy: alarm_oltlink: 02:00:6B:00:17:8F (desc: none) in REPORTTIMEOUT state
Jan 15 00:53:52 LTE-8X chip-proxy: ONT 02:00:6B:00:17:8C (desc: 1421) disconnected (OLT0[0])
Jan 15 00:54:49 LTE-8X chip-proxy: ONT 02:00:6B:00:17:8C is allocated by link 02:00:6B:00:17:8C
Jan 15 00:54:51 LTE-8X chip-proxy: ONT 02:00:6B:00:17:8C (desc: 1421) configure ok (OLT0[0])
Jan 15 01:00:41 LTE-8X chip-proxy: alarm_oltlink: 02:00:6B:00:17:8E (desc: none) in REPORTTIMEOUT state
Jan 15 01:00:41 LTE-8X chip-proxy: alarm_oltlink: 02:00:6B:00:17:8F (desc: none) in REPORTTIMEOUT state
Jan 15 01:12:29 LTE-8X chip-proxy: alarm_oltlink: 02:00:6B:00:17:8C (desc: 1421) in REPORTTIMEOUT state
Jan 15 01:12:29 LTE-8X chip-proxy: alarm_oltlink: 02:00:6B:00:17:8D (desc: 1421) in REPORTTIMEOUT state
Jan 15 01:12:29 LTE-8X chip-proxy: alarm_oltlink: 02:00:6B:00:17:8E (desc: none) in REPORTTIMEOUT state
Jan 15 01:12:29 LTE-8X chip-proxy: alarm_oltlink: 02:00:6B:00:17:8F (desc: none) in REPORTTIMEOUT state
Jan 15 01:12:30 LTE-8X chip-proxy: ONT 02:00:6B:00:17:8C (desc: 1421) disconnected (OLT0[0])
Jan 15 01:13:27 LTE-8X chip-proxy: ONT 02:00:6B:00:17:8C is allocated by link 02:00:6B:00:17:8C
Jan 15 01:13:29 LTE-8X chip-proxy: ONT 02:00:6B:00:17:8C (desc: 1421) configure ok (OLT0[0])
Jan 15 01:16:33 LTE-8X chip-proxy: alarm_oltlink: 02:00:6B:00:17:8E (desc: none) in REPORTTIMEOUT state
Jan 15 01:16:33 LTE-8X chip-proxy: alarm_oltlink: 02:00:6B:00:17:8F (desc: none) in REPORTTIMEOUT state
Jan 15 01:16:33 LTE-8X chip-proxy: alarm_oltlink: 02:00:6B:00:17:8C (desc: 1421) in REPORTTIMEOUT state
Jan 15 01:16:33 LTE-8X chip-proxy: alarm_oltlink: 02:00:6B:00:17:8D (desc: 1421) in REPORTTIMEOUT state
Jan 15 01:16:34 LTE-8X chip-proxy: ONT 02:00:6B:00:17:8C (desc: 1421) disconnected (OLT0[0])
Jan 15 01:17:31 LTE-8X chip-proxy: ONT 02:00:6B:00:17:8C is allocated by link 02:00:6B:00:17:8C
Jan 15 01:17:33 LTE-8X chip-proxy: ONT 02:00:6B:00:17:8C (desc: 1421) configure ok (OLT0[0])
Jan 15 01:21:34 LTE-8X chip-proxy: alarm_oltlink: 02:00:6B:00:17:8E (desc: none) in REPORTTIMEOUT state
Jan 15 01:21:34 LTE-8X chip-proxy: alarm_oltlink: 02:00:6B:00:17:8F (desc: none) in REPORTTIMEOUT state
Jan 15 01:42:27 LTE-8X chip-proxy: alarm_oltlink: 02:00:6B:00:17:8E (desc: none) in REPORTTIMEOUT state
Jan 15 01:42:27 LTE-8X chip-proxy: alarm_oltlink: 02:00:6B:00:17:8F (desc: none) in REPORTTIMEOUT state
Jan 15 02:03:20 LTE-8X chip-proxy: alarm_oltlink: 02:00:6B:00:17:8E (desc: none) in REPORTTIMEOUT state
Jan 15 02:03:20 LTE-8X chip-proxy: alarm_oltlink: 02:00:6B:00:17:8F (desc: none) in REPORTTIMEOUT state
Jan 15 02:24:12 LTE-8X chip-proxy: alarm_oltlink: 02:00:6B:00:17:8E (desc: none) in REPORTTIMEOUT state
Jan 15 02:24:13 LTE-8X chip-proxy: alarm_oltlink: 02:00:6B:00:17:8F (desc: none) in REPORTTIMEOUT state
Jan 15 02:45:05 LTE-8X chip-proxy: alarm_oltlink: 02:00:6B:00:17:8E (desc: none) in REPORTTIMEOUT state
Jan 15 02:45:06 LTE-8X chip-proxy: alarm_oltlink: 02:00:6B:00:17:8F (desc: none) in REPORTTIMEOUT state
Re: NTE-RG-1421G-Wac разрывы через 20мин
Добавлено: 13 окт 2017 09:39
Dirks G
Какая индикация на ONT?
Какой уровень сигнала приходит на ONT? На 4 линках проблема наблюдается?
Re: NTE-RG-1421G-Wac разрывы через 20мин
Добавлено: 13 окт 2017 14:33
alex-xxi
Проверили на 4 линках - проблема не наблюдается.
Подскажите корректные настройки для работы на 2 линках.
Re: NTE-RG-1421G-Wac разрывы через 20мин
Добавлено: 14 окт 2017 01:11
alex-xxi
Купленная партия NTE-RG-1421G-Wac лежит мертвым грузом. Не хотелось бы их возвращать обратно.
Re: NTE-RG-1421G-Wac разрывы через 20мин
Добавлено: 14 окт 2017 11:47
Dirks G
Приложите конфигурацию всех профилей, на которых наблюдается проблема.
Re: NTE-RG-1421G-Wac разрывы через 20мин
Добавлено: 15 окт 2017 01:59
alex-xxi
Проблема наблюдается при таких настройках:
Код: Выделить всё
PON-3(profile-rules)# rule show pon
0) 0: if (VID == 50) then ReplaceTagVID = 3; forward
1) 14: if (LinkIndex == 0x0) then path = port 0 queue 1; forward
2) 14: if (LinkIndex == 0x1) then path = port 0 queue 2; forward
PON-3(profile-rules)# rule show uni0
0) 0: if (VID == 3) then ReplaceTagVID = 50; forward
1) 14: if (Always) then path = link 0 queue 0; forward
Код: Выделить всё
PON-3(profile-path0)# show information
Index: 0
Description: Default profile
Link0 assigned to PATH ID = 0
Link1 assigned to PATH ID = 1
Link2 assigned to PATH ID = unassigned
Link3 assigned to PATH ID = unassigned
PON-3(profile-path0)# rule show path0
0) 10: if (Always) then (ClearDiscard) and (SetQueue 0) and (SetUnicastLink 0)
PON-3(profile-path0)# rule show path1
0) 10: if (Always) then (ClearDiscard) and (SetQueue 0) and (SetUnicastLink 1)
Код: Выделить всё
PON-3(profile-ports0)# show information
Index: 0
Description: Default profile
Links count: 2
PON port:
Auto downstream broadcast frame forwarding: yes
UNI0 port:
Enabled: yes
Autonegotiation: yes
Speed: 1Gbps
Duplex: full
Automatic learning entry limit: 64
Learned entry age limit: 60
UNI1 port:
Enabled: yes
Autonegotiation: yes
Speed: 100Mbps
Duplex: full
Automatic learning entry limit: 64
Learned entry age limit: 60
Re: NTE-RG-1421G-Wac разрывы через 20мин
Добавлено: 16 окт 2017 16:23
alex-xxi
В логах NTE-RG-1421G-Wac такие сообщения:
Код: Выделить всё
Date/Time Facility Severity Message
Jan 4 15:18:41 kern warn kernel: netdev path : veip0.4 -> veip0 -> epon0
Jan 4 15:18:41 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 15:18:41 kern info kernel: device veip0.4 entered promiscuous mode
Jan 4 15:18:41 kern info kernel: br2: port 1(veip0.4) entered forwarding state
Jan 4 15:18:41 kern info kernel: br2: port 1(veip0.4) entered forwarding state
Jan 4 15:18:41 kern warn kernel: netdev path : veip0.5 -> veip0 -> epon0
Jan 4 15:18:41 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 15:18:41 kern info kernel: device veip0.5 entered promiscuous mode
Jan 4 15:18:41 kern info kernel: br3: port 1(veip0.5) entered forwarding state
Jan 4 15:18:41 kern info kernel: br3: port 1(veip0.5) entered forwarding state
Jan 4 15:18:42 kern warn kernel: veip0.6 MAC address set to A8:F9:4B:2A:BF:3A
Jan 4 15:18:42 kern warn kernel: netdev path : veip0.6 -> veip0 -> epon0
Jan 4 15:18:42 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 15:18:42 kern warn kernel: veip0.1 MAC address set to A8:F9:4B:2A:BF:3B
Jan 4 15:18:42 kern warn kernel: netdev path : veip0.1 -> veip0 -> epon0
Jan 4 15:18:42 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 15:39:17 kern info kernel: device veip0.3 left promiscuous mode
Jan 4 15:39:17 kern info kernel: br1: port 1(veip0.3) entered disabled state
Jan 4 15:39:18 kern info kernel: device veip0.4 left promiscuous mode
Jan 4 15:39:18 kern info kernel: br2: port 1(veip0.4) entered disabled state
Jan 4 15:39:18 kern info kernel: device veip0.5 left promiscuous mode
Jan 4 15:39:18 kern info kernel: br3: port 1(veip0.5) entered disabled state
Jan 4 15:39:24 kern warn kernel: veip0.2 MAC address set to A8:F9:4B:2A:BF:39
Jan 4 15:39:24 kern warn kernel: netdev path : veip0.2 -> veip0 -> epon0
Jan 4 15:39:24 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 15:39:26 kern warn kernel: netdev path : veip0.3 -> veip0 -> epon0
Jan 4 15:39:26 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 15:39:26 kern info kernel: device veip0.3 entered promiscuous mode
Jan 4 15:39:26 kern info kernel: br1: port 1(veip0.3) entered forwarding state
Jan 4 15:39:26 kern info kernel: br1: port 1(veip0.3) entered forwarding state
Jan 4 15:39:26 kern warn kernel: netdev path : veip0.4 -> veip0 -> epon0
Jan 4 15:39:26 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 15:39:27 kern info kernel: device veip0.4 entered promiscuous mode
Jan 4 15:39:27 kern info kernel: br2: port 1(veip0.4) entered forwarding state
Jan 4 15:39:27 kern info kernel: br2: port 1(veip0.4) entered forwarding state
Jan 4 15:39:27 kern warn kernel: netdev path : veip0.5 -> veip0 -> epon0
Jan 4 15:39:27 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 15:39:27 kern info kernel: device veip0.5 entered promiscuous mode
Jan 4 15:39:27 kern info kernel: br3: port 1(veip0.5) entered forwarding state
Jan 4 15:39:27 kern info kernel: br3: port 1(veip0.5) entered forwarding state
Jan 4 15:39:27 kern warn kernel: veip0.6 MAC address set to A8:F9:4B:2A:BF:3A
Jan 4 15:39:27 kern warn kernel: netdev path : veip0.6 -> veip0 -> epon0
Jan 4 15:39:27 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 15:39:27 kern warn kernel: veip0.1 MAC address set to A8:F9:4B:2A:BF:3B
Jan 4 15:39:27 kern warn kernel: netdev path : veip0.1 -> veip0 -> epon0
Jan 4 15:39:27 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 16:00:16 kern info kernel: device veip0.3 left promiscuous mode
Jan 4 16:00:16 kern info kernel: br1: port 1(veip0.3) entered disabled state
Jan 4 16:00:16 kern info kernel: device veip0.4 left promiscuous mode
Jan 4 16:00:16 kern info kernel: br2: port 1(veip0.4) entered disabled state
Jan 4 16:00:17 kern info kernel: device veip0.5 left promiscuous mode
Jan 4 16:00:17 kern info kernel: br3: port 1(veip0.5) entered disabled state
Jan 4 16:00:22 kern warn kernel: veip0.2 MAC address set to A8:F9:4B:2A:BF:39
Jan 4 16:00:22 kern warn kernel: netdev path : veip0.2 -> veip0 -> epon0
Jan 4 16:00:22 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 16:00:25 kern warn kernel: netdev path : veip0.3 -> veip0 -> epon0
Jan 4 16:00:25 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 16:00:25 kern info kernel: device veip0.3 entered promiscuous mode
Jan 4 16:00:25 kern info kernel: br1: port 1(veip0.3) entered forwarding state
Jan 4 16:00:25 kern info kernel: br1: port 1(veip0.3) entered forwarding state
Jan 4 16:00:25 kern warn kernel: netdev path : veip0.4 -> veip0 -> epon0
Jan 4 16:00:25 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 16:00:25 kern info kernel: device veip0.4 entered promiscuous mode
Jan 4 16:00:25 kern info kernel: br2: port 1(veip0.4) entered forwarding state
Jan 4 16:00:25 kern info kernel: br2: port 1(veip0.4) entered forwarding state
Jan 4 16:00:25 kern warn kernel: netdev path : veip0.5 -> veip0 -> epon0
Jan 4 16:00:25 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 16:00:26 kern info kernel: device veip0.5 entered promiscuous mode
Jan 4 16:00:26 kern info kernel: br3: port 1(veip0.5) entered forwarding state
Jan 4 16:00:26 kern info kernel: br3: port 1(veip0.5) entered forwarding state
Jan 4 16:00:26 kern warn kernel: veip0.6 MAC address set to A8:F9:4B:2A:BF:3A
Jan 4 16:00:26 kern warn kernel: netdev path : veip0.6 -> veip0 -> epon0
Jan 4 16:00:26 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 16:00:26 kern warn kernel: veip0.1 MAC address set to A8:F9:4B:2A:BF:3B
Jan 4 16:00:26 kern warn kernel: netdev path : veip0.1 -> veip0 -> epon0
Jan 4 16:00:26 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 16:21:09 kern info kernel: device veip0.3 left promiscuous mode
Jan 4 16:21:09 kern info kernel: br1: port 1(veip0.3) entered disabled state
Jan 4 16:21:10 kern info kernel: device veip0.4 left promiscuous mode
Jan 4 16:21:10 kern info kernel: br2: port 1(veip0.4) entered disabled state
Jan 4 16:21:10 kern info kernel: device veip0.5 left promiscuous mode
Jan 4 16:21:10 kern info kernel: br3: port 1(veip0.5) entered disabled state
Jan 4 16:21:16 kern warn kernel: veip0.2 MAC address set to A8:F9:4B:2A:BF:39
Jan 4 16:21:16 kern warn kernel: netdev path : veip0.2 -> veip0 -> epon0
Jan 4 16:21:16 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 16:21:18 kern warn kernel: netdev path : veip0.3 -> veip0 -> epon0
Jan 4 16:21:18 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 16:21:18 kern info kernel: device veip0.3 entered promiscuous mode
Jan 4 16:21:18 kern info kernel: br1: port 1(veip0.3) entered forwarding state
Jan 4 16:21:18 kern info kernel: br1: port 1(veip0.3) entered forwarding state
Jan 4 16:21:18 kern warn kernel: netdev path : veip0.4 -> veip0 -> epon0
Jan 4 16:21:18 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 16:21:18 kern info kernel: device veip0.4 entered promiscuous mode
Jan 4 16:21:18 kern info kernel: br2: port 1(veip0.4) entered forwarding state
Jan 4 16:21:18 kern info kernel: br2: port 1(veip0.4) entered forwarding state
Jan 4 16:21:19 kern warn kernel: netdev path : veip0.5 -> veip0 -> epon0
Jan 4 16:21:19 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 16:21:19 kern info kernel: device veip0.5 entered promiscuous mode
Jan 4 16:21:19 kern info kernel: br3: port 1(veip0.5) entered forwarding state
Jan 4 16:21:19 kern info kernel: br3: port 1(veip0.5) entered forwarding state
Jan 4 16:21:19 kern warn kernel: veip0.6 MAC address set to A8:F9:4B:2A:BF:3A
Jan 4 16:21:19 kern warn kernel: netdev path : veip0.6 -> veip0 -> epon0
Jan 4 16:21:19 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 16:21:19 kern warn kernel: veip0.1 MAC address set to A8:F9:4B:2A:BF:3B
Jan 4 16:21:19 kern warn kernel: netdev path : veip0.1 -> veip0 -> epon0
Jan 4 16:21:19 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 16:41:58 kern info kernel: device veip0.3 left promiscuous mode
Jan 4 16:41:58 kern info kernel: br1: port 1(veip0.3) entered disabled state
Jan 4 16:41:58 kern info kernel: device veip0.4 left promiscuous mode
Jan 4 16:41:58 kern info kernel: br2: port 1(veip0.4) entered disabled state
Jan 4 16:41:59 kern info kernel: device veip0.5 left promiscuous mode
Jan 4 16:41:59 kern info kernel: br3: port 1(veip0.5) entered disabled state
Jan 4 16:42:03 kern warn kernel: veip0.2 MAC address set to A8:F9:4B:2A:BF:39
Jan 4 16:42:03 kern warn kernel: netdev path : veip0.2 -> veip0 -> epon0
Jan 4 16:42:03 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 16:42:06 kern warn kernel: netdev path : veip0.3 -> veip0 -> epon0
Jan 4 16:42:06 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 16:42:06 kern info kernel: device veip0.3 entered promiscuous mode
Jan 4 16:42:06 kern info kernel: br1: port 1(veip0.3) entered forwarding state
Jan 4 16:42:06 kern info kernel: br1: port 1(veip0.3) entered forwarding state
Jan 4 16:42:06 kern warn kernel: netdev path : veip0.4 -> veip0 -> epon0
Jan 4 16:42:06 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 16:42:06 kern info kernel: device veip0.4 entered promiscuous mode
Jan 4 16:42:06 kern info kernel: br2: port 1(veip0.4) entered forwarding state
Jan 4 16:42:06 kern info kernel: br2: port 1(veip0.4) entered forwarding state
Jan 4 16:42:06 kern warn kernel: netdev path : veip0.5 -> veip0 -> epon0
Jan 4 16:42:06 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 16:42:07 kern info kernel: device veip0.5 entered promiscuous mode
Jan 4 16:42:07 kern info kernel: br3: port 1(veip0.5) entered forwarding state
Jan 4 16:42:07 kern info kernel: br3: port 1(veip0.5) entered forwarding state
Jan 4 16:42:07 kern warn kernel: veip0.6 MAC address set to A8:F9:4B:2A:BF:3A
Jan 4 16:42:07 kern warn kernel: netdev path : veip0.6 -> veip0 -> epon0
Jan 4 16:42:07 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 16:42:07 kern warn kernel: veip0.1 MAC address set to A8:F9:4B:2A:BF:3B
Jan 4 16:42:07 kern warn kernel: netdev path : veip0.1 -> veip0 -> epon0
Jan 4 16:42:07 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 17:02:51 kern info kernel: device veip0.3 left promiscuous mode
Jan 4 17:02:51 kern info kernel: br1: port 1(veip0.3) entered disabled state
Jan 4 17:02:51 kern info kernel: device veip0.4 left promiscuous mode
Jan 4 17:02:51 kern info kernel: br2: port 1(veip0.4) entered disabled state
Jan 4 17:02:52 kern info kernel: device veip0.5 left promiscuous mode
Jan 4 17:02:52 kern info kernel: br3: port 1(veip0.5) entered disabled state
Jan 4 17:02:57 kern warn kernel: veip0.2 MAC address set to A8:F9:4B:2A:BF:39
Jan 4 17:02:57 kern warn kernel: netdev path : veip0.2 -> veip0 -> epon0
Jan 4 17:02:57 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 17:02:59 kern warn kernel: netdev path : veip0.3 -> veip0 -> epon0
Jan 4 17:02:59 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 17:02:59 kern info kernel: device veip0.3 entered promiscuous mode
Jan 4 17:02:59 kern info kernel: br1: port 1(veip0.3) entered forwarding state
Jan 4 17:02:59 kern info kernel: br1: port 1(veip0.3) entered forwarding state
Jan 4 17:03:00 kern warn kernel: netdev path : veip0.4 -> veip0 -> epon0
Jan 4 17:03:00 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 17:03:00 kern info kernel: device veip0.4 entered promiscuous mode
Jan 4 17:03:00 kern info kernel: br2: port 1(veip0.4) entered forwarding state
Jan 4 17:03:00 kern info kernel: br2: port 1(veip0.4) entered forwarding state
Jan 4 17:03:00 kern warn kernel: netdev path : veip0.5 -> veip0 -> epon0
Jan 4 17:03:00 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 17:03:00 kern info kernel: device veip0.5 entered promiscuous mode
Jan 4 17:03:00 kern info kernel: br3: port 1(veip0.5) entered forwarding state
Jan 4 17:03:00 kern info kernel: br3: port 1(veip0.5) entered forwarding state
Jan 4 17:03:01 kern warn kernel: veip0.6 MAC address set to A8:F9:4B:2A:BF:3A
Jan 4 17:03:01 kern warn kernel: netdev path : veip0.6 -> veip0 -> epon0
Jan 4 17:03:01 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 17:03:01 kern warn kernel: veip0.1 MAC address set to A8:F9:4B:2A:BF:3B
Jan 4 17:03:01 kern warn kernel: netdev path : veip0.1 -> veip0 -> epon0
Jan 4 17:03:01 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 17:23:44 kern info kernel: device veip0.3 left promiscuous mode
Jan 4 17:23:44 kern info kernel: br1: port 1(veip0.3) entered disabled state
Jan 4 17:23:44 kern info kernel: device veip0.4 left promiscuous mode
Jan 4 17:23:44 kern info kernel: br2: port 1(veip0.4) entered disabled state
Jan 4 17:23:45 kern info kernel: device veip0.5 left promiscuous mode
Jan 4 17:23:45 kern info kernel: br3: port 1(veip0.5) entered disabled state
Jan 4 17:23:50 kern warn kernel: veip0.2 MAC address set to A8:F9:4B:2A:BF:39
Jan 4 17:23:50 kern warn kernel: netdev path : veip0.2 -> veip0 -> epon0
Jan 4 17:23:50 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 17:23:53 kern warn kernel: netdev path : veip0.3 -> veip0 -> epon0
Jan 4 17:23:53 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 17:23:53 kern info kernel: device veip0.3 entered promiscuous mode
Jan 4 17:23:53 kern info kernel: br1: port 1(veip0.3) entered forwarding state
Jan 4 17:23:53 kern info kernel: br1: port 1(veip0.3) entered forwarding state
Jan 4 17:23:53 kern warn kernel: netdev path : veip0.4 -> veip0 -> epon0
Jan 4 17:23:53 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 17:23:53 kern info kernel: device veip0.4 entered promiscuous mode
Jan 4 17:23:53 kern info kernel: br2: port 1(veip0.4) entered forwarding state
Jan 4 17:23:53 kern info kernel: br2: port 1(veip0.4) entered forwarding state
Jan 4 17:23:53 kern warn kernel: netdev path : veip0.5 -> veip0 -> epon0
Jan 4 17:23:53 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 17:23:53 kern info kernel: device veip0.5 entered promiscuous mode
Jan 4 17:23:53 kern info kernel: br3: port 1(veip0.5) entered forwarding state
Jan 4 17:23:53 kern info kernel: br3: port 1(veip0.5) entered forwarding state
Jan 4 17:23:54 kern warn kernel: veip0.6 MAC address set to A8:F9:4B:2A:BF:3A
Jan 4 17:23:54 kern warn kernel: netdev path : veip0.6 -> veip0 -> epon0
Jan 4 17:23:54 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 17:23:54 kern warn kernel: veip0.1 MAC address set to A8:F9:4B:2A:BF:3B
Jan 4 17:23:54 kern warn kernel: netdev path : veip0.1 -> veip0 -> epon0
Jan 4 17:23:54 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 17:44:37 kern info kernel: device veip0.3 left promiscuous mode
Jan 4 17:44:37 kern info kernel: br1: port 1(veip0.3) entered disabled state
Jan 4 17:44:38 kern info kernel: device veip0.4 left promiscuous mode
Jan 4 17:44:38 kern info kernel: br2: port 1(veip0.4) entered disabled state
Jan 4 17:44:38 kern info kernel: device veip0.5 left promiscuous mode
Jan 4 17:44:38 kern info kernel: br3: port 1(veip0.5) entered disabled state
Jan 4 17:44:44 kern warn kernel: veip0.2 MAC address set to A8:F9:4B:2A:BF:39
Jan 4 17:44:44 kern warn kernel: netdev path : veip0.2 -> veip0 -> epon0
Jan 4 17:44:44 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 17:44:46 kern warn kernel: netdev path : veip0.3 -> veip0 -> epon0
Jan 4 17:44:46 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 17:44:46 kern info kernel: device veip0.3 entered promiscuous mode
Jan 4 17:44:46 kern info kernel: br1: port 1(veip0.3) entered forwarding state
Jan 4 17:44:46 kern info kernel: br1: port 1(veip0.3) entered forwarding state
Jan 4 17:44:47 kern warn kernel: netdev path : veip0.4 -> veip0 -> epon0
Jan 4 17:44:47 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 17:44:47 kern info kernel: device veip0.4 entered promiscuous mode
Jan 4 17:44:47 kern info kernel: br2: port 1(veip0.4) entered forwarding state
Jan 4 17:44:47 kern info kernel: br2: port 1(veip0.4) entered forwarding state
Jan 4 17:44:47 kern warn kernel: netdev path : veip0.5 -> veip0 -> epon0
Jan 4 17:44:47 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 17:44:47 kern info kernel: device veip0.5 entered promiscuous mode
Jan 4 17:44:47 kern info kernel: br3: port 1(veip0.5) entered forwarding state
Jan 4 17:44:47 kern info kernel: br3: port 1(veip0.5) entered forwarding state
Jan 4 17:44:47 kern warn kernel: veip0.6 MAC address set to A8:F9:4B:2A:BF:3A
Jan 4 17:44:47 kern warn kernel: netdev path : veip0.6 -> veip0 -> epon0
Jan 4 17:44:47 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Jan 4 17:44:48 kern warn kernel: veip0.1 MAC address set to A8:F9:4B:2A:BF:3B
Jan 4 17:44:48 kern warn kernel: netdev path : veip0.1 -> veip0 -> epon0
Jan 4 17:44:48 kern warn kernel: BCMVLAN : veip0 mode was set to RG
Re: NTE-RG-1421G-Wac разрывы через 20мин
Добавлено: 17 окт 2017 09:22
Dirks G
Напишите в личку из какой вы компании и вашу почту.
Re: NTE-RG-1421G-Wac разрывы через 20мин
Добавлено: 17 окт 2017 09:31
Dirks G
Какая индикация на ONT в момент разрыва?
Re: NTE-RG-1421G-Wac разрывы через 20мин
Добавлено: 17 окт 2017 13:37
alex-xxi
Dirks G писал(а):Какая индикация на ONT в момент разрыва?
В моменты разрыва на терминале никакая индикация не меняется.
Dirks G писал(а):Напишите в личку из какой вы компании и вашу почту.
Ответил в ЛС
Re: NTE-RG-1421G-Wac разрывы через 20мин
Добавлено: 28 ноя 2017 18:34
alex-xxi
Подскажите когда планируется выход прошивки для LTE-8X с устраненной проблемой?
Re: NTE-RG-1421G-Wac разрывы через 20мин
Добавлено: 04 дек 2017 17:00
churin
alex-xxi писал(а):Подскажите когда планируется выход прошивки для LTE-8X с устраненной проблемой?
Постараемся до конца года подготовить версию с решением.
Re: NTE-RG-1421G-Wac разрывы через 20мин
Добавлено: 18 янв 2018 17:19
alex-xxi
Есть информация о выходе новой версии ПО?
Re: NTE-RG-1421G-Wac разрывы через 20мин
Добавлено: 19 янв 2018 17:46
churin
alex-xxi писал(а):Есть информация о выходе новой версии ПО?
До конца месяца предоставим версию.
Re: NTE-RG-1421G-Wac разрывы через 20мин
Добавлено: 08 фев 2018 15:14
churin
alex-xxi, скажите вашу почту, вышлю прошивку LTE-8X