WEP-12AC и странное поведение на порту cisco

[Tamahome]

Странное поведение:
Hardware Version: 2v8
Device Description: WEP-12AC
Firmware Version: 1.11.2.7
После загрузки, минуты через 2-3 на порту cisco наблюдается следующее (включено debug vlan oir-events),и собственно никуда не уходит...
Вопрос, как это остановить?

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

Nov 22 16:17:42.968 MSK: STP CFG: found port cfg GigabitEthernet1/24 (517650F8)
Nov 22 16:17:42.968 MSK: STP CFG: get port param unknown 0 GigabitEthernet1/24 1=2 rc=1
Nov 22 16:17:42.968 MSK: STP CFG: found port cfg GigabitEthernet1/24 (517650F8)
Nov 22 16:17:42.968 MSK: STP CFG: get port param unknown 0 GigabitEthernet1/24 1=3 rc=1
Nov 22 16:17:42.968 MSK: STP CFG: found port cfg GigabitEthernet1/24 (517650F8)
Nov 22 16:17:42.968 MSK: STP CFG: get port param unknown 0 GigabitEthernet1/24 1=1 rc=1
Nov 22 16:17:42.968 MSK: STP CFG: found port cfg GigabitEthernet1/24 (517650F8)
Nov 22 16:17:42.968 MSK: STP CFG: get port param unknown 0 GigabitEthernet1/24 1=4 rc=1
Nov 22 16:17:42.968 MSK: STP CFG: found port cfg GigabitEthernet1/24 (517650F8)
Nov 22 16:17:42.968 MSK: STP CFG: get port param unknown 0 GigabitEthernet1/24 12=0 rc=1
Nov 22 16:17:42.968 MSK: STP CFG: found port cfg GigabitEthernet1/24 (517650F8)
Nov 22 16:17:42.968 MSK: STP CFG: get port param unknown 0 GigabitEthernet1/24 11=0 rc=1
Nov 22 16:17:42.968 MSK: STP CFG: found port cfg GigabitEthernet1/24 (517650F8)
Nov 22 16:17:42.968 MSK: STP CFG: get port param unknown 0 GigabitEthernet1/24 9=0 rc=1
Nov 22 16:17:42.968 MSK: STP CFG: found port cfg GigabitEthernet1/24 (517650F8)
Nov 22 16:17:42.968 MSK: STP CFG: get port param mst 0 GigabitEthernet1/24 10=0 rc=1
Nov 22 16:17:42.968 MSK: STP CFG: found port cfg GigabitEthernet1/24 (517650F8)
Nov 22 16:17:42.968 MSK: STP CFG: get port param mst 0 GigabitEthernet1/24 18=0 rc=1
Nov 22 16:17:42.968 MSK: STP CFG: found port cfg GigabitEthernet1/24 (517650F8)
Nov 22 16:17:42.968 MSK: STP CFG: get port param mst 0 GigabitEthernet1/24 18=0 rc=1
Nov 22 16:17:42.968 MSK: STP CFG: found port cfg GigabitEthernet1/24 (517650F8)
Nov 22 16:17:42.968 MSK: STP CFG: found port cfg GigabitEthernet1/24 (517650F8)
Nov 22 16:17:42.968 MSK: STP CFG: get port param unknown 0 GigabitEthernet1/24 7=3 rc=1
Nov 22 16:17:42.968 MSK: STP CFG: found port cfg GigabitEthernet1/24 (517650F8)
Nov 22 16:17:42.968 MSK: STP CFG: found port cfg GigabitEthernet1/24 (517650F8)
Nov 22 16:17:42.968 MSK: STP CFG: get port param unknown 0 GigabitEthernet1/24 4=0 rc=1
Nov 22 16:17:42.968 MSK: STP CFG: found port cfg GigabitEthernet1/24 (517650F8)
Nov 22 16:17:42.972 MSK: STP CFG: get port param unknown 0 GigabitEthernet1/24 3=0 rc=1
Nov 22 16:17:43.308 MSK: STP CFG: found port cfg GigabitEthernet1/39 (4BB364F0)
Nov 22 16:17:43.308 MSK: STP CFG: get port param unknown 0 GigabitEthernet1/39 1=2 rc=1
Nov 22 16:17:43.308 MSK: STP CFG: found port cfg GigabitEthernet1/39 (4BB364F0)
Nov 22 16:17:43.308 MSK: STP CFG: get port param unknown 0 GigabitEthernet1/39 1=3 rc=1
Nov 22 16:17:43.308 MSK: STP CFG: found port cfg GigabitEthernet1/39 (4BB364F0)
Nov 22 16:17:43.308 MSK: STP CFG: get port param unknown 0 GigabitEthernet1/39 1=1 rc=1
Nov 22 16:17:43.308 MSK: STP CFG: found port cfg GigabitEthernet1/39 (4BB364F0)
Nov 22 16:17:43.308 MSK: STP CFG: get port param unknown 0 GigabitEthernet1/39 1=4 rc=1
Nov 22 16:17:43.308 MSK: STP CFG: found port cfg GigabitEthernet1/39 (4BB364F0)
Nov 22 16:17:43.308 MSK: STP CFG: get port param unknown 0 GigabitEthernet1/39 12=0 rc=1
Nov 22 16:17:43.308 MSK: STP CFG: found port cfg GigabitEthernet1/39 (4BB364F0)
Nov 22 16:17:43.308 MSK: STP CFG: get port param unknown 0 GigabitEthernet1/39 11=0 rc=1
Nov 22 16:17:43.308 MSK: STP CFG: found port cfg GigabitEthernet1/39 (4BB364F0)
Nov 22 16:17:43.308 MSK: STP CFG: get port param unknown 0 GigabitEthernet1/39 9=0 rc=1
Nov 22 16:17:43.308 MSK: STP CFG: found port cfg GigabitEthernet1/39 (4BB364F0)
Nov 22 16:17:43.308 MSK: STP CFG: get port param mst 0 GigabitEthernet1/39 10=0 rc=1
Nov 22 16:17:43.308 MSK: STP CFG: found port cfg GigabitEthernet1/39 (4BB364F0)
Nov 22 16:17:43.308 MSK: STP CFG: get port param mst 0 GigabitEthernet1/39 18=0 rc=1
Nov 22 16:17:43.308 MSK: STP CFG: found port cfg GigabitEthernet1/39 (4BB364F0)
Nov 22 16:17:43.308 MSK: STP CFG: get port param mst 0 GigabitEthernet1/39 18=0 rc=1
Nov 22 16:17:43.308 MSK: STP CFG: found port cfg GigabitEthernet1/39 (4BB364F0)
Nov 22 16:17:43.308 MSK: STP CFG: found port cfg GigabitEthernet1/39 (4BB364F0)
Nov 22 16:17:43.308 MSK: STP CFG: get port param unknown 0 GigabitEthernet1/39 7=3 rc=1
Nov 22 16:17:43.308 MSK: STP CFG: found port cfg GigabitEthernet1/39 (4BB364F0)
Nov 22 16:17:43.308 MSK: STP CFG: found port cfg GigabitEthernet1/39 (4BB364F0)
Nov 22 16:17:43.308 MSK: STP CFG: get port param unknown 0 GigabitEthernet1/39 4=0 rc=1
Nov 22 16:17:43.308 MSK: STP CFG: found port cfg GigabitEthernet1/39 (4BB364F0)
Nov 22 16:17:43.308 MSK: STP CFG: get port param unknown 0 GigabitEthernet1/39 3=0 rc=1

