Lik

cmd-sequence 009 epon onu all-port storm-control mode 4 threshold 256 А такой шаблон если использовать на магистральной ону с 35 абонентов, Это не будет доставлять проблемы, или на магистральную ону нужно большее писать шторм контроль.?

Доброй ночи.Подскажите есть P3310C BIOS Version0.4.1 Firmware Version10.1.0E Build 46085 Есть вход в olt G3 и есть резервный вход G5, с такими же Vlan.Кто-то сталкивался с шаблоном.По умолчанию G3 в случает отвала линка Авто включение G5? OLT1-config#interface port-aggregator 1 OLT1-config_p1#switchport mode trunk interface GigaEthernet0/3 description AGG-LINK1 aggregator-group 1 mode lacp switchport mode trunk ! interface GigaEthernet0/5 description AGG-LINK2 aggregator-group 1 mode lacp switchport mode trunk

А не подскажете на домашний комп можно установить pon control нужно мониторинг BD com 3310c графики нагрузки с sfp портов.

забыл сказать, админы спасибо можете удалять тему.

Проблема решена, оказалось что тот кто настраивал голову указал, vlan1 ip 192.168.100.10 и что онушки есть тоже с такими маками по умолчанию. Заменил диапазон ip vlan1 и все закончилось.Всем спасибо за помощь хоть я не админ но с вашей помощью решил.

модуль с++ +7 просто я корень поставил на 1-8 а дальшее поставил 10-90+1-8 20-80_1-8 30-70+1-8 40-60+1.8 и 1-8 абонентов подключил 46 ону вот решил завтра препаять корень поставить на 1-4 два и повесить на 2 порта.

пусть сами разбираются.???

my-switch> my-switch>enable my-switch#config my-switch_config#show epon optical-transceiver-diagnosis interface EPON 0/1 interface Temperature(degree) Voltage(V) Current(mA) TxPower(dBm) ----------- --------------------- ------------ ------------- -------------- epon0/1 21.6 3.3 35.8 6.4 interface RxPower(dBm) ----------- -------------- epon0/1:2 -23.8 epon0/1:3 -27.6 epon0/1:4 -24.0 epon0/1:5 -15.1 epon0/1:6 -24.4 epon0/1:7 -26.5 epon0/1:8 -20.1 epon0/1:9 -26.5 epon0/1:10 -26.0 epon0/1:11 -25.3 epon0/1:13 -23.8 epon0/1:14 -25.0 epon0/1:15 -22.2 epon0/1:16 -22.4 epon0/1:17 -22.5 epon0/1:18 -26.7 epon0/1:19 -24.5 epon0/1:20 -25.6 --More--

my-switch_config#interface epON 0/1:46 onu ctc optical-transceiver-diagnosis operating temperature(degree): 26 supply voltage(V): 3.4 bias current(mA): 9.9 transmitted power(DBm): 1.8 received power(DBm): -25.7 my-switch_config#interface epON 0/1:17 onu ctc optical-transceiver-diagnosis operating temperature(degree): 32 supply voltage(V): 3.4 bias current(mA): 11.2 transmitted power(DBm): 1.7 received power(DBm): -20.9 my-switch_config#

my-switch> my-switch>enable my-switch#config my-switch_config#sh▒epon onu-software▒version sh▒epon onu-software▒version ^ Unknown command my-switch_config#epon onu-software▒version epon onu-software▒version ^

ну как сказать с месец наверно ранее не было доступа. это засвет медик 1310?

