UA.PON v6.0

onihack · 9 жовтня, 2017

Есть ли какие-то новости по MTU?

Тестировал транзит на подручных онушках. Результаты следующие:

MODEL Max MTU

bdcom P1501B -- 1571

Bdcom P1501C -- 1514

bdcom P1004C1 -- 1514

bdcom P1501C1 -- 1518

PICO PU-E510 -- >2000

BDCOM P3616-2TE Software, Version 10.1.0E Build 37273

Відредаговано 9 жовтня, 2017 onihack

passer · 10 жовтня, 2017

unicast mac address can not be set on pon or psg port

Это что значит? Встречается в логе P3310C c неопределенной периодичностью.

sery_volk_inc · 19 жовтня, 2017

Подскажите, от чего ОЛТ может не видеть мощности ONU? Вот такая картина на двух устройствах:

#show epon optical-transceiver-diagnosis
 interface    Temperature(degree)    Voltage(V)    Current(mA)    TxPower(dBm)
-----------  ---------------------  ------------  -------------  --------------
epon0/1      41.4                   3.3           14.6           6.3           
epon0/2      44.7                   3.3           13.4           5.2           
epon0/3      44.3                   3.3           12.8           6.3           
epon0/4      44.3                   3.4           12.9           6.4           
 interface    RxPower(dBm)
-----------  --------------
epon0/1:1    -39.9          
epon0/1:3    -39.9          
epon0/1:4    -39.9          
epon0/1:5    -39.9          
epon0/1:6    -39.9          
epon0/1:7    -39.9          
epon0/1:9    -39.9          
epon0/1:10   -39.9          
epon0/1:11   -39.9          
epon0/1:12   -39.9          
epon0/1:14   -39.9          
epon0/2:1    -39.9          
epon0/2:2    -39.9

Dimkers · 19 жовтня, 2017

Версия прошивки, что за онушки, СФП часом не ЗТЕ С++(для Гпон)? Фигню в сигналах встречал на пикотелах для Епон.

sery_volk_inc · 19 жовтня, 2017

Версия прошивки, что за онушки, СФП часом не ЗТЕ С++(для Гпон)? Фигню в сигналах встречал на пикотелах для Епон.

Прошивка 33463, ОЛТы P3310C. Онушки разные - XPON, v-solution, BDCOM. SFP действительно ZTE C++, но на ОЛТ P3310B сигнал отображается... Странно, что по snmp данные получить можно, и напрямую от онушки тоже.

preart · 19 жовтня, 2017

Странно, что по snmp данные получить можно, и напрямую от онушки тоже.

OLT и ONU отображают уровень принимаемого сигнала RxPower(dBm), соответственно Rx ONU и Rx OLT - это разные сигналы, измеряются разными устройствами. В Вашем случае есть проблема с измерением сигнала Rx на OLT.

Вот мой вывод (ONU BDCOM, SFP сейчас точно не скажу):

BDCOM(tm) P3310C Software, Version 10.1.0D Build 33463

 interface    Temperature(degree)    Voltage(V)    Current(mA)    TxPower(dBm)
-----------  ---------------------  ------------  -------------  --------------
epon0/1      36.3                   3.4           18.0           4.9
epon0/2      35.4                   3.4           16.1           4.8
epon0/3      0.0                    0.0           0.0            0.0
epon0/4      0.0                    0.0           0.0            0.0
 interface    RxPower(dBm)
-----------  --------------
epon0/2:1    -21.4
epon0/1:2    -22.1
epon0/2:4    -20.0
epon0/1:4    -19.3
epon0/1:6    -20.4
epon0/1:8    -19.3
...

А вот для сравнения сигнал, который получает ONU 0/1:2:

show ep int e0/1:2 onu ctc optical-transceiver-diagnosis
 operating temperature(degree): 35
 supply voltage(V): 3.3
 bias current(mA): 14.9
 transmitted power(DBm): 1.5
 received power(DBm): -17.3

Как видно уровни передачи и приёма на OLT и ONU разные.

Dimkers · 19 жовтня, 2017

Смените модули и все будет хорошо. Єти модули для Гпон, а не Епон.

Kiano · 19 жовтня, 2017

товарищи, не осилю 50 страниц сходу, но хочется почитать последнюю версию бестселлера, будьте добры ссылку

vetal_mix · 16 листопада, 2017

Добрый день. Летом было принято решение переходить на PON и соответственно для реализации нашей затеи прикупили ОЛТ BDCOM p3310c. Нагрузили абонентами, в парке в основном были онушки Fora, Начались хаотичные отвалы терминалов на 3 ветках (могли валиться пару с 1 ветки, пару со 2, еще несколько с 3), держалась 4 ветка на которой отвалов не было. Привели все ветки в норму по сигналам, проблема не исчезла. Отправили Олт на гарантийное обслуживание и перекинули всех на олт Picotel, ушли проблемы с отвалами. Оказалось "Дефект холодной пайки". Сеть растет, поэтому начали снова нагружать BDCOM, и начались снова сыпаться теже проблемы, но теперь и на 4 ветке.

Имеем:

1. ОЛТ P3310C

BDCOM P3310C Software, Version 10.1.0E Build 46085

2. Sfp c++ Foxgate

3. есть 11 онушек Fora (2 из которых установлены в стенде на 3 порту)

Olt_172.16.1.50#show epon int epon 0/3:1 onu ctc basic-info

ONU Vender ID : FORA

ONU MODEL ID : 101E

ONU ID : 1c87.7913.ea90

Hardware Version : V2.3

Software Version : V1.1.4

Firmware Version : 0x010101

Chipset Vendor ID :

Chipset MODEL ID : 0x9110

Chipset Revision : 40

Chipset Date : 14/01/01

Onu type : SFU

Support multillid : Not supported

Protection type : Not supported

Number of Pon : 1

Number of slot : 0

Support 5 types of port:

Number of GE port : 1

Battery Backup : 0

и 3 онушки Foxgate.

Проблема в отвале онушек Фора в хаотичном порядке (может отвалиться онушка у абона и тестовая онушка на 3 ветке). Периодичность отвалов тоже хаотичная.

Olt_172.16.1.50#show epon active-onu

Interface EPON0/3 has bound 2 active ONUs:

IntfName MAC Address Status OAM Status Distance(m) RTT(TQ) LastRegTime LastDeregTime LastDeregReason Alivetime

---------- -------------- --------------- ------------ ----------- ------- ------------------- ------------------- ----------------- ------------

EPON0/3:1 1c87.7913.ea90 auto-configured ctc-oam-oper 2161 1333 1970.01.01.13:52:43 1970.01.01.13:52:11 wire-down 0.01:29:36

EPON0/3:2 1c87.7913.ea7b auto-configured ctc-oam-oper 2161 1333 1970.01.01.15:20:30 1970.01.01.15:19:58 wire-down 0.00:01:49

Interface EPON0/4 has bound 12 active ONUs:

IntfName MAC Address Status OAM Status Distance(m) RTT(TQ) LastRegTime LastDeregTime LastDeregReason Alivetime

---------- -------------- --------------- ------------ ----------- ------- ------------------- ------------------- ----------------- ------------

EPON0/4:3 1c87.7913.ce6d auto-configured ctc-oam-oper 4628 2854 1970.01.01.15:20:30 1970.01.01.15:19:58 wire-down 0.00:01:49

EPON0/4:4 1c87.7913.f4b0 auto-configured ctc-oam-oper 4013 2475 1970.01.01.01:49:36 1970.01.01.01:49:04 wire-down 0.13:32:43

EPON0/4:5 1c87.7913.ba48 auto-configured ctc-oam-oper 4577 2823 1970.01.01.15:20:31 1970.01.01.15:19:58 wire-down 0.00:01:48

EPON0/4:7 8014.a867.d9c8 auto-configured ctc-oam-oper 2012 1241 1970.01.01.00:00:26 1970.01.01.00:00:24 unknow 0.15:21:53

EPON0/4:8 1c87.7913.ce3a auto-configured ctc-oam-oper 4553 2808 1970.01.01.13:50:54 1970.01.01.13:50:13 power-off 0.01:31:25

EPON0/4:9 1c87.7913.f9cc auto-configured ctc-oam-oper 4838 2984 1970.01.01.13:52:43 1970.01.01.13:52:11 wire-down 0.01:29:36

EPON0/4:10 1c87.7914.0d43 auto-configured ctc-oam-oper 4864 3000 1970.01.01.13:52:43 1970.01.01.13:52:11 wire-down 0.01:29:36

EPON0/4:11 1c87.7913.ea84 auto-configured ctc-oam-oper 4107 2533 1970.01.01.11:48:46 1970.01.01.11:48:14 wire-down 0.03:33:33

EPON0/4:12 1c87.7914.0d40 auto-configured ctc-oam-oper 4814 2969 1970.01.01.15:20:31 1970.01.01.15:19:58 wire-down 0.00:01:48

EPON0/4:13 8014.a867.d970 auto-configured ctc-oam-oper 1992 1229 1970.01.01.00:00:26 1970.01.01.00:00:24 unknow 0.15:21:53

EPON0/4:14 8014.a867.d9b8 auto-configured ctc-oam-oper 2182 1346 1970.01.01.02:46:57 1970.01.01.00:58:40 power-off 0.12:35:22

EPON0/4:15 1c87.7914.0d31 auto-configured ctc-oam-oper 4814 2969 1970.01.01.13:50:05 1970.01.01.13:49:33 wire-down 0.01:32:14

Сигналы:

Olt_172.16.1.50#show epon optical-transceiver-diagnosis int epon 0/3

interface Temperature(degree) Voltage(V) Current(mA) TxPower(dBm)

----------- --------------------- ------------ ------------- --------------

epon0/3 54.1 3.4 40.0 6.2

interface RxPower(dBm)

----------- --------------

epon0/3:1 -13.7

epon0/3:2 -13.3

Olt_172.16.1.50#show epon optical-transceiver-diagnosis int epon 0/4

interface Temperature(degree) Voltage(V) Current(mA) TxPower(dBm)

----------- --------------------- ------------ ------------- --------------

epon0/4 46.6 3.4 34.6 6.4

interface RxPower(dBm)

----------- --------------

epon0/4:3 -26.0

epon0/4:4 -25.5

