You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
Overview
As part of
Unable to show "metadata-from": No such page "_space_variables"
switch-over process, the
Unable to show "metadata-from": No such page "_space_variables"
must move the IP (floating IP) to a different NIC. The
Unable to show "metadata-from": No such page "_space_variables"
reconfigures the NICs appropriately and then broadcasts a GARP reply to inform neighboring devices about the change in the MAC address for the floating IP. Devices that receive the ARP packet then update their ARP tables with the new MAC address.
There is a minor different between
Unable to show "metadata-from": No such page "_space_variables"
'
Unable to show "metadata-from": No such page "_space_variables"
and hardware-based
Unable to show "metadata-from": No such page "_space_variables"
s. For the case of hardware-based SBCs during a switchover, both the IP and MAC addresses of the active node's non-management interfaces are migrated to the standby. For SBC SWe during a switchover, only the IP address is migrated from active to standby (the newly active node will use its own MAC addresses).
In both cases, the L2 tables of attached switches are updated; however in the case of SBC SWe, the routers' ARP tables must be updated as well.
Configuring Routers in SBC SWe Network
If a router in an
Unable to show "metadata-from": No such page "_space_variables"
network is not configured properly to handle Gratuitous Address Resolution Protocol (GARP) replies, calls will fail after an
Unable to show "metadata-from": No such page "_space_variables"
switch-over.
For example, the received Gratuitous ARP reply on a Juniper SRX device does not update the ARP cache by default. You must configure the router to enable ARP table update for switch-over to work properly.
A knowledge base article on how to enable the updating of the ARP cache for received gratuitous ARP replies is located here: