FWM refers to the NX-OS Forwarding Manager. The somewhat undocumented feature is known as (for the lack of a better name) FWM-Loop Detection. If you are using Cisco Nexus switches in your data center, you would be happy to know that NX-OS offers an interesting new tool you should add to your loop detection list. It seems a little too coincidental to not be related to the ISP mac address, but on the same hand, I can't find any reference.We all too familiar with the devastating impact a talented layer 2 loop could have on a data center lacking sufficient controls and processes. I have also trawled the configuration and there is no static reference and I have looked at all interfaces on the appliances and none have even a similar address.Ĭan anyone point me to some commands that might help, or, even offer up what may be going on here. I see nothing remotely close to the above mac addresses in the output on either of the appliances. I have gone onto both Checkpoints, and in every VS issued the following command: On the Cisco switches, I am also seeing the following mac address coming from the Checkpoint appliances and it seems to flap between each one but is never seen via both at the same time.

On the Cisco switches I am seeing the following mac address coming from our ISP on both switches: There is a single VPC towards one of the Checkpoint appliances and another VPC towards the other.

I have 2 devices in a VSX cluster and they are LACP connected to 2 CIsco 9K's running VPC. I'm after a bit of help regarding mac addresses on an appliance running R80.20.

Dynamic mac address learning