Каждый 5-10 минут поднимается и падает Line protocol на интерфейсе Vlan1

Добрый день!
На новом коммутаторе Cisco Catalyst WS-C2960-8TC-S сразу после включения обнаружена такая проблема - каждые несколько минут в консоль выводятся сообщения:

Oct 25 11:10:17.521: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Oct 25 11:11:07.626: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Oct 25 11:14:28.155: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Oct 25 11:15:18.328: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Oct 25 11:15:58.341: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Oct 25 11:16:48.480: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Oct 25 11:17:32.571: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Oct 25 11:18:22.667: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Oct 25 11:18:34.722: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Oct 25 11:19:24.886: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Oct 25 11:19:44.892: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Oct 25 11:20:35.107: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Oct 25 11:22:53.359: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Oct 25 11:23:43.548: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Oct 25 11:27:01.964: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Oct 25 11:27:52.094: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Oct 25 11:35:31.203: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Oct 25 11:36:21.308: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Oct 25 11:39:13.744: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Oct 25 11:40:03.824: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Oct 25 11:45:42.707: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Oct 25 11:46:58.960: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Oct 25 11:48:43.163: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Oct 25 11:49:33.193: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Oct 25 11:57:18.433: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Oct 25 11:58:08.681: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Oct 25 12:02:01.138: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Oct 25 12:02:51.285: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Oct 25 12:08:52.163: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Oct 25 12:09:42.201: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Oct 25 12:11:40.547: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Oct 25 12:12:30.778: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up

vlan1 настроен так:

interface Vlan1
ip address 10.23.5.1 255.255.248.0
no ip route-cache

предположение о том, что коммутаторы не могу договориться о скорости передачи не подтвердилось. после установки принудительно скорости на интерфейсе симптомы остались прежними.

interface FastEthernet0/8
speed 100
duplex full

прошивка такая:
Cisco IOS Software, C2960 Software (C2960-LANLITEK9-M), Version 12.2(50)SE5, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Tue 28-Sep-10 13:44 by prod_rel_team
Image text-base: 0x00003000, data-base: 0x01200000

ROM: Bootstrap program is C2960 boot loader
BOOTLDR: C2960 Boot Loader (C2960-HBOOT-M) Version 12.2(46r)SE, RELEASE SOFTWARE (fc2)


у меня нет сертификации по cisco, поэтому прошу быть снисходительными

может кто-нибудь помочь с этой проблемой?

0

физика проверенная?
ошибки на интерфейсе?
конфиг можно?

0

да, физика проверенная. подключали к разным устройствам и разными патч-кордами - и к д-линку и к hp procurve на разных скоростях - гигабит и 100 мегабит.
симптомы остаются.

ошибки на интерфейсе смотрятся каким образом? имеются в виду логи?
команда sh logging дает такой вывод:

Switch#sh log
Syslog logging: enabled (0 messages dropped, 0 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled)

No Active Message Discriminator.



No Inactive Message Discriminator.


Console logging: level debugging, 73066 messages logged, xml disabled,
filtering disabled
Monitor logging: level debugging, 0 messages logged, xml disabled,
filtering disabled
Buffer logging: level debugging, 73066 messages logged, xml disabled,
filtering disabled
Exception Logging: size (4096 bytes)
Count and timestamp logging messages: disabled
File logging: disabled
Persistent logging: disabled

No active filter modules.

Trap logging: level informational, 73050 message lines logged

Log Buffer (4096 bytes):
OWN: Line protocol on Interface Vlan1, changed state to down
Oct 25 13:20:57.388: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Oct 25 13:24:25.970: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Oct 25 13:25:16.034: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Oct 25 13:25:54.395: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Oct 25 13:25:55.393: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/8, changed state to down
Oct 25 13:25:58.413: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/8, changed state to up
Oct 25 13:26:27.429: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Oct 25 13:26:47.545: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Oct 25 13:27:37.742: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Oct 25 13:28:45.833: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Oct 25 13:29:35.988: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Oct 25 13:29:57.488: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Oct 25 13:30:27.503: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Oct 25 13:35:24.526: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Oct 25 13:35:25.508: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/8, changed state to down
Oct 25 13:35:28.519: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/8, changed state to up
Oct 25 13:35:57.536: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Oct 25 13:40:22.255: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Oct 25 13:41:12.343: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Oct 25 13:41:58.481: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Oct 25 13:43:29.841: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Oct 25 13:47:54.669: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Oct 25 13:47:55.659: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/8, changed state to down
Oct 25 13:47:58.679: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/8, changed state to up
Oct 25 13:48:27.687: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Oct 25 13:50:06.001: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Oct 25 13:50:56.115: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Oct 25 13:56:00.865: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Oct 25 13:56:50.961: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Oct 25 13:57:47.115: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Oct 25 13:58:37.253: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Oct 25 14:03:17.953: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Oct 25 14:04:07.999: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Oct 25 14:06:10.356: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Oct 25 14:07:00.587: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Oct 25 14:10:59.058: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Oct 25 14:11:49.230: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Oct 25 14:15:21.739: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Oct 25 14:17:01.983: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Oct 25 14:18:00.082: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to down
Oct 25 14:18:50.254: %LINEPROTO-5-UPDOWN: Line protocol on Interface Vlan1, changed state to up
Switch#


сам конфиг такой:

Switch#sh run
Building configuration...

