This is the actual IP address of the remote FCIP entity that this specific static route pertains to. Because this route is statically configured, as opposed to dynamically discovered via SLPv2, this address must be manually kept in sync with any change to the remote entity's actual IP addressing, or the static route will silently point at a stale, unreachable address. If a remote data center's FCIP entity is renumbered to a new IP address during a network migration, every static route entry on this side referencing the old address would need to be manually updated, unlike a dynamically-discovered route that would simply pick up the change.