epon0/4:5 -29.2

epon0/4:7 -28.2

epon0/4:8 -25.2

epon0/4:9 -27.6

epon0/4:10 -27.2

epon0/4:12 -27.6

epon0/4:13 -26.9

epon0/4:14 -28.8

epon0/4:15 -27.2

Dimkers · 16 листопада, 2017

грустные сигналы... 29 - пичаль... Чуть че, сразу лось будет

logic · 16 листопада, 2017

Фора до - 27 работает

vetal_mix · 16 листопада, 2017

Как показала практика, фора отлично работает и за 30 . Суть не в том, суть в одновременных отвалах на разных ветках. На тестовом стенде с 2 онушками наблюдался отвал одной при включении другой. И при этом валились на другой ветке онушки.

Dimkers · 16 листопада, 2017

В логах при отвалах что происходит?

vetal_mix · 16 листопада, 2017

Olt_172.16.1.50#Jan 1 23:08:26 Alarm LASER_ALWAYS_ON from OLT 0x03000000 port EPON0/4 pon_diID 10

Jan 1 23:08:26 timestamp 0, window 0, threshold 0, value 0

Jan 1 23:08:26 Alarm LASER_ALWAYS_ON from OLT 0x03000000 port EPON0/4 pon_diID 10

Jan 1 23:08:26 timestamp 0, window 0, threshold 0, value 0

Jan 1 23:08:45 %LINE-5-UPDOWN: Line on Interface EPON0/3, changed state to down

Jan 1 23:08:45 %LINEPROTO-5-UPDOWN: Line protocol on Interface EPON0/3, changed state to down

Jan 1 23:08:45 %EPON-ONUDEREG: ONU 1c87.7913.ea90 is deregistered on EPON0/3:1.

Jan 1 23:08:45 %EPON-ONUDEREG: ONU 1c87.7913.ce6d is deregistered on EPON0/4:3.

Jan 1 23:08:45 %EPON-ONUDEREG: ONU 1c87.7913.f9cc is deregistered on EPON0/4:9.

Jan 1 23:08:45 %EPON-ONUDEREG: ONU 1c87.7913.ea84 is deregistered on EPON0/4:11.

Jan 1 23:08:45 %EPON-ONUDEREG: ONU 1c87.7914.0d31 is deregistered on EPON0/4:15.

Jan 1 23:08:45 %EPON-ONUDEREG: ONU 1c87.7913.b64c is deregistered on EPON0/4:6.

Jan 1 23:08:46 %EPON-ONUDEREG: ONU 1c87.7914.0d40 is deregistered on EPON0/4:12.

Jan 1 23:08:46 %EPON-ONUDEREG: ONU 1c87.7913.f4b0 is deregistered on EPON0/4:4.

Jan 1 23:08:46 %EPON-ONUDEREG: ONU 1c87.7913.ea7b is deregistered on EPON0/3:2.

Jan 1 23:08:46 %EPON-ONUDEREG: ONU 1c87.7914.0d43 is deregistered on EPON0/4:10.

Jan 1 23:08:46 %EPON-ONUDEREG: ONU 1c87.7913.ba48 is deregistered on EPON0/4:5.

Jan 1 23:09:17 %LINE-5-UPDOWN: Line on Interface EPON0/3, changed state to up

Jan 1 23:09:17 %LINEPROTO-5-UPDOWN: Line protocol on Interface EPON0/3, changed state to up

Jan 1 23:09:17 %EPON-ONUREG: ONU 1c87.7913.ea90 is registered on EPON0/3:1.

Jan 1 23:09:17 %EPON-ONUREG: ONU 1c87.7913.ea7b is registered on EPON0/3:2.

Jan 1 23:09:17 %EPON-ONUREG: ONU 1c87.7914.0d31 is registered on EPON0/4:15.

Jan 1 23:09:17 %EPON-ONUAUTHEN: ONU 1c87.7913.ea90 is authenticated on EPON0/3:1.

Jan 1 23:09:17 %EPON-ONUAUTHEN: ONU 1c87.7913.ea7b is authenticated on EPON0/3:2.

Jan 1 23:09:17 %EPON-ONUAUTHEN: ONU 1c87.7914.0d31 is authenticated on EPON0/4:15.

Jan 1 23:09:17 %EPON-ONUREG: ONU 1c87.7913.ce6d is registered on EPON0/4:3.

Jan 1 23:09:18 %EPON-ONUREG: ONU 1c87.7913.b64c is registered on EPON0/4:6.

Jan 1 23:09:18 %EPON-ONUREG: ONU 1c87.7913.ea84 is registered on EPON0/4:11.

Jan 1 23:09:18 %EPON-ONUAUTHEN: ONU 1c87.7913.ce6d is authenticated on EPON0/4:3.

Jan 1 23:09:18 %EPON-ONUAUTHEN: ONU 1c87.7913.b64c is authenticated on EPON0/4:6.

Jan 1 23:09:18 %EPON-ONUAUTHEN: ONU 1c87.7913.ea84 is authenticated on EPON0/4:11.

Jan 1 23:09:18 %EPON-ONUREG: ONU 1c87.7914.0d40 is registered on EPON0/4:12.

