Mac address binding not worked at NE80.
But by below test, mac address binding was not worked, as a result customer open a major ticket & blame us your product is not support for mac address binding.
Customer was tried by below step:
Configure below in Router_A
Interface vlanif 2010
ip add 18.104.22.168 30
[ROUTER_A] interface Ethernet 9/1/11
port default vlan 2010
Configure ip 22.214.171.124 mask: 255.255.255.252 gw: 126.96.36.199 in Laptop 1 NIC card. And Connect Laptop 1 to ether 9/1/11. ping 188.8.131.52. Check the “dis arp” output of Router_A. Disconnect Laptop 1.
If step 2 ping is successful configure the below in Router_A for binding mac address of Laptop1 (F04D:A2C1:2A67).
[ROUTER_A] mac-address static F04D:A2C1:2A67 Ethernet 9/1/11
Connect Laptop 1 to ether 9/1/11.
Ping 184.108.40.206. Ping should be successful. Check the “dis arp” output of Router_A
Connect Laptop 2 (other Laptop which MAC address is different) to ether 9/1/11. Connect laptop 1 to ether 9/1/11.
Ping 220.127.116.11. Ping should not be successful. Check the “dis arp” output of Router_A
Step 6: If Laptop1 can ping but Laptop2 can’t ping then, we can say that mac address binding is working properly.
So, we propose them by below correct command at step 3 & test that again.
[Router_A]# arp static 18.104.22.168 F04D:A2C1:2A67 vid 10 int Eth 9/1/11
By above command they were successful & after that trust us.
Since customer blames us that your product is not support, in that time, we are in challenge.
So, we had collect operation log of that test procedure from customer & checked carefully. After deep analysis, we found the reason why it was not worked. They try to bind mac address with interface (mac-address static F04D:A2C1:2A67 Ethernet 9/1/11). Actually that was wrong; they should bind this mac address with IP instead interface.
I have shared with my other colleges the correct procedure & command of mac address bindingprocedure.