FAQs about VMware Live Cyber Recovery Auto-Support on change of IP and FQDN

Products

• VMware Live Recovery

Issue/Introduction

Symptoms:

With changes in VMware Live Cyber Recovery Auto-Support IPs and FQDNs, following message is received by users as forwarded by backend support:

Dear VMware Live Cyber Recovery (VLCR) Customer,
This communication is to notify you of a required update to the VMware Live Cyber Recovery auto-support system, which is part of the ongoing transition from VMware to Broadcom.

For On-Premises Protected Sites:
If your site utilizes a network firewall that restricts outgoing access on port 443 to specific IP addresses, you must update your firewall rules to allow connectivity for your VLCR connectors.
•    Recommendation: Allow access based on the new DNS name (listed below), if your firewall supports this functionality.
•    Alternative: If DNS-based rules are not supported, you must update your rules with the new IP address.

New Connectivity Information:

1. IP Address Update

•    Old Value: #.#.#.#/32
•    New Value: #.#.#.#/32

2. FQDN Update

•    Old Value: old-FQDN.com
•    New Value: new-FQDN.com

Environment

VMware Live Cyber Recovery

Resolution

1. Are these new IP and FQDN ready for testing? Telnet to both fail as of now.

   Ans : This new IP may not be reachable yet. It is for the new system that will flipped over to in coming days. This is just an ask to have the rules for network settings in place proactively to avoid any errors once this new system is used.
   
   

2. Is there a need to allow outbound port 443 to new IP and FQDN on physical firewall?

   Ans : Yes, physical firewalls in the network VLCR connectors are deployed in should allow port 443 access to this new IP and FQDN.
   
   

3. Is there any need to setup firewall rule on on‑premises VLCR connectors? Is there a configuration change required to redirect them to the new auto‑support system?

   Ans : No change is needed on VLCR connectors.
   
   

4. In the VLCR management GUI — is there any setting that needs to be updated?

   Ans : No change is needed from VLCR management GUI.
   
   

5. What would be the impact if this change is not made?

   Ans : In an instance of not performing this change, the VLCR connectors fails to forward logs (call home) to the auto-support server and thus during an incident of triaging manual collection is needed. There may be a warning in VLCR UI stating auto-support not reachable.
   
   

6. Would VM snapshot creation, replication or restore operations impacted on not making this change?
   
   Ans : No. It would not impact any of these operations if the recommended change is not made.

Additional Information

VMware Live Cyber Recovery の Auto-Support で使用する IPアドレス および FQDN 変更に関する FAQ