Здравейте имам развитие по темата.Най вероятно е от ъпдейта на FW чиито интерфейс и служи за arp таргет.Повдигнал съм тикет към фирмата производител.При развитие ще пиша.Благодаря.

Здравей и благодаря за отговора.Другата машина я рестартирах вчера и за това грешките за по малко /не съм убеден на 100% но мисля че се махат при рестарт/.Текущо като евент сходен с началото на грешките съдейки по старите messages те стават адски много и често след ъпдейт на фирмуера на въпросният гейт който гонят по arp машините /това е FW paloalto/ но не мога да си обясня какво може това да окаже влияние.Извадих машините текущо от всички полисита и проверки за трафик , но не се влияe от това.

Относно частта за монитора не съм технически по линукс толкова напреднал и не съм наясно как да го сторя ,ако може да дадете hint.

Версиите са еднкави , както и машините са 1:1 еднакви.

Съдържанието е по надолу.Цели с arp ИП адрес на FW който винаги съществува е там за да се разбира дали са живи.

PBX1:
Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)
Bonding Mode: fault-tolerance (active-backup)
Primary Slave: eth0 (primary_reselect always)
Currently Active Slave: eth0
MII Status: up
MII Polling Interval (ms): 0
Up Delay (ms): 0
Down Delay (ms): 0
ARP Polling Interval (ms): 100
ARP IP target/s (n.n.n.n form): ХХХХ

Slave Interface: eth0
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 57
Permanent HW addr: 00:1d:09:11:57:e4
Slave queue ID: 0

Slave Interface: eth1
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 2
Permanent HW addr: 00:1d:09:11:57:e6
Slave queue ID: 0

PBX2

Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)

Bonding Mode: fault-tolerance (active-backup)
Primary Slave: eth0 (primary_reselect always)
Currently Active Slave: eth0
MII Status: up
MII Polling Interval (ms): 0
Up Delay (ms): 0
Down Delay (ms): 0
ARP Polling Interval (ms): 100
ARP IP target/s (n.n.n.n form): XXXX

Slave Interface: eth0
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 6627
Permanent HW addr: 00:1d:09:11:54:36
Slave queue ID: 0

Slave Interface: eth1
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 2
Permanent HW addr: 00:1d:09:11:54:38
Slave queue ID: 0

DAMN.ЗА съжаление пак ми превключи без ерори в ethtool , и в ifconfig. А в messages бонда залупва между 2та интефейса.Кабелът е нов.Интересното е че и на другата централа в messages намирам подобни съобщения.2 те централи са с по 2 лан карти включени в 1 cisco.Прилагам лога от сиското + спаннинг трее конф.на порта.