EPON0/1:41Down0x00000000e067.b3c0.0e58N/AstaticlostunknowDetail EPON0/1:42ConnectCDT101Ze067.b3c1.5425N/Astaticauto-configuredN/ADetail EPON0/1:43ConnectCDT101Ze067.b3c0.0560N/Astaticauto-configuredN/ADetail EPON0/1:44ConnectCDT101Ze067.b3c1.571fpol-2staticauto-configuredN/ADetail EPON0/1:45DownCDT101Ze067.b3c0.051asov-10staticderegisteredpower-offDetail EPON0/1:46ConnectCDT101Ze067.b3c1.5733sov-10staticauto-configuredN/ADetail EPON0/2:1ConnectxPON101Ze067.b3b0.eea0N/Astaticauto-configuredN/ADetail EPON0/2:2ConnectCDT101Ze067.b3ba.d20cvol-5-1staticauto-configuredN/ADetail EPON0/2:3ConnectCDT101Ze067.b3ba.d4a0sta-4staticauto-configuredN/ADetail EPON0/2:4ConnectxPON101Ze067.b3b0.eea6Sv-37staticauto-configuredN/ADetail EPON0/2:5ConnectxPON101Ze067.b3be.fc42N/Astaticauto-configuredN/ADetail EPON0/2:6ConnectxPON101Ze067.b3be.fc6elenn-7staticauto-configuredN/ADetail EPON0/2:7ConnectCDT101Ze067.b3c0.095asv-12staticauto-configuredN/ADetail EPON0/2:8ConnectCDT101Ze067.b3c1.5429les-30staticauto-configuredN/ADetail EPON0/2:9ConnectCDT101Ze067.b3c1.5427les-3staticauto-configuredN/ADetail EPON0/2:10ConnectCDT101Ze067.b3c0.0df0

не неnу есть C data и без надписи тоже белые как c data

а не поможете с решением данной проблемы warnings(4)FEB 27 17:44:24%OLT: Interface EPON0/1:17's CTC OAM extension negotiated successfully! warnings(4)FEB 27 17:44:20%OLT: Interface EPON0/1:17's OAM Operational Status: Operational warnings(4)FEB 27 17:44:19%EPON-ONUAUTHEN: ONU e067.b3be.f8dc is authenticated on EPON0/1:17. warnings(4)FEB 27 17:44:19%EPON-ONUREG: ONU e067.b3be.f8dc is registered on EPON0/1:17. warnings(4)FEB 27 17:43:45%EPON-ONUDEREG: ONU e067.b3be.f8dc is deregistered on EPON0/1:17. warnings(4)FEB 27 17:43:43%OLT: Interface EPON0/1:17's OAM Operational Status: Linkfault warnings(4)FEB 27 17:43:43%OLT: Interface EPON0/1:17's OAM Operational Status: Linkfault warnings(4)FEB 27 17:43:43timestamp 0, window 0, threshold 0, value 0 warnings(4)FEB 27 17:43:43Alarm DYING_GASP from ONU e067.b3be.f8dc port EPON0/1:17 warnings(4)FEB 27 17:34:35%OLT: Interface EPON0/1:46's CTC OAM extension negotiated successfully! warnings(4)FEB 27 17:34:32%OLT: Interface EPON0/1:46's OAM Operational Status: Operational warnings(4)FEB 27 17:34:31%EPON-ONUAUTHEN: ONU e067.b3c1.5733 is authenticated on EPON0/1:46. warnings(4)FEB 27 17:34:31%EPON-ONUREG: ONU e067.b3c1.5733 is registered on EPON0/1:46. warnings(4)FEB 27 17:33:55%EPON-ONUDEREG: ONU e067.b3c1.5733 is deregistered on EPON0/1:46. warnings(4)FEB 27 17:33:53%OLT: Interface EPON0/1:46's OAM Operational Status: Linkfault warnings(4)FEB 27 17:33:53%OLT: Interface EPON0/1:46's OAM Operational Status: Linkfault

Всем огромное спасибо все заработало после выключения stp

да я понял спасибо утром поеду попробую в tel net login pasword enable no spanning-tree write all

нету админа всем всё похер пытаюсь сам разобраться. Тесть у меня на олт 5vlan 104 106 115 116 113 мне надо no spanning-tree vlan 104-116 ??

да длинк я вам так и не скажу ну знаю что защита от кольца там включена везде.А вот олт надо найти stf