Jan 1 23:09:18 %EPON-ONUREG: ONU 1c87.7914.0d43 is registered on EPON0/4:10.

Jan 1 23:09:18 %EPON-ONUAUTHEN: ONU 1c87.7914.0d40 is authenticated on EPON0/4:12.

Jan 1 23:09:18 %EPON-ONUAUTHEN: ONU 1c87.7914.0d43 is authenticated on EPON0/4:10.

Jan 1 23:09:18 %EPON-ONUREG: ONU 1c87.7913.f9cc is registered on EPON0/4:9.

Jan 1 23:09:19 %EPON-ONUREG: ONU 1c87.7913.f4b0 is registered on EPON0/4:4.

Jan 1 23:09:19 %EPON-ONUREG: ONU 1c87.7913.ba48 is registered on EPON0/4:5.

Jan 1 23:09:19 %EPON-ONUAUTHEN: ONU 1c87.7913.f9cc is authenticated on EPON0/4:9.

Jan 1 23:09:19 %EPON-ONUAUTHEN: ONU 1c87.7913.f4b0 is authenticated on EPON0/4:4.

Jan 1 23:09:19 %OLT: Interface EPON0/3:2's OAM Operational Status: Operational

Jan 1 23:09:19 %OLT: Interface EPON0/3:1's OAM Operational Status: Operational

Jan 1 23:09:19 %OLT: Interface EPON0/4:3's OAM Operational Status: Operational

Jan 1 23:09:19 %OLT: Interface EPON0/4:15's OAM Operational Status: Operational

Jan 1 23:09:19 %OLT: Interface EPON0/4:6's OAM Operational Status: Operational

Jan 1 23:09:19 %OLT: Interface EPON0/4:11's OAM Operational Status: Operational

Jan 1 23:09:19 %EPON-ONUAUTHEN: ONU 1c87.7913.ba48 is authenticated on EPON0/4:5.

Jan 1 23:09:20 %OLT: Interface EPON0/4:10's OAM Operational Status: Operational

Jan 1 23:09:20 %OLT: Interface EPON0/4:9's OAM Operational Status: Operational

Jan 1 23:09:20 %OLT: Interface EPON0/4:4's OAM Operational Status: Operational

Jan 1 23:09:20 %OLT: Interface EPON0/4:12's OAM Operational Status: Operational

Jan 1 23:09:20 %OLT: Interface EPON0/4:5's OAM Operational Status: Operational

Jan 1 23:09:22 %OLT: Interface EPON0/3:2's CTC OAM extension negotiated successfully!

Jan 1 23:09:22 %OLT: Interface EPON0/3:1's CTC OAM extension negotiated successfully!

Jan 1 23:09:22 %OLT: Interface EPON0/4:3's CTC OAM extension negotiated successfully!

Jan 1 23:09:22 %OLT: Interface EPON0/4:15's CTC OAM extension negotiated successfully!

Jan 1 23:09:22 %OLT: Interface EPON0/4:6's CTC OAM extension negotiated successfully!

Jan 1 23:09:22 %OLT: Interface EPON0/4:11's CTC OAM extension negotiated successfully!

Jan 1 23:09:24 %OLT: Interface EPON0/4:10's CTC OAM extension negotiated successfully!

Jan 1 23:09:24 %OLT: Interface EPON0/4:9's CTC OAM extension negotiated successfully!

Jan 1 23:09:24 %OLT: Interface EPON0/4:4's CTC OAM extension negotiated successfully!

Jan 1 23:09:24 %OLT: Interface EPON0/4:12's CTC OAM extension negotiated successfully!

Jan 1 23:09:24 %OLT: Interface EPON0/4:5's CTC OAM extension negotiated successfully!

Jan 1 23:09:26 Alarm LASER_ALWAYS_ON from OLT 0x03000000 port EPON0/4 pon_diID 10

Jan 1 23:09:26 timestamp 0, window 0, threshold 0, value 0

Jan 1 23:09:26 Alarm LASER_ALWAYS_ON from OLT 0x03000000 port EPON0/4 pon_diID 10

Jan 1 23:09:26 timestamp 0, window 0, threshold 0, value 0

Jan 1 23:10:15 %LINE-5-UPDOWN: Line on Interface EPON0/3, changed state to down

Jan 1 23:10:15 %LINEPROTO-5-UPDOWN: Line protocol on Interface EPON0/3, changed state to down

Jan 1 23:10:15 %EPON-ONUDEREG: ONU 1c87.7914.0d40 is deregistered on EPON0/4:12.

Jan 1 23:10:15 %EPON-ONUDEREG: ONU 1c87.7913.f4b0 is deregistered on EPON0/4:4.

Jan 1 23:10:15 %EPON-ONUDEREG: ONU 1c87.7913.ea7b is deregistered on EPON0/3:2.

Jan 1 23:10:15 %EPON-ONUDEREG: ONU 1c87.7913.ea90 is deregistered on EPON0/3:1.

Jan 1 23:10:15 %EPON-ONUDEREG: ONU 1c87.7913.ce6d is deregistered on EPON0/4:3.

Jan 1 23:10:15 %EPON-ONUDEREG: ONU 1c87.7913.b64c is deregistered on EPON0/4:6.

