mac flapping что это
Флапают маки в сети
Добрый день!
Возникла в сети проблема, прыгают маки по портам, вот логи:
006551: May 6 08:22:54: %SW_MATM-4-MACFLAP_NOTIF: Host 0023.33ad.7146 in vlan 500 is flapping between port Gi1/0/4 and port Gi1/0/12
006552: May 6 08:22:57: %SW_MATM-4-MACFLAP_NOTIF: Host 0023.33ad.7146 in vlan 500 is flapping between port Gi1/0/4 and port Gi1/0/12
006553: May 6 08:25:45: %SW_MATM-4-MACFLAP_NOTIF: Host 0023.33ad.7146 in vlan 500 is flapping between port Gi1/0/4 and port Gi1/0/12
006554: May 6 08:26:34: %SW_MATM-4-MACFLAP_NOTIF: Host 0023.33ad.7146 in vlan 500 is flapping between port Gi1/0/4 and port Gi1/0/12
mac адрес от cisco, int vlan 500 ядро слева.
Нейронные сети. Ошибка при обработке изоброжения для транировки сети
Здравствуйте, Работа над нейросетью в срде матлаб. На моменте с работой базой данных изображений.
Можно ли с помощью TcpListener производить операции в сети Интернет, а не в локальной сети
Добрый день, извиняюсь за идиотский вопрос, но можно ли с помощью TcpListener производить операции.
Расчет маски сети, деление на подсети, постройка сети.Теория
Помогите разобраться в теории деления сетей на подсети на основе данной задачи. требуется: 1).
spanning-tree mode rapid-pvst
spanning-tree extend system-id
spanning-tree vlan 1,5,200,400 priority 24576
spanning-tree vlan 10-11,100,300,500 priority 28672
!
vlan internal allocation policy ascending
!
vlan 5,10,200,300,400,500
!
!
interface GigabitEthernet1/0/1
switchport trunk encapsulation dot1q
switchport mode trunk
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
queue-set 2
mls qos trust cos
auto qos voip trust
spanning-tree portfast trunk
interface Vlan1
ip address 172.16.*.* 255.255.254.0
ip helper-address 172.16.*.*
standby authentication md5 key-chain
standby 1 ip 172.16.*.*
spanning-tree mode rapid-pvst
spanning-tree extend system-id
!
vlan internal allocation policy ascending
!
vlan 10,100,200,300,400,500
!
interface GigabitEthernet1/0/1
switchport access vlan 500
switchport mode access
switchport voice vlan 400
spanning-tree portfast
————————————-
interface GigabitEthernet1/0/51
switchport trunk encapsulation dot1q
switchport mode trunk
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
queue-set 2
mls qos trust cos
auto qos voip trust
spanning-tree portfast trunk
!
interface GigabitEthernet1/0/52
switchport trunk encapsulation dot1q
switchport mode trunk
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
queue-set 2
mls qos trust cos
auto qos voip trust
spanning-tree portfast trunk
Сегодня проблема повторилась. На уровне распределение сначала пошли логи:
1715: 001713: Jun 5 12:56:58: %SW_MATM-CLUSTER_MEMBER_5-4-MACFLAP_NOTIF: Host 0023.33ad.7146 in vlan 500 is flapping between port Gi1/0/47 and port Gi1/0/51
Порт gi1/0/47 смотрит в сторону access свитча
gi1/0/51 в сторону ядра.
На уровне ядра вот логи:
12176: 012174: Jun 5 12:56:58: %SW_MATM-4-MACFLAP_NOTIF: Host 0023.33ad.7146 in vlan 500 is flapping between port Gi1/0/4 and port Gi1/0/12
Порт gi1/0/4 в сторону уровня распределения
Порт gi1/0/12 соединяется с вторым ядром. Поднят HSRP
Проблема возникает с разной периодичностью, то раз в неделю, то раз в 2 недели.
В чем может быть проблема
Добавлено через 11 минут
вот полный конфиг ядра 1
Ядро 2 аналогично, только priority различны
Конфиг уровня распределения.
spanning-tree mode rapid-pvst
spanning-tree extend system-id
!
vlan internal allocation policy ascending
!
vlan 10,100,200,300,400,500
!
interface GigabitEthernet1/0/1
!
interface GigabitEthernet1/0/25
!
interface GigabitEthernet1/0/26
!
interface GigabitEthernet1/0/27
!
interface GigabitEthernet1/0/28
!
interface GigabitEthernet1/0/29
!
interface GigabitEthernet1/0/30
!
interface GigabitEthernet1/0/31
!
interface GigabitEthernet1/0/32
!
interface GigabitEthernet1/0/33
!
interface GigabitEthernet1/0/34
!
interface GigabitEthernet1/0/35
!
interface GigabitEthernet1/0/36
!
interface GigabitEthernet1/0/37
!
interface GigabitEthernet1/0/38
!
interface GigabitEthernet1/0/39
!
interface GigabitEthernet1/0/40
!
interface GigabitEthernet1/0/41
!
interface GigabitEthernet1/0/42
!
interface GigabitEthernet1/0/43
!
interface GigabitEthernet1/0/44
!
interface GigabitEthernet1/0/45
!
interface GigabitEthernet1/0/46
switchport trunk encapsulation dot1q
switchport mode trunk
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
queue-set 2
mls qos trust cos
auto qos voip trust
spanning-tree portfast trunk
!
interface GigabitEthernet1/0/47
switchport trunk encapsulation dot1q
switchport mode trunk
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
queue-set 2
mls qos trust cos
auto qos voip trust
spanning-tree portfast trunk
!
interface GigabitEthernet1/0/48
switchport trunk encapsulation dot1q
switchport mode trunk
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
queue-set 2
mls qos trust cos
auto qos voip trust
spanning-tree portfast trunk
!
interface GigabitEthernet1/0/49
switchport trunk encapsulation dot1q
switchport mode trunk
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
queue-set 2
mls qos trust cos
auto qos voip trust
spanning-tree portfast trunk
!
interface GigabitEthernet1/0/50
switchport trunk encapsulation dot1q
switchport mode trunk
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
queue-set 2
mls qos trust cos
auto qos voip trust
spanning-tree portfast trunk
!
interface GigabitEthernet1/0/51
switchport trunk encapsulation dot1q
switchport mode trunk
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
queue-set 2
mls qos trust cos
auto qos voip trust
spanning-tree portfast trunk
!
interface GigabitEthernet1/0/52
switchport trunk encapsulation dot1q
switchport mode trunk
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
queue-set 2
mls qos trust cos
auto qos voip trust
spanning-tree portfast trunk
!
interface Vlan1
ip address 172.16.*.* 255.255.255.0
Mac flapping что это
Доброе время суток, каждый день в одно и то же время с одним и тем же MAC адресом появляется ошибка почти на всех коммутаторах. sh mac ad данный мас не показывает, подскажите куда копать?
Nov 7 08:09:51 192.21.0.4 101: Nov 7 04:09:50.287: %SW_MATM-4-MACFLAP_NOTIF: Host 00e0.4c68.0056 in vlan 1 is flapping between port Gi1/0/16 and port Gi1/0/24
Nov 7 08:09:51 192.21.0.4 102: Nov 7 04:09:50.885: %SW_MATM-4-MACFLAP_NOTIF: Host 00e0.4c68.0056 in vlan 1 is flapping between port Gi1/0/16 and port Gi1/0/24
Nov 7 08:09:51 192.21.0.3 112: 000108: Nov 7 04:06:24.746: %SW_MATM-4-MACFLAP_NOTIF: Host 00e0.4c68.0056 in vlan 1 is flapping between port Gi0/26 and port Gi0/19
Nov 7 08:09:51 10.21.0.121 83: 000079: Nov 7 04:06:24.747: %SW_MATM-4-MACFLAP_NOTIF: Host 00e0.4c68.0056 in vlan 1 is flapping between port Gi0/26 and port Gi0/25
Nov 7 08:09:51 192.21.0.6 85: 000081: Nov 7 04:09:50.289: %SW_MATM-4-MACFLAP_NOTIF: Host 00e0.4c68.0056 in vlan 1 is flapping between port Gi0/23 and port Gi0/28
Nov 7 08:09:51 192.21.0.63 54: 000051: Nov 7 04:09:50.300: %SW_MATM-4-MACFLAP_NOTIF: Host 00e0.4c68.0056 in vlan 1 is flapping between port Gi1/0/24 and port Gi1/0/17
Nov 7 08:09:54 10.21.0.121 84: 000080: Nov 7 04:06:27.667: %SW_MATM-4-MACFLAP_NOTIF: Host 00e0.4c68.0056 in vlan 1 is flapping between port Gi0/25 and port Gi0/26
Nov 7 08:09:57 192.21.0.6 86: 000082: Nov 7 04:09:56.195: %SW_MATM-4-MACFLAP_NOTIF: Host 00e0.4c68.0056 in vlan 1 is flapping between port Gi0/28 and port Gi0/23
Nov 7 08:18:50 192.21.0.42 85: Nov 7 04:18:49.965: %SW_MATM-4-MACFLAP_NOTIF: Host 00e0.4c68.0056 in vlan 1 is flapping between port Fa0/3 and port Fa0/7
Nov 7 08:28:11 192.21.0.11 86: Nov 7 04:28:10.415: %SW_MATM-4-MACFLAP_NOTIF: Host 00e0.4c68.0056 in vlan 1 is flapping between port Fa0/10 and port Gi0/1
Nov 7 08:28:11 192.21.0.6 87: 000083: Nov 7 04:28:10.414: %SW_MATM-4-MACFLAP_NOTIF: Host 00e0.4c68.0056 in vlan 1 is flapping between port Gi0/28 and port Gi0/20
Nov 7 08:28:11 10.21.0.121 85: 000081: Nov 7 04:24:44.881: %SW_MATM-4-MACFLAP_NOTIF: Host 00e0.4c68.0056 in vlan 1 is flapping between port Gi0/24 and port Gi0/26
Nov 7 08:28:11 192.21.0.31 86: Nov 7 04:28:10.460: %SW_MATM-4-MACFLAP_NOTIF: Host 00e0.4c68.0056 in vlan 1 is flapping between port Fa0/2 and port Gi0/1
Nov 7 08:28:13 192.21.0.31 87: Nov 7 04:28:12.020: %SW_MATM-4-MACFLAP_NOTIF: Host 00e0.4c68.0056 in vlan 1 is flapping between port Gi0/1 and port Fa0/2
Nov 7 08:28:14 192.21.0.3 113: 000109: Nov 7 04:24:48.301: %SW_MATM-4-MACFLAP_NOTIF: Host 00e0.4c68.0056 in vlan 1 is flapping between port Gi0/20 and port Gi0/26
Nov 7 08:28:14 192.21.0.61 103: Nov 7 04:28:13.871: %SW_MATM-4-MACFLAP_NOTIF: Host 00e0.4c68.0056 in vlan 1 is flapping between port Fa0/4 and port Gi0/1
Nov 7 08:28:15 192.21.0.11 87: Nov 7 04:28:14.064: %SW_MATM-4-MACFLAP_NOTIF: Host 00e0.4c68.0056 in vlan 1 is flapping between port Gi0/1 and port Fa0/10
Nov 7 08:28:16 10.21.0.121 86: 000082: Nov 7 04:24:49.486: %SW_MATM-4-MACFLAP_NOTIF: Host 00e0.4c68.0056 in vlan 1 is flapping between port Gi0/24 and port Gi0/25
Nov 7 08:28:18 192.21.0.61 104: Nov 7 04:28:17.646: %SW_MATM-4-MACFLAP_NOTIF: Host 00e0.4c68.0056 in vlan 1 is flapping between port Fa0/4 and port Gi0/1
Nov 7 08:28:20 192.21.0.6 88: 000084: Nov 7 04:28:19.038: %SW_MATM-4-MACFLAP_NOTIF: Host 00e0.4c68.0056 in vlan 1 is flapping between port Gi0/20 and port Gi0/28
Nov 7 08:28:59 192.21.0.61 105: Nov 7 04:28:58.902: %SW_MATM-4-MACFLAP_NOTIF: Host 00e0.4c68.0056 in vlan 1 is flapping between port Gi0/1 and port Fa0/4
Nov 7 08:28:59 192.21.0.3 114: 000110: Nov 7 04:25:33.373: %SW_MATM-4-MACFLAP_NOTIF: Host 00e0.4c68.0056 in vlan 1 is flapping between port Gi0/24 and port Gi0/20
Nov 7 08:28:59 192.21.0.51 85: Nov 7 04:28:58.931: %SW_MATM-4-MACFLAP_NOTIF: Host 00e0.4c68.0056 in vlan 1 is flapping between port Fa0/11 and port Gi0/1
Nov 7 08:29:03 192.21.0.61 106: Nov 7 04:29:02.937: %SW_MATM-4-MACFLAP_NOTIF: Host 00e0.4c68.0056 in vlan 1 is flapping between port Gi0/1 and port Fa0/4
Nov 7 08:35:25 192.21.0.5 82: 000094: Nov 7 04:35:24.423: %SW_MATM-4-MACFLAP_NOTIF: Host 00e0.4c68.0056 in vlan 1 is flapping between port Gi1/0/21 and port Gi1/0/24
Nov 7 08:35:25 192.21.0.51 86: Nov 7 04:35:24.427: %SW_MATM-4-MACFLAP_NOTIF: Host 00e0.4c68.0056 in vlan 1 is flapping between port Gi0/1 and port Fa0/11
Nov 7 08:35:25 192.21.0.3 115: 000111: Nov 7 04:31:58.908: %SW_MATM-4-MACFLAP_NOTIF: Host 00e0.4c68.0056 in vlan 1 is flapping between port Gi0/23 and port Gi0/24
Nov 7 08:35:27 192.21.0.51 87: Nov 7 04:35:26.533: %SW_MATM-4-MACFLAP_NOTIF: Host 00e0.4c68.0056 in vlan 1 is flapping between port Fa0/11 and port Gi0/1
Nov 7 08:35:31 192.21.0.5 83: 000095: Nov 7 04:35:30.138: %SW_MATM-4-MACFLAP_NOTIF: Host 00e0.4c68.0056 in vlan 1 is flapping between port Gi1/0/24 and port Gi1/0/21
Nov 7 08:38:49 192.21.0.51 92: Nov 7 04:38:48.886: %SW_MATM-4-MACFLAP_NOTIF: Host 00e0.4c68.0056 in vlan 1 is flapping between port Gi0/1 and port Fa0/11
Nov 7 08:38:49 192.21.0.52 89: Nov 7 04:38:48.898: %SW_MATM-4-MACFLAP_NOTIF: Host 00e0.4c68.0056 in vlan 1 is flapping between port Fa0/17 and port Gi0/1
Nov 7 08:38:49 192.21.0.3 116: 000112: Nov 7 04:35:23.366: %SW_MATM-4-MACFLAP_NOTIF: Host 00e0.4c68.0056 in vlan 1 is flapping between port Gi0/22 and port Gi0/24
| 1. «Сыпится ошибка flapping на коммутаторах.» | + / – |  |
| Сообщение от rusadmin (ok) on 07-Ноя-13, 11:21 | ||
| Ответить | Правка | ^ к родителю #0 | Наверх | Cообщить модератору | ||
 | ||