о щас посмотрю а где найти sft не подскажете

Добрый день подскажите пожалуйста начинающему.Есть магистральный коммутатор dlink DGS-3120 c него включены Olt 3310 с переодичностью высыпаться пакеты на dgs 3120 во всех vlan.Открыл лог а у меня оба свитча 2и 20 порт атаки.Подскажите что может это быть и как найти данный срач.Извеняюсь за безспокойство я сам монтажник админа нету. DGS-3120-24SC:admin#sh log Command: show log Index Date Time Level Log Text ----- ---------- -------- ------- ---------------------------------------------- 58074 2019-06-01 20:27:41 INFO(6) Successful login through Telnet (Username: adm in, IP: 192.168.20.111) 58073 2019-06-01 20:27:36 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 58072 2019-06-01 20:27:35 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 58071 2019-06-01 20:27:13 WARN(4) Login failed through Telnet (Username: admin47 15555, IP: 192.168.20.111) 58070 2019-06-01 20:26:36 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 58069 2019-06-01 20:26:35 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 58068 2019-06-01 20:25:36 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 58067 2019-06-01 20:25:35 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 58066 2019-06-01 20:24:36 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 58065 2019-06-01 20:24:35 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 58064 2019-06-01 20:23:36 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 58063 2019-06-01 20:23:35 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 58062 2019-06-01 20:22:36 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 58061 2019-06-01 20:22:35 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 58060 2019-06-01 20:21:36 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 58059 2019-06-01 20:21:36 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 58058 2019-06-01 20:20:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 58057 2019-06-01 20:20:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 58056 2019-06-01 20:19:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 58055 2019-06-01 20:19:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 58054 2019-06-01 20:19:23 INFO(6) Successful login through Web (Username: admin, IP: 192.168.20.111) 58053 2019-06-01 20:18:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 58052 2019-06-01 20:18:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 58051 2019-06-01 20:17:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 58050 2019-06-01 20:17:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 58049 2019-06-01 20:16:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 58048 2019-06-01 20:16:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 58047 2019-06-01 20:15:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 58046 2019-06-01 20:15:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 58045 2019-06-01 20:14:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 58044 2019-06-01 20:14:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 58043 2019-06-01 20:13:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 58042 2019-06-01 20:13:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 58041 2019-06-01 20:12:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 58040 2019-06-01 20:12:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 58039 2019-06-01 20:11:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 58038 2019-06-01 20:11:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 58037 2019-06-01 20:10:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 58036 2019-06-01 20:10:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 58035 2019-06-01 20:09:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 58034 2019-06-01 20:09:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 58033 2019-06-01 20:08:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 58032 2019-06-01 20:08:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 58031 2019-06-01 20:07:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 58030 2019-06-01 20:07:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 58029 2019-06-01 20:06:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 58028 2019-06-01 20:06:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 58027 2019-06-01 20:05:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 58026 2019-06-01 20:05:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 58025 2019-06-01 20:04:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 58024 2019-06-01 20:04:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 58023 2019-06-01 20:04:14 NOTI(5) Topology changed (Instance:0, Port:1:24,MAC:44 -E4-D9-A9-9A-00) 58022 2019-06-01 20:04:13 NOTI(5) Topology changed (Instance:0, Port:1:24,MAC:44 -E4-D9-A9-9A-00) 58021 2019-06-01 20:03:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 58020 2019-06-01 20:03:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 58019 2019-06-01 20:02:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 58018 2019-06-01 20:02:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 58017 2019-06-01 20:01:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 58016 2019-06-01 20:01:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 58015 2019-06-01 20:00:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 58014 2019-06-01 20:00:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 58013 2019-06-01 19:59:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 58012 2019-06-01 19:59:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 58011 2019-06-01 19:58:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 58010 2019-06-01 19:58:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 58009 2019-06-01 19:57:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 58008 2019-06-01 19:57:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 58007 2019-06-01 19:56:37 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 58006 2019-06-01 19:56:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 58005 2019-06-01 19:55:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 58004 2019-06-01 19:55:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 58003 2019-06-01 19:54:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 58002 2019-06-01 19:54:36 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 58001 2019-06-01 19:53:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 58000 2019-06-01 19:53:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 57999 2019-06-01 19:52:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 57998 2019-06-01 19:52:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 57997 2019-06-01 19:51:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 57996 2019-06-01 19:51:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 57995 2019-06-01 19:50:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 57994 2019-06-01 19:50:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 57993 2019-06-01 19:49:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 57992 2019-06-01 19:49:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 57991 2019-06-01 19:48:37 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 57990 2019-06-01 19:48:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 57989 2019-06-01 19:47:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 57988 2019-06-01 19:47:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 57987 2019-06-01 19:46:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 57986 2019-06-01 19:46:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 57985 2019-06-01 19:45:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 57984 2019-06-01 19:45:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 57983 2019-06-01 19:44:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 57982 2019-06-01 19:44:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 57981 2019-06-01 19:43:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 57980 2019-06-01 19:43:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 57979 2019-06-01 19:42:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 57978 2019-06-01 19:42:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 57977 2019-06-01 19:41:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 57976 2019-06-01 19:41:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 57975 2019-06-01 19:40:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 57974 2019-06-01 19:40:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 57973 2019-06-01 19:39:37 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 57972 2019-06-01 19:39:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 57971 2019-06-01 19:38:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 57970 2019-06-01 19:38:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 57969 2019-06-01 19:37:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 57968 2019-06-01 19:37:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 57967 2019-06-01 19:36:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 57966 2019-06-01 19:36:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 57965 2019-06-01 19:35:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 57964 2019-06-01 19:35:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 57963 2019-06-01 19:34:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 57962 2019-06-01 19:34:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 57961 2019-06-01 19:33:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 57960 2019-06-01 19:33:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 57959 2019-06-01 19:32:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop) 57958 2019-06-01 19:32:37 INFO(6) Port <1:2> recover from BPDU under attacking s tate automatically 57957 2019-06-01 19:31:38 INFO(6) Port <1:2> enter BPDU under attacking state (m ode: drop)

