wing 5.8.5 reports AP's as down but they are not

[Phil_storey]

Hi All
We had a power outage last week, some parts of the network stayed up on the UPS and others the UPS's failed after 20 mins. since then the RFS shows that some of the AP's are down, but they have clients connected, I can get onto the AP's being shown as down via the AP's ip address, I have reset the units, but the RFS ( wing 5.8.5 ) still shows as down ?
I have also restarted the RFS units as well.
now Im confused ( Oh no I'm always confused , thats normal )

[Phil_storey]

Hi, This is the output from one of the AP7131's, Its very strange that the AP7532's seem unaffected. if any ap's were set to controller capable would that affect anything ?

I will drop the output of the RFS later, as they too have now dropped off the network
it goes from bad to worse 

ap7131-7-PC01(config)#show mint mlcp history
2017-07-02 20:39:37:Adoption state change: 'Waiting to retry' to 'No adopters found'
2017-07-02 20:39:26:cfgd notified dpd2 of unadoption, restart adoption after 11 seconds
2017-07-02 20:39:26:Adoption state change: 'Adopted' to 'Waiting to retry'
2017-07-02 20:39:26:Adopter 70.38.0A.F9 is no longer reachable, cfgd notified
2017-07-02 20:39:26:All adopters lost, restarting MLCP
2017-07-02 20:39:26:MLCP link vlan-1 offerer 70.38.0A.F9 lost, restarting discovery
2017-07-02 19:52:15:Received OK from cfgd, adoption complete to 70.38.0A.F9
2017-07-02 19:52:15:Waiting for cfgd OK, adopter should be 70.38.0A.F9
2017-07-02 19:52:15:Adoption state change: 'Connecting to adopter' to 'Waiting for Adoption OK'
2017-07-02 19:52:13:Adoption state change: 'No adopters found' to 'Connecting to adopter'
2017-07-02 19:52:13:Try to adopt to 70.38.0A.F9 (cluster master 70.38.0A.F9 in adopters)
2017-07-02 19:51:14:Adoption state change: 'Waiting to retry' to 'No adopters found'
2017-07-02 19:51:05:cfgd notified dpd2 of unadoption, restart adoption after 9 seconds
2017-07-02 19:51:05:Adoption state change: 'Adopted' to 'Waiting to retry'
2017-07-02 19:51:05:Adopter 70.38.0A.F9 is no longer reachable, cfgd notified
2017-07-02 19:51:05:MLCP created VLAN link on VLAN 1, offer from 00-15-70-38-0A-F9
2017-07-02 19:51:05:MLCP VLAN link already exists
2017-07-02 19:51:05:Sending MLCP Request to 00-15-70-38-0A-F9 vlan 1
2017-07-02 19:51:05:All adopters lost, restarting MLCP
2017-07-02 19:42:42:Received OK from cfgd, adoption complete to 70.38.0A.F9
2017-07-02 19:42:42:Waiting for cfgd OK, adopter should be 70.38.0A.F9
2017-07-02 19:42:42:Adoption state change: 'Connecting to adopter' to 'Waiting for Adoption OK'
2017-07-02 19:42:42:Adoption state change: 'Adoption failed' to 'Connecting to adopter'
2017-07-02 19:42:42:Try to adopt to 70.38.0A.F9 (cluster master 00.00.00.00 in adopters)
2017-07-02 19:42:12:Adoption state change: 'Connecting to adopter' to 'Adoption failed': Connection error 145
2017-07-02 19:41:47:Adoption state change: 'Waiting to retry' to 'Connecting to adopter'
2017-07-02 19:41:47:Try to adopt to 70.38.0A.F9 (cluster master 70.38.0A.F9 in adopters)
2017-07-02 19:41:40:MLCP created VLAN link on VLAN 1, offer from 00-15-70-38-0A-F9
2017-07-02 19:41:40:MLCP VLAN link already exists
2017-07-02 19:41:40:Sending MLCP Request to 00-15-70-38-0A-F9 vlan 1
2017-07-02 19:41:40:All adopters lost, restarting MLCP
2017-07-02 19:41:38:MLCP created VLAN link on VLAN 1, offer from 00-15-70-38-0A-F9
2017-07-02 19:41:38:Sending MLCP Request to 00-15-70-38-0A-F9 vlan 1
2017-07-02 19:41:38:MLCP link vlan-1 offerer 70.38.0A.F9 lost, restarting discovery
2017-07-02 19:41:38:cfgd notified dpd2 of unadoption, restart adoption after 9 seconds
2017-07-02 19:41:38:Adoption state change: 'Adopted' to 'Waiting to retry'
2017-07-02 19:40:50:Received OK from cfgd, adoption complete to 70.38.0A.F9
2017-07-02 19:40:50:Waiting for cfgd OK, adopter should be 70.38.0A.F9
2017-07-02 19:40:50:Adoption state change: 'Connecting to adopter' to 'Waiting for Adoption OK'
2017-07-02 19:40:50:Adoption state change: 'Waiting to retry' to 'Connecting to adopter'
2017-07-02 19:40:50:Try to adopt to 70.38.0A.F9 (cluster master 70.38.0A.F9 in adopters)
2017-07-02 19:40:38:MLCP created VLAN link on VLAN 1, offer from 00-15-70-38-0A-F9
2017-07-02 19:40:38:MLCP VLAN link already exists
2017-07-02 19:40:38:Sending MLCP Request to 00-15-70-38-0A-F9 vlan 1
2017-07-02 19:40:38:All adopters lost, restarting MLCP
2017-07-02 19:40:38:MLCP created VLAN link on VLAN 1, offer from 00-15-70-38-0A-F9
2017-07-02 19:40:38:Sending MLCP Request to 00-15-70-38-0A-F9 vlan 1
2017-07-02 19:40:38:MLCP link vlan-1 offerer 70.38.0A.F9 lost, restarting discovery
2017-07-02 19:40:38:cfgd notified dpd2 of unadoption, restart adoption after 12 seconds
2017-07-02 19:40:38:Adoption state change: 'Adopted' to 'Waiting to retry'
2017-07-02 19:39:43:Received OK from cfgd, adoption complete to 70.38.0A.F9
2017-07-02 19:39:42:Waiting for cfgd OK, adopter should be 70.38.0A.F9
2017-07-02 19:39:42:Adoption state change: 'Connecting to adopter' to 'Waiting for Adoption OK'
2017-07-02 19:39:39:Adoption state change: 'No adopters found' to 'Connecting to adopter'
2017-07-02 19:39:39:Try to adopt to 70.38.0A.F9 (cluster master 70.38.0A.F9 in adopters)
2017-07-02 19:39:34:Adoption state change: 'Waiting to retry' to 'No adopters found'
2017-07-02 19:39:29:cfgd notified dpd2 of unadoption, restart adoption after 5 seconds
2017-07-02 19:39:29:Adoption state change: 'Adopted' to 'Waiting to retry'
2017-07-02 19:39:29:Adopter 70.38.0A.F9 is no longer reachable, cfgd notified
2017-07-02 19:39:29:MLCP created VLAN link on VLAN 1, offer from 00-15-70-38-0A-F9
2017-07-02 19:39:29:MLCP VLAN link already exists
2017-07-02 19:39:29:Sending MLCP Request to 00-15-70-38-0A-F9 vlan 1
2017-07-02 19:39:29:All adopters lost, restarting MLCP
2017-07-02 19:38:48:Received OK from cfgd, adoption complete to 70.38.0A.F9
2017-07-02 19:38:48:Waiting for cfgd OK, adopter should be 70.38.0A.F9
2017-07-02 19:38:48:Adoption state change: 'Connecting to adopter' to 'Waiting for Adoption OK'
2017-07-02 19:38:48:Adoption state change: 'Waiting to retry' to 'Connecting to adopter'
2017-07-02 19:38:48:Try to adopt to 70.38.0A.F9 (cluster master 70.38.0A.F9 in adopters)
2017-07-02 19:38:38:MLCP created VLAN link on VLAN 1, offer from 00-15-70-38-0A-F9
2017-07-02 19:38:38:Sending MLCP Request to 00-15-70-38-0A-F9 vlan 1
2017-07-02 19:38:38:MLCP link vlan-1 offerer 70.38.0A.F9 lost, restarting discovery
2017-07-02 19:38:38:cfgd notified dpd2 of unadoption, restart adoption after 10 seconds
2017-07-02 19:38:38:Adoption state change: 'Adopted' to 'Waiting to retry'
2017-07-02 19:38:23:Received OK from cfgd, adoption complete to 70.38.0A.F9
2017-07-02 19:38:23:Waiting for cfgd OK, adopter should be 70.38.0A.F9
2017-07-02 19:38:23:Adoption state change: 'Connecting to adopter' to 'Waiting for Adoption OK'
2017-07-02 19:38:23:Adoption state change: 'Adoption failed' to 'Connecting to adopter'
2017-07-02 19:38:23:Try to adopt to 70.38.0A.F9 (cluster master 00.00.00.00 in adopters)
2017-07-02 19:37:53:Adoption state change: 'Connecting to adopter' to 'Adoption failed': Connection error 145
2017-07-02 19:37:27:Adoption state change: 'Adoption failed' to 'Connecting to adopter'
2017-07-02 19:37:27:Try to adopt to 70.38.0A.F9 (cluster master 00.00.00.00 in adopters)
2017-07-02 19:37:24:Adoption state change: 'Waiting for Adoption OK' to 'Adoption failed': Cluster master is unknown
2017-07-02 19:37:24:Adoption state change: 'Connecting to adopter' to 'Waiting for Adoption OK'
2017-07-02 19:37:24:Adoption state change: 'Adoption failed' to 'Connecting to adopter'
2017-07-02 19:37:24:Try to adopt to 70.38.0A.F9 (cluster master 00.00.00.00 in adopters)
2017-07-02 19:37:21:Adoption state change: 'Waiting for Adoption OK' to 'Adoption failed': Cluster master is unknown
2017-07-02 19:37:21:Adoption state change: 'Connecting to adopter' to 'Waiting for Adoption OK'
2017-07-02 19:37:21:Adoption state change: 'Adoption failed' to 'Connecting to adopter'
2017-07-02 19:37:21:Try to adopt to 70.38.0A.F9 (cluster master 00.00.00.00 in adopters)
2017-07-02 19:37:18:Adoption state change: 'Waiting for Adoption OK' to 'Adoption failed': Cluster master is unknown
2017-07-02 19:37:18:Adoption state change: 'Connecting to adopter' to 'Waiting for Adoption OK'
2017-07-02 19:37:18:Adoption state change: 'Adoption failed' to 'Connecting to adopter'
2017-07-02 19:37:18:Try to adopt to 70.38.0A.F9 (cluster master 00.00.00.00 in adopters)
2017-07-02 19:37:15:Adoption state change: 'Waiting for Adoption OK' to 'Adoption failed': Cluster master is unknown
2017-07-02 19:37:15:Adoption state change: 'Connecting to adopter' to 'Waiting for Adoption OK'
2017-07-02 19:37:12:Adoption state change: 'No adopters found' to 'Connecting to adopter'
2017-07-02 19:37:12:Try to adopt to 70.38.0A.F9 (cluster master 70.38.0A.F9 in adopters)
2017-07-02 19:37:11:Adoption state change: 'Adoption failed' to 'No adopters found'
2017-07-02 19:37:00:MLCP created VLAN link on VLAN 1, offer from 00-15-70-38-0A-F9
2017-07-02 19:37:00:MLCP VLAN link already exists
2017-07-02 19:37:00:Sending MLCP Request to 00-15-70-38-0A-F9 vlan 1
2017-07-02 19:37:00:All adopters lost, restarting MLCP
2017-07-02 19:36:41:Adoption state change: 'Connecting to adopter' to 'Adoption failed': Connection error 145
2017-07-02 19:36:16:Adoption state change: 'Waiting to retry' to 'Connecting to adopter'
2017-07-02 19:36:16:Try to adopt to 70.38.0A.F9 (cluster master 70.38.0A.F9 in adopters)
2017-07-02 19:36:10:MLCP created VLAN link on VLAN 1, offer from 00-15-70-38-0A-F9
2017-07-02 19:36:10:Sending MLCP Request to 00-15-70-38-0A-F9 vlan 1
2017-07-02 19:36:10:MLCP link vlan-1 offerer 70.38.0A.F9 lost, restarting discovery
2017-07-02 19:36:10:cfgd notified dpd2 of unadoption, restart adoption after 6 seconds
2017-07-02 19:36:10:Adoption state change: 'Adopted' to 'Waiting to retry'
2017-07-02 19:34:11:Received OK from cfgd, adoption complete to 70.38.0A.F9
2017-07-02 19:34:10:Waiting for cfgd OK, adopter should be 70.38.0A.F9
2017-07-02 19:34:10:Adoption state change: 'Connecting to adopter' to 'Waiting for Adoption OK'
2017-07-02 19:34:10:Adoption state change: 'Adoption failed' to 'Connecting to adopter'
2017-07-02 19:34:10:Try to adopt to 70.38.0A.F9 (cluster master 00.00.00.00 in adopters)
2017-07-02 19:33:40:Adoption state change: 'Connecting to adopter' to 'Adoption failed': Connection error 145
2017-07-02 19:33:15:Adoption state change: 'Waiting to retry' to 'Connecting to adopter'
2017-07-02 19:33:15:Try to adopt to 70.38.0A.F9 (cluster master 70.38.0A.F9 in adopters)
2017-07-02 19:33:08:MLCP created VLAN link on VLAN 1, offer from 00-15-70-38-0A-F9
2017-07-02 19:33:08:Sending MLCP Request to 00-15-70-38-0A-F9 vlan 1
2017-07-02 19:33:08:MLCP link vlan-1 offerer 70.38.0A.F9 lost, restarting discovery
2017-07-02 19:33:08:cfgd notified dpd2 of unadoption, restart adoption after 7 seconds
2017-07-02 19:33:08:Adoption state change: 'Adopted' to 'Waiting to retry'
2017-07-02 19:29:51:Received OK from cfgd, adoption complete to 70.38.0A.F9
2017-07-02 19:29:51:Waiting for cfgd OK, adopter should be 70.38.0A.F9
2017-07-02 19:29:51:Adoption state change: 'Connecting to adopter' to 'Waiting for Adoption OK'
2017-07-02 19:29:51:Adoption state change: 'Adoption failed' to 'Connecting to adopter'
2017-07-02 19:29:51:Try to adopt to 70.38.0A.F9 (cluster master 00.00.00.00 in adopters)
ap7131-7-PC01(config)#

[Andrew_Webster]

Phil,

Are there any other RFS devices connected anywhere on the network besides the two RFS7000s ?

As you said, the 7131 seem to be dropping off the network, so you'd need to track down why this is happening.

I find that the show mint mlcp history command is the most useful for troubleshooting adoption issues, but it takes some time to figure out what all the messages indicate.

You can try the following from the CLI of the Primary RFS:

show mint mlcp history The command will give you an output of all the mint level handshake going on between devices.

Here's what it looks like on the RFS when an AP is adopted (time goes backwards):

2017-06-14 09:37:10:Adopted 5C-0E-8B-34-E3-28 (0B.34.E3.28), cfgd notified
2017-06-14 09:37:10:Sending MLCP Offer to 0B.34.E3.28 (link_level=1, preferred=0, capacity=144)
2017-06-14 09:37:10:Sending MLCP Offer to 0B.34.E3.28 (link_level=1, preferred=0, capacity=144)
2017-06-14 09:37:10:Sending MLCP Offer to 0B.34.E3.28 (link_level=1, preferred=0, capacity=144)
2017-06-14 09:37:10:Sending MLCP Reply to (00.00.00.00,34,1,227.40.0.0:23566/5C-0E-8B-34-E3-28)
2017-06-14 09:37:10:Sending MLCP Offer to 0B.34.E3.28 (link_level=1, preferred=0, capacity=144)

To get the view from the 7131, you will also need to issue the same command on one of the 7131s that is not adopting. You should be able to SSH to it.

And this is what it looks like from the AP's perspective:

2017-06-14 09:37:10:Received OK from cfgd, adoption complete to 0B.1B.2A.E2
2017-06-14 09:37:10:Waiting for cfgd OK, adopter should be 0B.1B.2A.E2
2017-06-14 09:37:10:Adoption state change: 'Connecting to adopter' to 'Waiting for Adoption OK'
2017-06-14 09:37:10:Adoption state change: 'No adopters found' to 'Connecting to adopter'
2017-06-14 09:37:10:Try to adopt to 0B.1B.2A.E2 (cluster master 0B.1B.2A.E2 in adopters)

[Kendal_Ingraham]

On this note... at one time another provider installed a controller that started adopting our APs because we had a part of their network accessible. That's a good angle to search on.

[Phil_storey]

looking on the RFS events The AP's seem to be avaiable and then drop off

[Phil_storey]

Hi Andrew
the cluster is their
rfs7000-Backup* 70.38.0A.F9 00-15-70-38-0A-F9 False standby 00:01:30 ago
rfs7000-Primary 70.81.BE.8E 00-15-70-81-BE-8E True active self

But I might have a bigger problem, I set the syslog running and this is is what is comming in

Jun 30 16:02:46 172.17.146.105 2017-06-30T16:02:46.139223+01:00 rfs7000-Primary %DATAPLANE-4-DOSATTACK: IPSPOOF ATTACK: Source IP is Spoofed : Src IP : 10.0.0.138, Dst IP: 224.0.0.22, Src Mac: 58-98-35-9D-7A-44, Dst Mac: 01-00-5E-00-00-16, Proto = 2.
Jun 30 16:02:52 172.17.146.105 2017-06-30T16:02:52.698984+01:00 rfs7000-Primary %DEVICE-4-OFFLINE: Device 00-15-70-EB-7D-00(ap7131-2) is offline, last seen:10 minutes ago on switchport -
Jun 30 16:02:52 172.17.146.105 2017-06-30T16:02:52.704019+01:00 rfs7000-Primary %DEVICE-4-OFFLINE: Device 00-24-38-F3-72-00(ap7131-5) is offline, last seen:10 minutes ago on switchport -
Jun 30 16:02:52 172.17.146.105 2017-06-30T16:02:52.710750+01:00 rfs7000-Primary %DEVICE-4-OFFLINE: Device 00-15-70-EB-96-CC(ap7131-4-PC02) is offline, last seen:10 minutes ago on switchport -
Jun 30 16:03:02 172.17.146.105 2017-06-30T16:03:02.784410+01:00 rfs7000-Primary %DATAPLANE-4-ARPPOISON: ARP CACHE POISONING: Conflicting ethernet header and inner arp header :Ethernet Src Mac: 00-11-25-8E-2E-5E, Ethernet Dst Mac: FF-FF-FF-FF-FF-FF, ARP Src Mac: 00-03-FF-09-64-DE, ARP Dst Mac: 00-00-00-00-00-00, ARP Src IP: 172.17.152.4, ARP Target IP: 172.17.144.81 .
Jun 30 16:03:05 172.17.146.105 2017-06-30T16:03:05.921494+01:00 rfs7000-Primary %DATAPLANE-4-ARPPOISON: ARP CACHE POISONING: Conflicting ethernet header and inner arp header :Ethernet Src Mac: 00-11-25-8E-2E-5E, Ethernet Dst Mac: FF-FF-FF-FF-FF-FF, ARP Src Mac: 00-03-FF-9A-2E-5E, ARP Dst Mac: 00-00-00-00-00-00, ARP Src IP: 172.17.148.19, ARP Target IP: 172.17.144.71 .
Jun 30 16:03:07 172.17.146.105 2017-06-30T16:03:07.760199+01:00 rfs7000-Primary %DATAPLANE-4-ARPPOISON: ARP CACHE POISONING: Conflicting ethernet header and inner arp header :Ethernet Src Mac: 00-14-5E-A4-7D-04, Ethernet Dst Mac: FF-FF-FF-FF-FF-FF, ARP Src Mac: 00-03-FF-9D-4A-76, ARP Dst Mac: 00-00-00-00-00-00, ARP Src IP: 172.17.151.26, ARP Target IP: 172.17.144.71 .
Jun 30 16:03:24 172.17.146.105 2017-06-30T16:03:24.183555+01:00 rfs7000-Primary %DATAPLANE-4-ARPPOISON: ARP CACHE POISONING: Conflicting ethernet header and inner arp header :Ethernet Src Mac: 00-11-25-8E-2E-5E, Ethernet Dst Mac: FF-FF-FF-FF-FF-FF, ARP Src Mac: 00-03-FF-09-64-DE, ARP Dst Mac: 00-00-00-00-00-00, ARP Src IP: 172.17.152.4, ARP Target IP: 172.17.144.59 .
Jun 30 16:03:26 172.17.146.105 2017-06-30T16:03:26.885160+01:00 rfs7000-Primary %DATAPLANE-4-ARPPOISON: ARP CACHE POISONING: Conflicting ethernet header and inner arp header :Ethernet Src Mac: 00-11-25-8E-2E-5E, Ethernet Dst Mac: FF-FF-FF-FF-FF-FF, ARP Src Mac: Jun 30 16:02:46 172.17.146.105 2017-06-30T16:02:46.139223+01:00 rfs7000-Primary %DATAPLANE-4-DOSATTACK: IPSPOOF ATTACK: Source IP is Spoofed : Src IP : 10.0.0.138, Dst IP: 224.0.0.22, Src Mac: 58-98-35-9D-7A-44, Dst Mac: 01-00-5E-00-00-16, Proto = 2.
Jun 30 16:02:52 172.17.146.105 2017-06-30T16:02:52.698984+01:00 rfs7000-Primary %DEVICE-4-OFFLINE: Device 00-15-70-EB-7D-00(ap7131-2) is offline, last seen:10 minutes ago on switchport -
Jun 30 16:02:52 172.17.146.105 2017-06-30T16:02:52.704019+01:00 rfs7000-Primary %DEVICE-4-OFFLINE: Device 00-24-38-F3-72-00(ap7131-5) is offline, last seen:10 minutes ago on switchport -
Jun 30 16:02:52 172.17.146.105 2017-06-30T16:02:52.710750+01:00 rfs7000-Primary %DEVICE-4-OFFLINE: Device 00-15-70-EB-96-CC(ap7131-4-PC02) is offline, last seen:10 minutes ago on switchport -
Jun 30 16:03:02 172.17.146.105 2017-06-30T16:03:02.784410+01:00 rfs7000-Primary %DATAPLANE-4-ARPPOISON: ARP CACHE POISONING: Conflicting ethernet header and inner arp header :Ethernet Src Mac: 00-11-25-8E-2E-5E, Ethernet Dst Mac: FF-FF-FF-FF-FF-FF, ARP Src Mac: 00-03-FF-09-64-DE, ARP Dst Mac: 00-00-00-00-00-00, ARP Src IP: 172.17.152.4, ARP Target IP: 172.17.144.81 .
Jun 30 16:03:05 172.17.146.105 2017-06-30T16:03:05.921494+01:00 rfs7000-Primary %DATAPLANE-4-ARPPOISON: ARP CACHE POISONING: Conflicting ethernet header and inner arp header :Ethernet Src Mac: 00-11-25-8E-2E-5E, Ethernet Dst Mac: FF-FF-FF-FF-FF-FF, ARP Src Mac: 00-03-FF-9A-2E-5E, ARP Dst Mac: 00-00-00-00-00-00, ARP Src IP: 172.17.148.19, ARP Target IP: 172.17.144.71 .
Jun 30 16:03:07 172.17.146.105 2017-06-30T16:03:07.760199+01:00 rfs7000-Primary %DATAPLANE-4-ARPPOISON: ARP CACHE POISONING: Conflicting ethernet header and inner arp header :Ethernet Src Mac: 00-14-5E-A4-7D-04, Ethernet Dst Mac: FF-FF-FF-FF-FF-FF, ARP Src Mac: 00-03-FF-9D-4A-76, ARP Dst Mac: 00-00-00-00-00-00, ARP Src IP: 172.17.151.26, ARP Target IP: 172.17.144.71 .
Jun 30 16:03:24 172.17.146.105 2017-06-30T16:03:24.183555+01:00 rfs7000-Primary %DATAPLANE-4-ARPPOISON: ARP CACHE POISONING: Conflicting ethernet header and inner arp header :Ethernet Src Mac: 00-11-25-8E-2E-5E, Ethernet Dst Mac: FF-FF-FF-FF-FF-FF, ARP Src Mac: 00-03-FF-09-64-DE, ARP Dst Mac: 00-00-00-00-00-00, ARP Src IP: 172.17.152.4, ARP Target IP: 172.17.144.59 .
Jun 30 16:03:26 172.17.146.105 2017-06-30T16:03:26.885160+01:00 rfs7000-Primary %DATAPLANE-4-ARPPOISON: ARP CACHE POISONING: Conflicting ethernet header and inner arp header :Ethernet Src Mac: 00-11-25-8E-2E-5E, Ethernet Dst Mac: FF-FF-FF-FF-FF-FF, ARP Src Mac: 00-03-FF-9A-2E-5E, ARP Dst Mac: 00-00-00-00-00-00, ARP Src IP: 172.17.148.19, ARP Target IP: 172.17.144.71 .
Jun 30 16:03:28 172.17.146.105 2017-06-30T16:03:28.723856+01:00 rfs7000-Primary %DATAPLANE-4-ARPPOISON: ARP CACHE POISONING: Conflicting ethernet header and inner arp header :Ethernet Src Mac: 00-14-5E-A4-7D-04, Ethernet Dst Mac: FF-FF-FF-FF-FF-FF, ARP Src Mac: 00-03-FF-9D-4A-76, ARP Dst Mac: 00-00-00-00-00-00, ARP Src IP: 172.17.151.26, ARP Target IP: 172.17.144.71 .
, ARP Dst Mac: 00-00-00-00-00-00, ARP Src IP: 172.17.148.19, ARP Target IP: 172.17.144.71 .
Jun 30 16:03:28 172.17.146.105 2017-06-30T16:03:28.723856+01:00 rfs7000-Primary %DATAPLANE-4-ARPPOISON: ARP CACHE POISONING: Conflicting ethernet header and inner arp header :Ethernet Src Mac: 00-14-5E-A4-7D-04, Ethernet Dst Mac: FF-FF-FF-FF-FF-FF, ARP Src Mac: 00-03-FF-9D-4A-76, ARP Dst Mac: 00-00-00-00-00-00, ARP Src IP: 172.17.151.26, ARP Target IP: 172.17.144.71 .

I have enabled Arp trust on ge1

no stateful-packet-inspection-l2

no sure if this is correct,

This is where I'm clueless or should it be more clueless than usual 😞