Jan 1 23:10:15 %EPON-ONUDEREG: ONU 1c87.7913.f9cc is deregistered on EPON0/4:9.

Jan 1 23:10:16 %EPON-ONUDEREG: ONU 1c87.7913.ea84 is deregistered on EPON0/4:11.

Jan 1 23:10:16 %EPON-ONUDEREG: ONU 1c87.7914.0d31 is deregistered on EPON0/4:15.

Сегодня в логах появилась светящаяся онушка.

Dimkers · 16 листопада, 2017

Я думаю, что она появилась не сегодня как раз она и создает проблемы

Den_LocalNet · 16 листопада, 2017

а ткните пальцем в строчку где видно светящуюся онушку

vetal_mix · 17 листопада, 2017

Jan 1 23:09:26 Alarm LASER_ALWAYS_ON from OLT 0x03000000 port EPON0/4 pon_diID 10

Jan 1 23:09:26 timestamp 0, window 0, threshold 0, value 0

разве не эта строчка ?

Еще заметил, что с 22-00 до часов 12-00 отваливания происходят намного реже.

dsredline · 17 листопада, 2017

У нас такая строчка появлялась даже при включении 1 онушки , на стенде в офисе. Была где-то тема писали , что проблема проявляется на модуле Picotel, и что такой проблемы нет на FoxGate. Но у вас вроде FoxGate, в общем черт его знает... )

Відредаговано 17 листопада, 2017 dsredline

vetal_mix · 17 листопада, 2017

сейчас логи пишут:

Olt_1Nov 17 12:51:48 %EPON-ONUDEREG: ONU 1c87.7913.ce3a is deregistered on EPON0/4:8.

Nov 17 12:52:21 %EPON-ONUREG: ONU 1c87.7913.ce3a is registered on EPON0/4:8.

Nov 17 12:52:21 %EPON-ONUAUTHEN: ONU 1c87.7913.ce3a is authenticated on EPON0/4:8.

Nov 17 12:52:22 %OLT: Interface EPON0/4:8's OAM Operational Status: Operational

Nov 17 12:52:25 %OLT: Interface EPON0/4:8's CTC OAM extension negotiated successfully!

Nov 17 12:53:17 %VTY-3-AUTHEN: [iNFO] Vty waits for user's input timeout.

Nov 17 12:53:17 User default logouted from 172.16.1.150 on vty 1

Olt_172.16.1.50#Nov 17 13:01:59 %EPON-ONUDEREG: ONU 1c87.7913.ba48 is deregistered on EPON0/4:5.

Nov 17 13:01:59 %EPON-ONUDEREG: ONU 1c87.7913.ea84 is deregistered on EPON0/4:11.

Nov 17 13:01:59 %EPON-ONUDEREG: ONU 1c87.7914.0d31 is deregistered on EPON0/4:15.

Nov 17 13:01:59 %EPON-ONUDEREG: ONU 1c87.7914.0d43 is deregistered on EPON0/4:10.

Nov 17 13:01:59 %EPON-ONUDEREG: ONU 1c87.7914.0d40 is deregistered on EPON0/4:12.

Nov 17 13:01:59 %EPON-ONUDEREG: ONU 1c87.7913.b64c is deregistered on EPON0/4:6.

Nov 17 13:02:00 %EPON-ONUDEREG: ONU 1c87.7913.ce6d is deregistered on EPON0/4:3.

Nov 17 13:02:04 %EPON-ONUDEREG: ONU 1c87.7913.f9cc is deregistered on EPON0/4:9.

Nov 17 13:02:31 %EPON-ONUREG: ONU 1c87.7913.b64c is registered on EPON0/4:6.

Nov 17 13:02:31 %EPON-ONUREG: ONU 1c87.7914.0d31 is registered on EPON0/4:15.

Nov 17 13:02:31 %EPON-ONUAUTHEN: ONU 1c87.7913.b64c is authenticated on EPON0/4:6.

Nov 17 13:02:31 %EPON-ONUAUTHEN: ONU 1c87.7914.0d31 is authenticated on EPON0/4:15.

Nov 17 13:02:31 %EPON-ONUREG: ONU 1c87.7914.0d40 is registered on EPON0/4:12.

Nov 17 13:02:31 %EPON-ONUREG: ONU 1c87.7914.0d43 is registered on EPON0/4:10.

Nov 17 13:02:31 %EPON-ONUREG: ONU 1c87.7913.ba48 is registered on EPON0/4:5.

Nov 17 13:02:32 %EPON-ONUREG: ONU 1c87.7913.ea84 is registered on EPON0/4:11.

Nov 17 13:02:32 %EPON-ONUAUTHEN: ONU 1c87.7914.0d40 is authenticated on EPON0/4:12.

Nov 17 13:02:32 %EPON-ONUAUTHEN: ONU 1c87.7914.0d43 is authenticated on EPON0/4:10.

Nov 17 13:02:32 %EPON-ONUAUTHEN: ONU 1c87.7913.ba48 is authenticated on EPON0/4:5.

Nov 17 13:02:32 %EPON-ONUAUTHEN: ONU 1c87.7913.ea84 is authenticated on EPON0/4:11.

