When you add a neighbor device, we test the SysContact field to see if the device responds to SNMP (188.8.131.52.184.108.40.206.0). Then we test the IPNetToMediaTable value to see if their is ARP information (220.127.116.11.18.104.22.168).
Then we pull the whole IPNetToMediaTable for the client information. If the F5 supports this table, then we will work with it.
Can you confirm if the devices replies to these?
Getting the ARP table on the Viprion works. The problem is that the F5 Viprion is a Chassis based device that has up to 4 blades/modules in it. When you log into the device, you are basically logging into the the "master" of the stack. But the ARP entries are distributed across all blades. So doing the SNMP Get on that one module only gets the ARP entries that exist on that module, and not all the modules in the chassis. Each blade does have a unique IP address though, so if I had the ability to add more that one IP in the Neighbor scanning field, that would solve the issue.
Ok that makes sense. I've logged this as a feature request under enhancements for Neighbor Discovery.
I assume you have different subnets spread across this device correct? If each blade was serving a different subnet, you could add the neighbor device. Obviously this is probably an edge case and most people will not be able to do this.
Sorry there isn't a better work around today on this.