A node can have multiple NICs, with each NIC assigned one IP address in the deployed virtual machine.

These IP addresses are available in the NodeName:NICx_ip properties, where -x- is the NIC number.

In the sample Clustered Duke's Bank application, the Load Balancer node properties are shown as load_balancer:NIC0_ip and load_balancer:NIC1_ip because the Load Balancer node has two NICs defined. It is not guaranteed that NIC0 and NIC1 will be assigned to eth0 and eth1, respectively, in the virtual machine. The NICs are logical names in the blueprint for the network interfaces. These NICs are mapped to logical networks, which are mapped to specific cloud networks. The property NIC0_ip returns the IP address assigned to the virtual machine as defined in the blueprint, not the eth0 IP address in the virtual machine.

The load_balancer:ip property is also provided. This property refers to the IP address of the first NIC and NIC0. If a component needs IP addresses of all virtual machines in a cluster, it uses the all(NodeName:NICx_ip) property. To refer to the IP address of the current virtual machine, self:ip property is available. This property is useful for clustered nodes, as a component might need to know the virtual machine it is in, rather than the IP addresses of all the virtual machine in the cluster. To get the properties for a specific virtual machine in a cluster, you can use the all(NodeName:node_array_index) property. See Predefined Node Array Index Property.