06:12 PBX1 crmd[2417]:   notice: do_state_transition: State transition S_TRANSITION_ENGINE -> S_IDLE [ input=I_TE_SUCCESS cause=C_FSA_INTERNAL origin=notify_crmd ]
Jun 15 14:06:12 PBX1 kernel: bonding: bond0: link status definitely down for interface eth0, disabling it
Jun 15 14:06:12 PBX1 kernel: bonding: bond0: making interface eth1 the new active one.
Jun 15 14:06:12 PBX1 kernel: bonding: bond0: link status definitely up for interface eth0.
Jun 15 14:06:12 PBX1 kernel: bonding: bond0: making interface eth0 the new active one.
Jun 15 14:06:12 PBX1 kernel: bonding: bond0: link status definitely down for interface eth0, disabling it
Jun 15 14:06:12 PBX1 kernel: bonding: bond0: making interface eth1 the new active one.
Jun 15 14:06:12 PBX1 kernel: bonding: bond0: link status definitely up for interface eth0.
Jun 15 14:06:12 PBX1 kernel: bonding: bond0: making interface eth0 the new active one.
Jun 15 14:06:12 PBX1 kernel: bonding: bond0: link status definitely down for interface eth0, disabling it
Jun 15 14:06:12 PBX1 kernel: bonding: bond0: making interface eth1 the new active one.
Jun 15 14:06:13 PBX1 kernel: bonding: bond0: link status definitely up for interface eth0.
Jun 15 14:06:13 PBX1 kernel: bonding: bond0: making interface eth0 the new active one.
Jun 15 14:06:13 PBX1 kernel: bonding: bond0: link status definitely down for interface eth0, disabling it
Jun 15 14:06:13 PBX1 kernel: bonding: bond0: making interface eth1 the new active one.
Jun 15 14:06:13 PBX1 kernel: bonding: bond0: link status definitely up for interface eth0.
Jun 15 14:06:13 PBX1 kernel: bonding: bond0: making interface eth0 the new active one.
Jun 15 14:06:13 PBX1 kernel: bonding: bond0: link status definitely down for interface eth0, disabling it
Jun 15 14:06:13 PBX1 kernel: bonding: bond0: making interface eth1 the new active one.
Jun 15 14:06:13 PBX1 kernel: bonding: bond0: link status definitely up for interface eth0.
Jun 15 14:06:13 PBX1 kernel: bonding: bond0: making interface eth0 the new active one.
Jun 15 14:06:14 PBX1 kernel: bonding: bond0: link status definitely down for interface eth0, disabling it
Jun 15 14:06:14 PBX1 kernel: bonding: bond0: making interface eth1 the new active one.
Jun 15 14:06:14 PBX1 kernel: bonding: bond0: link status definitely up for interface eth0.
Jun 15 14:06:14 PBX1 kernel: bonding: bond0: making interface eth0 the new active one.
Jun 15 14:06:14 PBX1 kernel: bonding: bond0: link status definitely down for interface eth0, disabling it
Jun 15 14:06:14 PBX1 kernel: bonding: bond0: making interface eth1 the new active one.
Jun 15 14:06:14 PBX1 kernel: bonding: bond0: link status definitely up for interface eth0.
Jun 15 14:06:14 PBX1 kernel: bonding: bond0: making interface eth0 the new active one.
Jun 15 14:06:14 PBX1 kernel: bonding: bond0: link status definitely down for interface eth0, disabling it
Jun 15 14:06:14 PBX1 kernel: bonding: bond0: making interface eth1 the new active one.
Jun 15 14:06:15 PBX1 kernel: bonding: bond0: link status definitely up for interface eth0.
Jun 15 14:06:15 PBX1 kernel: bonding: bond0: making interface eth0 the new active one.
Jun 15 14:06:15 PBX1 kernel: bonding: bond0: link status definitely down for interface eth0, disabling it
Jun 15 14:06:15 PBX1 kernel: bonding: bond0: making interface eth1 the new active one.
Jun 15 14:06:15 PBX1 kernel: bonding: bond0: link status definitely up for interface eth0.
Jun 15 14:06:15 PBX1 kernel: bonding: bond0: making interface eth0 the new active one.
Jun 15 14:06:15 PBX1 kernel: bonding: bond0: link status definitely down for interface eth0, disabling it
Jun 15 14:06:15 PBX1 kernel: bonding: bond0: making interface eth1 the new active one.
Jun 15 14:06:15 PBX1 kernel: bonding: bond0: link status definitely up for interface eth0.
Jun 15 14:06:15 PBX1 kernel: bonding: bond0: making interface eth0 the new active one.
Jun 15 14:06:16 PBX1 kernel: bonding: bond0: link status definitely down for interface eth0, disabling it
Jun 15 14:06:16 PBX1 kernel: bonding: bond0: making interface eth1 the new active one.
Jun 15 14:06:16 PBX1 kernel: bonding: bond0: link status definitely up for interface eth0.
Jun 15 14:06:16 PBX1 kernel: bonding: bond0: making interface eth0 the new active one.
Jun 15 14:06:16 PBX1 kernel: bonding: bond0: link status definitely down for interface eth0, disabling it
Jun 15 14:06:16 PBX1 kernel: bonding: bond0: making interface eth1 the new active one.
Jun 15 14:06:16 PBX1 kernel: bonding: bond0: link status definitely up for interface eth0.
Jun 15 14:06:16 PBX1 kernel: bonding: bond0: making interface eth0 the new active one.
Jun 15 14:06:16 PBX1 kernel: bonding: bond0: link status definitely down for interface eth0, disabling it
Jun 15 14:06:16 PBX1 kernel: bonding: bond0: making interface eth1 the new active one.
Jun 15 14:06:17 PBX1 kernel: bonding: bond0: link status definitely up for interface eth0.
Jun 15 14:06:17 PBX1 kernel: bonding: bond0: making interface eth0 the new active one.
Jun 15 14:06:17 PBX1 kernel: bonding: bond0: link status definitely down for interface eth0, disabling it
Jun 15 14:06:17 PBX1 kernel: bonding: bond0: making interface eth1 the new active one.
Jun 15 14:06:17 PBX1 kernel: bonding: bond0: link status definitely up for interface eth0.
Jun 15 14:06:17 PBX1 kernel: bonding: bond0: making interface eth0 the new active one.
Jun 15 14:06:17 PBX1 kernel: bonding: bond0: link status definitely down for interface eth0, disabling it
Jun 15 14:06:17 PBX1 kernel: bonding: bond0: making interface eth1 the new active one.
Jun 15 14:06:17 PBX1 kernel: bonding: bond0: link status definitely up for interface eth0.
Jun 15 14:06:17 PBX1 kernel: bonding: bond0: making interface eth0 the new active one.
Jun 15 14:06:18 PBX1 kernel: bonding: bond0: link status definitely down for interface eth0, disabling it
Jun 15 14:06:18 PBX1 kernel: bonding: bond0: making interface eth1 the new active one.
Jun 15 14:06:18 PBX1 kernel: bonding: bond0: link status definitely up for interface eth0.
Jun 15 14:06:18 PBX1 kernel: bonding: bond0: making interface eth0 the new active one.
Jun 15 14:06:18 PBX1 kernel: bonding: bond0: link status definitely down for interface eth0, disabling it
Jun 15 14:06:18 PBX1 kernel: bonding: bond0: making interface eth1 the new active one.
Jun 15 14:06:18 PBX1 kernel: bonding: bond0: link status definitely up for interface eth0.
Jun 15 14:06:18 PBX1 kernel: bonding: bond0: making interface eth0 the new active one.
Jun 15 14:06:28 PBX1 attrd[2415]:   notice: attrd_trigger_update: Sending flush op to all hosts for: pingd (0)
Jun 15 14:06:28 PBX1 attrd[2415]:   notice: attrd_perform_update: Sent update 196: pingd=0
Jun 15 14:06:28 PBX1 crmd[2417]:   notice: do_state_transition: State transition S_IDLE -> S_PO

