Uncategorized

Layer3 connections on Aruba switches

On Cisco its quite convenient command “no switchport” , which  is used for layer3 connections between network devices. It disables spanning tree process on such interface:

#sh spanning-tree interface te1/4
no spanning tree info available for TenGigabitEthernet1/4

On Aruba though there are no such command and layer3 connection is done with help of VLANs (the same way as on Cisco behind the scenes).

On Aruba switch on layer3 link commands “spanning admin-edge-port” and “spanning-tree bpdu-filter”  should be used if on both ends are Aruba with layer3 interfaces.  However if on one end is Cisco (e.g. WAN router) and on other end is Aruba (e.g. L3 site switch), then such commands are not necessary as Cisco device on L3 interface will not have spanning tree process and not generate BPDUs.

Enabling RSTP (IEEE 802.1w) spanning tree on Aruba is done by following global commands:

spanning-tree force-version RSTP-operation

spanning-tree

 

 

 

 

network design, Uncategorized

Host is flapping between portX and portY

Mar 28 01:12:02 UTC: %SW_MATM-4-MACFLAP_NOTIF: Host 28d2.44ad.72be in vlan 60 is flapping between port Gi1/0/4 and port Po1
Mar 28 01:12:17 UTC: %SW_MATM-4-MACFLAP_NOTIF: Host 28d2.44ad.72be in vlan 60 is flapping between port Po1 and port Gi1/0/4
Mar 28 01:12:33 UTC: %SW_MATM-4-MACFLAP_NOTIF: Host 28d2.44ad.72be in vlan 60 is flapping between port Gi1/0/4 and port Po1
Mar 28 01:12:50 UTC: %SW_MATM-4-MACFLAP_NOTIF: Host 28d2.44ad.72be in vlan 60 is flapping between port Gi1/0/4 and port Po1
Mar 28 01:13:04 UTC: %SW_MATM-4-MACFLAP_NOTIF: Host 28d2.44ad.72be in vlan 60 is flapping between port Gi1/0/4 and port Po1

Such notifications in log file is an example of layer2 problem in the network: switch sees a certain MAC address on two different ports almost at the same time.