Skip to content

Commit 101d89c

Browse files
author
Radhika PC
committed
CLOUDSTACK-2301
1 parent 1686501 commit 101d89c

2 files changed

Lines changed: 30 additions & 17 deletions

File tree

docs/en-US/elastic-ip.xml

Lines changed: 30 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -21,16 +21,31 @@
2121
<section id="elastic-ip">
2222
<title>About Elastic IP</title>
2323
<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,
3032
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>
3449
<para>The EIP work flow is as follows:</para>
3550
<itemizedlist>
3651
<listitem>
@@ -48,7 +63,6 @@
4863
supported by NetScaler, in which the source IP address is replaced in the packets
4964
generated by a VM in the private network with the public IP address.</para>
5065
</note>
51-
<para/>
5266
</listitem>
5367
<listitem>
5468
<para>This default public IP will be released in two cases:</para>
@@ -68,12 +82,12 @@
6882
</itemizedlist>
6983
</listitem>
7084
</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>
7791
<para condition="admin">For more information on the Associate Public IP option, see <xref
7892
linkend="creating-network-offerings"/>.</para>
7993
<para condition="install">For more information on the Associate Public IP option, see the
@@ -83,7 +97,6 @@
8397
continue to get both public IP and private by default, irrespective of the network offering
8498
configuration.</para>
8599
</note>
86-
<para/>
87100
<para>New deployments which use the default shared network offering with EIP and ELB services to
88101
create a shared network in the Basic zone will continue allocating public IPs to each user
89102
VM.</para>
7.48 KB
Loading

0 commit comments

Comments
 (0)