Конфиг порта cisco бонален:

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

interface GigabitEthernet1/39
 description eltex-WIFI_td
 switchport
 switchport trunk encapsulation dot1q
 switchport trunk allowed vlan 607,614
 switchport mode trunk
end

[Olesja]

Добрый день!

Укажите модель Cisco и версию ОС.
Также необходима схема подключения.
В 39 порт подключена точка доступа, а что подключено в 24 порт? Приложите его конфигурацию.

Проблема была всегда или появилась после каких-то изменений/действий?
Точка доступа при этом работает корректно?

[Tamahome]

Добрый день.
Cisco 6509, версия:
Cisco IOS Software, s72033_rp Software (s72033_rp-ADVENTERPRISEK9-M), Version 15.1(2)SY7, RELEASE SOFTWARE (fc4)

в 24м порту шлюз Sterra
interface GigabitEthernet1/24
description s-terraLAN
ip vrf forwarding VPN
ip address 10.*.*.* 255.255.255.254
no cdp enable
end

С точкой проблем не замечено, просто интересует это поведение, которе обнаружили в режиме debug на cisco.

[Ruslan_]

Добрый день.
В приложенном логе данные сообщения наблюдаются и на интерфейсе Gi1/24, к которому подключена Sterra. Для начала вам следует обратиться в техническую поддержку Cisco и выяснить причину данных debug-сообщений.