за 3500гр это 10000 рубл, я зубами себе буду зачищать кабель, ей цена красная 500гр

с разных точек чтобы вход был не с одного vlan

Вроде сделал как сказали дома буду проверю

под острил

tracert mail.ru 3 4 ms 5 ms 2 ms dipt-gw.donbass.net 4 4 ms 2 ms 1 ms gw.donbass.net 5 8 ms 8 ms 8 ms ae7-3152.RT.KVT.KSH.RU.retn.net [87.245.239.172] 6 40 ms 42 ms 41 ms ae25-4.RT.LIM.WAW.PL.retn.net [87.245.233.143] 7 41 ms 42 ms 41 ms 52.95.218.176 8 * * * Превышен интервал ожидания для запроса. 9 * * * Превышен интервал ожидания для запроса. 0 * * * Превышен интервал ожидания для запроса. 1 * * * Превышен интервал ожидания для запроса. 2 * * * Превышен интервал ожидания для запроса. 3 * * * Превышен интервал ожидания для запроса. 4 * * * Превышен интервал ожидания для запроса. 5 62 ms 62 ms 61 ms 52.93.111.155 6 61 ms 62 ms 58 ms 54.239.107.115 7 94 ms 74 ms 75 ms 52.93.23.116 8 * * * Превышен интервал ожидания для запроса. 9 * * * Превышен интервал ожидания для запроса. 0 * * * Превышен интервал ожидания для запроса. 1 * * * Превышен интервал ожидания для запроса. 2 * * * Превышен интервал ожидания для запроса. 3 61 ms 61 ms 59 ms ec2-3-120-25-179.eu-central-1.compute.amazonaws. m [3.120.25.179] такое наверно на подконтрольное стороне не видели