|
21 | 21 | <section id="elastic-ip"> |
22 | 22 | <title>About Elastic IP</title> |
23 | 23 | <para>Elastic IP (EIP) addresses are the IP addresses that are associated with an account, and act |
24 | | - as static IP addresses. The account owner has complete control over the Elastic IP addresses |
25 | | - that belong to the account. You can allocate an Elastic IP to a VM of your choice from the EIP |
26 | | - pool of your account. Later if required you can reassign the IP address to a different VM. This |
27 | | - feature is extremely helpful during VM failure. Instead of replacing the VM which is down, the |
28 | | - IP address can be reassigned to a new VM in your account. Elastic IP service provides Static NAT |
29 | | - (1:1) service in an EIP-enabled basic zone. The default network offering, |
| 24 | + as static IP addresses. The account owner has the complete control over the Elastic IP addresses |
| 25 | + that belong to the account. As an account owner, you can allocate an Elastic IP to a VM of your |
| 26 | + choice from the EIP pool of your account. Later if required you can reassign the IP address to a |
| 27 | + different VM. This feature is extremely helpful during VM failure. Instead of replacing the VM |
| 28 | + which is down, the IP address can be reassigned to a new VM in your account. </para> |
| 29 | + <para>Similar to the public IP address, Elastic IP addresses are mapped to their associated |
| 30 | + private IP addresses by using StaticNAT. The EIP service is equipped with StaticNAT (1:1) |
| 31 | + service in an EIP-enabled basic zone. The default network offering, |
30 | 32 | DefaultSharedNetscalerEIPandELBNetworkOffering, provides your network with EIP and ELB network |
31 | | - services if a NetScaler device is deployed in your zone. Similar to the public IP address, |
32 | | - Elastic IP addresses are also mapped to their associated private IP addresses by using Stactic |
33 | | - NAT.</para> |
| 33 | + services if a NetScaler device is deployed in your zone. Consider the following illustration for |
| 34 | + more details.</para> |
| 35 | + <mediaobject> |
| 36 | + <imageobject> |
| 37 | + <imagedata fileref="./images/eip-ns-basiczone.png"/> |
| 38 | + </imageobject> |
| 39 | + <textobject> |
| 40 | + <phrase>eip-ns-basiczone.png: Elastic IP in a NetScaler-enabled Basic Zone.</phrase> |
| 41 | + </textobject> |
| 42 | + </mediaobject> |
| 43 | + <para>In the illustration, a NetScaler appliance is the default entry or exit point for the |
| 44 | + &PRODUCT; instances, and firewall is the default entry or exit point for the rest of the data |
| 45 | + center. Netscaler provides LB services and staticNAT service to the guest networks. The guest |
| 46 | + traffic in the pods and the Management Server are on different subnets / VLANs. The policy-based |
| 47 | + routing in the data center core switch sends the public traffic through the NetScaler, whereas |
| 48 | + the rest of the data center goes through the firewall. </para> |
34 | 49 | <para>The EIP work flow is as follows:</para> |
35 | 50 | <itemizedlist> |
36 | 51 | <listitem> |
|
48 | 63 | supported by NetScaler, in which the source IP address is replaced in the packets |
49 | 64 | generated by a VM in the private network with the public IP address.</para> |
50 | 65 | </note> |
51 | | - <para/> |
52 | 66 | </listitem> |
53 | 67 | <listitem> |
54 | 68 | <para>This default public IP will be released in two cases:</para> |
|
68 | 82 | </itemizedlist> |
69 | 83 | </listitem> |
70 | 84 | </itemizedlist> |
71 | | - <para>However, for the deployments where public IPs are limited resources, you have the |
72 | | - flexibility to choose not to allocate a public IP by default. You can use the Associate Public |
73 | | - IP option to turn on or off the automatic public IP assignment in the EIP-enabled Basic zones. |
74 | | - If you turn off the automatic public IP assignment while creating a network offering, only a |
75 | | - private IP is assigned to a VM when the VM is deployed with that network offering. Later, the |
76 | | - user can acquire an IP for the VM and enable static NAT.</para> |
| 85 | + <para>For the deployments where public IPs are limited resources, you have the flexibility to |
| 86 | + choose not to allocate a public IP by default. You can use the Associate Public IP option to |
| 87 | + turn on or off the automatic public IP assignment in the EIP-enabled Basic zones. If you turn |
| 88 | + off the automatic public IP assignment while creating a network offering, only a private IP is |
| 89 | + assigned to a VM when the VM is deployed with that network offering. Later, the user can acquire |
| 90 | + an IP for the VM and enable static NAT.</para> |
77 | 91 | <para condition="admin">For more information on the Associate Public IP option, see <xref |
78 | 92 | linkend="creating-network-offerings"/>.</para> |
79 | 93 | <para condition="install">For more information on the Associate Public IP option, see the |
|
83 | 97 | continue to get both public IP and private by default, irrespective of the network offering |
84 | 98 | configuration.</para> |
85 | 99 | </note> |
86 | | - <para/> |
87 | 100 | <para>New deployments which use the default shared network offering with EIP and ELB services to |
88 | 101 | create a shared network in the Basic zone will continue allocating public IPs to each user |
89 | 102 | VM.</para> |
|
0 commit comments