| 2. «Сыпится ошибка flapping на коммутаторах.» | + / – | |
| Сообщение от rusadmin (ok) on 07-Ноя-13, 11:22 | ||
| ||
| Ответить | Правка | ^ к родителю #1 | Наверх | Cообщить модератору | ||
| ||
| 3. «Сыпится ошибка flapping на коммутаторах.» | + / – |  |
Сообщение от Denis_56  (ok) on 14-Ноя-13, 09:02 | ||
PortFast включен, утром этот mac гуляет по всей сети | ||
| Ответить | Правка | ^ к родителю #2 | Наверх | Cообщить модератору | ||
| ||
| 4. «Сыпится ошибка flapping на коммутаторах.» | + / – |  |
| Сообщение от klincman (ok) on 15-Ноя-13, 03:25 | ||
Похоже на топологию с избыточными связями 🙂 Проанализируйте топологию своей сети на предмет наличия физических колец, хабов. | ||
| Ответить | Правка | ^ к родителю #3 | Наверх | Cообщить модератору | ||
| ||
| 5. «Сыпится ошибка flapping на коммутаторах.» | + / – | |
| Сообщение от Denis_56 (ok) on 15-Ноя-13, 14:29 | ||
все таки склоняюсь к вирусу (или какой-то утилите), которая при загрузке компьютера подставляет этот МАС, так как данный адрес всплывает на одних и тех же портах свичей | ||
| Ответить | Правка | ^ к родителю #4 | Наверх | Cообщить модератору | ||
| 6. «Сыпится ошибка flapping на коммутаторах.» | + / – | |
| Сообщение от Denis_56 (ok) on 19-Ноя-13, 10:14 | ||
MAC Address FlappingWhat Is MAC Address FlappingMAC address flapping does not occur frequently on a network unless a network loop occurs. If MAC address flapping frequently occurs on your network, you can quickly locate the fault and eliminate the loops according to alarms and MAC address flapping records. How to Detect MAC Address FlappingMAC address flapping detection determines whether MAC address flapping occurs by checking whether outbound interfaces in MAC address entries change frequently. After MAC address flapping detection is enabled, the device can report an alarm when MAC address flapping occurs. The alarm contains the flapping MAC address, VLAN ID, and outbound interfaces between which the MAC address flaps. A loop may exist between the outbound interfaces. The network administrator can locate the cause of the loop based on the alarm. Alternatively, the device can perform the action specified in the configuration of MAC address flapping detection to remove the loop automatically. The action can be quit-vlan (remove the interface from the VLAN) or error-down (shut down the interface). As shown in Figure 3-5, a network cable is incorrectly connected between SwitchC to SwitchD, causing a loop between SwitchB, SwitchC, and SwitchD. When Port1 of SwitchA receives a broadcast packet, SwitchA forwards the packet to SwitchB. The packet is then sent to Port2 of SwitchA. After MAC address flapping detection is configured on SwitchA, SwitchA can detect that the source MAC address of the packet flaps from Port1 to Port2. If the MAC address flaps between Port1 and Port2 frequently, SwitchA reports an alarm about MAC address flapping to alert the network administrator. MAC address flapping detection allows a device to detect changes in traffic transmission paths based on learned MAC addresses, but the device cannot obtain the entire network topology. It is recommended that this function be used on the interface connected to a user network where loops may occur. How to Prevent MAC Address FlappingMAC address flapping occurs on a network when the network has a loop or undergoes an attack. Network Development TeamMAC Flaps – why are they bad?What is a MAC Flap?A MAC Flap is caused when a switch receives packets from two different interfaces with the same source MAC address. If this makes no sense, perhaps a quick summary of how switching at layer 2 works will help. Switches learn where hosts are by examining the source MAC address in frames received on a port, and populating its MAC address-table with an entry for that MAC address and port. Say a device ‘A’ with MAC aaaa.aaaa.aaaa (hereafter aaaa) sends a frame to device ‘B’ with MAC address bbbb. Assume A is on port 0/1 and B is on port 0/2. The switch populates it MAC address-table something like: and floods the frame out of all other ports. When B replies the MAC address table becomes: and the switch forwards the frame to port 0/1 – there is no need to flood now since the location of A is known. If the switch were to then receive a frame on port 0/2 with a source MAC address of aaaa, there would be clash and the switch would log something like this: and the MAC address-table would become: What happens when B tries to send A a frame now? The switch won’t flood the frame as it knows a destination and it won’t send the frame back down the link – it gets dropped. Lab time…Let’s see if we can mimic this. This isn’t an easy thing to replicate so please forgive the artificial nature of the lab. I configured a switch with three hosts directly connected on VLAN 30. The hosts could ping each other and the MAC address-table was as follows: Host A had an IP of 192.168.30.1 and was on port 1. Host B was 192.168.30.30 and on port 2. Host C was 192.168.30.254 and on port 3. So, ping with host A: Next I manually set host A to have the same MAC address as host B (001a.2f22.d0c2). The results? Host B lost connectivity for a few seconds. Here is the switch mac address table after the clone: Here is what happened to Host B: Yes, this is the same impact you would have if two hosts had the same MAC on your network – there is a reason they need to be unique! What does all this mean?When you have an annexe VLAN [1] the backbone can be thought of as a series of Layer 2 switches for that VLAN. The ‘Broadcast Domain’ stretches over the entire Backbone. This means the CPU of every host (including our core switches) on a VLAN will receive every broadcast from every other host – this is not ideal but the only way we can offer the same subnet at multiple sites in this generation of the backbone. Another term sometimes used is ‘Failure Domain’. That is, a failure in part of the VLAN could impact the entire core. It is because of this risk to other units that we are keen to make sure annexe VLANs are tightly managed. [1] These are known as Layer 2 end-to-end VLANs as there is no routing involved. We have called them ‘switched’ VLANs in the past. VLANs with a Layer 3 interface or SVI on the backbone are known as Layer 3 Routed VLANs. To return to the the issues MAC flaps will cause on your network, each switch in the backbone has a MAC address-table for your VLAN. If for some reason your MAC addresses appear from different locations you will get dropped packets and our logs will fill up with messages which cause issues when we raise a support case with Cisco as our network appears to have loops. What could cause it?There are two or three common causes that we see. 1. Local LoopsIf you don’t run STP then you are far more likely to suffer from network loops. Here are a couple of resources: STP is your friend and Implementing Spanning Tree. The issue with an annexe VLAN is that a local loop is no longer so local and could cause problems everywhere, both for you and others. 2. NACThere is a legitimate but ill-advised network design which can cause issues. If you have a L2 NAC which forces all traffic through itself then it is possible that a frame will need to leave site A, get switched through to site B only to return to site A, all with the same MAC address. See the image below. I’ve represented the Backbone as one red switch and the ingress and egress ports as tunnel entrances and exits. This design mustn’t be used with the current generation of the backbone.
3. WirelessWe used to run OWL and eduroam (Phase 1) over two VLANs which spanned the entire core. Due to the issues I’ve mentioned we changed this last year. Now the VLANs are local to the FroDos and routed through the core. Prior to doing this it was possible to roam from access points connected to different FroDos and cause MAC flaps. What should I do next?We’re going to keep an eye on the logs and will let Units know if they are causing MAC flaps. We’ll work with you as far as possible to locate the source of the issue and get things stable. If you aren’t yet running STP please can I urge you do consider doing so. The new backbone is still some years off so for the good of everyone we need to work together to reduce this. For units which cannot resolve this we may need to look at reverting to a fully routed connection, with each Annexe having its own subnet. Do get in touch if you have any questions. 6 Responses to “MAC Flaps – why are they bad?”@Miguel switchport trunk allowed vlan 1,11,12 And show us “show interfaces trunk ” command effect before and after change MAC address is flapping between the pair of switch. SWITCH01#sh mac address-table address 00AA.02aa.1234 SWITCH02#sh mac address-table address 00AA.02aa.1234 I have a Cisco C3560 switch (core switch), which want to make a cisco switch EtherChannel SGE2010 another small business. When I switch the connection between, for a moment lifted the interface port-channel10, but over a time message is displayed:% SW_MATM-4-MACFLAP_NOTIF: Host xxxx.xxxx.xxxx in vlan1 is flapping beween port PO10 and port Gix/x La configuración del C3560 es: The switch supports only SGE2010 LACP protocol, which is configured in a single step, which is why I set it up the core switch so active. How I can solve my problem? Is there a configuration error on my core switch? Please help
| ||