----------------------------------------------------------------------------------------------------------------------
Jun 15 14:53:25 PBX2 dhcpd: DHCPACK on 10.66.250.85 to 00:15:fa:b8:f0:40 (SEP001                                                                                                              5FAB8F040) via bond0.2
Jun 15 14:53:40 PBX2 asterisk(asterisk)[17316]: INFO: 12 active channels 6 activ                                                                                                              e calls 517 calls processed
Jun 15 14:53:42 PBX2 dhcpd: DHCPREQUEST for 10.66.250.91 from 00:19:e7:d1:60:dc                                                                                                               (SEP0019E7D160DC) via bond0.2
Jun 15 14:53:42 PBX2 dhcpd: DHCPACK on 10.66.250.91 to 00:19:e7:d1:60:dc (SEP001                                                                                                              9E7D160DC) via bond0.2
Jun 15 14:53:49 PBX2 dhcpd: DHCPREQUEST for 10.66.250.151 from 00:19:e8:5d:78:a9                                                                                                               (SEP0019E85D78A9) via bond0.2
Jun 15 14:53:49 PBX2 dhcpd: DHCPACK on 10.66.250.151 to 00:19:e8:5d:78:a9 (SEP00                                                                                                              19E85D78A9) via bond0.2
Jun 15 14:54:10 PBX2 asterisk(asterisk)[17699]: INFO: 12 active channels 6 activ                                                                                                              e calls 519 calls processed
Jun 15 14:54:36 PBX2 dhcpd: isc-dhcpd-4.1.1-P1
Jun 15 14:54:36 PBX2 Xinetd(Xinetd)[18072]: INFO: checking "disable" in /etc/xin                                                                                                              etd.d/tftp
Jun 15 14:54:40 PBX2 asterisk(asterisk)[18484]: INFO: 0 active channels 0 active                                                                                                               calls 519 calls processed
Jun 15 14:54:45 PBX2 kernel: bonding: bond0: link status definitely down for int                                                                                                              erface eth0, disabling it
Jun 15 14:54:45 PBX2 kernel: bonding: bond0: making interface eth1 the new activ                                                                                                              e one.
Jun 15 14:54:45 PBX2 kernel: bonding: bond0: link status definitely up for inter                                                                                                              face eth0.
Jun 15 14:54:45 PBX2 kernel: bonding: bond0: making interface eth0 the new activ                                                                                                              e one.
Jun 15 14:55:10 PBX2 asterisk(asterisk)[18820]: INFO: 2 active channels 1 active                                                                                                               call 520 calls processed
Jun 15 14:55:40 PBX2 asterisk(asterisk)[19565]: INFO: 0 active channels 0 active                                                                                                               calls 520 calls processed
Jun 15 14:56:10 PBX2 asterisk(asterisk)[19870]: INFO: 2 active channels 1 active                                                                                                               call 521 calls processed
Jun 15 14:56:36 PBX2 dhcpd: isc-dhcpd-4.1.1-P1
Jun 15 14:56:36 PBX2 Xinetd(Xinetd)[20296]: INFO: checking "disable" in /etc/xin                                                                                                              etd.d/tftp
Jun 15 14:56:40 PBX2 asterisk(asterisk)[20713]: INFO: 2 active channels 1 active                                                                                                               call 521 calls processed
Jun 15 14:56:42 PBX2 kernel: bonding: bond0: link status definitely down for int                                                                                                              erface eth0, disabling it
Jun 15 14:56:42 PBX2 kernel: bonding: bond0: making interface eth1 the new activ                                                                                                              e one.
Jun 15 14:56:42 PBX2 kernel: bonding: bond0: link status definitely up for inter                                                                                                              face eth0.
Jun 15 14:56:42 PBX2 kernel: bonding: bond0: making interface eth0 the new act

