How to Create a Node on a Cloud Network Domain

Prerequisites:

1. Only the Primary Administrator or a User with the Network role can create Nodes
2. Data Center location must be MCP 2.0
3. Network Domain must be 'Advanced'. This feature is not supported on 'Essentials' Network Domains.
4. You cannot create a Node on the Network Domain SNAT Address.

Content / Solution:

1. From the Home page, click on the Data Center where the Network Domain on which you want to create a Node is located:
   
   
   

2. The Data Center dashboard will be displayed. Select the Network Domain on which you want to create a Node:
   
   
   

3. The Network Domain dashboard will be displayed. Click on the Load Balancing / Virtual IPs tab:
   
   
   

4. Click on the Actions button and select Add Nodes from he dropdown menu:
   
    

5. The Create Node dialog will be displayed:
   

   Note you can create multiple similar Nodes at the same time by clicking on the Add Node button on the form.
   
   

6. Fill out the Create Nodes form with the desired information:

   • IP Version - Both IPv4 and IPv6 are supported.
   • Node Name - Enter a descriptive Name for the Node. This name should be unique across the Network Domain.
     • Must begin with a letter 
     • May not include spaces 
     • Permitted special characters are "_" and "."
   • Node Destination IP Address
     • The IP Address does not have to be associated with a Cloud Server. It can be any IP as long as it is able to 'answer'.
       
     • The IP address cannot be in use by another Node on the same Network Domain.
     • For an IPv4 Node; the IP Address must be a valid IPv4 address in doc-decimal notation and can be RFC 1918 or non-RFC 1918 subject to the restrictions below:
       • The IP Address must not:
         • already be in use by a Virtual Listener on the same Network Domain.

         • already be in use by the externalIp of an existing NAT on the same Network Domain.

         • belong to a Public IPv4 Address Block already deployed on the same Network Domain.

         • belong to the Outside Transit VLAN Subnet of the same Network Domain or to any System-Restricted IP range both of which are described in Introduction to IP Addressing in MCP 2.0.

       • If the IP Address specified falls within the IP range of an existing VLAN on the Network Domain, there are additional criteria to ensure that routing functions correctly:

         • The IP address cannot be the Network Address (x.x.x.0) at the start of the IP range or the Broadcast Address (x.x.x.255) at the end of the IP range.

         • If the VLAN has Low gateway addressing, x.x.x.1-x.x.x.5 at the bottom of the VLAN range are system reserved and cannot be used.

         • If the VLAN has High gateway addressing, x.x.x.252 - x.x.x.254 at the bottom of the VLAN range are system reserved and cannot be used.

         • See Introduction to IP Addressing in MCP 2.0
     • For an IPv6 Node; the IP Address must be a valid IPv6 address in compressed or extended format subject to the restrictions below:
       • Site-local unicast addresses are not permitted.
       • Link-local unicast addresses are not permitted.
       • The first quad cannot be all zeros.
   • Description - The optional Description is limited to a maximum length of 255 characters.
   • Connection Limit - The maximum number of simultaneous connections permitted on the Node. Should be an integer between 1 and 100,000. The system default is set to 100,000.
   • Connection Rate Limit - The amount of new connections permitted every second. Should be an integer between 1 and 4,000. The system default is set to 4000.
   • Node Status - Describes what action the Node will take.
     
     • "Enabled" - Permits traffic.
     • "Disabled" - A Node continues to process persistent and active connections. It can accept new connections only if the connections belong to an existing persistence session.
     • "Forced Offline" - A Node allows existing connections to time out, but no new connections are allowed.
   • Node Health Monitor -  The procedure that the load balancer uses to verify that the Node is considered “healthy” and available for load balancing. 
     • "CCDEFAULT.Icmp" - Sends an ICMP ECHO request to the Node and considers the Node healthy if an ICMP ECHO reply is received. 
     • Note: A Health Monitor is not required. You can select 'None' from the drop down menu.
       
       

7. Once the form is complete, click the Create Node button:
    
   
   

8. The system will display a success message:
   
    

9. The system will create the Node and the UI will be updated to reflect the change:
    

   Note: The new Node will appear in the Unassigned Nodes folder until it is assigned to a Pool.