Перейти до

olt bd com 3310 BPDU under attacking state


Lik

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

Добрый день подскажите пожалуйста начинающему.Есть магистральный коммутатор 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)

Ссылка на сообщение
Поделиться на других сайтах

Отключаем на олте stp. Оно по умолчанию включено и соответственно срет bpdu пакетами в порт вышестоящего мутатора

Ссылка на сообщение
Поделиться на других сайтах

Длинк учавствует в кольце? Если нет то вырубайте глобально на свитче disable stp и после ещё config stp ports 1:1-1:24 state disable

Відредаговано NaviNavi
Ссылка на сообщение
Поделиться на других сайтах
1 минуту назад, Lik сказал:

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

На олте дайте комманду no spanning-tree

Ссылка на сообщение
Поделиться на других сайтах
7 минут назад, Lik сказал:

нету админа всем всё похер пытаюсь сам разобраться.

Тесть у меня на олт 5vlan 104 106 115 116 113 мне надо no spanning-tree vlan 104-116  ??

Просто no spanning-tree без влан и прочего. После этого сохранить конфиг нужно, на 3310в write комманда а на 3310с write all

Ссылка на сообщение
Поделиться на других сайтах
22 минуты назад, Lik сказал:

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

Если напрягает консоль - из вебки advanced configuration - stp config - protocol type "disable". Apply - save all.

 

 

Screenshot_20200224-201550.jpg

Ссылка на сообщение
Поделиться на других сайтах

 а не поможете с решением данной проблемы 

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

Ссылка на сообщение
Поделиться на других сайтах
11 минут назад, Lik сказал:

 а не поможете с решением данной проблемы 

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

вижу в дергающихся c-data. Готов поспорить что и тк-линки есть. версию фирмвари всех онушек в студию, наверно.

Відредаговано nedoinet
Ссылка на сообщение
Поделиться на других сайтах
1 минуту назад, Lik сказал:

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

Определяются как xpon с аналогичными маками) небрендированая цдата. Вся ветка себя так ведет?

Ссылка на сообщение
Поделиться на других сайтах

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

Ссылка на сообщение
Поделиться на других сайтах
12 минут назад, Lik сказал:

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

это засвет медик 1310?

Может тухлая онушка. Или тут было с месяц назад, что силан отгружвет онушки с косячной прошивкой, которые при включении несколько секунд "светят"

Ссылка на сообщение
Поделиться на других сайтах

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
     ^
 

Ссылка на сообщение
Поделиться на других сайтах

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

Вы должны быть пользователем, чтобы оставить комментарий

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

Зарегистрируйтесь для получения аккаунта. Это просто!

Зарегистрировать аккаунт

Вхід

Уже зарегистрированы? Войдите здесь.

Войти сейчас
×
×
  • Створити нове...