Nov 17 13:02:32 %OLT: Interface EPON0/4:15's OAM Operational Status: Operational

Nov 17 13:02:32 %OLT: Interface EPON0/4:6's OAM Operational Status: Operational

Nov 17 13:02:32 %EPON-ONUREG: ONU 1c87.7913.ce6d is registered on EPON0/4:3.

Nov 17 13:02:32 %EPON-ONUAUTHEN: ONU 1c87.7913.ce6d is authenticated on EPON0/4:3.

Nov 17 13:02:33 %OLT: Interface EPON0/4:11's OAM Operational Status: Operational

Nov 17 13:02:33 %OLT: Interface EPON0/4:10's OAM Operational Status: Operational

Nov 17 13:02:33 %OLT: Interface EPON0/4:5's OAM Operational Status: Operational

Nov 17 13:02:33 %OLT: Interface EPON0/4:12's OAM Operational Status: Operational

Nov 17 13:02:34 %OLT: Interface EPON0/4:3's OAM Operational Status: Operational

Nov 17 13:02:35 %OLT: Interface EPON0/4:15's CTC OAM extension negotiated successfully!

Nov 17 13:02:35 %OLT: Interface EPON0/4:6's CTC OAM extension negotiated successfully!

Nov 17 13:02:36 %EPON-ONUREG: ONU 1c87.7913.f9cc is registered on EPON0/4:9.

Nov 17 13:02:36 %EPON-ONUAUTHEN: ONU 1c87.7913.f9cc is authenticated on EPON0/4:9.

Nov 17 13:02:36 %OLT: Interface EPON0/4:11's CTC OAM extension negotiated successfully!

Nov 17 13:02:36 %OLT: Interface EPON0/4:10's CTC OAM extension negotiated successfully!

Nov 17 13:02:36 %OLT: Interface EPON0/4:5's CTC OAM extension negotiated successfully!

Nov 17 13:02:36 %OLT: Interface EPON0/4:12's CTC OAM extension negotiated successfully!

Nov 17 13:02:37 %OLT: Interface EPON0/4:9's OAM Operational Status: Operational

Nov 17 13:02:37 %OLT: Interface EPON0/4:3's CTC OAM extension negotiated successfully!

Nov 17 13:02:40 %OLT: Interface EPON0/4:9's CTC OAM extension negotiated successfully!

Nov 17 13:25:39 %EPON-ONUDEREG: ONU 1c87.7913.ba48 is deregistered on EPON0/4:5.

Nov 17 13:25:39 %EPON-ONUDEREG: ONU 1c87.7913.ea84 is deregistered on EPON0/4:11.

Nov 17 13:25:39 %EPON-ONUDEREG: ONU 1c87.7914.0d31 is deregistered on EPON0/4:15.

Nov 17 13:25:39 %EPON-ONUDEREG: ONU 1c87.7914.0d40 is deregistered on EPON0/4:12.

Nov 17 13:25:39 %EPON-ONUDEREG: ONU 1c87.7914.0d43 is deregistered on EPON0/4:10.

Nov 17 13:25:50 %EPON-ONUDEREG: ONU 1c87.7913.ce6d is deregistered on EPON0/4:3.

Nov 17 13:26:11 %EPON-ONUREG: ONU 1c87.7914.0d40 is registered on EPON0/4:12.

Nov 17 13:26:11 %EPON-ONUREG: ONU 1c87.7914.0d31 is registered on EPON0/4:15.

Nov 17 13:26:11 %EPON-ONUAUTHEN: ONU 1c87.7914.0d40 is authenticated on EPON0/4:12.

Nov 17 13:26:11 %EPON-ONUAUTHEN: ONU 1c87.7914.0d31 is authenticated on EPON0/4:15.

Nov 17 13:26:11 %EPON-ONUREG: ONU 1c87.7913.ea84 is registered on EPON0/4:11.

Nov 17 13:26:11 %EPON-ONUREG: ONU 1c87.7914.0d43 is registered on EPON0/4:10.

Nov 17 13:26:11 %EPON-ONUAUTHEN: ONU 1c87.7913.ea84 is authenticated on EPON0/4:11.

Nov 17 13:26:11 %EPON-ONUAUTHEN: ONU 1c87.7914.0d43 is authenticated on EPON0/4:10.

Nov 17 13:26:12 %EPON-ONUREG: ONU 1c87.7913.ba48 is registered on EPON0/4:5.

Nov 17 13:26:12 %EPON-ONUAUTHEN: ONU 1c87.7913.ba48 is authenticated on EPON0/4:5.

Nov 17 13:26:12 %OLT: Interface EPON0/4:11's OAM Operational Status: Operational

Nov 17 13:26:12 %OLT: Interface EPON0/4:15's OAM Operational Status: Operational

Nov 17 13:26:12 %OLT: Interface EPON0/4:10's OAM Operational Status: Operational

Nov 17 13:26:12 %OLT: Interface EPON0/4:12's OAM Operational Status: Operational

Nov 17 13:26:13 %OLT: Interface EPON0/4:5's OAM Operational Status: Operational

Nov 17 13:26:15 %OLT: Interface EPON0/4:11's CTC OAM extension negotiated successfully!

