In most deployments, some servers are deployed to a DMZ zone and some servers are deployed to a network protected by a firewall.

In the Clustered Duke's Bank sample application, the Load Balancer node is the only node that you should access from a public network. The Database and Appserver nodes must be deployed in a private network behind a firewall. The Load Balancer node must also have access to the Database and AppServer nodes.

In Application Services, to resolve this situation, you can define two NICs on the Load Balancer. Each NIC must specify a logical network name. At deployment time, the logical network is mapped to an actual cloud network. When a virtual machine is created, the number of NICs for the virtual machine are derived from the node.

In the Dukes Bank sample application, the Load Balancer node has two NICs, NIC0 pointing to ServiceNetwork and NIC1 pointing to MgmtNetwork. Database and Appserver nodes have one NIC pointing to the ServiceNetwork. At deployment time, ServiceNetwork can be mapped to a cloud network protected by firewall and MgmtNetwork can be mapped to a public cloud network.

Familiarize yourself with the predefined IP address property concept when you have multiple NICs in a virtual machine. See Predefined IP Address Property.


To add multiple NICs, select a node and click the NICS tab below the node.

You can add up to 10 NICs to a node.


To add a NIC, click the Add icon (Add a NIC.) and specify a logical network name.


(Optional) To be part of the same network as another node, pick the network name from the drop-down menu.


Click a different part of the canvas or press Enter to finish adding the NIC.


Click Save in the toolbar above the canvas to save your changes.

Deploy the application. See Deploying Applications.