Create Content

Description

This article describes how to set Re-IP Address Rules for a Target Server in a DRS Server Pair.

Prerequisites:

  1. User must be Primary Administrator or have the DRS role.
  2. Target Server must be in an MCP 2.0 Data Center location.
  3. VM Tools must be running on the Source Server.
  4. Consistency Group and Server Pair ID must be in a Normal state.
  5. The following fields and conditions are required for ALL servers:
    1. Server Pair ID
    2. DNS Server Addresses - at least one entry in a valid IPv4 or IPv6 address format is required.
      1. NOTES:
        1. On Windows OS, this input applies to all NICs.
        2. The system will not validate whether or not the IP Address is a valid DNS server or whether the Target Server can connect to the address given the firewall rules and network configuration. This means that you may end up with DNS problems if inputs are invalid.
    3. NIC ID - This input must be defined for every NIC on the Target Server.
  6. The following inputs are required if the Source Server OS is in the LINUX family (optional for WINDOWS family):
    1. Hostname
      1. Must be between 1 and 63 characters long.
      2. Can only contain  0-9, a-z, A-Z, and '-' characters.
    2. Domain
      1. Supports RFC 1123, which permits 0-9, a-z, A-Z, and '-' characters
  7. DNS suffix - If provided, entries must be valid DNS names per RFC 1123.
  8. If "Re-IP Network IPv4 NIC Address" input is provided:
    1. If the Re-IP Network IPv4 NIC Address is within the IPv4 range of the VLAN associated with Target Server NIC:
      1. Input for Re-IP Network Prefix Size cannot be provided.
      2. The input for Re-IP Network IPv4 NIC Address cannot be a restricted IPv4 in the Target Server NIC VLAN range:
        1. The Network Address (x.x.x.0) at the start of the VLAN associated with Target Server NIC.
        2. The Broadcast Address (x.x.x.255) at the end of the VLAN associated with Target Server NIC.
        3. A system reserved address in the VLAN associated with Target Server NIC.
        4. An exclusively reserved address in the VLAN associated with Target Server NIC.
      3. If the optional Re-IP Network IPv4 Gateway Address is provided, it must:
        1. Reside within the IPv4 range of the VLAN associated with Target Server NIC.
        2. Cannot be any of the restricted IPv4 addresses in the Target Server NIC VLAN range:
          1. The Re-IP Network IPv4 NIC Address.
          2. The Network Address (x.x.x.0) at the start of the VLAN associated with Target Server NIC.
          3. The Broadcast Address (x.x.x.255) at the end of the VLAN associated with Target Server NIC.
          4. A system reserved address in the VLAN associated with Target Server NIC with the exception of the gateway IP address of the VLAN associated with Target Server NIC.
            1. NOTE: The gateway can vary depending on whether the NIC is associated with a Low Addressed Attached VLAN, High Addressed Attached VLAN or a Detached VLAN. 
    2. If the Re-IP Network IPv4 NIC Address is NOT within the IPv4 range of the VLAN associated with Target Server NIC:
      1. The input for the Re-IP Network Prefix Size is required.
      2. If the optional Re-IP Network IPv4 Gateway Address is provided, it must:
        1. Be different than Re-IP Network IPv4 NIC Address.
        2. Re-IP Network IPv4 Gateway Address and Re-IP Network IPv4 NIC Address must both reside within the range defined by the Re-IP Network Prefix Size.
        3. Broadcast (x.x.x.255) and Network addresses (x.x.x.0) are allowed.
  9. Inputs must meet one of the following conditions so that the system can specify a gateway address for at least one NIC in the Target Server:
    1. Provide no Re-IP Network IPv4 NIC Address input on the Primary NIC.
      1. If no Re-IP Network IPv4 NIC Address is provided on the Primary NIC, the system will use the value currently stored in CloudControl for the Primary NIC.
    2. Provide the Re-IP Network IPv4 NIC Address input for the Primary NIC which is within the Primary NIC VLAN range.
    3. Provide the optional Re-IP Network IPv4 Gateway Address input on at least one NIC on the Target Server.

Content / Solution: 

Re-IP Address Function Overwrites All Settings Replicated from Source Server

The Re-IP address function will overwrite all Guest OS settings replicated from the Source Server as part of DRS Preview as described in How to Start a DRS Preview for a Consistency Group. Make sure to review both your Source Server settings and your Target Server environment to ensure the settings you're providing will work when implemented. 

  1. Click on the DRS for Cloud menu button and then select DRS Consistency Groups to navigate to the DRS Consistency Groups page:


  2. The DRS Consistency Groups dashboard will be displayed. Expand the Consistency Group by clicking on the  drop-down icon:


  3. Locate the Server pair for which you would like to enable Re-IP Address Rules. Click on the Actions menu and select NIC Configuration from the drop-down menu:

    • Note: Hovering your mouse over the  icon will display the DRS Consistency Group Server Pair Id and the State of the Server Pair

  4. The NIC Configuration will be displayed:

    • Note: This dialog displays information relating to the Server Pair, including:
      • Source Server
        • ID
        • Name
        • NIC Key
          • Note: The  icon indicates the Primary NIC
        • IPv4
        • IPv6
      • Target Server
        • ID
        • Name
        • IPv4
        • VLAN
        • Gateway
        • IPv4 Range

  5. Click the Enable Re-IP button in the top right-hand corner of the dialog. The dialog will expand. Enter the desired information in each field:

    • Host Name: The hostname to be applied to the Target Server

      • This value is required on Linux OS

    • Domain: Domain to be applied to the Target Server
      • This value is required on Linux OS
    • DNS Servers: Series of IPv4 or IPv6 addresses to be applied to the Target Server. 
      • This value is required for all Servers
    • DNS Suffix Search Order: Determines the DNS suffixes to attach to an unqualified single-label name before submission of a DNS query for that name
    • NetBIOS: Identifies whether NetBIOS is Enabled or Disabled on a NIC
    • Re-IP Mode: Indicates how the feature will determine the range of configurations available for a NIC. The options are:
      • Use Cloud Control: In this mode, values are fixed and copied from the current Target Server settings.
      • Explicit In Range: In this mode, only Re-IPv4 and Re-IPv4 Gateway values can be changed. The Prefix cannot be changed.
      • Explicit Out Of Range: In this mode, all three values - Re-IPv4, Prefix and Re-IPv4 Gateway can be changed.
    • Re-IPv4: The IPv4 Address that will be applied to the Target NIC
    • Prefix: IPv4 Prefix Address that will be applied to the Target NIC
    • Re-IPv4 Gateway: IPv4 Gateway Address that will be applied to the Target NIC

  6. Review the information you have entered in the fields and then click Save:


  7. The system will display a message indicating that the operation is in progress:


  8. Once the Re-IP Rule(s) have been applied, the display will indicate it with the Re-IP icon 


Once the Re-IP Address Rule(s) have been set, the settings passed will be applied to the Target Server when the Preview mode is initiated for the Consistency Group as described in How to Start a DRS Preview for a Consistency Group



Recently Updated