Skip to end of metadata
Go to start of metadata

Description

Describes an MCP 2.0 Node, which is the component within an MCP 2.0 VIP that provides access to a service usually for Load Balancing.

Content / Solution:

A Node is a dedicated server, which 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.

If you are not yet familiar with VIPs at MCP 2.0 data centers please refer to: Introduction to Virtual Listeners / VIPs in MCP 2.0

Nodes can be created and managed as part of Advanced and Enterprise Network Domains.

However, a Node is created implicitly each time that a NAT Rule is created, irrespective of whether or not the Network Domain is an Essentials Advanced, or Enterprise type Network Domain.

If the Network Domain hosting the Node is of the Advanced or Enterprise type it is possible to change the settings for the Node beneath a NAT. In this scenario, the Network Domain cannot be changed back to an Essentials type Network Domain until the Node has been returned to the default settings listed below. See How to View and Manage a Network Domain in a MCP 2.0 Data Center

  • A Node can be addressed using either IPv4 or IPv6. 
  • A Node must be enabled in order to receive traffic. 
  • A Node can map to the NIC IP address of a deployed Cloud Server or to a server hosted in infrastructure beyond the VLANs on the Network Domain by routing via an IPv4 or IPv6 address on a CPNC connection. For more information about CPNC see Introduction to Cloud Private Network Connection (CPNC).
  • However, the Node is entirely separate from Server NIC and changes to a Server (such as a change to the NIC IP address, removal of the NIC, or deletion of the Server itself) will not affect the Node.
  • A Node can be used in Pool Member(s) of multiple Pools. As such it can process traffic for multiple Virtual Listeners.
  • A Node can be used for a NAT Rule and as a Pool Member simultaneously. Note that this influences the behavior of NAT Rule deletion. See: How to Delete NAT Rules from a Network or Network Domain.

For detailed information on Node creation and management see:

Node Default and Minimum/Maximum Settings

The following settings classify a Node as "default":

  • Status: Enabled
  • Connection Limit: 1000
  • Connection Rate Limit: 400

The following settings are the allowed minimum/maximum settings:

  • Connection Limit: 1-100000
  • Connection Rate Limit: 1-4000