---------------------------------
сиско:
Jun 15 14:06:11.736: %SW_MATM-4-MACFLAP_NOTIF: Host 001d.0911.5436 in vlan 0000 is flapping between port Gi1/0/8 and port Gi2/0/8
Jun 15 14:06:11.736: %SW_MATM-4-MACFLAP_NOTIF: Host 001d.0911.5436 in vlan 2669 is flapping between port Gi1/0/8 and port Gi2/0/8
Jun 15 14:06:11.882: %SW_MATM-4-MACFLAP_NOTIF: Host 001d.0911.57e4 in vlan 4 is flapping between port Gi2/0/7 and port Gi1/0/7
Jun 15 14:06:11.883: %SW_MATM-4-MACFLAP_NOTIF: Host 001d.0911.57e4 in vlan 2603 is flapping between port Gi2/0/7 and port Gi1/0/7
Jun 15 14:06:11.883: %SW_MATM-4-MACFLAP_NOTIF: Host 001d.0911.57e4 in vlan 2669 is flapping between port Gi2/0/7 and port Gi1/0/7
Jun 15 14:06:11.884: %SW_MATM-4-MACFLAP_NOTIF: Host 001d.0911.57e4 in vlan 4 is flapping between port Gi2/0/7 and port Gi1/0/7
Jun 15 14:06:11.885: %SW_MATM-4-MACFLAP_NOTIF: Host 001d.0911.57e4 in vlan 60 is flapping between port Gi2/0/7 and port Gi1/0/7

-------------------
STP details
Port 7 (GigabitEthernet1/0/7) of VLAN0060 is designated forwarding
   Port path cost 4, Port priority 128, Port Identifier 128.7.
   Designated root has priority 32818, address 042a.e25a.1300
   Designated bridge has priority 32818, address 042a.e25a.1300
   Designated port id is 128.7, designated path cost 0
   Timers: message age 0, forward delay 0, hold 0
   Number of transitions to forwarding state: 1
   The port is in the portfast mode by portfast trunk configuration
   Link type is point-to-point by default
   BPDU: sent 2388, received 0

 Port 8 (GigabitEthernet1/0/8) of VLAN0060 is designated forwarding
   Port path cost 4, Port priority 128, Port Identifier 128.8.
   Designated root has priority 32818, address 042a.e25a.1300
   Designated bridge has priority 32818, address 042a.e25a.1300
   Designated port id is 128.8, designated path cost 0
   Timers: message age 0, forward delay 0, hold 0
   Number of transitions to forwarding state: 1
   The port is in the portfast mode by portfast trunk configuration
   Link type is point-to-point by default
   BPDU: sent 1990481, received 0