Nov 17 13:26:15 %OLT: Interface EPON0/4:15's CTC OAM extension negotiated successfully!

Nov 17 13:26:15 %OLT: Interface EPON0/4:10's CTC OAM extension negotiated successfully!

Nov 17 13:26:15 %OLT: Interface EPON0/4:12's CTC OAM extension negotiated successfully!

Nov 17 13:26:17 %OLT: Interface EPON0/4:5's CTC OAM extension negotiated successfully!

Nov 17 13:26:22 %EPON-ONUREG: ONU 1c87.7913.ce6d is registered on EPON0/4:3.

Nov 17 13:26:22 %EPON-ONUAUTHEN: ONU 1c87.7913.ce6d is authenticated on EPON0/4:3.

Nov 17 13:26:23 %OLT: Interface EPON0/4:3's OAM Operational Status: Operational

Nov 17 13:26:26 %OLT: Interface EPON0/4:3's CTC OAM extension negotiated successfully!

Куда копать уже не знаю. Абоны злющие, грозят расправой.

dsredline · 17 листопада, 2017

Я бы еще порекомендовал вам выкинуть сюда конфиг OLT, вдруг умные люди (а их тут много) да и найдут бок какой.

Відредаговано 17 листопада, 2017 dsredline

vetal_mix · 17 листопада, 2017

Согласен, вот мой конфиг.

!version 10.1.0E build 46085

service timestamps log date

service timestamps debug date

logging buffered 4096

!

hostname Olt_172.16.1.50

port-protected 1

!

epon mpcp-timeout 60

!

ip default-gateway 172.16.1.1

!

spanning-tree mode rstp

!

aaa authentication login default local

aaa authentication enable default enable

aaa authorization exec default local

!

username admin password 0

!

enable password 0 level 15

!

epon dynamic-binding-timeout 40

epon oam-version 1 0x21

epon oam-version 2 0x20

!

epon onu-config-template users77

cmd-sequence 001 epon onu port 1 ctc vlan mode tag 77

cmd-sequence 002 epon onu all-port loopback detect

!

!!slot 0 89

interface GigaEthernet0/1

description Uplink

switchport trunk vlan-untagged 1

switchport mode trunk

duplex full

!

interface GigaEthernet0/2

description Downolink

switchport trunk vlan-allowed 3,37,77,177,220,330

switchport trunk vlan-untagged 1

switchport mode trunk

duplex full

!

interface GigaEthernet0/3

switchport trunk vlan-untagged 1

switchport mode trunk

speed 1000

!

interface GigaEthernet0/4

switchport trunk vlan-untagged 1

switchport mode trunk

speed 1000

!

interface GigaEthernet0/5

switchport trunk vlan-untagged 1

switchport mode trunk

speed 1000

!

interface GigaEthernet0/6

switchport trunk vlan-untagged 1

switchport mode trunk

speed 1000

!

interface EPON0/1

epon pre-config-template users77 binded-onu-llid 1-64

epon bind-onu mac 1c87.7913.7fbf 4

switchport trunk vlan-allowed 3,37,77,177,220,330

switchport trunk vlan-untagged 1

switchport mode trunk

switchport protected 1

!

interface EPON0/1:4

!

interface EPON0/2

epon pre-config-template users77 binded-onu-llid 1-64

epon bind-onu mac fcfa.f7c5.fc3f 1

epon bind-onu mac 1c87.7914.0d07 2

switchport trunk vlan-untagged 1

switchport mode trunk

switchport protected 1

!

interface EPON0/2:1

!

interface EPON0/2:2

!

interface EPON0/3

epon onu-authen-method hybrid

epon pre-config-template users77 binded-onu-llid 1-64

epon bind-onu mac 1c87.7913.ea90 1

epon bind-onu mac 1c87.7913.ea7b 2

epon bind-onu mac 1c83.7913.ea7b 3

switchport trunk vlan-untagged 1

switchport mode trunk

switchport protected 1

!

interface EPON0/3:1

!

interface EPON0/3:2

!

interface EPON0/3:3

!

interface EPON0/4

epon pre-config-template users77 binded-onu-llid 1-64

epon onu-always-laser-on shut-time 200

epon bind-onu mac 8014.a867.d9c0 1

epon bind-onu mac 1c87.7914.1658 2

epon bind-onu mac 1c87.7913.ce6d 3

epon bind-onu mac 1c87.7913.f4b0 4

epon bind-onu mac 1c87.7913.ba48 5

epon bind-onu mac 1c87.7913.b64c 6

epon bind-onu mac 8014.a867.d9c8 7

epon bind-onu mac 1c87.7913.ce3a 8

epon bind-onu mac 1c87.7913.f9cc 9

epon bind-onu mac 1c87.7914.0d43 10

epon bind-onu mac 1c87.7913.ea84 11

epon bind-onu mac 1c87.7914.0d40 12

epon bind-onu mac 8014.a867.d970 13

epon bind-onu mac 8014.a867.d9b8 14

epon bind-onu mac 1c87.7914.0d31 15

switchport trunk vlan-untagged 1

switchport mode trunk

switchport protected 1

epon fec-rx

epon fec-tx

epon error-frame-alarm

!

interface EPON0/4:1

!

interface EPON0/4:2

