|
21 | 21 | --> |
22 | 22 | <section id="multiple-ip-nic"> |
23 | 23 | <title>Configuring Multiple IP Addresses on a Single NIC</title> |
24 | | - <para>&PRODUCT; now provides you the ability to associate multiple private IP addresses per guest |
25 | | - VM NIC. This feature is supported on all the network configurations—Basic, Advanced, and |
26 | | - VPC. Security Groups, Static NAT and Port forwarding services are supported on these additional |
27 | | - IPs. In addition to the primary IP, you can assign additional IPs to the guest VM NIC.</para> |
| 24 | + <para>&PRODUCT; provides you the ability to associate multiple private IP addresses per guest VM |
| 25 | + NIC. In addition to the primary IP, you can assign additional IPs to the guest VM NIC. This |
| 26 | + feature is supported on all the network configurations—Basic, Advanced, and VPC. Security |
| 27 | + Groups, Static NAT and Port forwarding services are supported on these additional IPs. </para> |
28 | 28 | <para>As always, you can specify an IP from the guest subnet; if not specified, an IP is |
29 | 29 | automatically picked up from the guest VM subnet. You can view the IPs associated with for each |
30 | | - guest VM NICs on the UI. You can apply NAT on these additional guest IPs by using firewall |
31 | | - configuration in the &PRODUCT; UI. You must specify the NIC to which the IP should be |
| 30 | + guest VM NICs on the UI. You can apply NAT on these additional guest IPs by using network |
| 31 | + configuration option in the &PRODUCT; UI. You must specify the NIC to which the IP should be |
32 | 32 | associated.</para> |
33 | | - <para>This feature is supported on XenServer, KVM, and VMware hypervisors.</para> |
34 | | - <note> |
35 | | - <para>You need to configure the secondary IP address on the guest VM. &PRODUCT; will |
36 | | - not configure the acquired IP address on the VM. Ensure that you assign IPs to NIC each |
37 | | - time the VM reboots.</para> |
38 | | - </note> |
39 | | - <para>Some of the use cases are described below:</para> |
40 | | - <itemizedlist> |
41 | | - <listitem> |
42 | | - <para>Building network appliances: Network appliances, such as firewalls and load balancers, |
43 | | - generally work best when they have access to multiple IP addresses on the network |
44 | | - interface.</para> |
45 | | - </listitem> |
46 | | - <listitem> |
47 | | - <para>Moving private IP addresses between interfaces or instances. Applications that are bound |
48 | | - to specific IP addresses can be moved between instances. </para> |
49 | | - </listitem> |
50 | | - <listitem> |
51 | | - <para>Hosting multiple SSL Websites on a single instance. You can install multiple SSL |
52 | | - certificates on a single instance, each associated with a distinct IP address.</para> |
53 | | - </listitem> |
54 | | - </itemizedlist> |
| 33 | + <para>This feature is supported on XenServer, KVM, and VMware hypervisors. Note that Basic zone |
| 34 | + security groups are not supported on VMware.</para> |
| 35 | + <section id="usecases-mip"> |
| 36 | + <title>Use Cases</title> |
| 37 | + <para>Some of the use cases are described below:</para> |
| 38 | + <itemizedlist> |
| 39 | + <listitem> |
| 40 | + <para>Network devices, such as firewalls and load balancers, generally work best when they |
| 41 | + have access to multiple IP addresses on the network interface.</para> |
| 42 | + </listitem> |
| 43 | + <listitem> |
| 44 | + <para>Moving private IP addresses between interfaces or instances. Applications that are |
| 45 | + bound to specific IP addresses can be moved between instances. </para> |
| 46 | + </listitem> |
| 47 | + <listitem> |
| 48 | + <para>Hosting multiple SSL Websites on a single instance. You can install multiple SSL |
| 49 | + certificates on a single instance, each associated with a distinct IP address.</para> |
| 50 | + </listitem> |
| 51 | + </itemizedlist> |
| 52 | + </section> |
| 53 | + <section id="guideline-nic"> |
| 54 | + <title>Guidelines</title> |
| 55 | + <para>To prevent IP conflict, configure different subnets when multiple networks are connected |
| 56 | + to the same VM.</para> |
| 57 | + </section> |
55 | 58 | <section id="workflow-rn"> |
56 | 59 | <title>Assigning Additional IPs to a VM</title> |
57 | 60 | <orderedlist> |
|
68 | 71 | <para>In the Details tab, click NICs.</para> |
69 | 72 | </listitem> |
70 | 73 | <listitem> |
71 | | - <para>Click View All.</para> |
| 74 | + <para>Click View Secondary IPs.</para> |
72 | 75 | </listitem> |
73 | 76 | <listitem> |
74 | | - <para>Click Acquire New IP, and click Yes in the confirmation dialog.</para> |
75 | | - <para>You are prompted for confirmation because, typically, IP addresses are a limited |
76 | | - resource. Within a few moments, the new IP address should appear with the state Allocated. |
77 | | - You can now use the IP address in Port Forwarding or StaticNAT rules.</para> |
| 77 | + <para>Click Acquire New Secondary IP, and click Yes in the confirmation dialog.</para> |
| 78 | + <para>You need to specify the secondary IP address on the guest VM. &PRODUCT; will not |
| 79 | + automatically configure the acquired IP address on the VM. Ensure that you assign IPs to |
| 80 | + NIC each time the VM reboots.</para> |
| 81 | + <para>Within a few moments, the new IP address should appear with the state Allocated. You |
| 82 | + can now use the IP address in Port Forwarding or StaticNAT rules.</para> |
78 | 83 | </listitem> |
79 | 84 | </orderedlist> |
80 | 85 | </section> |
81 | | - <section id="caveats"> |
| 86 | + <section id="caveats"> |
82 | 87 | <title>Port Forwarding and StaticNAT Services Changes</title> |
83 | 88 | <para>Because multiple IPs can be associated per NIC, you are allowed to select a desired IP for |
84 | 89 | the Port Forwarding and StaticNAT services. The default is the primary IP. To enable this |
|
0 commit comments