Skip to end of metadata
Go to start of metadata

Description

This article describes how to manage a Node on a Cloud Network Domain in a MCP 2.0 Data Center location, including:

A Node is a dedicated server that provides a network interface for a Virtual Listener (or Virtual Listeners). It is the lowest level building block required for VIP functionality at an MCP 2.0 Data Center and is the endpoint for traffic (i.e. the entity offering the service). Nodes are added to Pools as Pool Members.

Prerequisites:

  1. Only the Primary Administrator or a User with the Network role can manage 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. Recommended reading:

Content / Solution:

  1. From the Home page, select the MCP 2.0 Data Center where the Network Domain on which you want to manage a Node is located:


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


  3. The Network Domain dashboard will be displayed:

Edit Node

  1. Click on the Load Balancing / Virtual IPs tab, then click on the Manage gear for the Node you want to manage and select Edit Node from the dropdown menu:


  2. The Edit Node dialog will be displayed:

    Note: The Name, IP Version, and Destination IP Address cannot be edited. 

  3. Fill out the Edit Node form with the requested information:

    • 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.

  4. Once the Edit Node form has been filled out, click the Save button:


  5. The system will display a success message:


  6. The changes will be applied to the Node and the UI will be updated to reflect the changes:

Delete Node

  1. Click on the Load Balancing / Virtual IPs tab, then click on the Manage gear for the Node you want to delete and select Delete Node from the dropdown menu:

     

  2. The Delete Node confirmation dialog will be displayed. Click Delete:


  3. The system will display a success message:

     

  4. The Node will be deleted and the UI will be updated to reflect the change: 
     

Recently Updated