Current configuration : 3068 bytes
!
! Last configuration change at 10:57:10 UTC Thu Oct 25 2012 by 23-it
! NVRAM config last updated at 12:07:53 UTC Mon Jul 2 2012 by ru-it
!
version 12.2
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
!
hostname Switch
!
boot-start-marker
boot-end-marker
!
enable secret 5 ********************
!
username ***** password 7 ****************************
username ***** privilege 15 secret 5 *********************************
aaa new-model
!
!
aaa authentication login default local
aaa authorization exec default local
!
!
!
aaa session-id common
system mtu routing 1500
ip subnet-zero
!
!
ip domain-name baucenter.ru
!
!
crypto pki trustpoint TP-self-signed-711684736
enrollment selfsigned
subject-name cn=IOS-Self-Signed-Certificate-711684736
revocation-check none
rsakeypair TP-self-signed-711684736
!
!
crypto pki certificate chain TP-self-signed-711684736
certificate self-signed 01
30820249 308201B2 A0030201 02020101 300D0609 2A864886 F70D0101 04050030
30312E30 2C060355 04031325 494F532D 53656C66 2D536967 6E65642D 43657274
69666963 6174652D 37313136 38343733 36301E17 0D393330 33303130 30303130
335A170D 32303031 30313030 30303030 5A303031 2E302C06 03550403 1325494F
532D5365 6C662D53 69676E65 642D4365 72746966 69636174 652D3731 31363834
37333630 FF4EF0AF 06092A86 4886F70D 01010105 FF4EF0AF 00308189 02818100
BF36D418 03BBFE1B ABA9A6ED F5FAC655 E9351903 C708C7FB C0C7B710 AC7860F8
B0BD1E52 4D2EC06D 3C3F454A C281A08B 6C3EB801 6426F016 7449F391 D7CF99A9
EB71A3F1 851B22EE C5728E8D 928E6348 D285DF70 DF244494 41EBB8EE 6990AD54
B459E458 EAA938DF 5CC33003 ECC8FDBB 03D26CBC B0BF560E AED7D204 C42636E7
02030100 01A37330 71300F06 03551D13 0101FF04 05300301 01FF301E 0603551D
11041730 15821353 77697463 682E6261 7563656E 7465722E 7275301F 0603551D
23041830 1680144A A86AAA5B FF4EF0AF 67A21691 152B7C70 2A2D1730 1D060355
1D0E0416 04144AA8 6AAA5BFF 4EF0AF67 A2169115 2B7C702A 2D17300D 06092A86
4886F70D 01010405 00038181 0083C342 828FAAC6 A6A7E798 426E7E69 F4D8A8B6
0D5805DD B66B7E93 9313705D CA616664 2FF3CB23 2D8CFF91 66D25F97 90423E58
DFA22E6D 3292B975 0B9E722E 5763CBCA 5FDE6EDD FE9A02D7 ABA4872B 24735307
15B26F46 EBCB790A A261B2C1 89DBA26E BE1602C7 6C417CDD 5302220C F66DFF7A
7C22369D E77669DE 504240CB 68
quit
!
!
!
!
!
spanning-tree mode pvst
spanning-tree extend system-id
!
vlan internal allocation policy ascending
!
ip ssh version 2
!
interface FastEthernet0/1
switchport mode access
!
interface FastEthernet0/2
!
interface FastEthernet0/3
!
interface FastEthernet0/4
!
interface FastEthernet0/5
!
interface FastEthernet0/6
!
interface FastEthernet0/7
!
interface FastEthernet0/8
speed 100
duplex full
!
interface GigabitEthernet0/1
!
interface Vlan1
ip address 10.23.5.1 255.255.248.0
no ip route-cache
!
ip default-gateway 10.23.1.1
ip http server
ip http secure-server
!
control-plane
!
!
line con 0
line vty 0 4
privilege level 15
transport input ssh
line vty 5 15
privilege level 15
transport input ssh
!
end

Switch#

сейчас коммутатор подключен через интерфейс fa0/8

0

0

Switch#sh int fa0/8
FastEthernet0/8 is up, line protocol is up (connected)
Hardware is Fast Ethernet, address is d4a0.2a6b.7288 (bia d4a0.2a6b.7288)
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 100Mb/s, media type is 10/100BaseTX
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:13, output 00:00:01, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/0 (size/max)
5 minute input rate 4000 bits/sec, 6 packets/sec
5 minute output rate 1000 bits/sec, 1 packets/sec
173276 packets input, 13929003 bytes, 0 no buffer
Received 162010 broadcasts (34896 multicasts)
0 runts, 0 giants, 0 throttles
2 input errors, 2 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 34896 multicast, 0 pause input
0 input packets with dribble condition detected
24851 packets output, 1928286 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 PAUSE output
0 output buffer failures, 0 output buffers swapped out
Switch#

активность на нем есть потому что я коммутатор постоянно пингую

0

статус L1 для SVI всегда up, в то время как L2 статус тогда up, когда есть хотя бы один порт в соответствующем вилане в up, можно предположить, что перестраивается стп или по другой причине дергается интерфейс(-ы) принадлежащий этому vlan.

1

Отключение STP на vlan1 решило проблему.
Огромное спасибо за помощь.
Теперь, когда причина такого поведения известна будем настраивать работу STP так, чтобы он не перестраивался каждые 5 минут.
Еще раз спасибо!

0

Сообщение от Sandman319 Еще раз спасибо!

Всегда пожалуйста, ищите петлю в сети)

0

Сообщение от Jabbson ищите петлю в сети

а может быть дело не в петле?

0

Сообщение от jlevistk а может быть дело не в петле?

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

0

Сообщение от Jabbson надеюсь автор потом расскажет что было)

я тоже..)

0