другите 2 порта са по същият начин съответно за другите 2 лан карти.

Здравей.В ethtool не виждам аномалии.Прилагам лог.Засега след смяната на кабела не е имало превключване.

 ethtool -S eth1
NIC statistics:
     rx_bytes: 737015294
     rx_error_bytes: 0
     tx_bytes: 2095135
     tx_error_bytes: 0
     rx_ucast_packets: 8880
     rx_mcast_packets: 33419
     rx_bcast_packets: 11028714
     tx_ucast_packets: 5659
     tx_mcast_packets: 5039
     tx_bcast_packets: 7406
     tx_mac_errors: 0
     tx_carrier_errors: 0
     rx_crc_errors: 0
     rx_align_errors: 0
     tx_single_collisions: 0
     tx_multi_collisions: 0
     tx_deferred: 0
     tx_excess_collisions: 0
     tx_late_collisions: 0
     tx_total_collisions: 0
     rx_fragments: 0
     rx_jabbers: 0
     rx_undersize_packets: 0
     rx_oversize_packets: 0
     rx_64_byte_packets: 10402253
     rx_65_to_127_byte_packets: 598963
     rx_128_to_255_byte_packets: 37123
     rx_256_to_511_byte_packets: 31432
     rx_512_to_1023_byte_packets: 99
     rx_1024_to_1522_byte_packets: 1143
     rx_1523_to_9022_byte_packets: 0
     tx_64_byte_packets: 8166
     tx_65_to_127_byte_packets: 5237
     tx_128_to_255_byte_packets: 4626
     tx_256_to_511_byte_packets: 16
     tx_512_to_1023_byte_packets: 19
     tx_1024_to_1522_byte_packets: 40
     tx_1523_to_9022_byte_packets: 0
     rx_xon_frames: 0
     rx_xoff_frames: 0
     tx_xon_frames: 0
     tx_xoff_frames: 0
     rx_mac_ctrl_frames: 0
     rx_filtered_packets: 4105941
     rx_ftq_discards: 0
     rx_discards: 0
     rx_fw_discards: 0

Здравейте , за първа идея смених кабела веднага.Картата ми мина през ума и е възможно да е от нея.Някаква идея за по-дълбок анализ да и направя на работоспособността тъй като нищо не ми идва на ум а проблемът го прави в месеца 2-3 пъти максимум?
В ifconfig errors са 0 на всички интерфейси.

Здравейте.Наследихме linux centos 6.5 cluster s PBX на базата corosync + pacemaker.Съставен е от 2 машини с 2 лан карти.Напоследък обаче без да е променяно нищо машините превключват от първата към втората.
Като лог има единствено (поне където се сещам да видя аз) как интерфейса пада и се дига.В суича в който са сложени няма грешки и проблеми ,както и Spannig tree е изкл.В ifconfig няма грешки също за лан картата.Отворен съм за всякакви идей които да ме насочат какво може да води до това.Благодаря ви.

Jun 14 09:00:54 PBX1 kernel: bonding: bond0: making interface eth0 the new active one.
Jun 14 09:06:38 PBX1 kernel: bonding: bond0: link status definitely down for interface eth0, disabling it
Jun 14 09:06:38 PBX1 kernel: bonding: bond0: making interface eth1 the new active one.
Jun 14 09:06:39 PBX1 kernel: bonding: bond0: link status definitely up for interface eth0.
Jun 14 09:06:39 PBX1 kernel: bonding: bond0: making interface eth0 the new active one.
Jun 14 09:09:16 PBX1 kernel: bonding: bond0: link status definitely down for interface eth0, disabling it
Jun 14 09:09:16 PBX1 kernel: bonding: bond0: making interface eth1 the new active one.
Jun 14 09:09:16 PBX1 kernel: bonding: bond0: link status definitely up for interface eth0.
Jun 14 09:09:16 PBX1 kernel: bonding: bond0: making interface eth0 the new active one.