07-28-2024 07:45 PM - edited 07-28-2024 07:46 PM
I am preparing to build a LISP environment based on the commands listed on this site.
I am researching the details of two commands,
https://www.cisco.com/c/ja_jp/td/docs/routers/C8000V/Azure/deploying-cisco-catalyst-8000v-on-microsoft-azure/configure-l2- extension-for-public-cloud.html
https://cloudnetsec.blogspot.com/2019/01/azure-and-lisp-for-workload-migration.html?m=1
This command
1.lisp mobility subnet1 nbr-proxy-reply requests 3
→nbr-proxy-reply requests 3” Adjacent devices are not responding to arp requests.
An event has occurred.
Details are available at this site.
https://community.cisco.com/t5/routing/unable-to-ping-terminal-after-migration/m-p/5151775#M401878
2.map-notify-group 239.0.0.1
I looked up information about LISP from cisco navigate,
No Rows to show” and no useful information was found.
I have been trying to find out more information about LISP from https://cfnng.cisco.com/
Please provide more information on this command.
Solved! Go to Solution.
07-28-2024 11:15 PM
Hello @hina316
First command, lisp mobility subnet1 nbr-proxy-reply requests 3 ; it is specifically used to handle issues with neighboring devices not responding to ARP requests. The nbr-proxy-reply requests 3 portion instructs the device to send up to three proxy ARP replies to assist with the resolution of MAC addresses for these non-responsive neighbors. This can help maintain connectivity and ensure devices on the subnet can communicate effectively.
For a practical scenario, consider when migrating devices in a cloud environment like Azure, where traditional ARP responses might be disrupted. Using this command ensures continued communication even when direct ARP responses fail, improving network stability during migration processes.
As concerned map-notify-group 239.0.0.1 command, it configures a multicast group for sending map-notify messages. The IP address 239.0.0.1 is a multicast address used within the LISP architecture to notify devices in the group about mapping changes. This is essential for maintaining updated location information of devices in a LISP-enabled network, particularly in dynamic environments such as cloud deployments.
In the context of workload migration and cloud extensions, using a multicast group ensures that all relevant devices receive timely updates about network changes, reducing downtime and improving the efficiency of migrations and other network operations.