!

interface EPON0/4:3

!

interface EPON0/4:4

!

interface EPON0/4:5

!

interface EPON0/4:6

!

interface EPON0/4:7

!

interface EPON0/4:8

!

interface EPON0/4:9

!

interface EPON0/4:10

!

interface EPON0/4:11

!

interface EPON0/4:12

!

interface EPON0/4:13

!

interface EPON0/4:14

!

interface EPON0/4:15

!

!!slot end

!

interface VLAN3

description manager

ip address 172.16.1.50 255.255.255.0

!

vlan 37

name 37

!

vlan 1,3,37,77,110,177,220,330

!

ip http server

!

snmp-server community 0 public RO

!

line vty 0

exec-timeout 0

!

line vty 1

exec-timeout 0

!

line vty 2

exec-timeout 0

!

line vty 3

exec-timeout 0

!

line vty 4

exec-timeout 0

!

line vty 5

exec-timeout 0

!

line vty 6

exec-timeout 0

!

line vty 7

exec-timeout 0

!

line vty 8

exec-timeout 0

!

line vty 9

exec-timeout 0

!

line vty 10

exec-timeout 0

!

line vty 11

exec-timeout 0

!

line vty 12

exec-timeout 0

!

line vty 13

exec-timeout 0

!

line vty 14

exec-timeout 0

!

line vty 15

exec-timeout 0

!

line vty 16

exec-timeout 0

!

line vty 17

exec-timeout 0

!

line vty 18

exec-timeout 0

!

line vty 19

exec-timeout 0

!

line vty 20

exec-timeout 0

!

line vty 21

exec-timeout 0

!

line vty 22

exec-timeout 0

!

line vty 23

exec-timeout 0

!

line vty 24

exec-timeout 0

!

line vty 25

exec-timeout 0

!

line vty 26

exec-timeout 0

!

line vty 27

exec-timeout 0

!

line vty 28

exec-timeout 0

!

line vty 29

exec-timeout 0

!

line vty 30

exec-timeout 0

!

line vty 31

exec-timeout 0

!

time-zone tz 2 0

!

!Pending configurations for absent linecards:

!

!No configurations pending global

Den_LocalNet · 17 листопада, 2017

Jan 1 23:09:26 Alarm LASER_ALWAYS_ON from OLT 0x03000000 port EPON0/4 pon_diID 10

Jan 1 23:09:26 timestamp 0, window 0, threshold 0, value 0

разве не эта строчка ?

Еще заметил, что с 22-00 до часов 12-00 отваливания происходят намного реже.

У меня такое проскакивает на всех епон портах на столе без онушек вовсе. Модуля фоксгейт. На работу абонентов этот выхлоп в лог у меня не влияет.

boroda · 19 листопада, 2017

А сколько зарегистрировано онушек на ветках?

vetal_mix · 20 листопада, 2017

13 онушек на 4 ветке. на остальных пусто.

Приняли решение заменить форы на фоксгейты у абонентов. Если будет продолжаться такая же история - будем менять производителя

Відредаговано 20 листопада, 2017 vetal_mix

vetal_mix · 21 листопада, 2017

пришли онушки фоксгейт 1001wz. Везде пишут что совместим с бдком 3310. но увы, обвалы продолжаются, запустили на тестовую ветку 2 онушки, картина таже. Внутри пришедших фоксгейтов чип от zte,

фоксгейт:

ONU Vender ID : xPON ONU MODEL ID : 100Z ONU ID : e067.b337.8d21 Hardware Version : V2.3 Software Version : V1.1.4 Firmware Version : 0x010101 Chipset Vendor ID : Chipset MODEL ID : 0x9110 Chipset Revision : 40 Chipset Date : 14/01/01 Onu type : SFU Support multillid : Not supported Protection type : Not supported Number of Pon : 1 Number of slot : 0 Support 5 types of port: Number of GE port : 1 Battery Backup : 0 Olt_172.16.1.50_config# operating temperature(degree): 34 supply voltage(V): 3.3 bias current(mA): 18.5 transmitted power(DBm): 1.9 received power(DBm): -10.4

Фора

ONU Vender ID : FORA ONU MODEL ID : 101E ONU ID : 1c87.7913.f4b0 Hardware Version : V2.3 Software Version : V1.1.4 Firmware Version : 0x010101 Chipset Vendor ID : Chipset MODEL ID : 0x9110 Chipset Revision : 40 Chipset Date : 14/01/01 Onu type : SFU Support multillid : Not supported Protection type : Not supported Number of Pon : 1 Number of slot : 0 Support 5 types of port: Number of GE port : 1 Battery Backup : 0 Olt_172.16.1.50_config# operating temperature(degree): 29 supply voltage(V): 3.3 bias current(mA): 17.9 transmitted power(DBm): 1.9 received power(DBm): -22.4

Как видно, хардвейр и софтвейр версии совпадают, соответственно они одинаковые внутри но разные снаружи.... ((

Увійти

UA.PON v6.0

Рекомендованные сообщения

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

upiter

Den_LocalNet

KaYot

Posted Images

Создайте аккаунт или войдите в него для комментирования

Создать аккаунт

Вхід

Зараз на сторінці 0 користувачів