Merge branch '4.3' into 4.4

Conflicts:
	source/accounts.rst
	source/service_offerings.rst
diff --git a/.tx/config b/.tx/config
index 4bc5a06..bdbe794 100644
--- a/.tx/config
+++ b/.tx/config
@@ -2,103 +2,248 @@
 host = https://www.transifex.com
 type = PO
 
-[apache-cloudstack-administration-rtd.accounts]
+[apache-cloudstack-administration-rtd.44xaccounts]
 file_filter = source/locale/<lang>/LC_MESSAGES/accounts.po
 source_file = source/locale/pot/accounts.pot
 source_lang = en
 
-[apache-cloudstack-administration-rtd.administration]
+[apache-cloudstack-administration-rtd.44xadministration]
 file_filter = source/locale/<lang>/LC_MESSAGES/administration.po
 source_file = source/locale/pot/administration.pot
 source_lang = en
 
-[apache-cloudstack-administration-rtd.api]
+[apache-cloudstack-administration-rtd.44xapi]
 file_filter = source/locale/<lang>/LC_MESSAGES/api.po
 source_file = source/locale/pot/api.pot
 source_lang = en
 
-[apache-cloudstack-administration-rtd.events]
+[apache-cloudstack-administration-rtd.44xevents]
 file_filter = source/locale/<lang>/LC_MESSAGES/events.po
 source_file = source/locale/pot/events.pot
 source_lang = en
 
-[apache-cloudstack-administration-rtd.hosts]
+[apache-cloudstack-administration-rtd.44xhosts]
 file_filter = source/locale/<lang>/LC_MESSAGES/hosts.po
 source_file = source/locale/pot/hosts.pot
 source_lang = en
 
-[apache-cloudstack-administration-rtd.index]
+[apache-cloudstack-administration-rtd.44xindex]
 file_filter = source/locale/<lang>/LC_MESSAGES/index.po
 source_file = source/locale/pot/index.pot
 source_lang = en
 
-[apache-cloudstack-administration-rtd.management]
+[apache-cloudstack-administration-rtd.44xmanagement]
 file_filter = source/locale/<lang>/LC_MESSAGES/management.po
 source_file = source/locale/pot/management.pot
 source_lang = en
 
-[apache-cloudstack-administration-rtd.networking]
+[apache-cloudstack-administration-rtd.44xnetworking]
 file_filter = source/locale/<lang>/LC_MESSAGES/networking.po
 source_file = source/locale/pot/networking.pot
 source_lang = en
 
-[apache-cloudstack-administration-rtd.networking2]
-file_filter = source/locale/<lang>/LC_MESSAGES/networking2.po
-source_file = source/locale/pot/networking2.pot
-source_lang = en
-
-[apache-cloudstack-administration-rtd.projects]
+[apache-cloudstack-administration-rtd.44xprojects]
 file_filter = source/locale/<lang>/LC_MESSAGES/projects.po
 source_file = source/locale/pot/projects.pot
 source_lang = en
 
-[apache-cloudstack-administration-rtd.reliability]
+[apache-cloudstack-administration-rtd.44xreliability]
 file_filter = source/locale/<lang>/LC_MESSAGES/reliability.po
 source_file = source/locale/pot/reliability.pot
 source_lang = en
 
-[apache-cloudstack-administration-rtd.service_offerings]
+[apache-cloudstack-administration-rtd.44xservice_offerings]
 file_filter = source/locale/<lang>/LC_MESSAGES/service_offerings.po
 source_file = source/locale/pot/service_offerings.pot
 source_lang = en
 
-[apache-cloudstack-administration-rtd.storage]
+[apache-cloudstack-administration-rtd.44xstorage]
 file_filter = source/locale/<lang>/LC_MESSAGES/storage.po
 source_file = source/locale/pot/storage.pot
 source_lang = en
 
-[apache-cloudstack-administration-rtd.systemvm]
+[apache-cloudstack-administration-rtd.44xsystemvm]
 file_filter = source/locale/<lang>/LC_MESSAGES/systemvm.po
 source_file = source/locale/pot/systemvm.pot
 source_lang = en
 
-[apache-cloudstack-administration-rtd.templates]
+[apache-cloudstack-administration-rtd.44xtemplates]
 file_filter = source/locale/<lang>/LC_MESSAGES/templates.po
 source_file = source/locale/pot/templates.pot
 source_lang = en
 
-[apache-cloudstack-administration-rtd.troubleshooting]
+[apache-cloudstack-administration-rtd.44xtroubleshooting]
 file_filter = source/locale/<lang>/LC_MESSAGES/troubleshooting.po
 source_file = source/locale/pot/troubleshooting.pot
 source_lang = en
 
-[apache-cloudstack-administration-rtd.tuning]
+[apache-cloudstack-administration-rtd.44xtuning]
 file_filter = source/locale/<lang>/LC_MESSAGES/tuning.po
 source_file = source/locale/pot/tuning.pot
 source_lang = en
 
-[apache-cloudstack-administration-rtd.ui]
+[apache-cloudstack-administration-rtd.44xui]
 file_filter = source/locale/<lang>/LC_MESSAGES/ui.po
 source_file = source/locale/pot/ui.pot
 source_lang = en
 
-[apache-cloudstack-administration-rtd.usage]
+[apache-cloudstack-administration-rtd.44xusage]
 file_filter = source/locale/<lang>/LC_MESSAGES/usage.po
 source_file = source/locale/pot/usage.pot
 source_lang = en
 
-[apache-cloudstack-administration-rtd.virtual_machines]
+[apache-cloudstack-administration-rtd.44xvirtual_machines]
 file_filter = source/locale/<lang>/LC_MESSAGES/virtual_machines.po
 source_file = source/locale/pot/virtual_machines.pot
 source_lang = en
 
+[apache-cloudstack-administration-rtd.44xnetworking_and_traffic]
+file_filter = source/locale/<lang>/LC_MESSAGES/networking_and_traffic.po
+source_file = source/locale/pot/networking_and_traffic.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.44xnetworking--acquiring_an_ip_address]
+file_filter = source/locale/<lang>/LC_MESSAGES/networking/acquiring_an_ip_address.po
+source_file = source/locale/pot/networking/acquiring_an_ip_address.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.44xnetworking--advanced_zone_config]
+file_filter = source/locale/<lang>/LC_MESSAGES/networking/advanced_zone_config.po
+source_file = source/locale/pot/networking/advanced_zone_config.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.44xnetworking--basic_zone_config]
+file_filter = source/locale/<lang>/LC_MESSAGES/networking/basic_zone_config.po
+source_file = source/locale/pot/networking/basic_zone_config.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.44xnetworking--dns_and_dhcp]
+file_filter = source/locale/<lang>/LC_MESSAGES/networking/dns_and_dhcp.po
+source_file = source/locale/pot/networking/dns_and_dhcp.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.44xnetworking--elastic_ips]
+file_filter = source/locale/<lang>/LC_MESSAGES/networking/elastic_ips.po
+source_file = source/locale/pot/networking/elastic_ips.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.44xnetworking--external_firewalls_and_load_balancers]
+file_filter = source/locale/<lang>/LC_MESSAGES/networking/external_firewalls_and_load_balancers.po
+source_file = source/locale/pot/networking/external_firewalls_and_load_balancers.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.44xnetworking--global_server_load_balancing]
+file_filter = source/locale/<lang>/LC_MESSAGES/networking/global_server_load_balancing.po
+source_file = source/locale/pot/networking/global_server_load_balancing.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.44xnetworking--guest_ip_ranges]
+file_filter = source/locale/<lang>/LC_MESSAGES/networking/guest_ip_ranges.po
+source_file = source/locale/pot/networking/guest_ip_ranges.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.44xnetworking--guest_traffic]
+file_filter = source/locale/<lang>/LC_MESSAGES/networking/guest_traffic.po
+source_file = source/locale/pot/networking/guest_traffic.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.44xnetworking--inter_vlan_routing]
+file_filter = source/locale/<lang>/LC_MESSAGES/networking/inter_vlan_routing.po
+source_file = source/locale/pot/networking/inter_vlan_routing.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.44xnetworking--ip_forwarding_and_firewalling]
+file_filter = source/locale/<lang>/LC_MESSAGES/networking/ip_forwarding_and_firewalling.po
+source_file = source/locale/pot/networking/ip_forwarding_and_firewalling.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.44xnetworking--ip_load_balancing]
+file_filter = source/locale/<lang>/LC_MESSAGES/networking/ip_load_balancing.po
+source_file = source/locale/pot/networking/ip_load_balancing.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.44xnetworking--ip_reservation_in_guest_networks]
+file_filter = source/locale/<lang>/LC_MESSAGES/networking/ip_reservation_in_guest_networks.po
+source_file = source/locale/pot/networking/ip_reservation_in_guest_networks.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.44xnetworking--isolation_in_advanced_zone_with_vlan]
+file_filter = source/locale/<lang>/LC_MESSAGES/networking/isolation_in_advanced_zone_with_vlan.po
+source_file = source/locale/pot/networking/isolation_in_advanced_zone_with_vlan.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.44xnetworking--multiple_guest_networks]
+file_filter = source/locale/<lang>/LC_MESSAGES/networking/multiple_guest_networks.po
+source_file = source/locale/pot/networking/multiple_guest_networks.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.44xnetworking--multiple_ip_ranges]
+file_filter = source/locale/<lang>/LC_MESSAGES/networking/multiple_ip_ranges.po
+source_file = source/locale/pot/networking/multiple_ip_ranges.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.44xnetworking--multiple_ips_on_single_nic]
+file_filter = source/locale/<lang>/LC_MESSAGES/networking/multiple_ips_on_single_nic.po
+source_file = source/locale/pot/networking/multiple_ips_on_single_nic.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.44xnetworking--multiple_subnets_in_shared_network]
+file_filter = source/locale/<lang>/LC_MESSAGES/networking/multiple_subnets_in_shared_network.po
+source_file = source/locale/pot/networking/multiple_subnets_in_shared_network.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.44xnetworking--networking_in_pod]
+file_filter = source/locale/<lang>/LC_MESSAGES/networking/networking_in_pod.po
+source_file = source/locale/pot/networking/networking_in_pod.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.44xnetworking--networking_in_zone]
+file_filter = source/locale/<lang>/LC_MESSAGES/networking/networking_in_zone.po
+source_file = source/locale/pot/networking/networking_in_zone.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.44xnetworking--palo_alto_config]
+file_filter = source/locale/<lang>/LC_MESSAGES/networking/palo_alto_config.po
+source_file = source/locale/pot/networking/palo_alto_config.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.44xnetworking--persistent_networks]
+file_filter = source/locale/<lang>/LC_MESSAGES/networking/persistent_networks.po
+source_file = source/locale/pot/networking/persistent_networks.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.44xnetworking--portable_ips]
+file_filter = source/locale/<lang>/LC_MESSAGES/networking/portable_ips.po
+source_file = source/locale/pot/networking/portable_ips.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.44xnetworking--public_ips_and_vlans_for_accounts]
+file_filter = source/locale/<lang>/LC_MESSAGES/networking/public_ips_and_vlans_for_accounts.po
+source_file = source/locale/pot/networking/public_ips_and_vlans_for_accounts.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.44xnetworking--releasing_an_ip_address]
+file_filter = source/locale/<lang>/LC_MESSAGES/networking/releasing_an_ip_address.po
+source_file = source/locale/pot/networking/releasing_an_ip_address.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.44xnetworking--remote_access_vpn]
+file_filter = source/locale/<lang>/LC_MESSAGES/networking/remote_access_vpn.po
+source_file = source/locale/pot/networking/remote_access_vpn.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.44xnetworking--security_groups]
+file_filter = source/locale/<lang>/LC_MESSAGES/networking/security_groups.po
+source_file = source/locale/pot/networking/security_groups.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.44xnetworking--static_nat]
+file_filter = source/locale/<lang>/LC_MESSAGES/networking/static_nat.po
+source_file = source/locale/pot/networking/static_nat.pot
+source_lang = en
+
+[apache-cloudstack-administration-rtd.44xnetworking--virtual_private_cloud_config]
+file_filter = source/locale/<lang>/LC_MESSAGES/networking/virtual_private_cloud_config.po
+source_file = source/locale/pot/networking/virtual_private_cloud_config.pot
+source_lang = en
+
diff --git a/README.rst b/README.rst
index a866fbb..0b8430a 100644
--- a/README.rst
+++ b/README.rst
@@ -13,17 +13,20 @@
    specific language governing permissions and limitations
    under the License.
 
+
 Apache CloudStack
 =================
 
 Apache CloudStack is an Apache project, see <http://cloudstack.apache.org> for
 more information.
 
+
 Website
 =======
 
 This administration guide is on-line at <http://cloudstack-administration.readthedocs.org/en/latest/>
 
+
 Translation
 ===========
 
@@ -64,18 +67,114 @@
    sphinx-intl build --locale-dir source/locale
    make -e SPHINXOPTS="-D language='ja'" html
 
+
 Feedback
 ========
 
 Please send feedback to the mailing list at <dev@cloudstack.apache.org>,
 or the JIRA at <https://issues.apache.org/jira/browse/CLOUDSTACK>.
 
-Contributing
-============
 
-You can submit a pull request via github or submit patches via review board <https://reviews.apache.org>
+Contributing to the documentation
+=================================
 
-For information on how to contribute, please see the Contributing
-chapter in our documentation <http://cloudstack.apache.org/developers.html>
+Initial setup of your fork
+--------------------------
+
+In your browser, navigate to: https://github.com/apache/cloudstack-docs-admin
+
+Fork this repository by clicking on the 'Fork' button on the top right hand side.  The fork will happen and you will be taken to your own fork of the repository.  On the right hand side of the page of your fork, under 'HTTPS clone URL', copy the URL to your clipboard by clicking the the clipboard just right of the URL.
+
+On your computer, follow these steps to setup a local repository for working on the documentation:
+
+.. code:: bash
+
+   $ git clone https://github.com/YOUR_ACCOUNT/cloudstack-docs-admin.git
+   $ cd cloudstack-docs-admin
+   $ git remote add upstream https://github.com/apache/cloudstack-docs-admin.git
+   $ git checkout master
+   $ git fetch upstream
+   $ git merge upstream/master
 
 
+Making changes
+--------------
+
+It is important that you create a new branch to make changes on and that you do not change the `master` branch (other than to pull in changes from `upstream/master`).  In this case I will assume you will be creating a branch called `dev` to make your changes in.  This `dev` branch will be created on your local repository and will then be pushed to your forked repository on GitHub where you will create a Pull Request for the changes to be committed into the official documentation.
+
+It is good practice to create a new branch each time you want to contribute to the documentation and only track the changes for that pull request in this branch.
+
+.. code:: bash
+
+   $ git checkout -b dev
+   (make your changes)
+   $ git add .
+   $ git commit -a -m "commit message for your changes"
+
+.. note:: 
+   The `-b` specifies that you want to create a new branch called `dev`.  You only specify `-b` the first time because you are creating a new branch.  Once the `dev` branch exists, you can later switch to it with only `git checkout dev`.
+
+
+Merging `upstream/master` into your `dev` branch
+------------------------------------------------
+
+It is important that you maintain an up-to-date `master` branch in your local repository.  This is done by merging in the `upstream/master` (the official documentation repository) into your local repository.  You will want to do this before you start working on a feature as well as right before you submit your changes as a pull request.  You can also do this process periodically while you work on your changes to make sure you are working off the most recent version of the documentation.
+
+This process will do the following:
+
+#. Checkout your local `master` branch
+
+#. Synchronize your local `master` branch with the `upstream/master` so you have all the latest changes from the official docs
+
+#. Merge the latest changes from the official docs into your `dev` branch so it is up-to-date with the latest changes
+
+.. code:: bash
+
+   $ git checkout master
+   $ git fetch upstream
+   $ git merge upstream/master
+   $ git checkout dev
+   $ git pull . master
+
+.. note:: Now your `dev` branch is up-to-date with all the recent changes in the `upstream/master`.
+
+
+Making a pull request on GitHub to contribute your changes
+----------------------------------------------------------
+
+When you are happy with your changes and you want to contribute them, you will be creating a Pull Request on GitHub to do so.  This is done by pushing your changes to your forked repository (usually called 'origin') and then initiating a pull request.
+
+.. note:: Make sure you have merged `upstream/master` into your `dev` branch before you do this.
+
+.. code:: bash
+
+   $ git push origin master
+   $ git push origin dev
+
+Now that the `dev` branch has been pushed to your GitHub repository, you can initiate the pull request.  
+
+To initiate the pull request, do the following:
+
+#. Navigate your browser to your forked repository: https://github.com/YOUR_ACCOUNT/cloudstack-docs-admin
+
+#. Click the new button called 'Compare & pull request' that showed up just above the main area in your forked repository
+
+#. Enter a good description of the work you have done and then click 'Send pull request'
+
+If you are requested to make modifications to your proposed changes, make the changes locally on your `dev` branch, re-push the changes and submit the pull request again.
+
+
+Cleaning up after a successful pull request
+-------------------------------------------
+
+Once the `dev` branch has been committed into the `upstream/master` branch, your local `dev` branch and the `origin/dev` branch are not needed anymore.  If you want to make additional documentation changes, restart the process with a new branch.
+
+.. note:: Make sure that your changes are in `upstream/master` before you delete your `dev` and `origin/dev` branches!
+
+You can delete these deprecated branches with the following:
+
+.. code:: bash
+
+   $ git checkout master
+   $ git branch -D dev
+   $ git push origin :dev
diff --git a/source/_static/acslogo.png b/source/_static/acslogo.png
new file mode 100644
index 0000000..a938231
--- /dev/null
+++ b/source/_static/acslogo.png
Binary files differ
diff --git a/source/conf.py b/source/conf.py
index b181590..9811851 100644
--- a/source/conf.py
+++ b/source/conf.py
@@ -61,7 +61,7 @@
 # The short X.Y version.
 version = '4'
 # The full version, including alpha/beta/rc tags.
-release = '4.3'
+release = '4.4'
 
 # The language for content autogenerated by Sphinx. Refer to documentation
 # for a list of supported languages.
diff --git a/source/locale/pot/accounts.pot b/source/locale/pot/accounts.pot
index c7ed8fb..2bc6819 100644
--- a/source/locale/pot/accounts.pot
+++ b/source/locale/pot/accounts.pot
@@ -8,7 +8,7 @@
 msgstr ""
 "Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2014-03-31 14:08-0400\n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -17,393 +17,393 @@
 "Content-Transfer-Encoding: 8bit\n"
 
 #: ../../accounts.rst:18
-# 90951daa147540dab10f9d0c78d8c73b
+# bdc151e73be141a8ad0b4190c3102939
 msgid "Managing Accounts, Users and Domains"
 msgstr ""
 
 #: ../../accounts.rst:21
-# 661635f04f94452db5ca9e4dd563cef7
+# a49422e951994e72894009f0fc5cc963
 msgid "Accounts, Users, and Domains"
 msgstr ""
 
 #: ../../accounts.rst:24
-# a7494e04f72d469a86f3c67e958ed65f
+# 7316ca3f637249cbbf2f29bd75791600
 msgid "Accounts"
 msgstr ""
 
 #: ../../accounts.rst:26
-# 457dea8dff534d9aa75e2270c1e1ac6d
+# 7544ce31af194b279c9dcfb7ae37d3cc
 msgid "An account typically represents a customer of the service provider or a department in a large organization. Multiple users can exist in an account."
 msgstr ""
 
-#: ../../accounts.rst:31
-# b45cd9ee7d3e478cbb3c129943ce53d5
+#: ../../accounts.rst:32
+# e758840629a8483ba31892ff437911e1
 msgid "Domains"
 msgstr ""
 
-#: ../../accounts.rst:33
-# 10ebf41c7dbf4e65b1be24934d043965
+#: ../../accounts.rst:34
+# 3e28d2a36b0642c08a698f6a4426e72c
 msgid "Accounts are grouped by domains. Domains usually contain multiple accounts that have some logical relationship to each other and a set of delegated administrators with some authority over the domain and its subdomains. For example, a service provider with several resellers could create a domain for each reseller."
 msgstr ""
 
-#: ../../accounts.rst:39
-# 403c3bff584f41c6b9ee1d4ba5bc6241
+#: ../../accounts.rst:40
+# 79060520f2e046868f58925f3f2efc01
 msgid "For each account created, the Cloud installation creates three different types of user accounts: root administrator, domain administrator, and user."
 msgstr ""
 
-#: ../../accounts.rst:44
-# 65e0965c3efe4beb825b48109a593375
+#: ../../accounts.rst:46
+# 341bf7792d884c2d8180600a07351f62
 msgid "Users"
 msgstr ""
 
-#: ../../accounts.rst:46
-# 34892ebe1c424238b2d30be07cfbef77
+#: ../../accounts.rst:48
+# 8efee3ca63e44a4098ff5086e58f1249
 msgid "Users are like aliases in the account. Users in the same account are not isolated from each other, but they are isolated from users in other accounts. Most installations need not surface the notion of users; they just have one user per account. The same user cannot belong to multiple accounts."
 msgstr ""
 
-#: ../../accounts.rst:52
-# 31c0da272edb4413bba06570446855e5
+#: ../../accounts.rst:54
+# 67a573904306470f87a1f3f6ad52a15f
 msgid "Username is unique in a domain across accounts in that domain. The same username can exist in other domains, including sub-domains. Domain name can repeat only if the full pathname from root is unique. For example, you can create root/d1, as well as root/foo/d1, and root/sales/d1."
 msgstr ""
 
-#: ../../accounts.rst:57
-# 1754108df51d4b9aa2bfcab98e1b9bf0
+#: ../../accounts.rst:59
+# af85977a7aeb4aff9010bde059e08b23
 msgid "Administrators are accounts with special privileges in the system. There may be multiple administrators in the system. Administrators can create or delete other administrators, and change the password for any user in the system."
 msgstr ""
 
-#: ../../accounts.rst:63
-# 12ec03346ad2491195e691d8d6e3139b
+#: ../../accounts.rst:66
+# 8613eb42958647fba87ae1b922d58740
 msgid "Domain Administrators"
 msgstr ""
 
-#: ../../accounts.rst:65
-# 14a1bb86d2624ad3b4c82731fa8dd170
+#: ../../accounts.rst:68
+# 901efdb2c8554033b865587a48a319f9
 msgid "Domain administrators can perform administrative operations for users who belong to that domain. Domain administrators do not have visibility into physical servers or other domains."
 msgstr ""
 
-#: ../../accounts.rst:70
-# 39f193590cb5492691994021f7591f2e
+#: ../../accounts.rst:74
+# 5922a532b5814e479301a7d697eb8854
 msgid "Root Administrator"
 msgstr ""
 
-#: ../../accounts.rst:72
-# 97d51f9ba69843b5af3c3770b5e6a41d
+#: ../../accounts.rst:76
+# 20be104d0a134bab92309e774b538dd4
 msgid "Root administrators have complete access to the system, including managing templates, service offerings, customer care administrators, and domains"
 msgstr ""
 
-#: ../../accounts.rst:77
-# 0231216736c74923a934181f66c7be6d
+#: ../../accounts.rst:82
+# 7f9e7eaa9c5b4eaba5575b81514d4040
 msgid "Resource Ownership"
 msgstr ""
 
-#: ../../accounts.rst:79
-# 72eb8676abfd416cb9bbb177a3de84f6
+#: ../../accounts.rst:84
+# 3fad6f5edfb34464b707419ce6b7b4a6
 msgid "Resources belong to the account, not individual users in that account. For example, billing, resource limits, and so on are maintained by the account, not the users. A user can operate on any resource in the account provided the user has privileges for that operation. The privileges are determined by the role. A root administrator can change the ownership of any virtual machine from one account to any other account by using the assignVirtualMachine API. A domain or sub-domain administrator can do the same for VMs within the domain from one account to any other account in the domain or any of its sub-domains."
 msgstr ""
 
-#: ../../accounts.rst:90
-# ff5d0b1e1c574c599f7af2c724e6fed1
+#: ../../accounts.rst:96
+# f25ec45041cd435d83eaf32720407dd4
 msgid "Dedicating Resources to Accounts and Domains"
 msgstr ""
 
-#: ../../accounts.rst:92
-# 0a4bdfeefcbc4e6b90e29d85882276e5
+#: ../../accounts.rst:98
+# 8a6427fc034647e681a14ca03224406c
 msgid "The root administrator can dedicate resources to a specific domain or account that needs private infrastructure for additional security or performance guarantees. A zone, pod, cluster, or host can be reserved by the root administrator for a specific domain or account. Only users in that domain or its subdomain may use the infrastructure. For example, only users in a given domain can create guests in a zone dedicated to that domain."
 msgstr ""
 
-#: ../../accounts.rst:100
-# d6b26e49ebc04db7bc3a577de66cada3
+#: ../../accounts.rst:106
+# 13b20e92d1144d5da1089384a9ce4e59
 msgid "There are several types of dedication available:"
 msgstr ""
 
-#: ../../accounts.rst:104
-# dac518c9d097412c8fc411ea7ed6a9e7
+#: ../../accounts.rst:108
+# a62e7433baeb444386932b41fe5601fa
 msgid "Explicit dedication. A zone, pod, cluster, or host is dedicated to an account or domain by the root administrator during initial deployment and configuration."
 msgstr ""
 
-#: ../../accounts.rst:110
-# 574012d1f1984a9a8d7a720f9ea1c4d6
+#: ../../accounts.rst:112
+# 29fbffa86cfd49b4aa29ea7d373eaa03
 msgid "Strict implicit dedication. A host will not be shared across multiple accounts. For example, strict implicit dedication is useful for deployment of certain types of applications, such as desktops, where no host can be shared between different accounts without violating the desktop software's terms of license."
 msgstr ""
 
 #: ../../accounts.rst:118
-# a5988bb1ccf4413394ead18a5bf8d2b4
+# a821acd0f71541708e12788d2fbc5d75
 msgid "Preferred implicit dedication. The VM will be deployed in dedicated infrastructure if possible. Otherwise, the VM can be deployed in shared infrastructure."
 msgstr ""
 
-#: ../../accounts.rst:123
-# 599bcac969ab4007b46f4a44e3aab507
+#: ../../accounts.rst:124
+# b498c9fe36a94f2588d7a9e4494a761d
 msgid "How to Dedicate a Zone, Cluster, Pod, or Host to an Account or Domain"
 msgstr ""
 
-#: ../../accounts.rst:125
-# 235f58f9b9bd48eab66c66dc94d93e40
+#: ../../accounts.rst:126
+# 62ce22c4d6f346b79218ff7a937ee3e2
 msgid "For explicit dedication: When deploying a new zone, pod, cluster, or host, the root administrator can click the Dedicated checkbox, then choose a domain or account to own the resource."
 msgstr ""
 
-#: ../../accounts.rst:129
-# 99189fbc5d704126a534a43918bd1cc9
+#: ../../accounts.rst:130
+# 9dfe3b7a9e87411d9694c32c5e4f891e
 msgid "To explicitly dedicate an existing zone, pod, cluster, or host: log in as the root admin, find the resource in the UI, and click the Dedicate button. |button to dedicate a zone, pod,cluster, or host|"
 msgstr ""
 
-#: ../../accounts.rst:133
-# e7ebf6fbd7d048bf822061139e2b5a4c
+#: ../../accounts.rst:134
+# 90707af3ed2b4e6fa7875e9bdd890252
 msgid "For implicit dedication: The administrator creates a compute service offering and in the Deployment Planner field, chooses ImplicitDedicationPlanner. Then in Planner Mode, the administrator specifies either Strict or Preferred, depending on whether it is permissible to allow some use of shared resources when dedicated resources are not available. Whenever a user creates a VM based on this service offering, it is allocated on one of the dedicated hosts."
 msgstr ""
 
-#: ../../accounts.rst:142
-# 57e1c25d97df4d22b88b35dc599e45f7
+#: ../../accounts.rst:144
+# fda3697ce3a4454da72edbe9f02b3564
 msgid "How to Use Dedicated Hosts"
 msgstr ""
 
-#: ../../accounts.rst:144
-# b227acf3ae06498d99b21119713e2238
+#: ../../accounts.rst:146
+# cfd0e245a5a2498b9fa7c89160957ffe
 msgid "To use an explicitly dedicated host, use the explicit-dedicated type of affinity group (see `“Affinity Groups” <virtual_machines.html#affinity-groups>`_). For example, when creating a new VM, an end user can choose to place it on dedicated infrastructure. This operation will succeed only if some infrastructure has already been assigned as dedicated to the user's account or domain."
 msgstr ""
 
-#: ../../accounts.rst:152
-# f9c5cb26d6904347ad48d4ceba1481a6
+#: ../../accounts.rst:155
+# 86abbd3940f34e96a1ad71a01dc6339d
 msgid "Behavior of Dedicated Hosts, Clusters, Pods, and Zones"
 msgstr ""
 
-#: ../../accounts.rst:154
-# 05b28e9607634f78abda79633a1403cf
+#: ../../accounts.rst:157
+# a9963e63da4e48f2a2b7b7fdad96ba29
 msgid "The administrator can live migrate VMs away from dedicated hosts if desired, whether the destination is a host reserved for a different account/domain or a host that is shared (not dedicated to any particular account or domain). CloudStack will generate an alert, but the operation is allowed."
 msgstr ""
 
-#: ../../accounts.rst:160
-# ce25fc9a198a4cbeaabd2e2405325e9c
+#: ../../accounts.rst:163
+# a9a8992734b0490aac5bd5e5efa45483
 msgid "Dedicated hosts can be used in conjunction with host tags. If both a host tag and dedication are requested, the VM will be placed only on a host that meets both requirements. If there is no dedicated resource available to that user that also has the host tag requested by the user, then the VM will not deploy."
 msgstr ""
 
-#: ../../accounts.rst:166
-# aeb33b23037c45be909c3768cc8966b6
+#: ../../accounts.rst:169
+# 694b1842b07049c094a79e240c2db934
 msgid "If you delete an account or domain, any hosts, clusters, pods, and zones that were dedicated to it are freed up. They will now be available to be shared by any account or domain, or the administrator may choose to re-dedicate them to a different account or domain."
 msgstr ""
 
-#: ../../accounts.rst:171
-# 1ce4e0516a79477a817eb0619fbfb51e
+#: ../../accounts.rst:174
+# 9676e7d49a4247c0bd41a3d53e7482a1
 msgid "System VMs and virtual routers affect the behavior of host dedication. System VMs and virtual routers are owned by the CloudStack system account, and they can be deployed on any host. They do not adhere to explicit dedication. The presence of system vms and virtual routers on a host makes it unsuitable for strict implicit dedication. The host can not be used for strict implicit dedication, because the host already has VMs of a specific account (the default system account). However, a host with system VMs or virtual routers can be used for preferred implicit dedication."
 msgstr ""
 
-#: ../../accounts.rst:182
-# ad8c17e1de7c4cb4af2c8b55ee0a851c
+#: ../../accounts.rst:186
+# c3ac9b9cb46f4fa7b6ea8d96adc7111e
 msgid "Using an LDAP Server for User Authentication"
 msgstr ""
 
-#: ../../accounts.rst:184
-# d3eb07c14a05493ba2ff39ea53010821
+#: ../../accounts.rst:188
+# 4c358cdbd0ef4ea8bae9aa240f1b4e4a
 msgid "You can use an external LDAP server such as Microsoft Active Directory or ApacheDS to authenticate CloudStack end-users. Just map CloudStack accounts to the corresponding LDAP accounts using a query filter. The query filter is written using the query syntax of the particular LDAP server, and can include special wildcard characters provided by CloudStack for matching common values such as the user’s email address and name. CloudStack will search the external LDAP directory tree starting at a specified base directory and return the distinguished name (DN) and password of the matching user. This information along with the given password is used to authenticate the user.."
 msgstr ""
 
-#: ../../accounts.rst:195
-# efbc795d47b644b592c065f9221a5ecc
+#: ../../accounts.rst:199
+# 14c749c7da61408588c8e8cdaa11796c
 msgid "To set up LDAP authentication in CloudStack, call the CloudStack API command ldapConfig and provide the following:"
 msgstr ""
 
-#: ../../accounts.rst:200
-# 7826c9574e864a3fa3927d2452d6f247
+#: ../../accounts.rst:202
+# c4708aa56b75423080f17f84ec2a37a4
 msgid "Hostname or IP address and listening port of the LDAP server"
 msgstr ""
 
 #: ../../accounts.rst:204
-# 70b92e095a0749628ec280152921d951
+# ff4d11fcc40f4d5c86ce032c3d6e6a76
 msgid "Base directory and query filter"
 msgstr ""
 
-#: ../../accounts.rst:208
-# 4fe250c5d3ac44ab883b8c10af24f1fe
+#: ../../accounts.rst:206
+# 0b5fce75930e49b19cf1d00062c78539
 msgid "Search user DN credentials, which give CloudStack permission to search on the LDAP server"
 msgstr ""
 
-#: ../../accounts.rst:213
-# 2ceaa9828892484ebd391520d745991d
+#: ../../accounts.rst:209
+# c3d66516470141c3af861a4b24f45150
 msgid "SSL keystore and password, if SSL is used"
 msgstr ""
 
-#: ../../accounts.rst:216
-# 26d8fb1d67a74f8387452da5b3cce675
+#: ../../accounts.rst:213
+# 6e565fd7b02d4a97b86b380e839f129f
 msgid "Example LDAP Configuration Commands"
 msgstr ""
 
-#: ../../accounts.rst:218
-# 1c19000335be4f7ebdab1d79a7c4658c
+#: ../../accounts.rst:215
+# ee72e29a6b33456684ebcbfd012c075a
 msgid "To understand the examples in this section, you need to know the basic concepts behind calling the CloudStack API, which are explained in the Developer’s Guide."
 msgstr ""
 
-#: ../../accounts.rst:222
-# d7aafed8ded6431d8129d3bbe41769aa
+#: ../../accounts.rst:219
+# 065e58a0d0f74c8d84670251cf00c487
 msgid "The following shows an example invocation of ldapConfig with an ApacheDS LDAP server"
 msgstr ""
 
-#: ../../accounts.rst:229
-# 7214405299e94877a1c09f6c6287ee10
+#: ../../accounts.rst:226
+# 31d88144f8004adf8efd11cf7f9db7bd
 msgid "The command must be URL-encoded. Here is the same example without the URL encoding:"
 msgstr ""
 
-#: ../../accounts.rst:247
-# 74c45748c7614774911829b534605cc1
+#: ../../accounts.rst:244
+# 884cde7f5dbd499ba1c28ff09380c692
 msgid "The following shows a similar command for Active Directory. Here, the search base is the testing group within a company, and the users are matched up based on email address."
 msgstr ""
 
-#: ../../accounts.rst:255
-# e42d0dbce6674c9ba00d73998fb30e71
+#: ../../accounts.rst:252
+# d2675a267aa34f4ea3fe2bba2300b61c
 msgid "The next few sections explain some of the concepts you will need to know when filling out the ldapConfig parameters."
 msgstr ""
 
-#: ../../accounts.rst:259
-# a47324fc43df41cdbcae97f676f2536f
+#: ../../accounts.rst:257
+# befdce0cfd624549844139c917a82bb4
 msgid "Search Base"
 msgstr ""
 
-#: ../../accounts.rst:261
-# f44d14b0d741402087e0cc706bbb068e
+#: ../../accounts.rst:259
+# 1522f19d5a2a4e35a8bedc5d147a1af1
 msgid "An LDAP query is relative to a given node of the LDAP directory tree, called the search base. The search base is the distinguished name (DN) of a level of the directory tree below which all users can be found. The users can be in the immediate base directory or in some subdirectory. The search base may be equivalent to the organization, group, or domain name. The syntax for writing a DN varies depending on which LDAP server you are using. A full discussion of distinguished names is outside the scope of our documentation. The following table shows some examples of search bases to find users in the testing department.."
 msgstr ""
 
-#: ../../accounts.rst:272
+#: ../../accounts.rst:270
 #: ../../accounts.rst:328
-# c824c6d3616243eaa848cc45808ec373
-# 46c8c55831674fd3a12caa7352108fa4
+# 3649e87915d24059beec30463e0abd10
+# eb0f32160dd24b21991c2f454df60742
 msgid "LDAP Server"
 msgstr ""
 
-#: ../../accounts.rst:272
-# bf34c451c0994186b556742324006c30
+#: ../../accounts.rst:270
+# d8fb5f498afb4ee1aa6669b39f1e34be
 msgid "Example Search Base DN"
 msgstr ""
 
-#: ../../accounts.rst:274
+#: ../../accounts.rst:272
 #: ../../accounts.rst:330
-# c6940ea324fb4c99895c4d2152bfd32e
-# 359bafef7f4044e380b30643767ad285
+# 2e421fc0d49d4a819b31999dc3cae2e0
+# a0327a00878d45dab6dc0bc777814674
 msgid "ApacheDS"
 msgstr ""
 
-#: ../../accounts.rst:274
-# 2253d38b2ae84eeab805635117cf368c
+#: ../../accounts.rst:272
+# 6c854d5e6cdd4e3aadda7dd9be769a53
 msgid "OU=testing, O=project"
 msgstr ""
 
-#: ../../accounts.rst:275
+#: ../../accounts.rst:273
 #: ../../accounts.rst:331
-# ddf11f35901948058a34dff9cbca8c3d
-# 6d6eab10b7674a65aedf6c1f41312bf8
+# a1fbaf989c584a248386911c51fd2fba
+# c776e850eb3e4d64b262a32a9d302bfb
 msgid "Active Directory"
 msgstr ""
 
-#: ../../accounts.rst:275
-# 0fdc037b3c2746e0b455bd0594bf0bee
+#: ../../accounts.rst:273
+# 5d0095ff2d7044e7b60bc1754210dd3c
 msgid "OU=testing, DC=company"
 msgstr ""
 
-#: ../../accounts.rst:279
-# 03d46aff89114039bebeeea32fbcda86
+#: ../../accounts.rst:278
+# 8309dae488944f0aae3e84a8e1a97ac3
 msgid "Query Filter"
 msgstr ""
 
-#: ../../accounts.rst:281
-# 93b867a441bc4cddad5a72d6b9e51abf
+#: ../../accounts.rst:280
+# c523dbbf5dd94c62a2e3927a8f3123dc
 msgid "The query filter is used to find a mapped user in the external LDAP server. The query filter should uniquely map the CloudStack user to LDAP user for a meaningful authentication. For more information about query filter syntax, consult the documentation for your LDAP server."
 msgstr ""
 
-#: ../../accounts.rst:286
-# 94920970089b494395b1e5410ad30bb1
+#: ../../accounts.rst:285
+# f4f9c13ceefa4163962bd3cfab257852
 msgid "The CloudStack query filter wildcards are:"
 msgstr ""
 
-#: ../../accounts.rst:289
-# f7c82cdd777a4284b5adc6a920065f32
+#: ../../accounts.rst:288
+# bab683973b9045339c8df3488bc5dd1c
 msgid "Query Filter Wildcard"
 msgstr ""
 
-#: ../../accounts.rst:289
-# 2e1c45a30d2648c6878074583a6a4c7b
+#: ../../accounts.rst:288
+# a94af335cc864d9a962f1fb9b7b5f72c
 msgid "Description"
 msgstr ""
 
-#: ../../accounts.rst:291
-# b636b6a26b4942d390e3083bb99636ec
+#: ../../accounts.rst:290
+# 334393ba6786415e91a2ed1a22d26adb
 msgid "%u"
 msgstr ""
 
-#: ../../accounts.rst:291
-# b85fa10a6f7c473f9579fbee87abc7dc
+#: ../../accounts.rst:290
+# 151cd28e952d4ff98ff9d1544698ccb8
 msgid "User name"
 msgstr ""
 
-#: ../../accounts.rst:292
-# aaca04ef47ce4a6d957d7f999021beec
+#: ../../accounts.rst:291
+# f1f86cbcf39e412fb298da7653a123d3
 msgid "%e"
 msgstr ""
 
-#: ../../accounts.rst:292
-# 04104fb07bb94de38b10667d6fdadf04
+#: ../../accounts.rst:291
+# fdf52531788c41fabb814f45f07b178a
 msgid "Email address"
 msgstr ""
 
-#: ../../accounts.rst:293
-# ae0690d61f774148a22980a6ed2d4c98
+#: ../../accounts.rst:292
+# 6e5b529e3da248ee85f1e20f81bd8e1c
 msgid "%n"
 msgstr ""
 
-#: ../../accounts.rst:293
-# 5c8df2d1e58b4c88b7f6f76691f54e32
+#: ../../accounts.rst:292
+# 4704eb3b3e494ad3bc2105d98a3c84a9
 msgid "First and last name"
 msgstr ""
 
-#: ../../accounts.rst:296
-# fb24e5d77b0b4a369c988a18859c27b5
+#: ../../accounts.rst:295
+# 51612c6475e246f7b7d8a156605a2323
 msgid "The following examples assume you are using Active Directory, and refer to user attributes from the Active Directory schema."
 msgstr ""
 
-#: ../../accounts.rst:299
-# 53d9ff57793f490ea016d5c0dd2235e1
+#: ../../accounts.rst:298
+# d853815e3f894dcdbb92be883305dc5b
 msgid "If the CloudStack user name is the same as the LDAP user ID:"
 msgstr ""
 
-#: ../../accounts.rst:305
-# fe9b3901fa4c442dbba0966d900dc335
+#: ../../accounts.rst:304
+# d0bb623240d0410eb8d70ed22ba5a2f8
 msgid "If the CloudStack user name is the LDAP display name:"
 msgstr ""
 
-#: ../../accounts.rst:311
-# 67bfee8945324987bfa2debd1cbd0f29
+#: ../../accounts.rst:310
+# 0a96c3c2516946c1b4260fd4d4d6ffb7
 msgid "To find a user by email address:"
 msgstr ""
 
 #: ../../accounts.rst:318
-# 0a2a4f3d28a447ccafdcade93acec26e
+# 5b63c901fb5a4d208df8e362234d1cba
 msgid "Search User Bind DN"
 msgstr ""
 
 #: ../../accounts.rst:320
-# 9d07ca9ffe4d45e1a14848570aad2f64
+# 92769f4cb5be444cab0bcb685ebe1cc4
 msgid "The bind DN is the user on the external LDAP server permitted to search the LDAP directory within the defined search base. When the DN is returned, the DN and passed password are used to authenticate the CloudStack user with an LDAP bind. A full discussion of bind DNs is outside the scope of our documentation. The following table shows some examples of bind DNs."
 msgstr ""
 
 #: ../../accounts.rst:328
-# 3b0b6b5b036945e6bb5442cb94a46fcd
+# 7fcc45a0be9241b09a01d2287541d652
 msgid "Example Bind DN"
 msgstr ""
 
 #: ../../accounts.rst:330
-# 1cd4f20b644c4fd68eb8a37ef35f7b47
+# b4c0b2f84be54e32820cac392b6c9c75
 msgid "CN=Administrator,DC=testing,OU=project,OU=org"
 msgstr ""
 
 #: ../../accounts.rst:331
-# 2e60a99cfddd494c9de480a48304dfe3
+# 46e145ddbc9f47e08b21fa2631ed9fa7
 msgid "CN=Administrator, OU=testing, DC=company, DC=com"
 msgstr ""
 
 #: ../../accounts.rst:336
-# 16cd1707b0594271ae8a6ae3884ec80e
+# cbaaf7054abf480eb88b336ba62a097b
 msgid "SSL Keystore Path and Password"
 msgstr ""
 
 #: ../../accounts.rst:338
-# 074f3d04369241be9e56096bb7dded79
+# 8a6a84c57cc144edb9a20e63c71ddedc
 msgid "If the LDAP server requires SSL, you need to enable it in the ldapConfig command by setting the parameters ssl, truststore, and truststorepass. Before enabling SSL for ldapConfig, you need to get the certificate which the LDAP server is using and add it to a trusted keystore. You will need to know the path to the keystore and the password."
 msgstr ""
 
diff --git a/source/locale/pot/administration.pot b/source/locale/pot/administration.pot
index a70fd94..4c7627a 100644
--- a/source/locale/pot/administration.pot
+++ b/source/locale/pot/administration.pot
@@ -8,7 +8,7 @@
 msgstr ""
 "Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2014-03-31 14:08-0400\n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -16,48 +16,48 @@
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 
-#: ../../administration.rst:19
-# 5782522e7a564a9caa1ecc02e0977696
+#: ../../administration.rst:18
+# 29cfff43a2514946ad4c3499ebefbed6
 msgid "User Services"
 msgstr ""
 
-#: ../../administration.rst:21
-# 06114f8c3f954e45b8add1ef10ed3f6e
+#: ../../administration.rst:20
+# d7001feee3bd4b298a4c17869c0c45dc
 msgid "In addition to the physical and logical infrastructure of your cloud and the CloudStack software and servers, you also need a layer of user services so that people can actually make use of the cloud. This means not just a user UI, but a set of options and resources that users can choose from, such as templates for creating virtual machines, disk storage, and more. If you are running a commercial service, you will be keeping track of what services and resources users are consuming and charging them for that usage. Even if you do not charge anything for people to use your cloud – say, if the users are strictly internal to your organization, or just friends who are sharing your cloud – you can still keep track of what services they use and how much of them."
 msgstr ""
 
 #: ../../administration.rst:34
-# 08b7862dbeb64d2d8c3e46cacc0a995d
+# 8691c3078d2741dabb85f469a7b58373
 msgid "Service Offerings, Disk Offerings, Network Offerings, and Templates"
 msgstr ""
 
 #: ../../administration.rst:36
-# f761dfbfdddc4df58bc4fb22ad4c4ada
+# 82a1a03c5a234653b024700134d18169
 msgid "A user creating a new instance can make a variety of choices about its characteristics and capabilities. CloudStack provides several ways to present users with choices when creating a new instance:"
 msgstr ""
 
-#: ../../administration.rst:42
-# 46491c0220454387a6a1eaf3e9c62f68
+#: ../../administration.rst:40
+# 5b79acf1c4034cf09e56634938cbfd33
 msgid "Service Offerings, defined by the CloudStack administrator, provide a choice of CPU speed, number of CPUs, RAM size, tags on the root disk, and other choices. See Creating a New Compute Offering."
 msgstr ""
 
-#: ../../administration.rst:48
-# 2739214a038842799d6315fc83f2d7b9
+#: ../../administration.rst:44
+# d71f7d3d0dda4061838347d6fc7e35fc
 msgid "Disk Offerings, defined by the CloudStack administrator, provide a choice of disk size and IOPS (Quality of Service) for primary data storage. See Creating a New Disk Offering."
 msgstr ""
 
-#: ../../administration.rst:54
-# 7b90ec0921524642a75fc2610c86c276
+#: ../../administration.rst:48
+# c00720676a8a4c4a9d423dd5f5743f4c
 msgid "Network Offerings, defined by the CloudStack administrator, describe the feature set that is available to end users from the virtual router or external networking devices on a given guest network. See Network Offerings."
 msgstr ""
 
-#: ../../administration.rst:61
-# b5a2bc83e71142d2b6133c4d6266cab9
+#: ../../administration.rst:53
+# 169ad751a60e44929103a91c102ac2a2
 msgid "Templates, defined by the CloudStack administrator or by any CloudStack user, are the base OS images that the user can choose from when creating a new instance. For example, CloudStack includes CentOS as a template. See Working with Templates."
 msgstr ""
 
-#: ../../administration.rst:66
-# 2e2f04a2e3e449698ca4be2d9d1215fb
+#: ../../administration.rst:58
+# 81b027ebc2094409b6f28288660792c7
 msgid "In addition to these choices that are provided for users, there is another type of service offering which is available only to the CloudStack root administrator, and is used for configuring virtual infrastructure resources. For more information, see Upgrading a Virtual Router with System Service Offerings."
 msgstr ""
 
diff --git a/source/locale/pot/api.pot b/source/locale/pot/api.pot
index efa4adf..70a1475 100644
--- a/source/locale/pot/api.pot
+++ b/source/locale/pot/api.pot
@@ -8,7 +8,7 @@
 msgstr ""
 "Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2014-03-31 14:08-0400\n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -17,107 +17,107 @@
 "Content-Transfer-Encoding: 8bit\n"
 
 #: ../../api.rst:18
-# c9f373cc299e447998a4b0c51d6b30e1
+# 7499b008b97e41b59d4cdc3835758f36
 msgid "CloudStack API"
 msgstr ""
 
 #: ../../api.rst:20
-# 4f31f79497784c4eb83f19285c8fc8d4
+# 7a40beffc6484f108ad5202cb2a4e7c3
 msgid "The CloudStack API is a low level API that has been used to implement the CloudStack web UIs. It is also a good basis for implementing other popular APIs such as EC2/S3 and emerging DMTF standards."
 msgstr ""
 
 #: ../../api.rst:24
-# 0484938f098f467e94ea20aa2d3de1f0
+# 0e4247f81b8a4a83afa84f323d2697b9
 msgid "Many CloudStack API calls are asynchronous. These will return a Job ID immediately when called. This Job ID can be used to query the status of the job later. Also, status calls on impacted resources will provide some indication of their state."
 msgstr ""
 
 #: ../../api.rst:29
-# 59bb256e7c6841a89ab8fd907a34f08a
+# dc0b3fef72b74085a24d7e0c15cb227d
 msgid "The API has a REST-like query basis and returns results in XML or JSON."
 msgstr ""
 
 #: ../../api.rst:31
-# 3f40f7f90a3b4dd2a8b4ddbb30340800
+# 1f57015e966c480795b141ba3f87b86a
 msgid "See `the Developer’s Guide <https://cwiki.apache.org/confluence/display/CLOUDSTACK/Development+101>`_ and `the API Reference <http://cloudstack.apache.org/docs/api/>`_."
 msgstr ""
 
-#: ../../api.rst:35
-# 850a1709dc05430b81c947813bf2c387
+#: ../../api.rst:36
+# de3d35bb699f45f495251ceb69a2c238
 msgid "Provisioning and Authentication API"
 msgstr ""
 
-#: ../../api.rst:37
-# 4b899aee7aa147bbb8cbe8cc3fdd3436
+#: ../../api.rst:38
+# c8eb593d2c654d8db8d5ce7791bedd07
 msgid "CloudStack expects that a customer will have their own user provisioning infrastructure. It provides APIs to integrate with these existing systems where the systems call out to CloudStack to add/remove users.."
 msgstr ""
 
-#: ../../api.rst:41
-# d1809ac4f63b4171bd2bf7449f9af520
+#: ../../api.rst:42
+# f37cbbabb4af4c76977b51277f5cefa3
 msgid "CloudStack supports pluggable authenticators. By default, CloudStack assumes it is provisioned with the user’s password, and as a result authentication is done locally. However, external authentication is possible as well. For example, see Using an LDAP Server for User Authentication."
 msgstr ""
 
-#: ../../api.rst:48
-# e0f1a61ca7404d2fbe4cfa7a466e23a6
+#: ../../api.rst:50
+# a1cd31f63e9a4fe6869e80cdd8f2274f
 msgid "User Data and Meta Data"
 msgstr ""
 
-#: ../../api.rst:50
-# 4921f2bf02984bc0a308cc391af4cabf
+#: ../../api.rst:52
+# 8adea5c3508040cfb6f8475bc1f2f96c
 msgid "CloudStack provides API access to attach up to 32KB of user data to a deployed VM. Deployed VMs also have access to instance metadata via the virtual router."
 msgstr ""
 
-#: ../../api.rst:54
-# 076533995e0345db90168c6278c3460b
+#: ../../api.rst:56
+# 11a9a59d3f23401d8c639b7767af0a94
 msgid "User data can be accessed once the IP address of the virtual router is known. Once the IP address is known, use the following steps to access the user data:"
 msgstr ""
 
-#: ../../api.rst:58
-# cf43f38848f845f4a34393092ae8b81e
+#: ../../api.rst:60
+# 0b14bfd2cf6c41a98f39a406fdb83868
 msgid "Run the following command to find the virtual router."
 msgstr ""
 
-#: ../../api.rst:64
-# 6fff13e87cff49809caebf13b8fa61cb
+#: ../../api.rst:66
+# e0144a29051543d1aba1d5b18d18e033
 msgid "Access user data by running the following command using the result of the above command"
 msgstr ""
 
-#: ../../api.rst:71
-# cd37cb5d158343c29780503c5bca4540
+#: ../../api.rst:73
+# 8ebc1946ef8840c4b4c99d6194576997
 msgid "Meta Data can be accessed similarly, using a URL of the form http://10.1.1.1/latest/meta-data/{metadata type}. (For backwards compatibility, the previous URL http://10.1.1.1/latest/{metadata type} is also supported.) For metadata type, use one of the following:"
 msgstr ""
 
 #: ../../api.rst:78
-# e84e13e6d81f41fda2e53325bcf8196b
+# bed0120874a643b1b9d59bd6a4e9e404
 msgid "service-offering. A description of the VMs service offering"
 msgstr ""
 
-#: ../../api.rst:82
-# 62048249f8d2494db34980c3b1862e5b
+#: ../../api.rst:80
+# 71b8d766955140c3b512c2a9318fa115
 msgid "availability-zone. The Zone name"
 msgstr ""
 
-#: ../../api.rst:86
-# 7463be88f12e49e8aac8925ca6a5884f
+#: ../../api.rst:82
+# 2a80730691bb49e0b69de28d14feea03
 msgid "local-ipv4. The guest IP of the VM"
 msgstr ""
 
-#: ../../api.rst:90
-# ba16b21040764726a1202dde1d4e83d6
+#: ../../api.rst:84
+# 6f5c73e35f714f0f83b7c799a46c499f
 msgid "local-hostname. The hostname of the VM"
 msgstr ""
 
-#: ../../api.rst:94
-# 363adc60e20b4bfcb51004281919f11e
+#: ../../api.rst:86
+# ad4c5b53b2844aa9b7518ea0165e3c5a
 msgid "public-ipv4. The first public IP for the router. (E.g. the first IP of eth2)"
 msgstr ""
 
-#: ../../api.rst:99
-# 352781028d6f46f1b95f08adccbb1ff2
+#: ../../api.rst:89
+# 53db659838e1499c86e3674db658bbdb
 msgid "public-hostname. This is the same as public-ipv4"
 msgstr ""
 
-#: ../../api.rst:103
-# dc787ff8567442788d44cf46ab9a6462
+#: ../../api.rst:91
+# 760946f739514ea5be9f4c114716b1ba
 msgid "instance-id. The instance name of the VM"
 msgstr ""
 
diff --git a/source/locale/pot/events.pot b/source/locale/pot/events.pot
index 57799bc..0fe5136 100644
--- a/source/locale/pot/events.pot
+++ b/source/locale/pot/events.pot
@@ -8,7 +8,7 @@
 msgstr ""
 "Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2014-03-31 14:08-0400\n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -17,316 +17,316 @@
 "Content-Transfer-Encoding: 8bit\n"
 
 #: ../../events.rst:18
-# 102ed2ffb3fb4c3bb6029d0c7eb905de
+# 0defb3a9608c4824b34ed35d916fd0c4
 msgid "Event Notification"
 msgstr ""
 
 #: ../../events.rst:20
-# afc241a8b0d0496a8744768e3563fbe8
+# 37ebc4e9b0b148daaab42c65d71cc834
 msgid "An event is essentially a significant or meaningful change in the state of both virtual and physical resources associated with a cloud environment. Events are used by monitoring systems, usage and billing systems, or any other event-driven workflow systems to discern a pattern and make the right business decision. In CloudStack an event could be a state change of virtual or physical resources, an action performed by an user (action events), or policy based events (alerts)."
 msgstr ""
 
-#: ../../events.rst:29
-# 0fca00203fea49669148771eeedf55c3
+#: ../../events.rst:30
+# 82bc7c30085140f89344da554ad386a3
 msgid "Event Logs"
 msgstr ""
 
-#: ../../events.rst:31
-# 1d21fa8ae81748baa8e52f31043facf7
+#: ../../events.rst:32
+# c1d54e6d1a2d4cd6888ad99bf943ed83
 msgid "There are two types of events logged in the CloudStack Event Log. Standard events log the success or failure of an event and can be used to identify jobs or processes that have failed. There are also long running job events. Events for asynchronous jobs log when a job is scheduled, when it starts, and when it completes. Other long running synchronous jobs log when a job starts, and when it completes. Long running synchronous and asynchronous event logs can be used to gain more information on the status of a pending job or can be used to identify a job that is hanging or has not started. The following sections provide more information on these events.."
 msgstr ""
 
-#: ../../events.rst:43
-# 8a0c6176934d4aec840789a07a73084b
+#: ../../events.rst:45
+# 127295678f0c4cf084cf737444f11087
 msgid "Notification"
 msgstr ""
 
-#: ../../events.rst:45
-# 64816315eaa145ab8ad138648b2589e3
+#: ../../events.rst:47
+# a669e3079b7e41d1a82dd149bf00b011
 msgid "Event notification framework provides a means for the Management Server components to publish and subscribe to CloudStack events. Event notification is achieved by implementing the concept of event bus abstraction in the Management Server. An event bus is introduced in the Management Server that allows the CloudStack components and extension plug-ins to subscribe to the events by using the Advanced Message Queuing Protocol (AMQP) client. In CloudStack, a default implementation of event bus is provided as a plug-in that uses the RabbitMQ AMQP client. The AMQP client pushes the published events to a compatible AMQP server. Therefore all the CloudStack events are published to an exchange in the AMQP server."
 msgstr ""
 
-#: ../../events.rst:57
-# 69559e28bd3c4833a65e235470bd7ae9
+#: ../../events.rst:59
+# e41f3e4f6450467da27fc6dc4ebb2788
 msgid "A new event for state change, resource state change, is introduced as part of Event notification framework. Every resource, such as user VM, volume, NIC, network, public IP, snapshot, and template, is associated with a state machine and generates events as part of the state change. That implies that a change in the state of a resource results in a state change event, and the event is published in the corresponding state machine on the event bus. All the CloudStack events (alerts, action events, usage events) and the additional category of resource state change events, are published on to the events bus."
 msgstr ""
 
-#: ../../events.rst:68
-# c7c4a9021bb94d0d8c8806bdc797abc7
+#: ../../events.rst:71
+# 4aaf02080d184ab387923b45f39d5762
 msgid "Use Cases"
 msgstr ""
 
-#: ../../events.rst:70
-# 2b32e72970d74bd3b50d67a5c2b25913
+#: ../../events.rst:73
+# f7b5a1de0f014d2eabfe925d0c5c4e95
 msgid "The following are some of the use cases:"
 msgstr ""
 
-#: ../../events.rst:74
-# 785e64cd20c945e39b1fcd1248e29463
+#: ../../events.rst:75
+# 9be82bc2fe244fef9851d9adb481fdaf
 msgid "Usage or Billing Engines: A third-party cloud usage solution can implement a plug-in that can connects to CloudStack to subscribe to CloudStack events and generate usage data. The usage data is consumed by their usage software."
 msgstr ""
 
-#: ../../events.rst:81
-# 697fd51abda3475fbec2bfb2cf48eeee
+#: ../../events.rst:80
+# 2585685666874f3f8795c70fe2671356
 msgid "AMQP plug-in can place all the events on the a message queue, then a AMQP message broker can provide topic-based notification to the subscribers."
 msgstr ""
 
-#: ../../events.rst:87
-# 13d4c3bf275446aca6afcc5f13b12aa3
+#: ../../events.rst:84
+# ff10e0227bc04e2f86f15c3c534b7c47
 msgid "Publish and Subscribe notification service can be implemented as a pluggable service in CloudStack that can provide rich set of APIs for event notification, such as topics-based subscription and notification. Additionally, the pluggable service can deal with multi-tenancy, authentication, and authorization issues."
 msgstr ""
 
-#: ../../events.rst:94
-# 1aedf09c5c0b4effa9dd9117fcf5a102
+#: ../../events.rst:92
+# bdc9ac2f935c456fbd3778ddef6c91cf
 msgid "Configuration"
 msgstr ""
 
-#: ../../events.rst:96
-# 1520275479c3459fb8bb45890eae9935
+#: ../../events.rst:94
+# c2514aa04f964044bd2bd630f31b4d3f
 msgid "As a CloudStack administrator, perform the following one-time configuration to enable event notification framework. At run time no changes can control the behaviour."
 msgstr ""
 
-#: ../../events.rst:102
-# e80abe3d28594327a0464339d8818c44
+#: ../../events.rst:98
+# e94d4200515d4f15adbc52ca3bbf8c54
 msgid "Open ``'componentContext.xml``."
 msgstr ""
 
-#: ../../events.rst:106
-# 9df0be28f95041d19f82142547b7265b
+#: ../../events.rst:100
+# e2bbf37abe854d6cb8384bdd3c9d72b9
 msgid "Define a bean named ``eventNotificationBus`` as follows:"
 msgstr ""
 
-#: ../../events.rst:110
-# e46a3a197cc74df2a9eb8e5bd57ebf52
+#: ../../events.rst:102
+# 47bce54d52714df7bafac2b6d04dd816
 msgid "name : Specify a name for the bean."
 msgstr ""
 
-#: ../../events.rst:114
-# b203c95bc9f44afc81fbb8980802291e
+#: ../../events.rst:104
+# 4317cb3aa0fd4c7fa3f0e637f6cfea48
 msgid "server : The name or the IP address of the RabbitMQ AMQP server."
 msgstr ""
 
-#: ../../events.rst:118
-# 6e8c151c2dd847f1a2a160d97c119e86
+#: ../../events.rst:106
+# 0f6561172d38446db99181316f50e667
 msgid "port : The port on which RabbitMQ server is running."
 msgstr ""
 
-#: ../../events.rst:122
-# 42911e580f7a4f6fa5b5be87551390cb
+#: ../../events.rst:108
+# 7ff0aa3ff7af48fbbf4651a2d8e5f34d
 msgid "username : The username associated with the account to access the RabbitMQ server."
 msgstr ""
 
-#: ../../events.rst:127
-# 887fd9bc57b548f382e1c635c3dbb8a0
+#: ../../events.rst:111
+# 7193c434eaab44eda2d7d9b2b86c675d
 msgid "password : The password associated with the username of the account to access the RabbitMQ server."
 msgstr ""
 
-#: ../../events.rst:132
-# 4c518b7b80a941638553284affb8603e
+#: ../../events.rst:114
+# f765ea7d69504610a98a95fdb802fe32
 msgid "exchange : The exchange name on the RabbitMQ server where CloudStack events are published."
 msgstr ""
 
-#: ../../events.rst:135
-# f881113c3c1540c9a568b4bb01f37ff2
+#: ../../events.rst:117
+# 7ba933b1d4ec41c1a20f2cdca4275405
 msgid "A sample bean is given below:"
 msgstr ""
 
-#: ../../events.rst:148
-# c88f66382e86471fa752a96e8c286e51
+#: ../../events.rst:130
+# 07a04a0f79804e938092a93f3180770a
 msgid "The ``eventNotificationBus`` bean represents the ``org.apache.cloudstack.mom.rabbitmq.RabbitMQEventBus`` class."
 msgstr ""
 
-#: ../../events.rst:153
-# 3c84696f04ae4ad58c0edfe8eee24a49
+#: ../../events.rst:133
+# 83cdf82ae8c34a238d181c5bbaef30dd
 msgid "Restart the Management Server."
 msgstr ""
 
-#: ../../events.rst:156
-# 34f2df7b30c8489690de80ca02292b43
+#: ../../events.rst:137
+# 573b41c4def247f6981e828da7f54f82
 msgid "Standard Events"
 msgstr ""
 
-#: ../../events.rst:158
-#: ../../events.rst:191
-# 658ab70617ca480387c4446d2df3f783
-# e43e53282a8743bc94e7a3f26dacfeed
+#: ../../events.rst:139
+#: ../../events.rst:161
+# f503981d0a764de49d4acc01c70d6126
+# 9212f9cd71b542899ac8256d4a51026d
 msgid "The events log records three types of standard events."
 msgstr ""
 
-#: ../../events.rst:162
-#: ../../events.rst:195
-# 9400dae867ab48dfb95e9a05e8949fdb
-# cb299fcbd64849a7a47486675d1f6477
+#: ../../events.rst:141
+#: ../../events.rst:163
+# fab87560ba674752808dacaf3abfc44a
+# 94b40a1c0c98456399293f6a38102385
 msgid "INFO. This event is generated when an operation has been successfully performed."
 msgstr ""
 
-#: ../../events.rst:167
-#: ../../events.rst:200
-# 294607854e004c4fa685bb9760e11d2f
-# 26f912bd36f4415c9f6349109dbc880a
+#: ../../events.rst:144
+#: ../../events.rst:166
+# 49450fc963104f569e80611ac7179829
+# 13438410decf4526b0381dc44062ba76
 msgid "WARN. This event is generated in the following circumstances."
 msgstr ""
 
-#: ../../events.rst:171
-#: ../../events.rst:204
-# 8f26ab07f1da41c5a67f35568dee82ae
-# a962175d5c794f9e88b25a995aa3fe1a
+#: ../../events.rst:146
+#: ../../events.rst:168
+# c6197efc809f4a67baf05aa139cb10f5
+# a16599807269441f8f1799ae29968e11
 msgid "When a network is disconnected while monitoring a template download."
 msgstr ""
 
-#: ../../events.rst:176
-#: ../../events.rst:209
-# 41d6341dfbc74296aebd0eff9602f59a
-# 9bdea7d661d140718fea5fda4ae30615
+#: ../../events.rst:149
+#: ../../events.rst:171
+# 0e060afef9e84640b3c2da38436691e2
+# 019e604962174d4492cca7be02ad2647
 msgid "When a template download is abandoned."
 msgstr ""
 
-#: ../../events.rst:180
-#: ../../events.rst:213
-# d2d6ebc19c2f42138e8698f89ee29c6f
-# 93031d47c5704fb383a9e8149b602855
+#: ../../events.rst:151
+#: ../../events.rst:173
+# 8b3eabd5fcc0406bb83abe3863261df9
+# 19ccb6eebbc1446a8cb47056d2ad0274
 msgid "When an issue on the storage server causes the volumes to fail over to the mirror storage server."
 msgstr ""
 
-#: ../../events.rst:185
-#: ../../events.rst:218
-# 583a50a8c403401093490e43cbd95dfd
-# 52ea4911fdfe42a5af3cc9a97e48a987
+#: ../../events.rst:154
+#: ../../events.rst:176
+# 96793fba6d294c98bd8dcde72d0d9f49
+# 0b487b0c814145438366a847c93c52d8
 msgid "ERROR. This event is generated when an operation has not been successfully performed"
 msgstr ""
 
-#: ../../events.rst:189
-# 5b8500630feb40f4afb3b8f9e29a53a3
+#: ../../events.rst:159
+# b1c1824ddd304288bd0803e80d482bb9
 msgid "Long Running Job Events"
 msgstr ""
 
-#: ../../events.rst:222
-# c379b57670384b0b9da909afafca7292
+#: ../../events.rst:181
+# ffb5ee0896674a62a567e634fc725510
 msgid "Event Log Queries"
 msgstr ""
 
-#: ../../events.rst:224
-# 88a9f85fb3da4603bee07701eabb7806
+#: ../../events.rst:183
+# 0c75a642e72943e0bb28642902590c9b
 msgid "Database logs can be queried from the user interface. The list of events captured by the system includes:"
 msgstr ""
 
-#: ../../events.rst:229
-# cd15e4ae2eca4d55b7510293e7fd2bbd
+#: ../../events.rst:186
+# fe735d1b0444472aa47e381cd00eec61
 msgid "Virtual machine creation, deletion, and on-going management operations"
 msgstr ""
 
-#: ../../events.rst:234
-# 2df022a424dc41b699e1367171be2d50
+#: ../../events.rst:189
+# e331126149b64023bf0e7655bbcb2991
 msgid "Virtual router creation, deletion, and on-going management operations"
 msgstr ""
 
-#: ../../events.rst:238
-# d36f900c99fb40fa94804d5e52af7822
+#: ../../events.rst:191
+# 33b99484fca246c48ceff95aac8b52d2
 msgid "Template creation and deletion"
 msgstr ""
 
-#: ../../events.rst:242
-# 2e97521ac7be4b15b4892a30073bc966
+#: ../../events.rst:193
+# 7969071933104816945f05e9f3a597e3
 msgid "Network/load balancer rules creation and deletion"
 msgstr ""
 
-#: ../../events.rst:246
-# f59bcdcfa249464a800cad1cd97cfc0f
+#: ../../events.rst:195
+# 91ecfa5192134ffeafe5043cff29432a
 msgid "Storage volume creation and deletion"
 msgstr ""
 
-#: ../../events.rst:250
-# 8bd53c90bb38449fbbadd472c0930466
+#: ../../events.rst:197
+# b0c0672f35af4003870943a16b461337
 msgid "User login and logout"
 msgstr ""
 
-#: ../../events.rst:253
-# 1e928be3f4e54e8f8b6532879b4e5f7e
+#: ../../events.rst:201
+# 57cfb09e85c842b581f3a0f38609a9c4
 msgid "Deleting and Archiving Events and Alerts"
 msgstr ""
 
-#: ../../events.rst:255
-# 13275df9c48f45ccba383ca172df3874
+#: ../../events.rst:203
+# b4160055fbd946979df299cf40a75777
 msgid "CloudStack provides you the ability to delete or archive the existing alerts and events that you no longer want to implement. You can regularly delete or archive any alerts or events that you cannot, or do not want to resolve from the database."
 msgstr ""
 
-#: ../../events.rst:260
-# 1371e435af2d4271b9db506b9e5c40aa
+#: ../../events.rst:208
+# 7bdab572982c4739808182e94b589c7e
 msgid "You can delete or archive individual alerts or events either directly by using the Quickview or by using the Details page. If you want to delete multiple alerts or events at the same time, you can use the respective context menu. You can delete alerts or events by category for a time period. For example, you can select categories such as **USER.LOGOUT**, **VM.DESTROY**, **VM.AG.UPDATE**, **CONFIGURATION.VALUE.EDI**, and so on. You can also view the number of events or alerts archived or deleted."
 msgstr ""
 
-#: ../../events.rst:269
-# c8695ccfaf37456c9fe6e0ec4d207a62
+#: ../../events.rst:217
+# cf46cdd4536a4a93912df2f4e88af8a1
 msgid "In order to support the delete or archive alerts, the following global parameters have been added:"
 msgstr ""
 
-#: ../../events.rst:274
-# d437d10a6c5c4d4fac98d68635980067
+#: ../../events.rst:220
+# 19ff2e090cf24d30aeacde33ec972af1
 msgid "**alert.purge.delay**: The alerts older than specified number of days are purged. Set the value to 0 to never purge alerts automatically."
 msgstr ""
 
-#: ../../events.rst:279
-# 368c17d62d6043429befbae6871a04c0
+#: ../../events.rst:223
+# e3ccfdc51da14488bc9e44623c64d707
 msgid "**alert.purge.interval**: The interval in seconds to wait before running the alert purge thread. The default is 86400 seconds (one day)."
 msgstr ""
 
-#: ../../events.rst:283
-# 57dd9b95bbcf4bfd87ebf5cbaef78931
+#: ../../events.rst:228
+# a6eda71ad15940c2b58724ff74f97e26
 msgid "Archived alerts or events cannot be viewed in the UI or by using the API. They are maintained in the database for auditing or compliance purposes."
 msgstr ""
 
-#: ../../events.rst:288
-# ec3e8f0b43514403afc0a9e47f381c0c
+#: ../../events.rst:234
+# 7c40293965f24130896768ea8223a152
 msgid "Permissions"
 msgstr ""
 
-#: ../../events.rst:290
-# 7db5396af5d24382a51e418ced931fff
+#: ../../events.rst:236
+# e43e679e6a304ae1b78e11f56bed12b2
 msgid "Consider the following:"
 msgstr ""
 
-#: ../../events.rst:294
-# 2814ee39c91e4c2e832d73a1a39839b5
+#: ../../events.rst:238
+# c5bd820d9a5e487b9440609da1e22551
 msgid "The root admin can delete or archive one or multiple alerts or events."
 msgstr ""
 
-#: ../../events.rst:299
-# 01be1c88e97f4e9eae1e310e28045ae2
+#: ../../events.rst:241
+# 51b4fa6e53064c7088052c69d7a1b4fe
 msgid "The domain admin or end user can delete or archive one or multiple events."
 msgstr ""
 
-#: ../../events.rst:303
-# 8d806f13fadd4080bae10069ad330bbc
+#: ../../events.rst:246
+# bea2b3dcb4bb41468a31793133ffeb06
 msgid "Procedure"
 msgstr ""
 
-#: ../../events.rst:307
-# 0670181e1983452ab571f7ae6ce4d594
+#: ../../events.rst:248
+# aa16543921984837a7f59142ad2df67d
 msgid "Log in as administrator to the CloudStack UI."
 msgstr ""
 
-#: ../../events.rst:311
-# 3ab15d176fec4a14a47ed28c4e81a0bc
+#: ../../events.rst:250
+# f8b2ec5bdbf749d2bf704ff20c063c89
 msgid "In the left navigation, click Events."
 msgstr ""
 
-#: ../../events.rst:315
-# 3dfc816afe4744f1a2b5aa030c3be966
+#: ../../events.rst:252
+# 5519a86ae5b04a68b972ee88e37deffe
 msgid "Perform either of the following:"
 msgstr ""
 
-#: ../../events.rst:319
-# 3308c260b9c8454bb6109c2b36420617
+#: ../../events.rst:254
+# fd1193e3ff83466aa226d4834dea269d
 msgid "To archive events, click Archive Events, and specify event type and date."
 msgstr ""
 
-#: ../../events.rst:324
-# 3563bec70a3f40aa9bfd26494bda8c93
+#: ../../events.rst:257
+# abfda9e22c7f42f3a4ff488ff755e59e
 msgid "To archive events, click Delete Events, and specify event type and date."
 msgstr ""
 
-#: ../../events.rst:329
-# f0ab5197a41b478684c629f86f95fc12
+#: ../../events.rst:260
+# 58b630d17160410ab6757d134aa17a62
 msgid "Click OK."
 msgstr ""
 
diff --git a/source/locale/pot/hosts.pot b/source/locale/pot/hosts.pot
index da72b99..6314be5 100644
--- a/source/locale/pot/hosts.pot
+++ b/source/locale/pot/hosts.pot
@@ -8,7 +8,7 @@
 msgstr ""
 "Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2014-03-31 14:08-0400\n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -17,812 +17,812 @@
 "Content-Transfer-Encoding: 8bit\n"
 
 #: ../../hosts.rst:18
-# 592d97db5d074967b8037886828bbbf7
+# d162d1d06fd7403885aaa50b51be64cf
 msgid "Working with Hosts"
 msgstr ""
 
 #: ../../hosts.rst:21
-# eb6157eff5a24266a1934dce1cc5c38e
+# 6c9e070451664a89a2bab7d9dcb4892e
 msgid "Adding Hosts"
 msgstr ""
 
 #: ../../hosts.rst:23
-# 8278623233e349e2bbe063bea7e23268
+# 0fea464db7a843f6930b135daf0f6eef
 msgid "Additional hosts can be added at any time to provide more capacity for guest VMs. For requirements and instructions, see `“Adding a Host” <http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/latest/configuration.html#adding-a-host>`_."
 msgstr ""
 
-#: ../../hosts.rst:28
-# d13936e89f4e4d9ea480d52a5c693cab
+#: ../../hosts.rst:29
+# 8d309023c45240b78a9ddce49978e18c
 msgid "Scheduled Maintenance and Maintenance Mode for Hosts"
 msgstr ""
 
-#: ../../hosts.rst:30
-# c80faa4e959d4bf6a547b8898e582f71
+#: ../../hosts.rst:31
+# 7a2b019ac10a47c39de133fdc1a06f3d
 msgid "You can place a host into maintenance mode. When maintenance mode is activated, the host becomes unavailable to receive new guest VMs, and the guest VMs already running on the host are seamlessly migrated to another host not in maintenance mode. This migration uses live migration technology and does not interrupt the execution of the guest."
 msgstr ""
 
-#: ../../hosts.rst:37
-# 050155d6fe2d4fe9bfb03ae737991f51
+#: ../../hosts.rst:39
+# af2fbe9bb8ff4ab29c19fbb7dc7d6a2b
 msgid "vCenter and Maintenance Mode"
 msgstr ""
 
-#: ../../hosts.rst:39
-# 6e6dd514ac534a609dbba7282dd7d14e
+#: ../../hosts.rst:41
+# d2d9b481634d47499c874f1781439746
 msgid "To enter maintenance mode on a vCenter host, both vCenter and CloudStack must be used in concert. CloudStack and vCenter have separate maintenance modes that work closely together."
 msgstr ""
 
 #: ../../hosts.rst:45
-# 1e1a327f506545d588b5c2dac6a6be66
+# 1757e266dc494d81be5c3b51608b8507
 msgid "Place the host into CloudStack's \"scheduled maintenance\" mode. This does not invoke the vCenter maintenance mode, but only causes VMs to be migrated off the host"
 msgstr ""
 
 #: ../../hosts.rst:49
-# 10b6ab6a7f494f5e8df3db13ccfd3af8
+# d96d3c3231d445ffbe5379d2f572a864
 msgid "When the CloudStack maintenance mode is requested, the host first moves into the Prepare for Maintenance state. In this state it cannot be the target of new guest VM starts. Then all VMs will be migrated off the server. Live migration will be used to move VMs off the host. This allows the guests to be migrated to other hosts with no disruption to the guests. After this migration is completed, the host will enter the Ready for Maintenance mode."
 msgstr ""
 
-#: ../../hosts.rst:59
-# 1628c924f80a4f4e9f5becf74ad3f0ee
+#: ../../hosts.rst:57
+# a0302fba3abb4768b9ea6456150d1e34
 msgid "Wait for the \"Ready for Maintenance\" indicator to appear in the UI."
 msgstr ""
 
-#: ../../hosts.rst:63
-# 4adef7c4df77454e8bd00237cd21e93c
+#: ../../hosts.rst:59
+# bb2fe5471107450db78672f18f6c459b
 msgid "Now use vCenter to perform whatever actions are necessary to maintain the host. During this time, the host cannot be the target of new VM allocations."
 msgstr ""
 
-#: ../../hosts.rst:69
-# 7d67902696d54dba85c98361d7218cc4
+#: ../../hosts.rst:63
+# 465e081898184a07a0da7751a1b9540b
 msgid "When the maintenance tasks are complete, take the host out of maintenance mode as follows:"
 msgstr ""
 
-#: ../../hosts.rst:74
-# a3f38b02fdc24e5e9b3c51227bb08fd7
+#: ../../hosts.rst:66
+# d513b1610d3f4e3c94c36672598225ef
 msgid "First use vCenter to exit the vCenter maintenance mode."
 msgstr ""
 
-#: ../../hosts.rst:76
-# d4f34ccb4d9b4a1bb09958fa5cf4de5e
+#: ../../hosts.rst:68
+# 20604374352a49e78c96fc359907798b
 msgid "This makes the host ready for CloudStack to reactivate it."
 msgstr ""
 
-#: ../../hosts.rst:80
-# fc22d153282549d19896184eb37b2090
+#: ../../hosts.rst:70
+# 268a4bfa21584498b9c29213e959d532
 msgid "Then use CloudStack's administrator UI to cancel the CloudStack maintenance mode"
 msgstr ""
 
-#: ../../hosts.rst:83
-# ce24285fd2e84a2d8e071223d9f7aa23
+#: ../../hosts.rst:73
+# 473e00df4c58462d9df612fdba5c4996
 msgid "When the host comes back online, the VMs that were migrated off of it may be migrated back to it manually and new VMs can be added."
 msgstr ""
 
-#: ../../hosts.rst:87
-# 1be609d82bc7437ab1f435f587dee885
+#: ../../hosts.rst:78
+# 8026febd757948bdb38b4f85cbd4c425
 msgid "XenServer and Maintenance Mode"
 msgstr ""
 
-#: ../../hosts.rst:89
-# 4801359e1b504036a523926cb3083fcf
+#: ../../hosts.rst:80
+# 38555be75efd4fed91c3479a883493d1
 msgid "For XenServer, you can take a server offline temporarily by using the Maintenance Mode feature in XenCenter. When you place a server into Maintenance Mode, all running VMs are automatically migrated from it to another host in the same pool. If the server is the pool master, a new master will also be selected for the pool. While a server is Maintenance Mode, you cannot create or start any VMs on it."
 msgstr ""
 
-#: ../../hosts.rst:96
-# 4a08aa70600a434a8cf5feeb551dd509
+#: ../../hosts.rst:87
+# 456e5e6e17bf41909c0b487227d097cd
 msgid "**To place a server in Maintenance Mode:**"
 msgstr ""
 
-#: ../../hosts.rst:100
-#: ../../hosts.rst:123
-# f29fecea7fd547a4ac456396de215514
-# e5801557c9ac4721b34dd0390e57621f
+#: ../../hosts.rst:89
+#: ../../hosts.rst:104
+# 5de27d0060754518bf21cd3ed27ed05a
+# 568c45e59b4f4b2294d24752311a5022
 msgid "In the Resources pane, select the server, then do one of the following:"
 msgstr ""
 
-#: ../../hosts.rst:105
-# 1c753ac55dcb457ca6a65e85506faea1
+#: ../../hosts.rst:92
+# a31b8242b89b4b24a48e8d242ed46718
 msgid "Right-click, then click Enter Maintenance Mode on the shortcut menu."
 msgstr ""
 
-#: ../../hosts.rst:110
-# 457c53ac36f14ed5a1f83bc59f41713a
+#: ../../hosts.rst:95
+# 1e90893580c44442be56fd686ba4aab4
 msgid "On the Server menu, click Enter Maintenance Mode."
 msgstr ""
 
-#: ../../hosts.rst:114
-# 8870ed34b2dc4486ac8f411a890d72c4
+#: ../../hosts.rst:97
+# 95cf013b55004f2486b693b9a9bdb52d
 msgid "Click Enter Maintenance Mode."
 msgstr ""
 
-#: ../../hosts.rst:116
-# 2433c930578741a1909765bc2bade385
+#: ../../hosts.rst:99
+# e9120c5408d94ba89b65157b49de36ae
 msgid "The server's status in the Resources pane shows when all running VMs have been successfully migrated off the server."
 msgstr ""
 
-#: ../../hosts.rst:119
-# 42be08f037604e5a9f47001de252d369
+#: ../../hosts.rst:102
+# c8ae2b6b96814aa8a04dc2ceebbacabb
 msgid "**To take a server out of Maintenance Mode:**"
 msgstr ""
 
-#: ../../hosts.rst:128
-# f57ec4b8d883455d81686a1fd40f6160
+#: ../../hosts.rst:107
+# ae539b7f53ce42e8b161a38c897302a8
 msgid "Right-click, then click Exit Maintenance Mode on the shortcut menu."
 msgstr ""
 
-#: ../../hosts.rst:133
-# 7d8e71c7ffbc4d71a75266dfba6b84df
+#: ../../hosts.rst:110
+# ee115cfaf80446f49c0e9fae828c783e
 msgid "On the Server menu, click Exit Maintenance Mode."
 msgstr ""
 
-#: ../../hosts.rst:137
-# 8d0f538994db4767b7f9417b1cb41871
+#: ../../hosts.rst:112
+# 7edbfea17cdb4c4a85766a3d46ccf8da
 msgid "Click Exit Maintenance Mode."
 msgstr ""
 
-#: ../../hosts.rst:140
-# bd837a82be2c48858847657c7b3cfdaa
+#: ../../hosts.rst:116
+# e6edc76480294c5faf6518aaf5f6aacb
 msgid "Disabling and Enabling Zones, Pods, and Clusters"
 msgstr ""
 
-#: ../../hosts.rst:142
-# 3aea5f5c94fc4404a3d7c5f194da767d
+#: ../../hosts.rst:118
+# 144624e6273f4b5c94ed3f88c8fc95e3
 msgid "You can enable or disable a zone, pod, or cluster without permanently removing it from the cloud. This is useful for maintenance or when there are problems that make a portion of the cloud infrastructure unreliable. No new allocations will be made to a disabled zone, pod, or cluster until its state is returned to Enabled. When a zone, pod, or cluster is first added to the cloud, it is Disabled by default."
 msgstr ""
 
-#: ../../hosts.rst:149
-# a9c8925bb2d04ecc9962de6fd0fbc1fd
+#: ../../hosts.rst:125
+# 9fbfab10c6be45a3bd2f6c231c6737bb
 msgid "To disable and enable a zone, pod, or cluster:"
 msgstr ""
 
-#: ../../hosts.rst:153
-# 32c0489f474c4fecb77b83336097e9db
+#: ../../hosts.rst:127
+# 71e22a46ce644865b910006aaa048a8d
 msgid "Log in to the CloudStack UI as administrator"
 msgstr ""
 
-#: ../../hosts.rst:157
-#: ../../hosts.rst:447
-# 6b89d161130140ffbf2ccaee055008a3
-# 2f4cd598e62c47168a2ed22c6bec7674
+#: ../../hosts.rst:129
+#: ../../hosts.rst:404
+# 50c0cd124fa643fdbbc561152e0dbabf
+# e16a19456eb441b4ab3cf57ec846a391
 msgid "In the left navigation bar, click Infrastructure."
 msgstr ""
 
-#: ../../hosts.rst:161
-# 5ce0a640f1954756b46305873f389ad9
+#: ../../hosts.rst:131
+# 11fd25d319484ab2b87f09c842be5134
 msgid "In Zones, click View More."
 msgstr ""
 
-#: ../../hosts.rst:165
-# 3d333ceeab284ce5ad02f60c1fa67471
+#: ../../hosts.rst:133
+# c9caf60acf104601bc0f0f946d22b0c5
 msgid "If you are disabling or enabling a zone, find the name of the zone in the list, and click the Enable/Disable button. |enable-disable.png|"
 msgstr ""
 
-#: ../../hosts.rst:170
-# 0a4cfd78743b4e2c83066e46ce8464f8
+#: ../../hosts.rst:136
+# 222f496a2d1e456589a79442f4ed34a5
 msgid "If you are disabling or enabling a pod or cluster, click the name of the zone that contains the pod or cluster."
 msgstr ""
 
-#: ../../hosts.rst:175
-# 0dc7b10cd00b48c1a2c77859a0cd940a
+#: ../../hosts.rst:139
+# 8de91492f6c848dca361c3822956148a
 msgid "Click the Compute tab."
 msgstr ""
 
-#: ../../hosts.rst:179
-# c7daddfdce6e4da6bb743f31b20c08df
+#: ../../hosts.rst:141
+# 260854995dc747e8b0224b78525f9646
 msgid "In the Pods or Clusters node of the diagram, click View All."
 msgstr ""
 
-#: ../../hosts.rst:183
-# 35005e277f71455ca42dd6d65bf92a77
+#: ../../hosts.rst:143
+# 5496ff56c1c74d689c2d2453c38b4708
 msgid "Click the pod or cluster name in the list."
 msgstr ""
 
-#: ../../hosts.rst:187
-# e96437e7b142420f990a2c0717d1e472
+#: ../../hosts.rst:145
+# 893e62d5abbf47a38a0dd2c1a53d6a5a
 msgid "Click the Enable/Disable button. |enable-disable.png|"
 msgstr ""
 
-#: ../../hosts.rst:190
-# 5ab36fe8716644fa8a74b1315198f7d3
+#: ../../hosts.rst:149
+# 8f3d3ce8e0c64e67aea7a02d485fb245
 msgid "Removing Hosts"
 msgstr ""
 
-#: ../../hosts.rst:192
-# 2915247620714f17b21f9124f39d894e
+#: ../../hosts.rst:151
+# 984b62f5ee574b5fa2921a9c51086739
 msgid "Hosts can be removed from the cloud as needed. The procedure to remove a host depends on the hypervisor type."
 msgstr ""
 
-#: ../../hosts.rst:196
-# 04254d2838064c639d5331ae3ffc4753
+#: ../../hosts.rst:156
+# 65240cc22f554f09bdc03200b95bd05d
 msgid "Removing XenServer and KVM Hosts"
 msgstr ""
 
-#: ../../hosts.rst:198
-# eccc01ddbac946f9800dccea47e31ba9
+#: ../../hosts.rst:158
+# 879cec7da3564798aa9e0d864809678d
 msgid "A node cannot be removed from a cluster until it has been placed in maintenance mode. This will ensure that all of the VMs on it have been migrated to other Hosts. To remove a Host from the cloud:"
 msgstr ""
 
-#: ../../hosts.rst:204
-# 82565e09d51041738069677fb128372d
+#: ../../hosts.rst:162
+# 7b965bf8884a4bcba98b12aab945722c
 msgid "Place the node in maintenance mode."
 msgstr ""
 
-#: ../../hosts.rst:206
-# dd04ef23348a42fc815ff0a376123868
+#: ../../hosts.rst:164
+# 1301a77070374e238eb438818854da08
 msgid "See `“Scheduled Maintenance and Maintenance Mode for Hosts” <#scheduled-maintenance-and-maintenance-mode-for-hosts>`_."
 msgstr ""
 
-#: ../../hosts.rst:211
-# fed544dd8c474c2581684a87c9dae984
+#: ../../hosts.rst:167
+# 6cb63d9356e643f1b3e032a8056a89ee
 msgid "For KVM, stop the cloud-agent service."
 msgstr ""
 
-#: ../../hosts.rst:215
-# 1f7547325d9a4881a6768dd009061aae
+#: ../../hosts.rst:169
+# 3a90c7e2a9224f36b01d73a1df4cd39c
 msgid "Use the UI option to remove the node."
 msgstr ""
 
-#: ../../hosts.rst:217
-# f00eeb5fdaae4a9cbd1e36d610e270ac
+#: ../../hosts.rst:171
+# 400a182ceace4cef87ffe6c731ea45cd
 msgid "Then you may power down the Host, re-use its IP address, re-install it, etc"
 msgstr ""
 
-#: ../../hosts.rst:221
-# ae67d2137019437192ee7fbe0d451012
+#: ../../hosts.rst:176
+# b9297a05564a41f8aa6995f8f1e2265a
 msgid "Removing vSphere Hosts"
 msgstr ""
 
-#: ../../hosts.rst:223
-# b5b44fe095f645ed89753427c54c129e
+#: ../../hosts.rst:178
+# c32ebbedc8304707ab76b57248d80fee
 msgid "To remove this type of host, first place it in maintenance mode, as described in `“Scheduled Maintenance and Maintenance Mode for Hosts” <#scheduled-maintenance-and-maintenance-mode-for-hosts>`_. Then use CloudStack to remove the host. CloudStack will not direct commands to a host that has been removed using CloudStack. However, the host may still exist in the vCenter cluster."
 msgstr ""
 
-#: ../../hosts.rst:231
-# 2634c1aab86c49d6847a1cb6b9ca885d
+#: ../../hosts.rst:187
+# dd4d1c612fb44dc195061dd566beec5e
 msgid "Re-Installing Hosts"
 msgstr ""
 
-#: ../../hosts.rst:233
-# 4a42ccaecda646bca2ac6ac89016ca33
+#: ../../hosts.rst:189
+# 0ee9288a566b4631b2e8f680cfbe5b47
 msgid "You can re-install a host after placing it in maintenance mode and then removing it. If a host is down and cannot be placed in maintenance mode, it should still be removed before the re-install."
 msgstr ""
 
-#: ../../hosts.rst:238
-# 65deb360368a4ef6aeac7a84cfe5c1ab
+#: ../../hosts.rst:195
+# c85fb73c99e34c10b3289143d58b305b
 msgid "Maintaining Hypervisors on Hosts"
 msgstr ""
 
-#: ../../hosts.rst:240
-# b927785c512c4eb79d94c141907bf453
+#: ../../hosts.rst:197
+# af548f5aa95e4755a881574a77d625fd
 msgid "When running hypervisor software on hosts, be sure all the hotfixes provided by the hypervisor vendor are applied. Track the release of hypervisor patches through your hypervisor vendor’s support channel, and apply patches as soon as possible after they are released. CloudStack will not track or notify you of required hypervisor patches. It is essential that your hosts are completely up to date with the provided hypervisor patches. The hypervisor vendor is likely to refuse to support any system that is not up to date with patches."
 msgstr ""
 
-#: ../../hosts.rst:250
-# 6e001d3995a4461a98eb2c84399f8040
+#: ../../hosts.rst:207
+# fb13ff2e1e1c478e8ee99dbb7a71c69d
 msgid "The lack of up-do-date hotfixes can lead to data corruption and lost VMs."
 msgstr ""
 
-#: ../../hosts.rst:252
-# 24e34948fedb4eebaaa0b332c6b3ea55
+#: ../../hosts.rst:209
+# 0132d3f953a446e7af2712c1f7f204d9
 msgid "(XenServer) For more information, see `Highly Recommended Hotfixes for XenServer in the CloudStack Knowledge Base <http://docs.cloudstack.org/Knowledge_Base/Possible_VM_corruption_if_XenServer_Hotfix_is_not_Applied/Highly_Recommended_Hotfixes_for_XenServer_5.6_SP2>`_."
 msgstr ""
 
-#: ../../hosts.rst:255
-# e291026e0bcb4fc19c5f5ec67fb27962
+#: ../../hosts.rst:215
+# a2b8576f632f48e8b6556fe7958a2b4e
 msgid "Changing Host Password"
 msgstr ""
 
-#: ../../hosts.rst:257
-# a2ecdc3bf4ea4777a754dbf829ae95cf
+#: ../../hosts.rst:217
+# 026b9758a8234d5d82e1fd3c20d9f9d6
 msgid "The password for a XenServer Node, KVM Node, or vSphere Node may be changed in the database. Note that all Nodes in a Cluster must have the same password."
 msgstr ""
 
-#: ../../hosts.rst:261
-# 932a8d5023a3408bb325bb9976e78c9f
+#: ../../hosts.rst:221
+# d662651348254d968559ee61ec677c9d
 msgid "To change a Node's password:"
 msgstr ""
 
-#: ../../hosts.rst:265
-# 02c81a7d530c40cfa1a6acfbdd7d7db5
+#: ../../hosts.rst:223
+# eac8c72d0110440e8d47f458d4dfa691
 msgid "Identify all hosts in the cluster."
 msgstr ""
 
-#: ../../hosts.rst:269
-# 5493aaf270c04495a774d707812f6b71
+#: ../../hosts.rst:225
+# 6c429aa99fc44f4e85ed4eda61090335
 msgid "Change the password on all hosts in the cluster. Now the password for the host and the password known to CloudStack will not match. Operations on the cluster will fail until the two passwords match."
 msgstr ""
 
-#: ../../hosts.rst:275
-# 5a61d0b0dad244d5943f0f9a28393c34
+#: ../../hosts.rst:229
+# bd29f4605f0b40a9822294fd0cba68e4
 msgid "Get the list of host IDs for the host in the cluster where you are changing the password. You will need to access the database to determine these host IDs. For each hostname \"h\" (or vSphere cluster) that you are changing the password for, execute:"
 msgstr ""
 
-#: ../../hosts.rst:286
-# 6581ccaebb344383ac2fc40ddd20df3a
+#: ../../hosts.rst:238
+# ae93d4bde54f48ef9b96126a36220883
 msgid "This should return a single ID. Record the set of such IDs for these hosts."
 msgstr ""
 
-#: ../../hosts.rst:291
-# 081546910b424a93a45df2dee1cc04ca
+#: ../../hosts.rst:241
+# 6e33a985c6204813a3beec13959e029a
 msgid "Update the passwords for the host in the database. In this example, we change the passwords for hosts with IDs 5, 10, and 12 to \"password\"."
 msgstr ""
 
-#: ../../hosts.rst:300
-# 08354d3af75c417c8f3bb81415fabd09
+#: ../../hosts.rst:251
+# 36d8dc7ed9b3447a819222bfb445bd10
 msgid "Over-Provisioning and Service Offering Limits"
 msgstr ""
 
-#: ../../hosts.rst:302
-# a3bafa57323548dd9a6431f678eee017
+#: ../../hosts.rst:253
+# 3e5ec1fcb0cf49fda1383c022d23de87
 msgid "(Supported for XenServer, KVM, and VMware)"
 msgstr ""
 
-#: ../../hosts.rst:304
-# 0b69ea7e552248b1be401f196dfbb5d3
+#: ../../hosts.rst:255
+# 3633dc63fade45ad8b1bc222bb9ad425
 msgid "CPU and memory (RAM) over-provisioning factors can be set for each cluster to change the number of VMs that can run on each host in the cluster. This helps optimize the use of resources. By increasing the over-provisioning ratio, more resource capacity will be used. If the ratio is set to 1, no over-provisioning is done."
 msgstr ""
 
-#: ../../hosts.rst:310
-# e80bfc39f5a24aec99fa634cef445579
+#: ../../hosts.rst:261
+# 43467fc7868049cab2d4374ff0094af1
 msgid "The administrator can also set global default over-provisioning ratios in the cpu.overprovisioning.factor and mem.overprovisioning.factor global configuration variables. The default value of these variables is 1: over-provisioning is turned off by default."
 msgstr ""
 
-#: ../../hosts.rst:315
-# 22e46dfef84e43f088ea1c9ba56b012b
+#: ../../hosts.rst:266
+# 253e39db71ed47619ec617fb7a5397ac
 msgid "Over-provisioning ratios are dynamically substituted in CloudStack's capacity calculations. For example:"
 msgstr ""
 
-#: ../../hosts.rst:318
-# aeb35836bd204db3878f47e711625690
+#: ../../hosts.rst:269
+# 48cbfebf2e804785ba7f9631cb010778
 msgid "Capacity = 2 GB Over-provisioning factor = 2 Capacity after over-provisioning = 4 GB"
 msgstr ""
 
-#: ../../hosts.rst:322
-# fb3b9278bc9d46c7a2c77e1f574c1151
+#: ../../hosts.rst:273
+# af111e47b7cc4e53825770d523defc61
 msgid "With this configuration, suppose you deploy 3 VMs of 1 GB each:"
 msgstr ""
 
-#: ../../hosts.rst:324
-# 9feabccde7a04110b98c75d65bdfb257
+#: ../../hosts.rst:275
+# 851386252faa45d69618b89e2ff7ba8e
 msgid "Used = 3 GB Free = 1 GB"
 msgstr ""
 
-#: ../../hosts.rst:327
-# 5fb90dd3e25942db89cf99b12028bc9f
+#: ../../hosts.rst:278
+# fdd299fb9bed44d696ed49d97cd8779d
 msgid "The administrator can specify a memory over-provisioning ratio, and can specify both CPU and memory over-provisioning ratios on a per-cluster basis."
 msgstr ""
 
-#: ../../hosts.rst:331
-# 116d6bee32f044cbbd7e4da1d643e5b7
+#: ../../hosts.rst:282
+# 13239c1da0164d2e88a9275d8083e8aa
 msgid "In any given cloud, the optimum number of VMs for each host is affected by such things as the hypervisor, storage, and hardware configuration. These may be different for each cluster in the same cloud. A single global over-provisioning setting can not provide the best utilization for all the different clusters in the cloud. It has to be set for the lowest common denominator. The per-cluster setting provides a finer granularity for better utilization of resources, no matter where the CloudStack placement algorithm decides to place a VM."
 msgstr ""
 
-#: ../../hosts.rst:340
-# 52d81b5edf1e4675934e117fe3f7e39b
+#: ../../hosts.rst:291
+# 14bb9814011f4bb6972aeb18939b2e6c
 msgid "The overprovisioning settings can be used along with dedicated resources (assigning a specific cluster to an account) to effectively offer different levels of service to different accounts. For example, an account paying for a more expensive level of service could be assigned to a dedicated cluster with an over-provisioning ratio of 1, and a lower-paying account to a cluster with a ratio of 2."
 msgstr ""
 
-#: ../../hosts.rst:347
-# c36163afa88548cfba86a4569c955329
+#: ../../hosts.rst:298
+# a04ae50db280409bacc1c0752456eb1b
 msgid "When a new host is added to a cluster, CloudStack will assume the host has the capability to perform the CPU and RAM over-provisioning which is configured for that cluster. It is up to the administrator to be sure the host is actually suitable for the level of over-provisioning which has been set."
 msgstr ""
 
-#: ../../hosts.rst:354
-# edc95af891bf48bf9348b06cd982309c
+#: ../../hosts.rst:306
+# bc9d355b0e014b5ab9fd367c9e80ab24
 msgid "Limitations on Over-Provisioning in XenServer and KVM"
 msgstr ""
 
-#: ../../hosts.rst:358
-#: ../../hosts.rst:465
-# cc00f5f645f64e0697ca6ebdd96d0def
-# fa75f18b499847fd8e2399cb4259df55
+#: ../../hosts.rst:308
+#: ../../hosts.rst:416
+# c556b8018bbd4fee9f244adf40b4f51d
+# 536dc98cafb74355b90a4bea9be01f99
 msgid "In XenServer, due to a constraint of this hypervisor, you can not use an over-provisioning factor greater than 4."
 msgstr ""
 
-#: ../../hosts.rst:363
-# 0a8e4b3712eb41eb98132d75c64a88a7
+#: ../../hosts.rst:311
+# a9dd662370ca407596ca9fa0b313a3af
 msgid "The KVM hypervisor can not manage memory allocation to VMs dynamically. CloudStack sets the minimum and maximum amount of memory that a VM can use. The hypervisor adjusts the memory within the set limits based on the memory contention."
 msgstr ""
 
-#: ../../hosts.rst:369
-# f2fe7c9bf6004d17af2fc11f9e60bcb5
+#: ../../hosts.rst:318
+# 4eb1b9a8ad484a8fa8cb381ce6b52eb2
 msgid "Requirements for Over-Provisioning"
 msgstr ""
 
-#: ../../hosts.rst:371
-# bee683fe8af6414ba2ce5829f1cce894
+#: ../../hosts.rst:320
+# b5394f77c74e479980f2f996e9f81251
 msgid "Several prerequisites are required in order for over-provisioning to function properly. The feature is dependent on the OS type, hypervisor capabilities, and certain scripts. It is the administrator's responsibility to ensure that these requirements are met."
 msgstr ""
 
-#: ../../hosts.rst:377
-# ac320e5915bc4d5e92bae95824019630
+#: ../../hosts.rst:327
+# 4fc500a083b4403998ada5877b9d0de0
 msgid "Balloon Driver"
 msgstr ""
 
-#: ../../hosts.rst:379
-# 90096ecdf9dd4377bedd8eacc44a5805
+#: ../../hosts.rst:329
+# 9e1eb0f5b30a4a9cbebcf773c16bf440
 msgid "All VMs should have a balloon driver installed in them. The hypervisor communicates with the balloon driver to free up and make the memory available to a VM."
 msgstr ""
 
-#: ../../hosts.rst:384
-#: ../../hosts.rst:410
-# 3a85924afec74d44a1d3d84552e06e8f
-# 8cce762b3d4c48b5aaa49bca9049a7b8
+#: ../../hosts.rst:335
+#: ../../hosts.rst:365
+# 588dfd76655d44b999fcc554493271ee
+# 876a75ef59a549349b25f46f2f3fc8bf
 msgid "XenServer"
 msgstr ""
 
-#: ../../hosts.rst:386
-# 2bce40c454304c82b26a1b0275e7d257
+#: ../../hosts.rst:337
+# cc2308bc95464b93a3dc5631c6edb411
 msgid "The balloon driver can be found as a part of xen pv or PVHVM drivers. The xen pvhvm drivers are included in upstream linux kernels 2.6.36+."
 msgstr ""
 
-#: ../../hosts.rst:390
-# 9514bde1f9244064beacff1f13d21855
+#: ../../hosts.rst:342
+# db7f94775ac3401c8e7da496601ce4d7
 msgid "VMware"
 msgstr ""
 
-#: ../../hosts.rst:392
-# 1721067bf51441578864874e46fb712f
+#: ../../hosts.rst:344
+# db5f8890af6c435aa86e4c6106f0d83e
 msgid "The balloon driver can be found as a part of the VMware tools. All the VMs that are deployed in a over-provisioned cluster should have the VMware tools installed."
 msgstr ""
 
-#: ../../hosts.rst:397
-# fdfc3291197e40cbb6918abad409e86f
+#: ../../hosts.rst:350
+# e051f09fe032421881651a264ec5562c
 msgid "KVM"
 msgstr ""
 
-#: ../../hosts.rst:399
-# 393102255c6a4f449aa9100faef98786
+#: ../../hosts.rst:352
+# 9c51a6068b774e919cd552b525963bef
 msgid "All VMs are required to support the virtio drivers. These drivers are installed in all Linux kernel versions 2.6.25 and greater. The administrator must set CONFIG\\_VIRTIO\\_BALLOON=y in the virtio configuration."
 msgstr ""
 
-#: ../../hosts.rst:405
-# 02e47b485a7e4c9792ff13a65325ff98
+#: ../../hosts.rst:359
+# c8150c4e5af743bd8897bbd116c538d7
 msgid "Hypervisor capabilities"
 msgstr ""
 
-#: ../../hosts.rst:407
-# 24056966cd1e43f4b55061b3d1952313
+#: ../../hosts.rst:361
+# efc1f0769cdf44d0aee285aed27c7e0f
 msgid "The hypervisor must be capable of using the memory ballooning."
 msgstr ""
 
-#: ../../hosts.rst:412
-# cbb4ca754be34de8ac7f1de22df461b5
+#: ../../hosts.rst:367
+# 8b282cb5f7914088be3b38b87b604492
 msgid "The DMC (Dynamic Memory Control) capability of the hypervisor should be enabled. Only XenServer Advanced and above versions have this feature."
 msgstr ""
 
-#: ../../hosts.rst:416
-# 134f00ef1ff74950a8dff3d90e185df3
+#: ../../hosts.rst:372
+# 11e7b221209c4b97ab044dbbb6c53b0e
 msgid "VMware, KVM"
 msgstr ""
 
-#: ../../hosts.rst:418
-# cbf853d94adb42db8f9447bcc6c094b4
+#: ../../hosts.rst:374
+# c289bebec04c474c9497ce81216e04f1
 msgid "Memory ballooning is supported by default."
 msgstr ""
 
-#: ../../hosts.rst:421
-# fe751eb8be7f47c4ac053e41b99a0c3f
+#: ../../hosts.rst:378
+# fd73c49bd922450fb7a771ebb8586d6d
 msgid "Setting Over-Provisioning Ratios"
 msgstr ""
 
-#: ../../hosts.rst:423
-# 362d1a967cde49bd8c050e25ce11a418
+#: ../../hosts.rst:380
+# 7d8bbd43174f499a98270e1aad9301bd
 msgid "There are two ways the root admin can set CPU and RAM over-provisioning ratios. First, the global configuration settings cpu.overprovisioning.factor and mem.overprovisioning.factor will be applied when a new cluster is created. Later, the ratios can be modified for an existing cluster."
 msgstr ""
 
-#: ../../hosts.rst:429
-# 1f116a42dfc04347bf2fbc30976a7fe1
+#: ../../hosts.rst:386
+# 6930197d999a4c1bb3e8bca13bb10c00
 msgid "Only VMs deployed after the change are affected by the new setting. If you want VMs deployed before the change to adopt the new over-provisioning ratio, you must stop and restart the VMs. When this is done, CloudStack recalculates or scales the used and reserved capacities based on the new over-provisioning ratios, to ensure that CloudStack is correctly tracking the amount of free capacity."
 msgstr ""
 
-#: ../../hosts.rst:437
-# 93a9d4a11ea3467bab17fb3f4cd0dad6
+#: ../../hosts.rst:394
+# fe4660151e234650980661b9975d4c77
 msgid "It is safer not to deploy additional new VMs while the capacity recalculation is underway, in case the new values for available capacity are not high enough to accommodate the new VMs. Just wait for the new used/available values to become available, to be sure there is room for all the new VMs you want."
 msgstr ""
 
-#: ../../hosts.rst:439
-# e0366b1e2fa54380bcd721e1a380fc53
+#: ../../hosts.rst:400
+# 443b0ee66d0b40bdad6e11ac6c4eb123
 msgid "To change the over-provisioning ratios for an existing cluster:"
 msgstr ""
 
-#: ../../hosts.rst:443
-# 7ffed21dabe7462b8e09848f5725cc96
+#: ../../hosts.rst:402
+# b796b807352f4f8285fca177e9417577
 msgid "Log in as administrator to the CloudStack UI."
 msgstr ""
 
-#: ../../hosts.rst:451
-# 4d7c773d04964e5b9f50c9425f2787da
+#: ../../hosts.rst:406
+# 450e03bbb9974112bec16a0dca62c829
 msgid "Under Clusters, click View All."
 msgstr ""
 
-#: ../../hosts.rst:455
-# 84bddff125d543f283dd83cce8892998
+#: ../../hosts.rst:408
+# dc9598fec6f74c74a82c2311ff962b5d
 msgid "Select the cluster you want to work with, and click the Edit button."
 msgstr ""
 
-#: ../../hosts.rst:459
-# 519a8079ef6b4d2eb83eb8537dfed6e8
+#: ../../hosts.rst:410
+# 4574765089c64df0a53ffd4b0d9052a0
 msgid "Fill in your desired over-provisioning multipliers in the fields CPU overcommit ratio and RAM overcommit ratio. The value which is intially shown in these fields is the default value inherited from the global configuration settings."
 msgstr ""
 
-#: ../../hosts.rst:468
-# 8e7465fb587642f5aac407e899b0ad64
+#: ../../hosts.rst:421
+# 2652eabbfcd64f92bab0644f7cddd8d6
 msgid "Service Offering Limits and Over-Provisioning"
 msgstr ""
 
-#: ../../hosts.rst:470
-# 0d6a4122110b4dee8cff81972c293a1f
+#: ../../hosts.rst:423
+# d88ad9813f6448ec9277039383ab3f86
 msgid "Service offering limits (e.g. 1 GHz, 1 core) are strictly enforced for core count. For example, a guest with a service offering of one core will have only one core available to it regardless of other activity on the Host."
 msgstr ""
 
-#: ../../hosts.rst:475
-# 480c139ad92a490a8cf4bf6004be1bf8
+#: ../../hosts.rst:428
+# 0a5fa05e882e493f8d41201840eb0cd9
 msgid "Service offering limits for gigahertz are enforced only in the presence of contention for CPU resources. For example, suppose that a guest was created with a service offering of 1 GHz on a Host that has 2 GHz cores, and that guest is the only guest running on the Host. The guest will have the full 2 GHz available to it. When multiple guests are attempting to use the CPU a weighting factor is used to schedule CPU resources. The weight is based on the clock speed in the service offering. Guests receive a CPU allocation that is proportionate to the GHz in the service offering. For example, a guest created from a 2 GHz service offering will receive twice the CPU allocation as a guest created from a 1 GHz service offering. CloudStack does not perform memory over-provisioning."
 msgstr ""
 
-#: ../../hosts.rst:488
-# 6973ca6704974a47964898e5e0e218dc
+#: ../../hosts.rst:442
+# 86b75c2fbf034662ac3133fe63acefea
 msgid "VLAN Provisioning"
 msgstr ""
 
-#: ../../hosts.rst:490
-# 5b73126100d24f48a0f831790b6172db
+#: ../../hosts.rst:444
+# 9d66a1eb7d4d4d88818d5d5d00bb285a
 msgid "CloudStack automatically creates and destroys interfaces bridged to VLANs on the hosts. In general the administrator does not need to manage this process."
 msgstr ""
 
-#: ../../hosts.rst:494
-# 4e2359bef8e1410d98f92288a2f72a96
+#: ../../hosts.rst:448
+# 7cfe38c7368a44d1b920f68fbb7e2b5e
 msgid "CloudStack manages VLANs differently based on hypervisor type. For XenServer or KVM, the VLANs are created on only the hosts where they will be used and then they are destroyed when all guests that require them have been terminated or moved to another host."
 msgstr ""
 
-#: ../../hosts.rst:499
-# cfd189a826f9412e8b54976947f52b54
+#: ../../hosts.rst:453
+# a681bdc643fc41a49688c3a833dce9ac
 msgid "For vSphere the VLANs are provisioned on all hosts in the cluster even if there is no guest running on a particular Host that requires the VLAN. This allows the administrator to perform live migration and other functions in vCenter without having to create the VLAN on the destination Host. Additionally, the VLANs are not removed from the Hosts when they are no longer needed."
 msgstr ""
 
-#: ../../hosts.rst:506
-# fc44fd764b804474b12d380d2b22dc04
+#: ../../hosts.rst:460
+# 162b7ae68b2d41db83c3bc6d32e86e6b
 msgid "You can use the same VLANs on different physical networks provided that each physical network has its own underlying layer-2 infrastructure, such as switches. For example, you can specify VLAN range 500 to 1000 while deploying physical networks A and B in an Advanced zone setup. This capability allows you to set up an additional layer-2 physical infrastructure on a different physical NIC and use the same set of VLANs if you run out of VLANs. Another advantage is that you can use the same set of IPs for different customers, each one with their own routers and the guest networks on different physical NICs."
 msgstr ""
 
-#: ../../hosts.rst:517
-# 06f9c538941f4e3ca83477adfe036a8b
+#: ../../hosts.rst:472
+# d4316f84d139424ab25c6fb9292b2840
 msgid "VLAN Allocation Example"
 msgstr ""
 
-#: ../../hosts.rst:519
-# 7a8e238fd6a447e9803e0fcd39957760
+#: ../../hosts.rst:474
+# ea6edc6b827c4791a53ea10997662dae
 msgid "VLANs are required for public and guest traffic. The following is an example of a VLAN allocation scheme:"
 msgstr ""
 
-#: ../../hosts.rst:523
-# 97aaca38941d42f183baf9eb2c560eec
+#: ../../hosts.rst:478
+# 558c3d372c85421390186a570da26dee
 msgid "VLAN IDs"
 msgstr ""
 
-#: ../../hosts.rst:523
-# d6cbed5a64fc49fda68543d1a54823ec
+#: ../../hosts.rst:478
+# b6c7ef27f668454dbb5adb9a9c190c98
 msgid "Traffic type"
 msgstr ""
 
-#: ../../hosts.rst:523
-# c6a593644e2848398fdf1b4c86458434
+#: ../../hosts.rst:478
+# 2dc30077851f4826beeaeb3c808e6452
 msgid "Scope"
 msgstr ""
 
-#: ../../hosts.rst:525
-# df3262b199df4244a2cb492f3134ee68
+#: ../../hosts.rst:480
+# 46e966a312a047cfa77c7292aaba1fdb
 msgid "less than 500"
 msgstr ""
 
-#: ../../hosts.rst:525
-# 5fc5eed1fae7464bb9bd0cd832cb9901
+#: ../../hosts.rst:480
+# c6ffd280911a498f99904379cc538935
 msgid "Management traffic."
 msgstr ""
 
-#: ../../hosts.rst:525
-# d7ca9d9a93904c57808e9baf286d1374
+#: ../../hosts.rst:480
+# bb76ee312d884069ac0a101cfc2680d2
 msgid "Reserved for administrative purposes.  CloudStack software can access this, hypervisors, system VMs."
 msgstr ""
 
-#: ../../hosts.rst:526
-# 816d6141016845e68cc5cfbb70a5ca4a
+#: ../../hosts.rst:481
+# 1307c25d94c447a08ebf7b1f47d76fa7
 msgid "500-599"
 msgstr ""
 
-#: ../../hosts.rst:526
-# 4c6772a236b949c6a827887e55f468dc
+#: ../../hosts.rst:481
+# fb79eefe00ad444eaf660e4c6c7571b7
 msgid "VLAN carrying public traffic."
 msgstr ""
 
-#: ../../hosts.rst:526
-# 9788f1148534421f8b3e69b0a2291d4c
+#: ../../hosts.rst:481
+# 0c7d0d0d68c94f5f889f1e32dcb564cb
 msgid "CloudStack accounts."
 msgstr ""
 
-#: ../../hosts.rst:527
-# faa736af78474fec844134eb7ee8f8e8
+#: ../../hosts.rst:482
+# 9ab975c827154ebd84ab2f50936736b8
 msgid "600-799"
 msgstr ""
 
-#: ../../hosts.rst:527
-#: ../../hosts.rst:528
-# 00cdf19f243d48eda62692e050cca578
-# 968535793b2646eda10843e74d06390c
+#: ../../hosts.rst:482
+#: ../../hosts.rst:483
+# e33f1854a40043ed9d323fa1f1a3519d
+# 1dfa7469eec44ea6b03b34b9c6f7504e
 msgid "VLANs carrying guest traffic."
 msgstr ""
 
-#: ../../hosts.rst:527
-# 4c9c92a88e4240c8a3eb4021856220ab
+#: ../../hosts.rst:482
+# e10058e68df14ced9dda12d02876f4c4
 msgid "CloudStack accounts. Account-specific VLAN is chosen from this pool."
 msgstr ""
 
-#: ../../hosts.rst:528
-# 821a9f34a9dd4ccbbcb7099bc2e120ff
+#: ../../hosts.rst:483
+# 26028e0cc17c46ceae4008c85730b970
 msgid "800-899"
 msgstr ""
 
-#: ../../hosts.rst:528
-# a0b968ec993843e7b61e267dcffdc110
+#: ../../hosts.rst:483
+# a894ab0d32654721aa09284c57bbabc4
 msgid "CloudStack accounts. Account-specific VLAN chosen by CloudStack admin to assign to that account."
 msgstr ""
 
-#: ../../hosts.rst:529
-# eebf870170034248bf44689d980f22fd
+#: ../../hosts.rst:484
+# 4a297ddc517048fab79c4a44c5ad0b99
 msgid "900-999"
 msgstr ""
 
-#: ../../hosts.rst:529
-# fcaefad65c864f0aa12decdbc8ea1a9f
+#: ../../hosts.rst:484
+# 404678aaa64349f8924466d04c12db32
 msgid "VLAN carrying guest traffic"
 msgstr ""
 
-#: ../../hosts.rst:529
-# dbc8efd08bdb47939963f1e1ade787c4
+#: ../../hosts.rst:484
+# 185277c2c47d409cb9ec68e3f03ceddc
 msgid "CloudStack accounts. Can be scoped by project, domain, or all accounts."
 msgstr ""
 
-#: ../../hosts.rst:530
-# b91c7c3931aa46dbaddfffb5b3497d75
+#: ../../hosts.rst:485
+# 5032da4e90be448f905a4ee48df7d8ed
 msgid "greater than 1000"
 msgstr ""
 
-#: ../../hosts.rst:530
-# 11b667ae6cb04cc68d5a10a133cee37b
+#: ../../hosts.rst:485
+# af16d28d60df4d84b3951c37a78f02bc
 msgid "Reserved for future use"
 msgstr ""
 
-#: ../../hosts.rst:534
-# 10b73559efa5445caf021d488a10c300
+#: ../../hosts.rst:490
+# ef44b9e8dc084564a01254fc196c3b9e
 msgid "Adding Non Contiguous VLAN Ranges"
 msgstr ""
 
-#: ../../hosts.rst:536
-# 632b0960356d40aabb5f7262a942d317
+#: ../../hosts.rst:492
+# 5b73c96b899144be9a84d12c7ed11d55
 msgid "CloudStack provides you with the flexibility to add non contiguous VLAN ranges to your network. The administrator can either update an existing VLAN range or add multiple non contiguous VLAN ranges while creating a zone. You can also use the UpdatephysicalNetwork API to extend the VLAN range."
 msgstr ""
 
-#: ../../hosts.rst:544
-# 22166092fd8e4f749f83b22e91ed0a19
+#: ../../hosts.rst:498
+# 957172517a6845a3915b26e7b95812d0
 msgid "Log in to the CloudStack UI as an administrator or end user."
 msgstr ""
 
-#: ../../hosts.rst:548
-# c3cc468f1166400fbf2d5bbccec17632
+#: ../../hosts.rst:500
+# cb713605543d4f8eb0ffd5bec494839d
 msgid "Ensure that the VLAN range does not already exist."
 msgstr ""
 
-#: ../../hosts.rst:552
-# 0cca254c9b6c4adab9fca2d53a8d2a99
+#: ../../hosts.rst:502
+# 6543749bf38741be83173b69828b1f49
 msgid "In the left navigation, choose Infrastructure."
 msgstr ""
 
-#: ../../hosts.rst:556
-# 501e52d3dc124b9b81b1a94a93af9f28
+#: ../../hosts.rst:504
+# 7bd96bd6e7fd4c94bd7be28295bd46de
 msgid "On Zones, click View More, then click the zone to which you want to work with."
 msgstr ""
 
-#: ../../hosts.rst:561
-# 6a6640c67ea34b0b9a0ca859696174c0
+#: ../../hosts.rst:507
+# 29ea322032104b06880f1204aa29a145
 msgid "Click Physical Network."
 msgstr ""
 
-#: ../../hosts.rst:565
-# 9df7f0d650ab4fa8868898684c3025ba
+#: ../../hosts.rst:509
+# a6e5a25d6929406594577a6b3f074454
 msgid "In the Guest node of the diagram, click Configure."
 msgstr ""
 
-#: ../../hosts.rst:569
-# 81b5cc6e8b5e4cffada11d5628cf542b
+#: ../../hosts.rst:511
+# b85881c793b045978846d5eb97408757
 msgid "Click Edit |edit-icon.png|."
 msgstr ""
 
-#: ../../hosts.rst:571
-# 128ddb2b1a0b403eaa01728b573229e2
+#: ../../hosts.rst:513
+# 061af0a695ad4e1abcd195287ee6e0ef
 msgid "The VLAN Ranges field now is editable."
 msgstr ""
 
-#: ../../hosts.rst:575
-# ecf3f3c2e0a24b78aed1b4ed3eb44f3c
+#: ../../hosts.rst:515
+# 131fadb281474dc597e34d3fe0d6d444
 msgid "Specify the start and end of the VLAN range in comma-separated list."
 msgstr ""
 
-#: ../../hosts.rst:577
-# 16e7961826d14270960e64272b17457a
+#: ../../hosts.rst:517
+# aaf0146792d5487297eff314b521c053
 msgid "Specify all the VLANs you want to use, VLANs not specified will be removed if you are adding new ranges to the existing list."
 msgstr ""
 
-#: ../../hosts.rst:582
-# d6cbf61222844716888f5f8f862bfd82
+#: ../../hosts.rst:520
+# d7cd1af070644a71ae33b79fbc724b87
 msgid "Click Apply."
 msgstr ""
 
-#: ../../hosts.rst:585
-# 87d75c37a1ca4312b9d73ae90c39dacf
+#: ../../hosts.rst:524
+# 9685350eac754d8c889dc8da19292529
 msgid "Assigning VLANs to Isolated Networks"
 msgstr ""
 
-#: ../../hosts.rst:587
-# 329c29ef5c0640298b62d8621919a04e
+#: ../../hosts.rst:526
+# 31001908f2bd40018f7b77a9001e50c7
 msgid "CloudStack provides you the ability to control VLAN assignment to Isolated networks. As a Root admin, you can assign a VLAN ID when a network is created, just the way it's done for Shared networks."
 msgstr ""
 
-#: ../../hosts.rst:591
-# d463cc2b2e6b45efbc688fae2f8c844e
+#: ../../hosts.rst:530
+# 47af367fd0e74e9c98c07d5fd93d9a6a
 msgid "The former behaviour also is supported — VLAN is randomly allocated to a network from the VNET range of the physical network when the network turns to Implemented state. The VLAN is released back to the VNET pool when the network shuts down as a part of the Network Garbage Collection. The VLAN can be re-used either by the same network when it is implemented again, or by any other network. On each subsequent implementation of a network, a new VLAN can be assigned."
 msgstr ""
 
-#: ../../hosts.rst:599
-# 67f26f616c1d468f9f43fbad3a96d653
+#: ../../hosts.rst:538
+# 1ba6d80370024ab596ffd9d4ae6294cc
 msgid "Only the Root admin can assign VLANs because the regular users or domain admin are not aware of the physical network topology. They cannot even view what VLAN is assigned to a network."
 msgstr ""
 
-#: ../../hosts.rst:603
-# 8cb6b5c237b24db2a036745c714fd0c1
+#: ../../hosts.rst:542
+# f8d82f2f80da4f4fbdef3b4308538511
 msgid "To enable you to assign VLANs to Isolated networks,"
 msgstr ""
 
-#: ../../hosts.rst:607
-# aa68c2b731f44e8ca5e7b12992e491e4
+#: ../../hosts.rst:544
+# 51e781fd8ac2474f896774fe185ff585
 msgid "Create a network offering by specifying the following:"
 msgstr ""
 
-#: ../../hosts.rst:611
-# 6ac8335147a0424ea30c996690f508f6
+#: ../../hosts.rst:546
+# 38ae271a7f7f4855a4353c109d01d761
 msgid "**Guest Type**: Select Isolated."
 msgstr ""
 
-#: ../../hosts.rst:615
-# a4d3756da9654670af81f81ef51f5bea
+#: ../../hosts.rst:548
+# 136f37de7a6f4b1ead01c213603a4a47
 msgid "**Specify VLAN**: Select the option."
 msgstr ""
 
-#: ../../hosts.rst:617
-# 418a868357c54463be949ae219831e3f
+#: ../../hosts.rst:550
+# ba4c14a8b3d94e1fbeccb6afd28ec4ad
 msgid "For more information, see the CloudStack Installation Guide."
 msgstr ""
 
-#: ../../hosts.rst:621
-# c7ae08cd2c954f069c402e2f29bd6498
+#: ../../hosts.rst:552
+# 42fbeadc772741cdb88549a149bef4c4
 msgid "Using this network offering, create a network."
 msgstr ""
 
-#: ../../hosts.rst:623
-# b76ebd2ac4ec4be88b31ead41a0ffa76
+#: ../../hosts.rst:554
+# b08c9effb9bf43ecb0e42699daf88922
 msgid "You can create a VPC tier or an Isolated network."
 msgstr ""
 
-#: ../../hosts.rst:627
-# c827ff2cdfaa40c0a2f5dcefd4637b6f
+#: ../../hosts.rst:556
+# d1ae253e49f3473a9ee2ed29b8447270
 msgid "Specify the VLAN when you create the network."
 msgstr ""
 
-#: ../../hosts.rst:629
-# 8e3918b569284ecc9204e3c58114c951
+#: ../../hosts.rst:558
+# d4c5557c8994473ba6ca182dc7149c44
 msgid "When VLAN is specified, a CIDR and gateway are assigned to this network and the state is changed to Setup. In this state, the network will not be garbage collected."
 msgstr ""
 
-#: ../../hosts.rst:634
-# 710699c1ce8949f781a434db64439614
+#: ../../hosts.rst:563
+# 89369b26917b4d54ad28290b37c59b53
 msgid "You cannot change a VLAN once it's assigned to the network. The VLAN remains with the network for its entire life cycle."
 msgstr ""
 
diff --git a/source/locale/pot/index.pot b/source/locale/pot/index.pot
index 0f29df7..8133094 100644
--- a/source/locale/pot/index.pot
+++ b/source/locale/pot/index.pot
@@ -8,7 +8,7 @@
 msgstr ""
 "Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2014-03-31 14:08-0400\n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -16,88 +16,113 @@
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
 
-#: ../../index.rst:22
-# d7684c4811fb465d8e5523136e60776b
+#: ../../index.rst:23
+# 84926a62ef4145eb8258fb18cc990020
 msgid "Welcome to CloudStack Administration Documentation"
 msgstr ""
 
-#: ../../index.rst:25
-# 89ba74160fc34ab384dce20831bba66f
+#: ../../index.rst:29
+# 17401d6f4fa445e288e17f050447db52
+msgid "We are in the process of changing documentation format as well as hosting mechanism. Please be patient with us as we migrate our entire documentation to this new setup."
+msgstr ""
+
+#: ../../index.rst:32
+# 3ed721b0cbc84d29b41f1f88c145794b
+msgid "This guide is aimed at Administrators of a CloudStack based Cloud, for Release Notes, Installation and General introduction to CloudStack see the following guides:"
+msgstr ""
+
+#: ../../index.rst:36
+# 6bdec416d5864e24a626b2a1672d12fc
+msgid "`Documentation Start <http://docs.cloudstack.apache.org>`_"
+msgstr ""
+
+#: ../../index.rst:38
+# 59647f13b4c6495bb231941872f8615c
+msgid "`Installation Guide <http://docs.cloudstack.apache.org/projects/cloudstack-installation>`_"
+msgstr ""
+
+#: ../../index.rst:40
+# 3cb4b38db39a4954baa74c5207e46806
+msgid "`Release Notes <http://docs.cloudstack.apache.org/projects/cloudstack-release-notes>`_"
+msgstr ""
+
+#: ../../index.rst:44
+# 62705a3d035f4c9894e165081f5341b0
 msgid "User Interface"
 msgstr ""
 
-#: ../../index.rst:33
-# 0b869c712c0549f794b04850fc92bbf0
+#: ../../index.rst:53
+# 253ae3a9066e4b22aa50e77c73b69357
 msgid "Managing Accounts, Users and Domains"
 msgstr ""
 
-#: ../../index.rst:41
-# ade0aa6c65934d08b9439c9b55d76991
+#: ../../index.rst:62
+# bb51dd2b7b6d4b6287d5b832dd1ef9f3
 msgid "Using Projects to Organize User Resources"
 msgstr ""
 
-#: ../../index.rst:48
-# a4efa62c4fe0431e97cf1e8a8afa3c4c
+#: ../../index.rst:70
+# fcbcd54779cb4d14b7c28ea8e525c2ff
 msgid "Service Offerings"
 msgstr ""
 
-#: ../../index.rst:56
-# 784d8d28e28c49e588607297adc80f3b
+#: ../../index.rst:79
+# 2fed4745955e4e73b1b3bd6c4664a015
 msgid "Setting up Networking for Users"
 msgstr ""
 
-#: ../../index.rst:64
-# 99a275b31677470fb19d20cc2cfb3a66
+#: ../../index.rst:88
+# 37cb22ac86ef4acb9c046bc1dc7f7de4
 msgid "Working with Virtual Machines"
 msgstr ""
 
-#: ../../index.rst:72
-# 8f3d1a01a82d4daca2072ce17e85191b
+#: ../../index.rst:97
+# 625c8add441e4edeac86a1ec4f792cec
 msgid "Working with Templates"
 msgstr ""
 
-#: ../../index.rst:80
-# b618e01117be4bc8917aab2189ec3be4
+#: ../../index.rst:106
+# 7ad29a9c67c74560b24731372d219e23
 msgid "Working with Hosts"
 msgstr ""
 
-#: ../../index.rst:88
-# 1d07b6cc6bd74b689edf5f3f6305e11f
+#: ../../index.rst:115
+# a3332c4666934361ad83c88e6946f7f7
 msgid "Working with Storage"
 msgstr ""
 
-#: ../../index.rst:96
-# 538bdb71f1c34206a75745c0c45b8669
+#: ../../index.rst:124
+# f2f20fd23af44019b1f0578d399c9ecc
 msgid "Working with System Virtual Machines"
 msgstr ""
 
-#: ../../index.rst:104
-# da80feddb6be416fb7a724951d7f6049
+#: ../../index.rst:133
+# 73fe247fe2a14cf08be624ae4f8d5926
 msgid "Working with Usage"
 msgstr ""
 
-#: ../../index.rst:112
-# 89016757f86c44379eb90b8ea75b6d40
+#: ../../index.rst:142
+# 5d20c3a9b5124254a155ba5a519c85ca
 msgid "Managing Networks and Traffic"
 msgstr ""
 
-#: ../../index.rst:120
-# 4c1cbbb4d99f4c8bace30f6c0edbdd98
+#: ../../index.rst:151
+# c591434a39994a6fa8546f4b1115eb07
 msgid "Managing the Cloud"
 msgstr ""
 
-#: ../../index.rst:128
-# 769cb32397e246beb100d0a77e9bf7ab
+#: ../../index.rst:160
+# 1ffdcf555b9a45d58d6a0e3b4d670037
 msgid "System Reliability and Availability"
 msgstr ""
 
-#: ../../index.rst:136
-# 2256c3b81c7b49e18235f85ab474184f
+#: ../../index.rst:169
+# 8422886b2cfe4b9c9d2adf3afd86f37f
 msgid "Tuning"
 msgstr ""
 
-#: ../../index.rst:144
-# 1577c7120b3648449625d8806030fe2b
+#: ../../index.rst:178
+# c05956039d98457abe5c11b6f7661b23
 msgid "Events and Troubleshooting"
 msgstr ""
 
diff --git a/source/locale/pot/management.pot b/source/locale/pot/management.pot
index e68a324..96ab7aa 100644
--- a/source/locale/pot/management.pot
+++ b/source/locale/pot/management.pot
@@ -8,7 +8,7 @@
 msgstr ""
 "Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2014-03-31 14:08-0400\n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -17,442 +17,442 @@
 "Content-Transfer-Encoding: 8bit\n"
 
 #: ../../management.rst:18
-# 62fa0deba316409090e6e208765342a7
+# 36cc316d379647279da05d191cf9e9b5
 msgid "Managing the Cloud"
 msgstr ""
 
 #: ../../management.rst:21
-# a792503e467d4d97a1d4aa55140452a5
+# 0dc09dfbe9e34a9cb51831005d8fc025
 msgid "Using Tags to Organize Resources in the Cloud"
 msgstr ""
 
 #: ../../management.rst:23
-# c61cae44c33f4a3b93bcbde61e020c22
+# 3ead5d7ddceb4d98a278abeeed0683c2
 msgid "A tag is a key-value pair that stores metadata about a resource in the cloud. Tags are useful for categorizing resources. For example, you can tag a user VM with a value that indicates the user's city of residence. In this case, the key would be \"city\" and the value might be \"Toronto\" or \"Tokyo.\" You can then request CloudStack to find all resources that have a given tag; for example, VMs for users in a given city."
 msgstr ""
 
 #: ../../management.rst:30
-# b8bee7f6ee524c41a62546c3926fc5a6
+# 6388318fab6c44f58fd92b854f510717
 msgid "You can tag a user virtual machine, volume, snapshot, guest network, template, ISO, firewall rule, port forwarding rule, public IP address, security group, load balancer rule, project, VPC, network ACL, or static route. You can not tag a remote access VPN."
 msgstr ""
 
 #: ../../management.rst:35
-# 41f9c119f564420ebc0b2ce07d6a5211
+# 87e95cabe82f4b7f86c2cd1cc303b912
 msgid "You can work with tags through the UI or through the API commands createTags, deleteTags, and listTags. You can define multiple tags for each resource. There is no limit on the number of tags you can define. Each tag can be up to 255 characters long. Users can define tags on the resources they own, and administrators can define tags on any resources in the cloud."
 msgstr ""
 
 #: ../../management.rst:42
-# 4987c5d196e64161aae21901c96b4c37
+# c2db56ab546245ec9d37ccf72573c16c
 msgid "An optional input parameter, \"tags,\" exists on many of the list\\* API commands. The following example shows how to use this new parameter to find all the volumes having tag region=canada OR tag city=Toronto:"
 msgstr ""
 
 #: ../../management.rst:55
-# 7914681bd50244bcaf4169707987eb00
+# 0d735394ca9f48f8a4ef3c5d0a25741d
 msgid "The following API commands have the \"tags\" input parameter:"
 msgstr ""
 
-#: ../../management.rst:59
-# 61fbca041dee4db2aade53a7cf792de7
+#: ../../management.rst:57
+# 6d986331aa5d4971bab13111a8471d36
 msgid "listVirtualMachines"
 msgstr ""
 
-#: ../../management.rst:63
-# ba0235266c3845cc96ba7fcf7de44466
+#: ../../management.rst:59
+# b0e2702f6aed49a8831ae5c2983a18c9
 msgid "listVolumes"
 msgstr ""
 
-#: ../../management.rst:67
-# 1c68c5c60b174ea2a71f39ba93a211ac
+#: ../../management.rst:61
+# 97c53594680a4cecb64e3f1a5ea2a2f3
 msgid "listSnapshots"
 msgstr ""
 
-#: ../../management.rst:71
-# 9f05731121b4498e9e51a500a79f2511
+#: ../../management.rst:63
+# 0217180a24604d579084142d07f11299
 msgid "listNetworks"
 msgstr ""
 
-#: ../../management.rst:75
-# 36599c953977457c84ecffc6c9395338
+#: ../../management.rst:65
+# dcf958a652304820818033fc441226e7
 msgid "listTemplates"
 msgstr ""
 
-#: ../../management.rst:79
-# c3b6ffcb5da240cea465ea296dd4ccfd
+#: ../../management.rst:67
+# 296660956a3b4ce5b02c4c7f1272e889
 msgid "listIsos"
 msgstr ""
 
-#: ../../management.rst:83
-# 6a47e3c18c6f476bb22295c172479796
+#: ../../management.rst:69
+# 69e88bee17394199a778180f3304fbf0
 msgid "listFirewallRules"
 msgstr ""
 
-#: ../../management.rst:87
-# 08d8500b98314effbb3d7916236f7e2b
+#: ../../management.rst:71
+# 7954e7afc0334bc7bfcf16492195bb49
 msgid "listPortForwardingRules"
 msgstr ""
 
-#: ../../management.rst:91
-# 2a42e7c362bc427eba13e2d7e7bf7380
+#: ../../management.rst:73
+# d273e10141d84eecbdc74ec901700d11
 msgid "listPublicIpAddresses"
 msgstr ""
 
-#: ../../management.rst:95
-# 4509004a0c73478ca0a184d142eb4a57
+#: ../../management.rst:75
+# b3e40262a34d4590bed84b8d5fc62798
 msgid "listSecurityGroups"
 msgstr ""
 
-#: ../../management.rst:99
-# fd868f656abb4c0fb6f87da360511519
+#: ../../management.rst:77
+# e8f6e365e1da4b499d6b852d6c3e1162
 msgid "listLoadBalancerRules"
 msgstr ""
 
-#: ../../management.rst:103
-# e65694d6fab44e9d946a5866f926091c
+#: ../../management.rst:79
+# 3c8faeeede5147fb911f022fd5858210
 msgid "listProjects"
 msgstr ""
 
-#: ../../management.rst:107
-# 830852c2a7c84d06b6c01a444f0b1b66
+#: ../../management.rst:81
+# a9805315805e4d75b977c3428bcde48a
 msgid "listVPCs"
 msgstr ""
 
-#: ../../management.rst:111
-# 9f2367d8d4df4802bb1c90dcd52a411f
+#: ../../management.rst:83
+# bfab0c32d8364cd9a3e762e7992888f1
 msgid "listNetworkACLs"
 msgstr ""
 
-#: ../../management.rst:115
-# 8afa8bc38679406e95930eda004cc27b
+#: ../../management.rst:85
+# 46fab81fefa1469eb87698342b0f045e
 msgid "listStaticRoutes"
 msgstr ""
 
-#: ../../management.rst:119
-# 073cb1458dc443a1b9e2e791e168eafe
+#: ../../management.rst:89
+# 489808dcb1c9407cbe2bd271c02ce89a
 msgid "Reporting CPU Sockets"
 msgstr ""
 
-#: ../../management.rst:121
-# d3bc3b48bddd4f228b7fde7ad5520fd3
+#: ../../management.rst:91
+# 7d8f4e987714451e9db1c9e749f8b1ca
 msgid "PRODUCT manages different types of hosts that contains one or more physical CPU sockets. CPU socket is considered as a unit of measure used for licensing and billing cloud infrastructure. PRODUCT provides both UI and API support to collect the CPU socket statistics for billing purpose. The Infrastructure tab has a new tab for CPU sockets. You can view the statistics for CPU sockets managed by PRODUCT, which in turn reflects the size of the cloud. The CPU Socket page will give you the number of hosts and sockets used for each host type."
 msgstr ""
 
-#: ../../management.rst:130
-# 179f99e5b8df40a1ba2a0197f6341be2
+#: ../../management.rst:100
+# dec087784ccd48c49189c3f0ed1811a9
 msgid "Log in to the PRODUCT UI."
 msgstr ""
 
-#: ../../management.rst:132
-# 57d62b4d9b054608adfe2e064e3dd8f8
+#: ../../management.rst:102
+# 012d9d141d8745a48fd182b1cab1f8f1
 msgid "In the left navigation bar, click Infrastructure."
 msgstr ""
 
-#: ../../management.rst:134
-# 8e60a5440ac44537a259df5ffe6c34a6
+#: ../../management.rst:104
+# 991d040f4ccc467f87019591608beea8
 msgid "On CPU Sockets, click View all."
 msgstr ""
 
-#: ../../management.rst:136
-# 1ae3d6da93ee4bbd939915b25643adf5
+#: ../../management.rst:106
+# 1f3a30df3d8746f291bc00e761d59f3e
 msgid "The CPU Socket page is displayed. The page shows the number of hosts and CPU sockets based on hypervisor types."
 msgstr ""
 
-#: ../../management.rst:141
-# 4478c2a6941346c4a839b782797026a0
+#: ../../management.rst:111
+# 3d662bf06abc42bd951d16844faada76
 msgid "Changing the Database Configuration"
 msgstr ""
 
-#: ../../management.rst:143
-# b70d57ac66ee464eae4b05c578e89c8e
+#: ../../management.rst:113
+# 638ca3cbc00844789edafb4eb0e60df5
 msgid "The CloudStack Management Server stores database configuration information (e.g., hostname, port, credentials) in the file ``/etc/cloudstack/management/db.properties``. To effect a change, edit this file on each Management Server, then restart the Management Server."
 msgstr ""
 
-#: ../../management.rst:149
-# d69ee7ee9b9646d7a8a016fccc2db9e4
+#: ../../management.rst:119
+# a0530bddfe5a47a69ac27ef0a2c38a2e
 msgid "Changing the Database Password"
 msgstr ""
 
-#: ../../management.rst:151
-# d84602682dbf4f349b1478edbbf567d1
+#: ../../management.rst:121
+# 6ede044a32ac422baed2cd80afc2e114
 msgid "You may need to change the password for the MySQL account used by CloudStack. If so, you'll need to change the password in MySQL, and then add the encrypted password to ``/etc/cloudstack/management/db.properties``."
 msgstr ""
 
-#: ../../management.rst:158
-# 46979db784d447698778e73ecb8eaf02
+#: ../../management.rst:126
+# 803fea7347b74457808913e8d34560e4
 msgid "Before changing the password, you'll need to stop CloudStack's management server and the usage engine if you've deployed that component."
 msgstr ""
 
-#: ../../management.rst:169
-# 530bd78524724552bfa1d927234ca3b7
+#: ../../management.rst:135
+# 83b051e006ce4a898817788447a54253
 msgid "Next, you'll update the password for the CloudStack user on the MySQL server."
 msgstr ""
 
-#: ../../management.rst:176
-# 342e9a0cf7114011a7a6e9909df7a65a
+#: ../../management.rst:142
+# a6ed0f9a1e5f41d9883e8ab8e6ed7157
 msgid "At the MySQL shell, you'll change the password and flush privileges:"
 msgstr ""
 
-#: ../../management.rst:186
-# c906e56dd67a40f9a09b8fd0c69cca61
+#: ../../management.rst:150
+# 5042ed8fa23b4aa6bf244fb7e8d21d0b
 msgid "The next step is to encrypt the password and copy the encrypted password to CloudStack's database configuration (``/etc/cloudstack/management/db.properties``)."
 msgstr ""
 
-#: ../../management.rst:195
-# 966a4c741fcc455d95a07582cd1148e2
+#: ../../management.rst:160
+# 08fe5ba4a2844019b7c34948af80d3e9
 msgid "File encryption type"
 msgstr ""
 
-#: ../../management.rst:197
-# 6b56e1a2563f4b379240d045e9066699
+#: ../../management.rst:162
+# a985e48a20754561ae6daee44e6d79a8
 msgid "Note that this is for the file encryption type. If you're using the web encryption type then you'll use password=\"management\\_server\\_secret\\_key\""
 msgstr ""
 
-#: ../../management.rst:203
-# 12e8a0b52c124abfa87ae48dfc2bef1f
+#: ../../management.rst:166
+# 41348185b9bc4aa59d47266350f37bea
 msgid "Now, you'll update ``/etc/cloudstack/management/db.properties`` with the new ciphertext. Open ``/etc/cloudstack/management/db.properties`` in a text editor, and update these parameters:"
 msgstr ""
 
-#: ../../management.rst:214
-# 05fa3e47277c4963819e7b9d1ac941db
+#: ../../management.rst:175
+# 3224048da0604d5e8ff7b22550451ce5
 msgid "After copying the new password over, you can now start CloudStack (and the usage engine, if necessary)."
 msgstr ""
 
-#: ../../management.rst:223
-# ab0e0b55f2304115bfd6653d5a7e0dd9
+#: ../../management.rst:185
+# b42158e718f44c4ab881833d2dbc0929
 msgid "Administrator Alerts"
 msgstr ""
 
-#: ../../management.rst:225
-# 4fc127299b7e4745978235d4354bbccb
+#: ../../management.rst:187
+# f35a6a1c63244c84b73055d401027bf8
 msgid "The system provides alerts and events to help with the management of the cloud. Alerts are notices to an administrator, generally delivered by e-mail, notifying the administrator that an error has occurred in the cloud. Alert behavior is configurable."
 msgstr ""
 
-#: ../../management.rst:230
-# 76ae47fe37774d1483c1b5363a6d4202
+#: ../../management.rst:192
+# ff3195bd128540cca761c8b00697d461
 msgid "Events track all of the user and administrator actions in the cloud. For example, every guest VM start creates an associated event. Events are stored in the Management Server’s database."
 msgstr ""
 
-#: ../../management.rst:234
-# a1e3c013206f4c6ab4e6995a41e2fb3b
+#: ../../management.rst:196
+# 6b6c7d267ebc4ecdba5787f75ed95d52
 msgid "Emails will be sent to administrators under the following circumstances:"
 msgstr ""
 
-#: ../../management.rst:238
-# 3bd4b2bfb7784f4c85a053970508cc79
+#: ../../management.rst:198
+# 239b319d590244788e6be621087e695a
 msgid "The Management Server cluster runs low on CPU, memory, or storage resources"
 msgstr ""
 
-#: ../../management.rst:243
-# b200b975c0a74ffcba301baf70b4cbee
+#: ../../management.rst:201
+# 11bbb0a3f5de4024ac7e944c1603e026
 msgid "The Management Server loses heartbeat from a Host for more than 3 minutes"
 msgstr ""
 
-#: ../../management.rst:248
-# ccb116becdc34d05b675e0dd815eb45f
+#: ../../management.rst:204
+# f6a69a83f8bb45a193d273cbd63ac7bd
 msgid "The Host cluster runs low on CPU, memory, or storage resources"
 msgstr ""
 
-#: ../../management.rst:251
-# 34703bd556ff4860a1b4276a8c595679
+#: ../../management.rst:208
+# 267b4ae8b12e42d69f646aa22992388d
 msgid "Sending Alerts to External SNMP and Syslog Managers"
 msgstr ""
 
-#: ../../management.rst:253
-# 2cd893dc03494c9f9d2e89a38be1365e
+#: ../../management.rst:210
+# 030acb1fc907414196ead65866a918b0
 msgid "In addition to showing administrator alerts on the Dashboard in the CloudStack UI and sending them in email, CloudStack can also send the same alerts to external SNMP or Syslog management software. This is useful if you prefer to use an SNMP or Syslog manager to monitor your cloud."
 msgstr ""
 
-#: ../../management.rst:259
-# 183fd5a09ba94d239b50995e39c6d1bb
+#: ../../management.rst:216
+# ae64dcb892834822b7480195c2882a8c
 msgid "The alerts which can be sent are:"
 msgstr ""
 
-#: ../../management.rst:261
-# 9c0f28eb90514f2885638a6cc4c911d0
+#: ../../management.rst:218
+# 814ff89fb6f444fc96a8b87a532bc28f
 msgid "The following is the list of alert type numbers. The current alerts can be found by calling listAlerts."
 msgstr ""
 
-#: ../../management.rst:373
-# fcd80afc6c874d05a553c2385a73b1de
+#: ../../management.rst:330
+# cac2d1c9d3a34cb29f25fc81630f96dc
 msgid "You can also display the most up to date list by calling the API command ``listAlerts``."
 msgstr ""
 
-#: ../../management.rst:376
-# 55bd3cff1d234d10b6874e5bd2208730
+#: ../../management.rst:334
+# 0ead10e6a3664baf84b6199d70dfb243
 msgid "SNMP Alert Details"
 msgstr ""
 
-#: ../../management.rst:378
-# b7f474def21a45019ad42f1dcb03434e
+#: ../../management.rst:336
+# 77c8d073d21f41859f495f2b0120f7ef
 msgid "The supported protocol is SNMP version 2."
 msgstr ""
 
-#: ../../management.rst:380
-# 93853f006fe94159a30cfacd98bacaef
+#: ../../management.rst:338
+# 164535e01fe54071916fc21626d662af
 msgid "Each SNMP trap contains the following information: message, podId, dataCenterId, clusterId, and generationTime."
 msgstr ""
 
-#: ../../management.rst:384
-# 7b720e085e5a440280e905349f42fd5e
+#: ../../management.rst:343
+# be99b465676b4d13ae21a9bd33ff94ef
 msgid "Syslog Alert Details"
 msgstr ""
 
-#: ../../management.rst:386
-# 632fd4dd34df40eaab1b80869ea0ef29
+#: ../../management.rst:345
+# 653fb8fc18ea4f17ab01fe630ed6783b
 msgid "CloudStack generates a syslog message for every alert. Each syslog message incudes the fields alertType, message, podId, dataCenterId, and clusterId, in the following format. If any field does not have a valid value, it will not be included."
 msgstr ""
 
-#: ../../management.rst:395
-# 16294475b8e9426f92abe561d0af9d18
+#: ../../management.rst:354
+# 7c74aa344fe948a39e5bff24928b78fa
 msgid "For example:"
 msgstr ""
 
-#: ../../management.rst:402
-# 033011aa33934bbea10d0f9348ad5744
+#: ../../management.rst:361
+# b3bcf49651e44cc189085099c9309174
 msgid "Configuring SNMP and Syslog Managers"
 msgstr ""
 
-#: ../../management.rst:404
-# 6c85d75e087e497288d50df030ecea6f
+#: ../../management.rst:363
+# b5638ebd1bd5442ab77995897186ed0c
 msgid "To configure one or more SNMP managers or Syslog managers to receive alerts from CloudStack:"
 msgstr ""
 
-#: ../../management.rst:409
-# c688dbbc722f42a5be3cb7cec4b0b7e8
+#: ../../management.rst:366
+# 377884390b154436a6ce3913008b664c
 msgid "For an SNMP manager, install the CloudStack MIB file on your SNMP manager system. This maps the SNMP OIDs to trap types that can be more easily read by users. The file must be publicly available. For more information on how to install this file, consult the documentation provided with the SNMP manager."
 msgstr ""
 
-#: ../../management.rst:417
-# b89ad48e4ed84c129f21d619c068d364
+#: ../../management.rst:372
+# a32632406531434cbf5c4c261b1f69b6
 msgid "Edit the file /etc/cloudstack/management/log4j-cloud.xml."
 msgstr ""
 
-#: ../../management.rst:425
-# 4b3128207e8349a9ad7401fc69b17a2b
+#: ../../management.rst:378
+# 8ba1745b7c924d888e2595a379d2db32
 msgid "Add an entry using the syntax shown below. Follow the appropriate example depending on whether you are adding an SNMP manager or a Syslog manager. To specify multiple external managers, separate the IP addresses and other configuration values with commas (,)."
 msgstr ""
 
-#: ../../management.rst:430
-# fd1b4680483c4c89a013cdc0b216cd85
+#: ../../management.rst:384
+# 6cd8468c57974817b400436e8e445394
 msgid "The recommended maximum number of SNMP or Syslog managers is 20 for each."
 msgstr ""
 
-#: ../../management.rst:432
-# e2aaea38ebe14fa09cad5de41d56840f
+#: ../../management.rst:387
+# d399f22c73ea4836a3776bd53493aaf9
 msgid "The following example shows how to configure two SNMP managers at IP addresses 10.1.1.1 and 10.1.1.2. Substitute your own IP addresses, ports, and communities. Do not change the other values (name, threshold, class, and layout values)."
 msgstr ""
 
-#: ../../management.rst:450
-# 3b890460b1ab4e089a42043ac96ead1b
+#: ../../management.rst:405
+# 57b464a769fd4128a163f5613f5f1c96
 msgid "The following example shows how to configure two Syslog managers at IP addresses 10.1.1.1 and 10.1.1.2. Substitute your own IP addresses. You can set Facility to any syslog-defined value, such as LOCAL0 - LOCAL7. Do not change the other values."
 msgstr ""
 
-#: ../../management.rst:468
-# 6519d2611cb9461c9db740d0a6a88955
+#: ../../management.rst:421
+# 9ac4b5f945144653a9fb6df9185afba4
 msgid "If your cloud has multiple Management Server nodes, repeat these steps to edit log4j-cloud.xml on every instance."
 msgstr ""
 
-#: ../../management.rst:473
-# 8f72a4c1d1a8453b87cc53aa201f48b4
+#: ../../management.rst:424
+# d82882ad1f8e447fb1ddbf2141ca0f1e
 msgid "If you have made these changes while the Management Server is running, wait a few minutes for the change to take effect."
 msgstr ""
 
-#: ../../management.rst:476
-# 27c6084b918c4be5af71768e4b0d44db
+#: ../../management.rst:427
+# c74a110e35d5496db9637e208ca69f0c
 msgid "**Troubleshooting:** If no alerts appear at the configured SNMP or Syslog manager after a reasonable amount of time, it is likely that there is an error in the syntax of the <appender> entry in log4j-cloud.xml. Check to be sure that the format and settings are correct."
 msgstr ""
 
-#: ../../management.rst:483
-# 6c4c318782b24c9f8ca91f295b54c425
+#: ../../management.rst:435
+# 6e66a0c8054b4278923a1680c1d13f92
 msgid "Deleting an SNMP or Syslog Manager"
 msgstr ""
 
-#: ../../management.rst:485
-# 333c2a71b97e46b2b464c7febe95676e
+#: ../../management.rst:437
+# daed36b7b2304574be3a327f0fdaae34
 msgid "To remove an external SNMP manager or Syslog manager so that it no longer receives alerts from CloudStack, remove the corresponding entry from the file ``/etc/cloudstack/management/log4j-cloud.xml``."
 msgstr ""
 
-#: ../../management.rst:490
-# 41d170a469ed480ba6aeb1e5fad947d3
+#: ../../management.rst:443
+# 13024d28ec5a4e0d9d54dc264f048c4c
 msgid "Customizing the Network Domain Name"
 msgstr ""
 
-#: ../../management.rst:492
-# 710127df750e46a29414e4b5949fdd84
+#: ../../management.rst:445
+# 47fe94d226e941e8971730847123ac7e
 msgid "The root administrator can optionally assign a custom DNS suffix at the level of a network, account, domain, zone, or entire CloudStack installation, and a domain administrator can do so within their own domain. To specify a custom domain name and put it into effect, follow these steps."
 msgstr ""
 
-#: ../../management.rst:500
-# 987b6416037e4b1ea4964ea02e0857b8
+#: ../../management.rst:451
+# 12a0d889b85a42dfb2f7a37556be8592
 msgid "Set the DNS suffix at the desired scope"
 msgstr ""
 
-#: ../../management.rst:504
-# 4a55e259b9f540b28cdf2a67892b7742
+#: ../../management.rst:453
+# 8f9f57e29f9c404d9930091f8630a427
 msgid "At the network level, the DNS suffix can be assigned through the UI when creating a new network, as described in `“Adding an Additional Guest Network” <networking2#adding-an-additional-guest-network>`_ or with the updateNetwork command in the CloudStack API."
 msgstr ""
 
-#: ../../management.rst:511
-# 9bbd2a476c3946808b3e2adb221d3e39
+#: ../../management.rst:459
+# c091289d2eee46e89ea79afc752a76bf
 msgid "At the account, domain, or zone level, the DNS suffix can be assigned with the appropriate CloudStack API commands: createAccount, editAccount, createDomain, editDomain, createZone, or editZone."
 msgstr ""
 
-#: ../../management.rst:518
-# 96dae8eb905745c4bdd5bd0cdd34a994
+#: ../../management.rst:464
+# 3aa8bfbb66e6499eaf26bd3d496d6bf8
 msgid "At the global level, use the configuration parameter guest.domain.suffix. You can also use the CloudStack API command updateConfiguration. After modifying this global configuration, restart the Management Server to put the new setting into effect."
 msgstr ""
 
-#: ../../management.rst:525
-# 9a8fe7370653486b84e2578fe98f0907
+#: ../../management.rst:469
+# ea55aed82e8440d191210e6219afd4b4
 msgid "To make the new DNS suffix take effect for an existing network, call the CloudStack API command updateNetwork. This step is not necessary when the DNS suffix was specified while creating a new network."
 msgstr ""
 
-#: ../../management.rst:529
-# b990678db82f4ca593bdbf4d333df20e
+#: ../../management.rst:473
+# c4c8780f62264aef9166fb7abb03b23d
 msgid "The source of the network domain that is used depends on the following rules."
 msgstr ""
 
-#: ../../management.rst:534
-# 128ab344160241e0b8edba4e6f9eb6ce
+#: ../../management.rst:476
+# ed54e22f6c384a979fdd24525a23d6f4
 msgid "For all networks, if a network domain is specified as part of a network's own configuration, that value is used."
 msgstr ""
 
-#: ../../management.rst:539
-# 39bda91169304fcbb776da4b1eb65182
+#: ../../management.rst:479
+# b62736506f044912b7508f5bcfca6b0b
 msgid "For an account-specific network, the network domain specified for the account is used. If none is specified, the system looks for a value in the domain, zone, and global configuration, in that order."
 msgstr ""
 
-#: ../../management.rst:545
-# 7e6ca25cc96d442cb4abbcaa1a058fb6
+#: ../../management.rst:483
+# e4424d33ec9549389255552629bbdd2a
 msgid "For a domain-specific network, the network domain specified for the domain is used. If none is specified, the system looks for a value in the zone and global configuration, in that order."
 msgstr ""
 
-#: ../../management.rst:551
-# 3366663c410b4c01bc0ede1967e0057c
+#: ../../management.rst:487
+# 3d1ebf272ba647ef8f54fcd126b4806c
 msgid "For a zone-specific network, the network domain specified for the zone is used. If none is specified, the system looks for a value in the global configuration."
 msgstr ""
 
-#: ../../management.rst:556
-# 574bfe6275184a228bf29c18f7d01f4e
+#: ../../management.rst:493
+# b6795b367f9a4a56bd542d1303ef6706
 msgid "Stopping and Restarting the Management Server"
 msgstr ""
 
-#: ../../management.rst:558
-# 03e70a994f15444d8c76fed8ea185b6c
+#: ../../management.rst:495
+# bbd28a885afc4bd6918951b631b80c85
 msgid "The root administrator will need to stop and restart the Management Server from time to time."
 msgstr ""
 
-#: ../../management.rst:561
-# 03739589fbc44d29b6c184ac61cd2bc1
+#: ../../management.rst:498
+# 0d670244a1804343a1935015f8eaa6fb
 msgid "For example, after changing a global configuration parameter, a restart is required. If you have multiple Management Server nodes, restart all of them to put the new parameter value into effect consistently throughout the cloud.."
 msgstr ""
 
-#: ../../management.rst:566
-# d45ce656da614e40af35f65d5da5b4c4
+#: ../../management.rst:503
+# 180fc3fdda44467f97b04959693747c5
 msgid "To stop the Management Server, issue the following command at the operating system prompt on the Management Server node:"
 msgstr ""
 
-#: ../../management.rst:573
-# d6a59f81a7de46bfba9fc759713e09d5
+#: ../../management.rst:510
+# 02d90290579d496098aed77584f7a2d3
 msgid "To start the Management Server:"
 msgstr ""
 
diff --git a/source/locale/pot/networking.pot b/source/locale/pot/networking.pot
index 64d1056..0c5c206 100644
--- a/source/locale/pot/networking.pot
+++ b/source/locale/pot/networking.pot
@@ -8,7 +8,7 @@
 msgstr ""
 "Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
 "Report-Msgid-Bugs-To: \n"
-"POT-Creation-Date: 2014-03-31 14:08-0400\n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
@@ -17,749 +17,749 @@
 "Content-Transfer-Encoding: 8bit\n"
 
 #: ../../networking.rst:18
-# 378fc355da2a4f7d8546a95fd9b3f5dc
+# e178ac0be7b0492e8a2edc6ed9be7a7b
 msgid "Setting Up Networking for Users"
 msgstr ""
 
 #: ../../networking.rst:21
-# 17e4cb5cdf264aa19e3578731bf842c4
+# 04f3cd2def1648f2a118dc72cdd5a592
 msgid "Overview of Setting Up Networking for Users"
 msgstr ""
 
 #: ../../networking.rst:23
-# 96d37a14970944b58909ecaace082018
+# 60188130ecb74037bd537749bcaf4750
 msgid "People using cloud infrastructure have a variety of needs and preferences when it comes to the networking services provided by the cloud. As a CloudStack administrator, you can do the following things to set up networking for your users:"
 msgstr ""
 
-#: ../../networking.rst:30
-# 3db74da31e2046a8908c67bf3c665472
+#: ../../networking.rst:28
+# fb8952bb97144229abe5a477941ae76a
 msgid "Set up physical networks in zones"
 msgstr ""
 
-#: ../../networking.rst:34
-# 94e40111c3614cebb720933c53c016bb
+#: ../../networking.rst:30
+# 8dd6941ef2c54c6bbabf956d9eb0680a
 msgid "Set up several different providers for the same service on a single physical network (for example, both Cisco and Juniper firewalls)"
 msgstr ""
 
-#: ../../networking.rst:39
-# f7ee99dc067d4b129ec339cb1799e0cd
+#: ../../networking.rst:33
+# d4c8d144d71e47c7b10f71c182941308
 msgid "Bundle different types of network services into network offerings, so users can choose the desired network services for any given virtual machine"
 msgstr ""
 
-#: ../../networking.rst:45
-# c5a8692df93942eca2c97aa1872928c6
+#: ../../networking.rst:37
+# f5309ffd41a14f77a9dd77113c106332
 msgid "Add new network offerings as time goes on so end users can upgrade to a better class of service on their network"
 msgstr ""
 
-#: ../../networking.rst:50
-# f11d70f72e114c728425a80bf2c162c5
+#: ../../networking.rst:40
+# 13b07adc896a416793148e27ab919b13
 msgid "Provide more ways for a network to be accessed by a user, such as through a project of which the user is a member"
 msgstr ""
 
-#: ../../networking.rst:54
-# aa05ae98bb2a4229a3c0478a99a39fe6
+#: ../../networking.rst:45
+# 75c4f2f501724f68be26715201e81f13
 msgid "About Virtual Networks"
 msgstr ""
 
-#: ../../networking.rst:56
-# a08bd43e29f54560ba910cb343eb5f53
+#: ../../networking.rst:47
+# 6e8b5c92233f49618f96673822e130e6
 msgid "A virtual network is a logical construct that enables multi-tenancy on a single physical network. In CloudStack a virtual network can be shared or isolated."
 msgstr ""
 
-#: ../../networking.rst:61
-# d1784c41349f444cbaaffea5119ee4bf
+#: ../../networking.rst:53
+# e96b2f098a274b148edc9883c7424a27
 msgid "Isolated Networks"
 msgstr ""
 
-#: ../../networking.rst:63
-# db4418e95acd4fa69374025ca81020cb
+#: ../../networking.rst:55
+# 3358619f0382468a9d2f2aea99522408
 msgid "An isolated network can be accessed only by virtual machines of a single account. Isolated networks have the following properties."
 msgstr ""
 
-#: ../../networking.rst:68
-# 554e4288f8524114a4bcf6da37435d19
+#: ../../networking.rst:58
+# c84b0ce76be64977bad2361a036a55cf
 msgid "Resources such as VLAN are allocated and garbage collected dynamically"
 msgstr ""
 
-#: ../../networking.rst:73
-# 55a8c8a3a194402a9e55453f2ec86253
+#: ../../networking.rst:61
+# 3eb29ededba94d0dbcb168491b1acda6
 msgid "There is one network offering for the entire network"
 msgstr ""
 
-#: ../../networking.rst:77
-# 6da623bb1302444ebd2054fdbf1743b7
+#: ../../networking.rst:63
+# ff059c44a53e4765b488337444f9fd70
 msgid "The network offering can be upgraded or downgraded but it is for the entire network"
 msgstr ""
 
-#: ../../networking.rst:80
-# c3f3fb10b1b84b56b1a7c5c1d57144f7
+#: ../../networking.rst:66
+# d147367777724c05a61626c7756aae05
 msgid "For more information, see `“Configure Guest Traffic in an Advanced Zone” <networking2.html#configure-guest-traffic-in-an-advanced-zone>`_."
 msgstr ""
 
-#: ../../networking.rst:83
-# 774c3f3c464645b68e37c9d0558753fc
+#: ../../networking.rst:71
+# 9cb58dfba63248058b6e4c2370250e1f
 msgid "Shared Networks"
 msgstr ""
 
-#: ../../networking.rst:85
-# a3d1aa420b2e4d5b9d13ffb9fc397614
+#: ../../networking.rst:73
+# 4b159336d5054af78283deb65966e56d
 msgid "A shared network can be accessed by virtual machines that belong to many different accounts. Network Isolation on shared networks is accomplished by using techniques such as security groups, which is supported only in Basic zones in CloudStack 3.0.3 and later versions."
 msgstr ""
 
-#: ../../networking.rst:92
-# 0046613bd7254cef901e0515e4a83759
+#: ../../networking.rst:78
+# 0eed59cfbc8447e98bc84e58489e3ae7
 msgid "Shared Networks are created by the administrator"
 msgstr ""
 
-#: ../../networking.rst:96
-# 4f8d81c8a66e42688826ed6e2e945dcb
+#: ../../networking.rst:80
+# b29eadf838f449549e16a2e745f711af
 msgid "Shared Networks can be designated to a certain domain"
 msgstr ""
 
-#: ../../networking.rst:100
-# ed54831a452d415eaadb8ceee4586eca
+#: ../../networking.rst:82
+# 956864b9c95e4fb98178b4a0ad4918d3
 msgid "Shared Network resources such as VLAN and physical network that it maps to are designated by the administrator"
 msgstr ""
 
-#: ../../networking.rst:105
-# da3c9bed2af34e42a36b14d2b5ff6541
+#: ../../networking.rst:85
+# a9b84145482e4171bdf228084a5d51f4
 msgid "Shared Networks can be isolated by security groups"
 msgstr ""
 
-#: ../../networking.rst:109
-# 0b46085b309e4593b1de03c7e4b4bf9c
+#: ../../networking.rst:87
+# 345abc742c6749aeb975b3453c70c387
 msgid "Public Network is a shared network that is not shown to the end users"
 msgstr ""
 
-#: ../../networking.rst:113
-# 44ffaf3770314f4c887d620f8aca1f78
+#: ../../networking.rst:89
+# 743e27f0ef1d415180cce8da2bb79724
 msgid "Source NAT per zone is not supported in Shared Network when the service provider is virtual router. However, Source NAT per account is supported. For information, see `“Configuring a Shared Guest Network” <networking2.html#configuring-a-shared-guest-network>`_."
 msgstr ""
 
-#: ../../networking.rst:119
-# f6678b56239e4ca6bde83febb7adfae4
+#: ../../networking.rst:96
+# dfed0497ec374d71927a32da736f6b28
 msgid "Runtime Allocation of Virtual Network Resources"
 msgstr ""
 
-#: ../../networking.rst:121
-# e38a78ac1a6049de83a965db1b35dae3
+#: ../../networking.rst:98
+# 33c1cc37caa3449d8a22888ee5706153
 msgid "When you define a new virtual network, all your settings for that network are stored in CloudStack. The actual network resources are activated only when the first virtual machine starts in the network. When all virtual machines have left the virtual network, the network resources are garbage collected so they can be allocated again. This helps to conserve network resources."
 msgstr ""
 
-#: ../../networking.rst:129
-# 8ab8ea2db95d4c4f810705a814fb93b9
+#: ../../networking.rst:107
+# c7699333b3c747f09b34f3a541caa725
 msgid "Network Service Providers"
 msgstr ""
 
-#: ../../networking.rst:132
-# d6ce8ef140484edcb8039a76dc385b9e
+#: ../../networking.rst:110
+# 90bd799fd2444d978136f72070afd1ca
 msgid "For the most up-to-date list of supported network service providers, see the CloudStack UI or call `listNetworkServiceProviders`."
 msgstr ""
 
-#: ../../networking.rst:134
-# 1cbf32a3d9944d6f8bb5bd6c44f80f49
+#: ../../networking.rst:113
+# 3f97bb088f7240d99034a78ca6adf65f
 msgid "A service provider (also called a network element) is hardware or virtual appliance that makes a network service possible; for example, a firewall appliance can be installed in the cloud to provide firewall service. On a single network, multiple providers can provide the same network service. For example, a firewall service may be provided by Cisco or Juniper devices in the same physical network."
 msgstr ""
 
-#: ../../networking.rst:141
-# 8f25fd00ebd8421db4c8b732bc40daf3
+#: ../../networking.rst:120
+# e52ed5139a664c31acccd845de73897d
 msgid "You can have multiple instances of the same service provider in a network (say, more than one Juniper SRX device)."
 msgstr ""
 
-#: ../../networking.rst:144
-# c16afb129f964ce0b4f26b864fc15cfb
+#: ../../networking.rst:123
+# 013a36e42a254aaa98b7e3ad9ea97db8
 msgid "If different providers are set up to provide the same service on the network, the administrator can create network offerings so users can specify which network service provider they prefer (along with the other choices offered in network offerings). Otherwise, CloudStack will choose which provider to use whenever the service is called for."
 msgstr ""
 
-#: ../../networking.rst:150
-# 54e114cc45464476b77ca5d8de1ce4bb
+#: ../../networking.rst:129
+# eb5e7f69942b448f906dc822400a348c
 msgid "*Supported Network Service Providers*"
 msgstr ""
 
-#: ../../networking.rst:152
-# 3d10447bdf2c432586a4e5610ae5ab5e
+#: ../../networking.rst:131
+# d43ecfbdacb84dac9d6ffe5229f277a3
 msgid "CloudStack ships with an internal list of the supported service providers, and you can choose from this list when creating a network offering."
 msgstr ""
 
-#: ../../networking.rst:157
-# e743e99990144f939fc3a63349774ce0
+#: ../../networking.rst:136
+# 5dd3d24c6aa149cd8be77c9e90e924fa
 msgid "Virtual Router"
 msgstr ""
 
-#: ../../networking.rst:157
-# f79fe8d0744940bfa69f362edb14c35f
+#: ../../networking.rst:136
+# 8f9be66568214ef19761bdd0b1e87a0a
 msgid "Citrix NetScaler"
 msgstr ""
 
-#: ../../networking.rst:157
-# d86abf81c8de465b9cede26a7720dace
+#: ../../networking.rst:136
+# dccb0ff066124e7ca8f1f4b1df9b566a
 msgid "Juniper SRX"
 msgstr ""
 
-#: ../../networking.rst:157
-# 023e0ba83f2f413890cf4eac19ab30fc
+#: ../../networking.rst:136
+# b6c9b2cf119641999eeded8e8069824f
 msgid "F5 BigIP"
 msgstr ""
 
-#: ../../networking.rst:157
-# 4cc8fae5e06d4938a3d6777a1f49b7ef
+#: ../../networking.rst:136
+# 4eec0320581e47cea2b8b9a6eb5c5b70
 msgid "Host based (KVM/Xen)"
 msgstr ""
 
-#: ../../networking.rst:160
-# 538c6cf7488a4cf1b2790816cb3796d3
+#: ../../networking.rst:139
+# 2c2f1239e908471a929feb91a02e08dd
 msgid "Remote Access VPN"
 msgstr ""
 
-#: ../../networking.rst:160
-#: ../../networking.rst:162
-#: ../../networking.rst:164
-#: ../../networking.rst:164
-#: ../../networking.rst:166
-#: ../../networking.rst:166
-#: ../../networking.rst:166
-#: ../../networking.rst:168
-#: ../../networking.rst:170
-#: ../../networking.rst:172
-#: ../../networking.rst:172
-#: ../../networking.rst:174
-#: ../../networking.rst:174
-#: ../../networking.rst:174
-#: ../../networking.rst:176
-#: ../../networking.rst:176
-# 9d3882428ce14164ae21556dd4f71980
-# 9f18b0853a44447f9f9a8c1e8f154ad5
-# e0be26ab6fad4753893deb50337a6730
-# 7aa2d2ff8735493a9a3a6b5eb8d46f1d
-# 65fb94ad60864e47837bd7097c7e950b
-# c98aa239bbbf48af9ab5709b1ce4d85f
-# 1fdc23d97e81478caf0d9a4ddc729069
-# 024d3b3a60ca47228a4cbd600dccbe1f
-# 71139b53fe904bd4a018ae8097a371d1
-# c9f2815cd2864ed9be683e676444d21e
-# f5651ed2f2a74438a882ca58fa5379c4
-# b803d31092d74127a0d71cf5ec01e6de
-# f0378ae48126424bb889176fd22f0f26
-# 5c6b625d8fd64373a5a58eb8be434d7d
-# a5a7cbf6009341a5970e96d746a90485
-# 4093e40696754637b985dac12d3c3a9d
+#: ../../networking.rst:139
+#: ../../networking.rst:141
+#: ../../networking.rst:143
+#: ../../networking.rst:143
+#: ../../networking.rst:145
+#: ../../networking.rst:145
+#: ../../networking.rst:145
+#: ../../networking.rst:147
+#: ../../networking.rst:149
+#: ../../networking.rst:151
+#: ../../networking.rst:151
+#: ../../networking.rst:153
+#: ../../networking.rst:153
+#: ../../networking.rst:153
+#: ../../networking.rst:155
+#: ../../networking.rst:155
+# 3ae9d08f24164c359e5553b13dd96db0
+# 0c7c9adabf9449babcb4553e3a59b52b
+# 411fef44341e42758013621c4a23b6b6
+# 6c934e881e7849368f5400433ea69f81
+# 1fc336068db6481183d8a01c5746f5e0
+# 8a397af8cc344e41b52173b2d9bce329
+# 8a7faf6012614a33a03fce7b63e06032
+# f4b01e6ad27f435bbe4aa4b14adc6cd9
+# 60fc90d0645a4e70a2b43c269d7d92ab
+# 72abbb0d60bb43e7ac7ca73f206aa8dd
+# 3f6508ced2f04ac2adcd337ac022d6b0
+# 5492ba67a1304fdb9b75910ef384ac85
+# 1b2c1c6af0814e59bd1d64623dec20d6
+# 76efa1585e2241eaaae3e5a45da37007
+# 933c860bae084ab4846ad9f7270712aa
+# c38c824dc105481f82f564a1071efb74
 msgid "Yes"
 msgstr ""
 
-#: ../../networking.rst:160
-#: ../../networking.rst:160
-#: ../../networking.rst:160
-#: ../../networking.rst:160
-#: ../../networking.rst:162
-#: ../../networking.rst:162
-#: ../../networking.rst:162
-#: ../../networking.rst:162
-#: ../../networking.rst:164
-#: ../../networking.rst:164
-#: ../../networking.rst:164
-#: ../../networking.rst:166
-#: ../../networking.rst:166
-#: ../../networking.rst:168
-#: ../../networking.rst:168
-#: ../../networking.rst:168
-#: ../../networking.rst:168
-#: ../../networking.rst:170
-#: ../../networking.rst:170
-#: ../../networking.rst:170
-#: ../../networking.rst:170
-#: ../../networking.rst:172
-#: ../../networking.rst:172
-#: ../../networking.rst:172
-#: ../../networking.rst:174
-#: ../../networking.rst:174
-#: ../../networking.rst:176
-#: ../../networking.rst:176
-#: ../../networking.rst:176
-# cf6cd7e627894bb399d4b2a2e8935730
-# c3739de5a9764c0ab1a9eec12242ba2f
-# b9904b520f854271863c5edcd444465b
-# d6acc1800a59467cb6b4a593f7406d73
-# 47da62cd78544702b598db9bfa70aa28
-# 8b8bcaa926154fa8a8da6ebe379fecc0
-# aaffd78d2bd642cb86e191db5ed57113
-# eb30654a90c149bcb276e1dbdf484b74
-# 9e327f9dff554171807add97cd2d1086
-# b0c5b421a56f45dc914f8da460b23bbc
-# 511fe014c5594bdea7000aaf6d83bfdd
-# 78332347e8df424599c7e2ae65ffdfe5
-# d61f0398e7c64d2b938caf47076f9b33
-# 9f358aeca54544e79a112777b0be0386
-# 8dc5b57a7f834fa1897d63f2d907cca3
-# 5e6786c934114eafba47a9285f24c1a3
-# 4bc2d4a340ab4e3285bb620d3f3f7cae
-# 8afc553c7dfb446dab37feab5d539e84
-# c6d4fcc0d2e24f26993278c0224e9a2a
-# b8ce0003e3dd4d43b1f2509c03ff2456
-# 68be8c9eb09c4f56ae0a82896449d23e
-# 8a22ab4b1b144f7c81adf05c887c7d30
-# 990514caa33a45b8aa649b0f23afcccd
-# adcbfe0ed8f84271af55d6e2e9042250
-# 0f0d09b47b7742bc8039484cf91cc212
-# a5faef20128445dcbffe80d358fa2f2e
-# 3abe142c737841929ddfd4c25902d9a2
-# 3f06f8c6b0844269a865cbe05fed4dbb
-# 56624add510a4e4e96cc0fbb740e66b9
+#: ../../networking.rst:139
+#: ../../networking.rst:139
+#: ../../networking.rst:139
+#: ../../networking.rst:139
+#: ../../networking.rst:141
+#: ../../networking.rst:141
+#: ../../networking.rst:141
+#: ../../networking.rst:141
+#: ../../networking.rst:143
+#: ../../networking.rst:143
+#: ../../networking.rst:143
+#: ../../networking.rst:145
+#: ../../networking.rst:145
+#: ../../networking.rst:147
+#: ../../networking.rst:147
+#: ../../networking.rst:147
+#: ../../networking.rst:147
+#: ../../networking.rst:149
+#: ../../networking.rst:149
+#: ../../networking.rst:149
+#: ../../networking.rst:149
+#: ../../networking.rst:151
+#: ../../networking.rst:151
+#: ../../networking.rst:151
+#: ../../networking.rst:153
+#: ../../networking.rst:153
+#: ../../networking.rst:155
+#: ../../networking.rst:155
+#: ../../networking.rst:155
+# d7b2c2af7ecd47769b0c7bb3013e1bbd
+# beb488a16e4646b3aa87280ad9216415
+# ad48bd439e3148fa94443e2df8acd5a1
+# 5151e216286b45c3b574d6658543a92c
+# ebc177c1de7040e687bb410d7c258141
+# c4efe853b93e471b814a74e0ed31f17d
+# e8ffc6413ca549d69b9a74e6508574d1
+# 8245b2e9c1934761a766679012c0a805
+# 16ec8446477c4c68aabd30136ee67fc0
+# 8a8f9ec35bea40f1853aba71a675887e
+# ec884b7505904c66b59ae39b287f3682
+# a1222a93d01240518b5a74fc57aee793
+# e4317cd2542d43ab90a5f054e18a7e58
+# 82eb13cd8e6a4c14828982cb7c145778
+# fdceedef2f9e43bbbb62a4fb09483cf2
+# 10e8e962affb46bd999d66cae4c189c0
+# 0c5c555a0d3748ac9a84b51b0aaff10a
+# 07903eb7e9fc46fbb91c64c77357409f
+# 98c2b214043b41dea4181a3d1d4726d8
+# ce61ff1d67ff4e90a5a5a722d0fef5f0
+# ded424a7c1b345f398e02e70edea8a5a
+# 9feb3d9ea53b45c5a8e95492710b7124
+# 562866fe2ede4c5f838067549ca5b4bd
+# f21d80c3b07e4fd69b54807235ed3cdb
+# e2d5fa4c2d874e8e90d4022e41f6a3ef
+# 4f7bcdd07de343638f1983951581d2a9
+# 6491fc2c462b4ae5ace77aa2cb534435
+# 248462887faa478ab6a39350b06d8262
+# 5f0d4dc5583a4a2eab7336f826b54b67
 msgid "No"
 msgstr ""
 
-#: ../../networking.rst:162
-# e4a4c959124946818756ed66cb87561f
+#: ../../networking.rst:141
+# ab9d28c06dcf43d6b43310410d730272
 msgid "DNS/DHCP/User Data"
 msgstr ""
 
-#: ../../networking.rst:164
-#: ../../networking.rst:213
-#: ../../networking.rst:347
-# 8fa7de81857c47bf95dbb457c47ad0ee
-# 3ee09c09bfb4473d97f2902efd5a8dc2
-# 19c378b323184814a5616bd38baac90d
+#: ../../networking.rst:143
+#: ../../networking.rst:180
+#: ../../networking.rst:288
+# ec9a836945d54daa80b2790549b0e124
+# 98b80ddeb60c417e839a5e695b989f52
+# 155333ae90b64d45959ef29649a45d44
 msgid "Firewall"
 msgstr ""
 
-#: ../../networking.rst:166
-#: ../../networking.rst:209
-# cee9dbc5210747198f81a673f44a12f9
-# f948b5d0102c45b59800ce77524e1e61
+#: ../../networking.rst:145
+#: ../../networking.rst:178
+# ec3524d24a7c47479fbc5f696c94c8ba
+# 5d871878b8f6400babacd35334ff571b
 msgid "Load Balancing"
 msgstr ""
 
-#: ../../networking.rst:168
-# 5a07c7f449494ff6863e789adde970a6
+#: ../../networking.rst:147
+# e9f00e30da4347368893885b9ebf0951
 msgid "Elastic IP"
 msgstr ""
 
-#: ../../networking.rst:170
-# 10fe6e755ee449b181436d52a65d114c
+#: ../../networking.rst:149
+# 2665ea2a6b90470e81ee706892bc8f12
 msgid "Elastic LB"
 msgstr ""
 
+#: ../../networking.rst:151
 #: ../../networking.rst:172
-#: ../../networking.rst:197
-#: ../../networking.rst:348
-# f6ab100ea87b42e7ac418826469fbbab
-# 89757ebd8a6a4f00b3c75bf99bc10ee8
-# f84a82fdc1174b07a63be45eb129877b
+#: ../../networking.rst:289
+# b07356b446e34c669846ad2c208ed183
+# 522b28c564644bf68213f95712c5b120
+# 2177095ff4a24da29d588bb4cd3c2f4a
 msgid "Source NAT"
 msgstr ""
 
+#: ../../networking.rst:153
 #: ../../networking.rst:174
-#: ../../networking.rst:201
-#: ../../networking.rst:351
-# bdd8361aec614d1d88b3744f189c4415
-# ad01893a0c484fb091cf1e5d092fdc80
-# b1c7bbe203744800a2b447343c326b1a
+#: ../../networking.rst:292
+# eea6bbfe102d498e8fed5cb73cc69b0d
+# c02a1aa3d43f4cde9668b0c049f5ca68
+# fdd23b4cdd3f4aa4a540bf84253e6a5b
 msgid "Static NAT"
 msgstr ""
 
+#: ../../networking.rst:155
 #: ../../networking.rst:176
-#: ../../networking.rst:205
-#: ../../networking.rst:354
-# 06fc70b280b249f380499674c2c4b04e
-# 8568edfad82b413fadcc6a7f88f09caa
-# 2968ac56dd7343a8aafe6eb21f1fd292
+#: ../../networking.rst:295
+# b4c037f8d0f1486a8b571d432c94dfc2
+# 218d3d03262e42b2aff11ea6d99f0a49
+# 3ec6fc2e436743f7bf4b9704948e4af3
 msgid "Port Forwarding"
 msgstr ""
 
-#: ../../networking.rst:180
-# cbe50c4a0b834778a33a13b921dc6816
+#: ../../networking.rst:160
+# 479f4b962b404a428355bb406c787cd9
 msgid "Network Offerings"
 msgstr ""
 
-#: ../../networking.rst:183
-# 02abde9be17140019afedd547b9803b6
+#: ../../networking.rst:163
+# 25cda5fdd680428d82d9dc0b90b9da3f
 msgid "For the most up-to-date list of supported network services, see the CloudStack UI or call listNetworkServices."
 msgstr ""
 
-#: ../../networking.rst:185
-# ffb8cf5d807844839de681dda6fbac69
+#: ../../networking.rst:166
+# 746c329fee3d40298682a774fc0e1ce0
 msgid "A network offering is a named set of network services, such as:"
 msgstr ""
 
-#: ../../networking.rst:189
-#: ../../networking.rst:342
-# 81bef347f73f480d99fe3b774343e95a
-# 7ac52f84225841a9b0722b7da042b868
+#: ../../networking.rst:168
+#: ../../networking.rst:283
+# 1f84716ebc364d34a628de273bfae124
+# 50ebc53bb5124166b60910b97ac86bc4
 msgid "DHCP"
 msgstr ""
 
-#: ../../networking.rst:193
-#: ../../networking.rst:343
-# e657c892333148a896e62c25f0270de2
-# cb2df25d008a4c8b8dc95cb508b6108d
+#: ../../networking.rst:170
+#: ../../networking.rst:284
+# 883e0ebe77d94552b3e24415615a7bd9
+# 206e31a90b27475a957f3a6347b7e15d
 msgid "DNS"
 msgstr ""
 
-#: ../../networking.rst:217
-#: ../../networking.rst:357
-# 343e51150ca849f9a2fd1732bd5f57ce
-# e17fb858985f47528d2cd7bb3abb2ef2
+#: ../../networking.rst:182
+#: ../../networking.rst:298
+# c7ba4a3ce199420a8e1ffa59b6b5aa77
+# e018337607ad4a9d90fe4ef3ab26189e
 msgid "VPN"
 msgstr ""
 
-#: ../../networking.rst:221
-# 8bd55493dec640089760b46be49c832b
+#: ../../networking.rst:184
+# 0c8566ee7245401e89972f62635febae
 msgid "(Optional) Name one of several available providers to use for a given service, such as Juniper for the firewall"
 msgstr ""
 
-#: ../../networking.rst:226
-# 23bc443c0915486e927b945665f7e8e5
+#: ../../networking.rst:187
+# 010067ad73c94e95ad457ead1a816c4e
 msgid "(Optional) Network tag to specify which physical network to use"
 msgstr ""
 
-#: ../../networking.rst:228
-# a58f1c2f9e4644848265743394fedf70
+#: ../../networking.rst:189
+# 27fc0e1384a041e280aad1d5c6497be1
 msgid "When creating a new VM, the user chooses one of the available network offerings, and that determines which network services the VM can use."
 msgstr ""
 
-#: ../../networking.rst:231
-# ad1942baddc2480e88346f41b83f27ca
+#: ../../networking.rst:192
+# f0629abea4a3489ab43c6616754295d7
 msgid "The CloudStack administrator can create any number of custom network offerings, in addition to the default network offerings provided by CloudStack. By creating multiple custom network offerings, you can set up your cloud to offer different classes of service on a single multi-tenant physical network. For example, while the underlying physical wiring may be the same for two tenants, tenant A may only need simple firewall protection for their website, while tenant B may be running a web server farm and require a scalable firewall solution, load balancing solution, and alternate networks for accessing the database backend."
 msgstr ""
 
-#: ../../networking.rst:243
-# a559cfad18634227802c97abe0c02a8d
+#: ../../networking.rst:204
+# f84d6b9ac9d44d159518d14cc74cef39
 msgid "If you create load balancing rules while using a network service offering that includes an external load balancer device such as NetScaler, and later change the network service offering to one that uses the CloudStack virtual router, you must create a firewall rule on the virtual router for each of your existing load balancing rules so that they continue to function."
 msgstr ""
 
-#: ../../networking.rst:245
-# cbc7fbcc3e6348d3908586739dbdb6f9
+#: ../../networking.rst:211
+# 6a193ad193634184b47093dfab78d48b
 msgid "When creating a new virtual network, the CloudStack administrator chooses which network offering to enable for that network. Each virtual network is associated with one network offering. A virtual network can be upgraded or downgraded by changing its associated network offering. If you do this, be sure to reprogram the physical network to match."
 msgstr ""
 
-#: ../../networking.rst:251
-# 8b73057c0c584686894e081c92eea81b
+#: ../../networking.rst:217
+# 514547d261a44dbba069882e1163a863
 msgid "CloudStack also has internal network offerings for use by CloudStack system VMs. These network offerings are not visible to users but can be modified by administrators."
 msgstr ""
 
-#: ../../networking.rst:256
-# 4d0b8c9601714fac8c47073432d9e949
+#: ../../networking.rst:223
+# 9eab025e1e0b4102aabc5ed825ad3513
 msgid "Creating a New Network Offering"
 msgstr ""
 
-#: ../../networking.rst:258
-# 0fa5ee2229ff43078785d734c21c6b05
+#: ../../networking.rst:225
+# 101c5c58b3164f2d91d7c068fa2ddc13
 msgid "To create a network offering:"
 msgstr ""
 
-#: ../../networking.rst:262
-# 714f4a8335f74b50b2b380ea0835002c
+#: ../../networking.rst:227
+# ad144ea208224f0ba8bfd3d268ebaa1a
 msgid "Log in with admin privileges to the CloudStack UI."
 msgstr ""
 
-#: ../../networking.rst:266
-# 64031cf3f054467b9761f61d4c992bbc
+#: ../../networking.rst:229
+# 7183c1c87f1e4a549609755e3b609e22
 msgid "In the left navigation bar, click Service Offerings."
 msgstr ""
 
-#: ../../networking.rst:270
-# 2101d4a328014f82bb6ef04a97fb0ad3
+#: ../../networking.rst:231
+# 22b7bae2bee145399e00d289bccc7917
 msgid "In Select Offering, choose Network Offering."
 msgstr ""
 
-#: ../../networking.rst:274
-# 8bf2efa20d1c4622a49ae4a0b6dcbf05
+#: ../../networking.rst:233
+# ef1169d122904044a6c0246757cbbb46
 msgid "Click Add Network Offering."
 msgstr ""
 
-#: ../../networking.rst:278
-# e8766f68e8ed4da6b03e3af2140b0d80
+#: ../../networking.rst:235
+# 3479c8e9a5ef4f458aa9a86725ea9a15
 msgid "In the dialog, make the following choices:"
 msgstr ""
 
-#: ../../networking.rst:282
-# 75d57bbc650d443d8b718a6cff553561
+#: ../../networking.rst:237
+# b9faa7d006ed43108fcd33897fea3a5f
 msgid "**Name**. Any desired name for the network offering."
 msgstr ""
 
-#: ../../networking.rst:286
-# 7b961fe0b52e4394b4a2a5c534a0281a
+#: ../../networking.rst:239
+# 28d48401d7c74f61a6251f06e8e33ea5
 msgid "**Description**. A short description of the offering that can be displayed to users."
 msgstr ""
 
-#: ../../networking.rst:291
-# b36f9adc538b411399e9bb7eedd9ede1
+#: ../../networking.rst:242
+# a81d203163fd41108b4ed24231b5c84d
 msgid "**Network Rate**. Allowed data transfer rate in MB per second."
 msgstr ""
 
-#: ../../networking.rst:295
-# 9d644252577743f494f2701d3f95b837
+#: ../../networking.rst:244
+# bf34e4c1410c487c81e21d82564c0ceb
 msgid "**Guest Type**. Choose whether the guest network is isolated or shared."
 msgstr ""
 
-#: ../../networking.rst:298
-# f952fc596b554510abfff2e7086d1b47
+#: ../../networking.rst:247
+# 636bbcf4e8ff4e89bc5a3263fa3152fd
 msgid "For a description of this term, see `“About Virtual Networks” <#about-virtual-networks>`_."
 msgstr ""
 
-#: ../../networking.rst:303
-# 4faa7ce7f56d45a0b9b28ab153d54696
+#: ../../networking.rst:250
+# d9e50bd69812476c975c4eb28509a054
 msgid "**Persistent**. Indicate whether the guest network is persistent or not. The network that you can provision without having to deploy a VM on it is termed persistent network. For more information, see `“Persistent Networks” <networking2.html#persistent-networks>`_."
 msgstr ""
 
-#: ../../networking.rst:311
-# e7f9363df01c4b10bca858974859c9f0
+#: ../../networking.rst:256
+# a78fcf61c20941b4a0074b52d456b4fb
 msgid "**Specify VLAN**. (Isolated guest networks only) Indicate whether a VLAN could be specified when this offering is used. If you select this option and later use this network offering while creating a VPC tier or an isolated network, you will be able to specify a VLAN ID for the network you create."
 msgstr ""
 
-#: ../../networking.rst:319
-# 18a5a261ef97492783748484bdd7253e
+#: ../../networking.rst:262
+# 0c356efbc6b1453083e1df0e795cfc3f
 msgid "**VPC**. This option indicate whether the guest network is Virtual Private Cloud-enabled. A Virtual Private Cloud (VPC) is a private, isolated part of CloudStack. A VPC can have its own virtual network topology that resembles a traditional physical network. For more information on VPCs, see `“About Virtual Private Clouds” <networking2.html#about-virtual-private-clouds>`_."
 msgstr ""
 
-#: ../../networking.rst:328
-# 510455b8922645178e4b65ac6ea03074
+#: ../../networking.rst:269
+# 99699a8ca7b8442b9273331bf3721599
 msgid "**Supported Services**. Select one or more of the possible network services. For some services, you must also choose the service provider; for example, if you select Load Balancer, you can choose the CloudStack virtual router or any other load balancers that have been configured in the cloud. Depending on which services you choose, additional fields may appear in the rest of the dialog box."
 msgstr ""
 
-#: ../../networking.rst:336
-# 848c619314564e039dde5bb033f1e105
+#: ../../networking.rst:277
+# 92f1a16c1ffe4ceb84808c9ba972cbd4
 msgid "Based on the guest network type selected, you can see the following supported services:"
 msgstr ""
 
-#: ../../networking.rst:340
-# 067698001bec491d8fc5da16e8cc4977
+#: ../../networking.rst:281
+# 88a57a6470eb454ba571d8fde5632a82
 msgid "Supported Services"
 msgstr ""
 
-#: ../../networking.rst:340
-# 082297be434e4d349883eba64e1823fc
+#: ../../networking.rst:281
+# d4aa55848ef645639458f908896ac697
 msgid "Description"
 msgstr ""
 
-#: ../../networking.rst:340
-# db17d52f55764b76b8435be1ec2074b0
+#: ../../networking.rst:281
+# f8724e6bbae14251ae83b23169d9420f
 msgid "Isolated"
 msgstr ""
 
-#: ../../networking.rst:340
-# 4205e1ffe3b64c5693fdb740cda418af
+#: ../../networking.rst:281
+# 23bd72f8680a493682d6741602166846
 msgid "Shared"
 msgstr ""
 
-#: ../../networking.rst:342
-#: ../../networking.rst:343
-# df8baf4211044f108c91f3f6c0e24f20
-# 698d83cab39d406cb37e6185f6294670
+#: ../../networking.rst:283
+#: ../../networking.rst:284
+# b488c5b17c004a7b88b330efbc3bc05f
+# 9817c5466dbe4abf99c2de124120bbed
 msgid "For more information, see `“DNS and DHCP” <networking2.html#dns-and-dhcp>`_."
 msgstr ""
 
-#: ../../networking.rst:342
-#: ../../networking.rst:342
-#: ../../networking.rst:343
-#: ../../networking.rst:343
-#: ../../networking.rst:344
-#: ../../networking.rst:344
-#: ../../networking.rst:347
-#: ../../networking.rst:347
-#: ../../networking.rst:348
-#: ../../networking.rst:348
-#: ../../networking.rst:351
-#: ../../networking.rst:351
-#: ../../networking.rst:354
-#: ../../networking.rst:357
-#: ../../networking.rst:359
-#: ../../networking.rst:361
-#: ../../networking.rst:363
-# 805e347c65e64c3487ba61961339baad
-# 23025c3016ac4b1e8a702c33cde28ea7
-# 2da3a8e5b0e2474e934d7132d1e14dd0
-# 7e3249a14ead45599a181314690d0f9c
-# 01605fd514bc4b5cb1b53970d0e3bafa
-# 38fb8a3f30b044b1bc1f17a899253152
-# 302e53129bee49f58cd18d77c82d1d7d
-# 7904ea495a294d47b5f60c1ae82b3cf9
-# e6321736963444f5a2a5a0d63dae4628
-# a6d8711696ae4c65b2ddad646846e398
-# a45176c2843d4f00b795b93389e07d23
-# 17e75d9784d74f69a498b086a3e1f610
-# f86900fd609948eba216b7a53fd99ba8
-# 2a0310279b294d7aa5fccdfdfb283c5f
-# afcb530f4be04708984c4a202cf24904
-# 7895e040465840ef880398bb1062364c
-# 78c72a0d4ef44f929d74c807f28a290a
+#: ../../networking.rst:283
+#: ../../networking.rst:283
+#: ../../networking.rst:284
+#: ../../networking.rst:284
+#: ../../networking.rst:285
+#: ../../networking.rst:285
+#: ../../networking.rst:288
+#: ../../networking.rst:288
+#: ../../networking.rst:289
+#: ../../networking.rst:289
+#: ../../networking.rst:292
+#: ../../networking.rst:292
+#: ../../networking.rst:295
+#: ../../networking.rst:298
+#: ../../networking.rst:300
+#: ../../networking.rst:302
+#: ../../networking.rst:304
+# c4875cd1ba3341f0801c282d362f1d24
+# d065a3aee4944733bff2d01f26b75c7f
+# 9f736e032cce456ebb4f77be38b5e58f
+# 7df1ac5d383948bd84380b75c4e098af
+# 3ba5059895ef4d1c85924407662447ee
+# 3e841c3844b94853b7a8aaaed25cd4ad
+# c77eeef8c5314be099fb3716d3445a66
+# 25f106d12a764b078bb2b6524ad18215
+# f63379e1fe44403bb4b003d91fc04f93
+# 4f4951219e654f71ba852ba5238e8851
+# 15ddd915917341cb80019e9b900a4731
+# 8dacf6aaa0704e9db73a0126c94e16e5
+# 50e87369ed7e48e29d7cb426767a5ed8
+# c1b167740f9e43c2a17a96fbf65930bf
+# 22a23c6ed73740b8a269adc46484bd2a
+# bb47b4ce2443499aa4f5308fec5ed187
+# 8754a866d8d14c92a6556744cf012422
 msgid "Supported"
 msgstr ""
 
-#: ../../networking.rst:344
-# 2dec5922a2294cc480f3f05d1bd945c4
+#: ../../networking.rst:285
+# 50819151ad5442aeb2570677b2632a46
 msgid "Load Balancer"
 msgstr ""
 
-#: ../../networking.rst:344
-# 388ef4db2cdc42b2ae647f16f589956e
+#: ../../networking.rst:285
+# b9edc8827ba44d2db0f62206a215e670
 msgid "If you select Load Balancer, you can choose the CloudStack virtual router or any other load balancers that have been configured in the cloud."
 msgstr ""
 
-#: ../../networking.rst:347
-# f7c3d40254e14277836751f9ec34a7f4
+#: ../../networking.rst:288
+# 2e489054cb1e4a35ac3e90f70c1f1255
 msgid "For more information, see the Administration Guide."
 msgstr ""
 
-#: ../../networking.rst:348
-# 3173c380050745e6ad4b7b92d36511db
+#: ../../networking.rst:289
+# 8e117eda9d13423c93e568f0818cc4d9
 msgid "If you select Source NAT, you can choose the CloudStack virtual router or any other Source NAT providers that have been configured in the cloud."
 msgstr ""
 
-#: ../../networking.rst:351
-# 27b525b30dff4fe3916f070201dad176
+#: ../../networking.rst:292
+# aba8109b051a46d89785cb597e382503
 msgid "If you select Static NAT, you can choose the CloudStack virtual router or any other Static NAT providers that have been configured in the cloud."
 msgstr ""
 
-#: ../../networking.rst:354
-# 89f8c6b4aa8847c2887fa86705dd9fc9
+#: ../../networking.rst:295
+# d932fb3f0c49487e8fb03f47c8ec3137
 msgid "If you select Port Forwarding, you can choose the CloudStack virtual router or any other Port Forwarding providers that have been configured in the cloud."
 msgstr ""
 
-#: ../../networking.rst:354
-#: ../../networking.rst:357
-#: ../../networking.rst:359
-#: ../../networking.rst:361
-#: ../../networking.rst:363
-# 39935b90efc0487db70afc5717e01d83
-# 104dd89e6b6b43eaa5334b8d5b5f5f53
-# 89b082d6787c4b188960b061c7a04a11
-# cb004398c5fd45f09a4c14efda2ba7ce
-# e196626d888c4e44adcc5559c162e76e
+#: ../../networking.rst:295
+#: ../../networking.rst:298
+#: ../../networking.rst:300
+#: ../../networking.rst:302
+#: ../../networking.rst:304
+# ba3080b2df494a6194c5a4ec14bd1410
+# 5c07262385d1478c927953b93692e644
+# 23f57ac958b34548a1c2d23a776e1da8
+# c3490a0f19134b8b886f204a4794c427
+# 111a4f3a414c443cb13dcb958326620f
 msgid "Not Supported"
 msgstr ""
 
-#: ../../networking.rst:357
-# acae22d0beeb4a5586a1cad5230e9a16
+#: ../../networking.rst:298
+# ab512b24e90a4f0fbeff2872914232bf
 msgid "For more information, see `“Remote Access VPN” <networking2.html#remote-access-vpn>`_."
 msgstr ""
 
-#: ../../networking.rst:359
-# 25d327d1ea194c4f9fad29644ad234cf
+#: ../../networking.rst:300
+# bc836dbec7dd41098535b7062953abf7
 msgid "User Data"
 msgstr ""
 
-#: ../../networking.rst:359
-# a86728de7e1b4f4aa18f8f727e9ec771
+#: ../../networking.rst:300
+# 2ee92986a8924dd1a8704e477e3ce1a6
 msgid "For more information, see `“User Data and Meta Data” <api.html#user-data-and-meta-data>`_."
 msgstr ""
 
-#: ../../networking.rst:361
-# 24ec41e6903441df91985a2b8263e940
+#: ../../networking.rst:302
+# c84e2a3c0cb2440f96442843325bf941
 msgid "Network ACL"
 msgstr ""
 
-#: ../../networking.rst:361
-# 3cbcb6d20c0340c289ccf8ee0816ded6
+#: ../../networking.rst:302
+# 1a00657b608e45b9b31d17dedf1209d9
 msgid "For more information, see `“Configuring Network Access Control List” <networking2.html#configuring-network-access-control-list>`_."
 msgstr ""
 
-#: ../../networking.rst:363
-# 7cb17996648848c898d5952be68b74cf
+#: ../../networking.rst:304
+# 72b47ce7c25a4820af0c52549a594235
 msgid "Security Groups"
 msgstr ""
 
-#: ../../networking.rst:363
-# b2e84782193f4cbbadbe57ee0930d0fa
+#: ../../networking.rst:304
+# 08f3a340905b433990695bcc9c4fdd28
 msgid "For more information, see `“Adding a Security Group” <networking2.html#adding-a-security-group>`_."
 msgstr ""
 
-#: ../../networking.rst:370
-# e70f833484e94ba689ce3ba1a4b96c13
+#: ../../networking.rst:309
+# e235b3337dbb400c90ecee3f5837fde2
 msgid "**System Offering**. If the service provider for any of the services selected in Supported Services is a virtual router, the System Offering field appears. Choose the system service offering that you want virtual routers to use in this network. For example, if you selected Load Balancer in Supported Services and selected a virtual router to provide load balancing, the System Offering field appears so you can choose between the CloudStack default system service offering and any custom system service offerings that have been defined by the CloudStack root administrator."
 msgstr ""
 
-#: ../../networking.rst:380
-# 43b34d0af71d489ca3e2b5cf1b16c934
+#: ../../networking.rst:319
+# 34b519afb51c4d1f9b1718b0f32cb527
 msgid "For more information, see `“System Service Offerings” <service_offerings.html#system-service-offerings>`_."
 msgstr ""
 
-#: ../../networking.rst:384
-# 2752b779a38b4d959c80d66f531a23d3
+#: ../../networking.rst:322
+# 66fb3b1df7164cd6bc37c61a61367d73
 msgid "**LB Isolation**: Specify what type of load balancer isolation you want for the network: Shared or Dedicated."
 msgstr ""
 
-#: ../../networking.rst:387
-# 46399957be6d41b2979acc5bb8a854e2
+#: ../../networking.rst:325
+# a07b6242746142e18198a5bf7356254f
 msgid "**Dedicated**: If you select dedicated LB isolation, a dedicated load balancer device is assigned for the network from the pool of dedicated load balancer devices provisioned in the zone. If no sufficient dedicated load balancer devices are available in the zone, network creation fails. Dedicated device is a good choice for the high-traffic networks that make full use of the device's resources."
 msgstr ""
 
-#: ../../networking.rst:395
-# 955c3d93a3eb49dfbf4aa835ab91ddb6
+#: ../../networking.rst:333
+# 1481728f6860436790f1bbdf1de1b4d0
 msgid "**Shared**: If you select shared LB isolation, a shared load balancer device is assigned for the network from the pool of shared load balancer devices provisioned in the zone. While provisioning CloudStack picks the shared load balancer device that is used by the least number of accounts. Once the device reaches its maximum capacity, the device will not be allocated to a new account."
 msgstr ""
 
-#: ../../networking.rst:405
-# ef915a99816543cdb9ec79a04b12edb7
+#: ../../networking.rst:341
+# 232eced6797144d7b6cb941627e8d2e6
 msgid "**Mode**: You can select either Inline mode or Side by Side mode:"
 msgstr ""
 
-#: ../../networking.rst:407
-# 55d2e7b518ca4905b53e95f5e33620f0
+#: ../../networking.rst:343
+# 7684aca0c54c44fb9871f784de706a13
 msgid "**Inline mode**: Supported only for Juniper SRX firewall and BigF5 load balancer devices. In inline mode, a firewall device is placed in front of a load balancing device. The firewall acts as the gateway for all the incoming traffic, then redirect the load balancing traffic to the load balancer behind it. The load balancer in this case will not have the direct access to the public network."
 msgstr ""
 
-#: ../../networking.rst:415
-# 39292129cf2a4209ba5f76220fa6f8f3
+#: ../../networking.rst:351
+# a5a609bdc196450fb249b0fed2b62618
 msgid "**Side by Side**: In side by side mode, a firewall device is deployed in parallel with the load balancer device. So the traffic to the load balancer public IP is not routed through the firewall, and therefore, is exposed to the public network."
 msgstr ""
 
-#: ../../networking.rst:422
-# 5b49b6db7f9248748b051cd86bbeb3e6
+#: ../../networking.rst:356
+# fddae68fcb5145e68976043eb707eed5
 msgid "**Associate Public IP**: Select this option if you want to assign a public IP address to the VMs deployed in the guest network. This option is available only if"
 msgstr ""
 
-#: ../../networking.rst:428
-# c93e0c1cc09645c8af8abc86082a8cfb
+#: ../../networking.rst:360
+# b6cedd774fb4418b8c7f09c30e492ac5
 msgid "Guest network is shared."
 msgstr ""
 
-#: ../../networking.rst:432
-# 854f813bb8dd41f6a6c9758906509b86
+#: ../../networking.rst:362
+# c011835f1c314df2afcb840630a7ff99
 msgid "StaticNAT is enabled."
 msgstr ""
 
-#: ../../networking.rst:436
-# d14fd96be5f346aa9321354e32489e9b
+#: ../../networking.rst:364
+# fcd9521a7c684aaaaacf045798eaaf33
 msgid "Elastic IP is enabled."
 msgstr ""
 
-#: ../../networking.rst:438
-# dfaca3652ee64df0a3bac4e699a494fb
+#: ../../networking.rst:366
+# 9818049dc1484f41b94a2c0c3904838d
 msgid "For information on Elastic IP, see `“About Elastic IP” <networking2.html#about-elastic-ip>`_."
 msgstr ""
 
-#: ../../networking.rst:442
-# d5a841361fe14001a46d6a5310aca5bf
+#: ../../networking.rst:369
+# 6c9c68a68ab14d30a00460dd3b13f8a6
 msgid "**Redundant router capability**: Available only when Virtual Router is selected as the Source NAT provider. Select this option if you want to use two virtual routers in the network for uninterrupted connection: one operating as the master virtual router and the other as the backup. The master virtual router receives requests from and sends responses to the user’s VM. The backup virtual router is activated only when the master is down. After the failover, the backup becomes the master virtual router. CloudStack deploys the routers on different hosts to ensure reliability if one host is down."
 msgstr ""
 
-#: ../../networking.rst:455
-# 580303d29adc4bbc97763c93dba3acc0
+#: ../../networking.rst:380
+# e5994ec5233c4a979624fa1fc8593822
 msgid "**Conserve mode**: Indicate whether to use conserve mode. In this mode, network resources are allocated only when the first virtual machine starts in the network. When conservative mode is off, the public IP can only be used for a single service. For example, a public IP used for a port forwarding rule cannot be used for defining other services, such as StaticNAT or load balancing. When the conserve mode is on, you can define more than one service on the same public IP."
 msgstr ""
 
-#: ../../networking.rst:465
-# c521afbaf7ff46ac97fd58fbc5b6b357
+#: ../../networking.rst:390
+# 6a2faa335b6b42588d747ac83fc4770b
 msgid "If StaticNAT is enabled, irrespective of the status of the conserve mode, no port forwarding or load balancing rule can be created for the IP. However, you can add the firewall rules by using the createFirewallRule command."
 msgstr ""
 
-#: ../../networking.rst:469
-# 398b07e9909440cb9af01eda7c190c87
+#: ../../networking.rst:395
+# 029a76d3e8444e15981d3fda29b8982e
 msgid "**Tags**: Network tag to specify which physical network to use."
 msgstr ""
 
-#: ../../networking.rst:473
-# 228ba6bcfa4e47429f666a1da30b31a6
+#: ../../networking.rst:397
+# e0d7d2460dba47d29922d3dcf0d16dc5
 msgid "**Default egress policy**: Configure the default policy for firewall egress rules. Options are Allow and Deny. Default is Allow if no egress policy is specified, which indicates that all the egress traffic is accepted when a guest network is created from this offering."
 msgstr ""
 
-#: ../../networking.rst:479
-# 10673613d31446f89ee73ede461ae140
+#: ../../networking.rst:403
+# 6cf9fba73dda48b8801d8608ce2f52a4
 msgid "To block the egress traffic for a guest network, select Deny. In this case, when you configure an egress rules for an isolated guest network, rules are added to allow the specified traffic."
 msgstr ""
 
-#: ../../networking.rst:485
-# 0878f452756346e9b614df490e386e84
+#: ../../networking.rst:407
+# fcfc7b9313f94bbda5ac1afbd8168f7c
 msgid "Click Add."
 msgstr ""
 
diff --git a/source/locale/pot/networking/acquiring_an_ip_address.pot b/source/locale/pot/networking/acquiring_an_ip_address.pot
new file mode 100644
index 0000000..1d9eb2e
--- /dev/null
+++ b/source/locale/pot/networking/acquiring_an_ip_address.pot
@@ -0,0 +1,73 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/acquiring_an_ip_address.rst:18
+# aec0c098f53f452cb8665fc7b69cd182
+msgid "Acquiring a New IP Address"
+msgstr ""
+
+#: ../../networking/acquiring_an_ip_address.rst:20
+# 6113064b39bc4682869acf44286131ad
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr ""
+
+#: ../../networking/acquiring_an_ip_address.rst:22
+# ccc7a493b9b940c2b706c15e852b3e93
+msgid "In the left navigation, choose Network."
+msgstr ""
+
+#: ../../networking/acquiring_an_ip_address.rst:24
+# 9a6973f9449e4414a4643a6da352263e
+msgid "Click the name of the network where you want to work with."
+msgstr ""
+
+#: ../../networking/acquiring_an_ip_address.rst:26
+# beaa083fcce64bb48e44a47c9b4ab745
+msgid "Click View IP Addresses."
+msgstr ""
+
+#: ../../networking/acquiring_an_ip_address.rst:28
+# 76867ce630364509a651c09137cab94e
+msgid "Click Acquire New IP."
+msgstr ""
+
+#: ../../networking/acquiring_an_ip_address.rst:30
+# 35698ea68aa24ff79ce9dc09c1d12caf
+msgid "The Acquire New IP window is displayed."
+msgstr ""
+
+#: ../../networking/acquiring_an_ip_address.rst:32
+# 4819ef07622d41fd818aef83d9752ac2
+msgid "Specify whether you want cross-zone IP or not."
+msgstr ""
+
+#: ../../networking/acquiring_an_ip_address.rst:34
+# 342295d34e8e4252b2850d040aca7909
+msgid "If you want Portable IP click Yes in the confirmation dialog. If you want a normal Public IP click No."
+msgstr ""
+
+#: ../../networking/acquiring_an_ip_address.rst:37
+# 9a4837aaa4c940b78c8aa311245b748a
+msgid "For more information on Portable IP, see `\"Portable IPs\" <#portable-ips>`_."
+msgstr ""
+
+#: ../../networking/acquiring_an_ip_address.rst:40
+# 2ee8ad57fe20463893a86f3fe6eb669f
+msgid "Within a few moments, the new IP address should appear with the state Allocated. You can now use the IP address in port forwarding or static NAT rules."
+msgstr ""
+
diff --git a/source/locale/pot/networking/advanced_zone_config.pot b/source/locale/pot/networking/advanced_zone_config.pot
new file mode 100644
index 0000000..06f6bca
--- /dev/null
+++ b/source/locale/pot/networking/advanced_zone_config.pot
@@ -0,0 +1,252 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/advanced_zone_config.rst:19
+# bcc6293e20c4470c938be75c5f17196e
+msgid "Advanced Zone Physical Network Configuration"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:21
+# 65ad7a2b34f848cd9f21c2d2d51f06f6
+msgid "Within a zone that uses advanced networking, you need to tell the Management Server how the physical network is set up to carry different kinds of traffic in isolation."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:27
+# 360066243e5b4ffc894a816b7e903923
+msgid "Configure Guest Traffic in an Advanced Zone"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:29
+# ed393c6319d54e98ba44a7577315044b
+msgid "These steps assume you have already logged in to the CloudStack UI. To configure the base guest network:"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:32
+# e3081f9e98e446d6855a2e72cba9849d
+msgid "In the left navigation, choose Infrastructure. On Zones, click View More, then click the zone to which you want to add a network."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:35
+#: ../../networking/advanced_zone_config.rst:87
+# 7e76a728cc8a43778d79ff577c30b3f2
+# 22748233c6cf4d06b5ba94259fe1e6e9
+msgid "Click the Network tab."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:37
+#: ../../networking/advanced_zone_config.rst:89
+# 1c9241340a4d47a58af0ae3e10893ea1
+# 2c90664c2e9647c59a36e2a8f25d1a87
+msgid "Click Add guest network."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:39
+# cbb8ccbe13b34ed88593d4cf688451a1
+msgid "The Add guest network window is displayed:"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:41
+# ef5079e0fa7f4e5c8bac3410c02fa00f
+msgid "|addguestnetwork.png|"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:43
+# ec8bb470f4924bd0af5b256494fbf0f5
+msgid "Provide the following information:"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:45
+# fa32f98dfeb04b68b79b01e6ef0e1fcf
+msgid "**Name**: The name of the network. This will be user-visible"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:47
+# f38e902b2f2c4fe78960c5d37c4a3609
+msgid "**Display Text**: The description of the network. This will be user-visible"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:50
+# c1e74ac05b5a4eacb568d9201d733f74
+msgid "**Zone**: The zone in which you are configuring the guest network."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:52
+# 1bb07d209bd44e82b5f43507bb058db9
+msgid "**Network offering**: If the administrator has configured multiple network offerings, select the one you want to use for this network"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:55
+# a33441c2621f415eb45dbc077a63e7bb
+msgid "**Guest Gateway**: The gateway that the guests should use"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:57
+# 7f50db013a5941939cff931a256abb58
+msgid "**Guest Netmask**: The netmask in use on the subnet the guests will use"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:60
+# 186fd6f7a8de48fea845645978a6b332
+msgid "Click OK."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:64
+# 6c2ac4e12f5f4a8c8788df54295b6e31
+msgid "Configure Public Traffic in an Advanced Zone"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:66
+# 7e91e673073d49e69f1ec92976a0d118
+msgid "In a zone that uses advanced networking, you need to configure at least one range of IP addresses for Internet traffic."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:71
+# c4aa53c641a347da9da814dfc32940a5
+msgid "Configuring a Shared Guest Network"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:73
+# d5ac14718de945a5ae1eda9e0574d9cf
+msgid "Log in to the CloudStack UI as administrator."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:75
+# 9a3fd0f929374352a6cf52cc9790dfb1
+msgid "In the left navigation, choose Infrastructure."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:77
+# dbfd04e800154df197a15cb258be6d3f
+msgid "On Zones, click View More."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:79
+# 7f633e5cc4504dfdaa399fcb8ab6c22e
+msgid "Click the zone to which you want to add a guest network."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:81
+# 173dd051e7a1433d90061cca03962fc4
+msgid "Click the Physical Network tab."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:83
+# e48da344ca7241429e6404ab7b137b39
+msgid "Click the physical network you want to work with."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:85
+# 0e03928f490a4bf5acd9028fed3fd8d8
+msgid "On the Guest node of the diagram, click Configure."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:91
+# 9272a3e9c02b4d3fb7e88cd90f63e56f
+msgid "The Add guest network window is displayed."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:93
+# 271290c4c54643a9a8cc203840b4bb3b
+msgid "Specify the following:"
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:95
+# a69cf77fdc48441b9a0e41233bf3d4db
+msgid "**Name**: The name of the network. This will be visible to the user."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:97
+# 924d5df6b0f643c3ad34cdfa02548391
+msgid "**Description**: The short description of the network that can be displayed to users."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:100
+# 8c68c64196cb4b548290e4a3e9851553
+msgid "**VLAN ID**: The unique ID of the VLAN."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:102
+# 0711300a6023445c91c8a4d7926a8e04
+msgid "**Isolated VLAN ID**: The unique ID of the Secondary Isolated VLAN."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:105
+# dbbc4b85106a407f9bb4532a5c1a40a2
+msgid "**Scope**: The available scopes are Domain, Account, Project, and All."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:108
+# 46fd996ba0b241efa0f21c9f22c7c77d
+msgid "**Domain**: Selecting Domain limits the scope of this guest network to the domain you specify. The network will not be available for other domains. If you select Subdomain Access, the guest network is available to all the sub domains within the selected domain."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:114
+# 79bd2bf86f74472db3b4cba26ef143dd
+msgid "**Account**: The account for which the guest network is being created for. You must specify the domain the account belongs to."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:118
+# f3de2d8830134ab195b04b7e4b74b215
+msgid "**Project**: The project for which the guest network is being created for. You must specify the domain the project belongs to."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:122
+# e03c5c4ff8d646cdb1a4029a794765e5
+msgid "**All**: The guest network is available for all the domains, account, projects within the selected zone."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:125
+# 74217dea4b9c4d8faa89e1ea6b2c754e
+msgid "**Network Offering**: If the administrator has configured multiple network offerings, select the one you want to use for this network."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:129
+# 587275eb7b1249e590763c8b0fb81d41
+msgid "**Gateway**: The gateway that the guests should use."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:131
+# 8123de4fbb1d4a1cba01cb099365b448
+msgid "**Netmask**: The netmask in use on the subnet the guests will use."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:133
+# 129d7c2b8ec442cb802ec894eb871959
+msgid "**IP Range**: A range of IP addresses that are accessible from the Internet and are assigned to the guest VMs."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:136
+# 8ea844eb28e94825bdefeba5cc1e143c
+msgid "If one NIC is used, these IPs should be in the same CIDR in the case of IPv6."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:139
+# 1a2dacdd2a984c978ad1455bdb6c04b8
+msgid "**IPv6 CIDR**: The network prefix that defines the guest network subnet. This is the CIDR that describes the IPv6 addresses in use in the guest networks in this zone. To allot IP addresses from within a particular address block, enter a CIDR."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:144
+# d17e32d82ae849139dda243c9ddc9676
+msgid "**Network Domain**: A custom DNS suffix at the level of a network. If you want to assign a special domain name to the guest VM network, specify a DNS suffix."
+msgstr ""
+
+#: ../../networking/advanced_zone_config.rst:148
+# e200da9c829a41109b13173bce7f11ca
+msgid "Click OK to confirm."
+msgstr ""
+
diff --git a/source/locale/pot/networking/basic_zone_config.pot b/source/locale/pot/networking/basic_zone_config.pot
new file mode 100644
index 0000000..529851f
--- /dev/null
+++ b/source/locale/pot/networking/basic_zone_config.pot
@@ -0,0 +1,28 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/basic_zone_config.rst:19
+# bf16fca54893437db5aad5aa3f2e6e2c
+msgid "Basic Zone Physical Network Configuration"
+msgstr ""
+
+#: ../../networking/basic_zone_config.rst:21
+# 153ba46cfcf14ac28f2db2730d2e43af
+msgid "In a basic network, configuring the physical network is fairly straightforward. You only need to configure one guest network to carry traffic that is generated by guest VMs. When you first add a zone to CloudStack, you set up the guest network through the Add Zone screens."
+msgstr ""
+
diff --git a/source/locale/pot/networking/dns_and_dhcp.pot b/source/locale/pot/networking/dns_and_dhcp.pot
new file mode 100644
index 0000000..f43cebc
--- /dev/null
+++ b/source/locale/pot/networking/dns_and_dhcp.pot
@@ -0,0 +1,28 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/dns_and_dhcp.rst:18
+# 727de7b64d0e4c34bddda54359ed846d
+msgid "DNS and DHCP"
+msgstr ""
+
+#: ../../networking/dns_and_dhcp.rst:20
+# f58ccb2c24bb47c0872a16c74d47f121
+msgid "The Virtual Router provides DNS and DHCP services to the guests. It proxies DNS requests to the DNS server configured on the Availability Zone."
+msgstr ""
+
diff --git a/source/locale/pot/networking/elastic_ips.pot b/source/locale/pot/networking/elastic_ips.pot
new file mode 100644
index 0000000..0ceb120
--- /dev/null
+++ b/source/locale/pot/networking/elastic_ips.pot
@@ -0,0 +1,98 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/elastic_ips.rst:18
+# 68f25b7a2e514065b563d7ccdd72f355
+msgid "About Elastic IPs"
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:20
+# bf34049aef4a4cddb2aa0169d49b5281
+msgid "Elastic IP (EIP) addresses are the IP addresses that are associated with an account, and act as static IP addresses. The account owner has the complete control over the Elastic IP addresses that belong to the account. As an account owner, you can allocate an Elastic IP to a VM of your choice from the EIP pool of your account. Later if required you can reassign the IP address to a different VM. This feature is extremely helpful during VM failure. Instead of replacing the VM which is down, the IP address can be reassigned to a new VM in your account."
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:29
+# 8b249afbc2664b01a564524559d5c5fd
+msgid "Similar to the public IP address, Elastic IP addresses are mapped to their associated private IP addresses by using StaticNAT. The EIP service is equipped with StaticNAT (1:1) service in an EIP-enabled basic zone. The default network offering, DefaultSharedNetscalerEIPandELBNetworkOffering, provides your network with EIP and ELB network services if a NetScaler device is deployed in your zone. Consider the following illustration for more details."
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:37
+# deef19d6b1414dbb967743f1b7cef2df
+msgid "|eip-ns-basiczone.png|"
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:39
+# a1f02d4922ed4bbb8941ccc048f0b0b4
+msgid "In the illustration, a NetScaler appliance is the default entry or exit point for the CloudStack instances, and firewall is the default entry or exit point for the rest of the data center. Netscaler provides LB services and staticNAT service to the guest networks. The guest traffic in the pods and the Management Server are on different subnets / VLANs. The policy-based routing in the data center core switch sends the public traffic through the NetScaler, whereas the rest of the data center goes through the firewall."
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:48
+# 28c78bf967714b33884e97cfa4ca307b
+msgid "The EIP work flow is as follows:"
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:50
+# 773cd4ac9b6d4973832aafd2d0cf2f9e
+msgid "When a user VM is deployed, a public IP is automatically acquired from the pool of public IPs configured in the zone. This IP is owned by the VM's account."
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:54
+# 23a70289953d415c81e8dd6ebc86423c
+msgid "Each VM will have its own private IP. When the user VM starts, Static NAT is provisioned on the NetScaler device by using the Inbound Network Address Translation (INAT) and Reverse NAT (RNAT) rules between the public IP and the private IP."
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:60
+# bfa50768ea9b496599aa1804e3437f25
+msgid "Inbound NAT (INAT) is a type of NAT supported by NetScaler, in which the destination IP address is replaced in the packets from the public network, such as the Internet, with the private IP address of a VM in the private network. Reverse NAT (RNAT) is a type of NAT supported by NetScaler, in which the source IP address is replaced in the packets generated by a VM in the private network with the public IP address."
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:67
+# cef50f723bd34b298098fab0ed2c2328
+msgid "This default public IP will be released in two cases:"
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:69
+# 954fad75b2bd41d1b16f50f819a7e300
+msgid "When the VM is stopped. When the VM starts, it again receives a new public IP, not necessarily the same one allocated initially, from the pool of Public IPs."
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:73
+# a5713ccdbc7f41dea9e1fb5bd2a81337
+msgid "The user acquires a public IP (Elastic IP). This public IP is associated with the account, but will not be mapped to any private IP. However, the user can enable Static NAT to associate this IP to the private IP of a VM in the account. The Static NAT rule for the public IP can be disabled at any time. When Static NAT is disabled, a new public IP is allocated from the pool, which is not necessarily be the same one allocated initially."
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:81
+# a8f5524c22bd4ddf82fd8d2d6240b94f
+msgid "For the deployments where public IPs are limited resources, you have the flexibility to choose not to allocate a public IP by default. You can use the Associate Public IP option to turn on or off the automatic public IP assignment in the EIP-enabled Basic zones. If you turn off the automatic public IP assignment while creating a network offering, only a private IP is assigned to a VM when the VM is deployed with that network offering. Later, the user can acquire an IP for the VM and enable static NAT."
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:90
+# 89cea0807df84e08bd3c61dbf7579d80
+msgid "For more information on the Associate Public IP option, see `\"Creating a New Network Offering\" <networking.html#creating-a-new-network-offering>`_."
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:94
+# e8e0a7038ebb4ea181ba58c3f4cdc0ed
+msgid "The Associate Public IP feature is designed only for use with user VMs. The System VMs continue to get both public IP and private by default, irrespective of the network offering configuration."
+msgstr ""
+
+#: ../../networking/elastic_ips.rst:98
+# 116e2d3d7abc4e4b89e08770c938b985
+msgid "New deployments which use the default shared network offering with EIP and ELB services to create a shared network in the Basic zone will continue allocating public IPs to each user VM."
+msgstr ""
+
diff --git a/source/locale/pot/networking/external_firewalls_and_load_balancers.pot b/source/locale/pot/networking/external_firewalls_and_load_balancers.pot
new file mode 100644
index 0000000..ebe9d94
--- /dev/null
+++ b/source/locale/pot/networking/external_firewalls_and_load_balancers.pot
@@ -0,0 +1,703 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:18
+# 9b2c57c96864404ab39ea18532184a3c
+msgid "External Firewalls and Load Balancers"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:20
+# 406fa3a599d74b6fb0f6a893d839784a
+msgid "CloudStack is capable of replacing its Virtual Router with an external Juniper SRX device and an optional external NetScaler or F5 load balancer for gateway and load balancing services. In this case, the VMs use the SRX as their gateway."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:27
+# e50bcd9fe60e430d85efc883354624a5
+msgid "About Using a NetScaler Load Balancer"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:29
+# 1cf32061da5449a2a6dc5887c27b0d72
+msgid "Citrix NetScaler is supported as an external network element for load balancing in zones that use isolated networking in advanced zones. Set up an external load balancer when you want to provide load balancing through means other than CloudStack's provided virtual router."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:35
+# 188f8456b75c41ffadbc92d637327f54
+msgid "In a Basic zone, load balancing service is supported only if Elastic IP or Elastic LB services are enabled."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:38
+# 7189603a0b934b4b8f4de77ccc774586
+msgid "When NetScaler load balancer is used to provide EIP or ELB services in a Basic zone, ensure that all guest VM traffic must enter and exit through the NetScaler device. When inbound traffic goes through the NetScaler device, traffic is routed by using the NAT protocol depending on the EIP/ELB configured on the public IP to the private IP. The traffic that is originated from the guest VMs usually goes through the layer 3 router. To ensure that outbound traffic goes through NetScaler device providing EIP/ELB, layer 3 router must have a policy-based routing. A policy-based route must be set up so that all traffic originated from the guest VM's are directed to NetScaler device. This is required to ensure that the outbound traffic from the guest VM's is routed to a public IP by using NAT.For more information on Elastic IP, see `\"About Elastic IP\" <#about-elastic-ip>`_."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:52
+# baddaa181f054bb5b0b41e5dcce1387e
+msgid "The NetScaler can be set up in direct (outside the firewall) mode. It must be added before any load balancing rules are deployed on guest VMs in the zone."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:56
+# 263c8a9eb9d147ad91ae71970d65bd41
+msgid "The functional behavior of the NetScaler with CloudStack is the same as described in the CloudStack documentation for using an F5 external load balancer. The only exception is that the F5 supports routing domains, and NetScaler does not. NetScaler can not yet be used as a firewall."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:61
+# 79187d2fbfa743c39e8c524304235dc2
+msgid "To install and enable an external load balancer for CloudStack management, see External Guest Load Balancer Integration in the Installation Guide."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:65
+# d3c851ee525b49599c01646d4d1e2dd5
+msgid "The Citrix NetScaler comes in three varieties. The following summarizes how these variants are treated in CloudStack."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:68
+# 64aec7c1c44049498dcf6c10b4fa5605
+msgid "**MPX**"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:70
+# b8df1ce8dfa14d8c8ecc441c6f71748f
+msgid "Physical appliance. Capable of deep packet inspection. Can act as application firewall and load balancer"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:73
+# 3a1ec0e897e34118a0fbeb78f64a544a
+msgid "In advanced zones, load balancer functionality fully supported without limitation. In basic zones, static NAT, elastic IP (EIP), and elastic load balancing (ELB) are also provided."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:77
+# 68d5e27c550d40cd921b14324d33692a
+msgid "**VPX**"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:79
+# 886b66d79fd049739f35d53684946f35
+msgid "Virtual appliance. Can run as VM on XenServer, ESXi, and Hyper-V hypervisors. Same functionality as MPX"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:82
+# acdf8d15b2b740579349caa99d8ff14f
+msgid "Supported on ESXi and XenServer. Same functional support as for MPX. CloudStack will treat VPX and MPX as the same device type."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:85
+# 632775a416fd40bfb11895ae39b883e9
+msgid "**SDX**"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:87
+# 94896445c73d42c7a8a8b30da3d762a9
+msgid "Physical appliance. Can create multiple fully isolated VPX instances on a single appliance to support multi-tenant usage"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:90
+# 7272ab89523e416fba357a4ceb24b459
+msgid "CloudStack will dynamically provision, configure, and manage the life cycle of VPX instances on the SDX. Provisioned instances are added into CloudStack automatically - no manual configuration by the administrator is required. Once a VPX instance is added into CloudStack, it is treated the same as a VPX on an ESXi host."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:98
+# e712ff0906b7463083ac7a8f9b19847c
+msgid "Configuring SNMP Community String on a RHEL Server"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:100
+# a0e11ba7efae4e63a0cd9eb015162722
+msgid "The SNMP Community string is similar to a user id or password that provides access to a network device, such as router. This string is sent along with all SNMP requests. If the community string is correct, the device responds with the requested information. If the community string is incorrect, the device discards the request and does not respond."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:106
+# d9a8fc53fc4949bda74cb44fbcb04146
+msgid "The NetScaler device uses SNMP to communicate with the VMs. You must install SNMP and configure SNMP Community string for a secure communication between the NetScaler device and the RHEL machine."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:110
+# 9f7d96642a9b435ab7687ecf88e6f6de
+msgid "Ensure that you installed SNMP on RedHat. If not, run the following command:"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:117
+# 657a8fba85b14585be4a9165ba95128b
+msgid "Edit the /etc/snmp/snmpd.conf file to allow the SNMP polling from the NetScaler device."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:120
+# 752d34a607b64dbea0348f5551d5cebc
+msgid "Map the community name into a security name (local and mynetwork, depending on where the request is coming from):"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:124
+# 07b1fa6ac91c4aa186c434d633b0384e
+msgid "Use a strong password instead of public when you edit the following table."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:133
+# f8acb0abc31c4fd0ab9300c705ba1f72
+msgid "Setting to 0.0.0.0 allows all IPs to poll the NetScaler server."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:135
+# 327a4b1c1e4d429c83dc1e1628f8376a
+msgid "Map the security names into group names:"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:145
+# 193cbe00950147958924521840ba4405
+msgid "Create a view to allow the groups to have the permission to:"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:151
+# 39191ba80aa24e32898e8a79892fb7cf
+msgid "Grant access with different write permissions to the two groups to the view you created."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:160
+# ca08ac1ab89442c9a42c7d59efa70e6b
+msgid "Unblock SNMP in iptables."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:166
+# f161affb624f4139be0750f3dc19f505
+msgid "Start the SNMP service:"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:172
+# 60eb8801ebf44b97b3b4cc63348013b6
+msgid "Ensure that the SNMP service is started automatically during the system startup:"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:181
+# 8893688efc574dbfba90b00df9f467bd
+msgid "Initial Setup of External Firewalls and Load Balancers"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:183
+# 2149019287d549649f77e49102f3a8e2
+msgid "When the first VM is created for a new account, CloudStack programs the external firewall and load balancer to work with the VM. The following objects are created on the firewall:"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:187
+# 7bec0089c55040c9bcc3b75a4ce9ae0b
+msgid "A new logical interface to connect to the account's private VLAN. The interface IP is always the first IP of the account's private subnet (e.g. 10.1.1.1)."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:191
+# 5d690ff5c70b4951a41d9ccf663e1e5d
+msgid "A source NAT rule that forwards all outgoing traffic from the account's private VLAN to the public Internet, using the account's public IP address as the source address"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:195
+# a8b478c2d3334a0aa56507a774978095
+msgid "A firewall filter counter that measures the number of bytes of outgoing traffic for the account"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:198
+# 438d673ffaa3412c98761796e1c9043c
+msgid "The following objects are created on the load balancer:"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:200
+# 07491865d4a3476293c53ae24c343c78
+msgid "A new VLAN that matches the account's provisioned Zone VLAN"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:202
+# 3691e62805b34e95acd2ff232154ca0d
+msgid "A self IP for the VLAN. This is always the second IP of the account's private subnet (e.g. 10.1.1.2)."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:207
+# 1e387fca9feb4a08825eb2dfe3547fb0
+msgid "Ongoing Configuration of External Firewalls and Load Balancers"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:209
+# 133336c3018e4957ba148ad3a8f85ed4
+msgid "Additional user actions (e.g. setting a port forward) will cause further programming of the firewall and load balancer. A user may request additional public IP addresses and forward traffic received at these IPs to specific VMs. This is accomplished by enabling static NAT for a public IP address, assigning the IP to a VM, and specifying a set of protocols and port ranges to open. When a static NAT rule is created, CloudStack programs the zone's external firewall with the following objects:"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:218
+# cfcd0d08f25142019221555a1a499683
+msgid "A static NAT rule that maps the public IP address to the private IP address of a VM."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:221
+# 76e196b931384143a2f1b65467f003dd
+msgid "A security policy that allows traffic within the set of protocols and port ranges that are specified."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:224
+# b6b755f7fb5a4d4d9495bfe3b0eac10e
+msgid "A firewall filter counter that measures the number of bytes of incoming traffic to the public IP."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:227
+# 077fa026b5954737b4af75e98a4dd1e8
+msgid "The number of incoming and outgoing bytes through source NAT, static NAT, and load balancing rules is measured and saved on each external element. This data is collected on a regular basis and stored in the CloudStack database."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:234
+# a882754de1c64a389513a78637f3325d
+msgid "Load Balancer Rules"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:236
+# 9b95ee51dc6e4026905b950584948d63
+msgid "A CloudStack user or administrator may create load balancing rules that balance traffic received at a public IP to one or more VMs. A user creates a rule, specifies an algorithm, and assigns the rule to a set of VMs."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:242
+# 7ac5de99c5694e0b89ceb6d4c39e0dfb
+msgid "If you create load balancing rules while using a network service offering that includes an external load balancer device such as NetScaler, and later change the network service offering to one that uses the CloudStack virtual router, you must create a firewall rule on the virtual router for each of your existing load balancing rules so that they continue to function."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:253
+# b09aa6c58aa84b8f89b3293a64ca17fd
+msgid "Adding a Load Balancer Rule"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:255
+# 1bc40a00c2f341118db65e97bbbcf986
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:257
+# 57f7d8a61234427abc813c4208e84192
+msgid "In the left navigation, choose Network."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:259
+# d947318aba7746718816eb5c7e29e9b1
+msgid "Click the name of the network where you want to load balance the traffic."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:262
+# 20fc7dedf2cf482d94d8977ac64c6b0d
+msgid "Click View IP Addresses."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:264
+# aff4544b414847af82ceceb0bd4e3b55
+msgid "Click the IP address for which you want to create the rule, then click the Configuration tab."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:267
+# a84c70dc6b4f4d7c8f5a2d1f82b59355
+msgid "In the Load Balancing node of the diagram, click View All."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:269
+# 698c929938644fa88bcaa781f68ea4e7
+msgid "In a Basic zone, you can also create a load balancing rule without acquiring or selecting an IP address. CloudStack internally assign an IP when you create the load balancing rule, which is listed in the IP Addresses page when the rule is created."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:274
+# 2991ed0062324ee88859d10be3c6d280
+msgid "To do that, select the name of the network, then click Add Load Balancer tab. Continue with #7."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:277
+# f62541afe2764660ba42de5ab1903be0
+msgid "Fill in the following:"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:279
+# 9d106d6a229045acbfc2622c0c395bd9
+msgid "**Name**: A name for the load balancer rule."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:281
+# 75090eb93c0c438fbb12cc3c26d20ef9
+msgid "**Public Port**: The port receiving incoming traffic to be balanced."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:284
+# 61dc53b8703148608a98d96de9b2f3f7
+msgid "**Private Port**: The port that the VMs will use to receive the traffic."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:287
+# 9e98c799101c44728527da77d95553ee
+msgid "**Algorithm**: Choose the load balancing algorithm you want CloudStack to use. CloudStack supports a variety of well-known algorithms. If you are not familiar with these choices, you will find plenty of information about them on the Internet."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:292
+# 1fc198ccbf4e4718beba8aaec97b2a38
+msgid "**Stickiness**: (Optional) Click Configure and choose the algorithm for the stickiness policy. See Sticky Session Policies for Load Balancer Rules."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:296
+# 8d672e758cc24f2da82cbdd82c83ea21
+msgid "**AutoScale**: Click Configure and complete the AutoScale configuration as explained in :ref:`conf-autoscale`."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:299
+# 33ab79892f344fde975f3d6c32cd9b12
+msgid "**Health Check**: (Optional; NetScaler load balancers only) Click Configure and fill in the characteristics of the health check policy. See :ref:`health-check`."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:303
+# d643db9463b745c7ac1f19daad8358dd
+msgid "**Ping path (Optional)**: Sequence of destinations to which to send health check queries. Default: / (all)."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:306
+# b33a72d1050241329dd52806584f0b49
+msgid "**Response time (Optional)**: How long to wait for a response from the health check (2 - 60 seconds). Default: 5 seconds."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:309
+# 885f1763ea71493ea93ba841259240b3
+msgid "**Interval time (Optional)**: Amount of time between health checks (1 second - 5 minutes). Default value is set in the global configuration parameter lbrule\\_health check\\_time\\_interval."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:314
+# 82dd529deb534e00b11b709fad1a829f
+msgid "**Healthy threshold (Optional)**: Number of consecutive health check successes that are required before declaring an instance healthy. Default: 2."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:318
+# 8c946ad8aa9b402ba1d7808681a90216
+msgid "**Unhealthy threshold (Optional)**: Number of consecutive health check failures that are required before declaring an instance unhealthy. Default: 10."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:322
+# 8bd4120f80ff41368605d05b647ee837
+msgid "Click Add VMs, then select two or more VMs that will divide the load of incoming traffic, and click Apply."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:325
+# 9720f8ded014448394288000a5c40217
+msgid "The new load balancer rule appears in the list. You can repeat these steps to add more load balancer rules for this IP address."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:330
+# 3ccedfb3a9324eb1860d1924ac909e3a
+msgid "Sticky Session Policies for Load Balancer Rules"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:332
+# b33d98749eb5488a8a02cad61861c752
+msgid "Sticky sessions are used in Web-based applications to ensure continued availability of information across the multiple requests in a user's session. For example, if a shopper is filling a cart, you need to remember what has been purchased so far. The concept of \"stickiness\" is also referred to as persistence or maintaining state."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:338
+# 68678f9c4f934ed796779a0d4121e91a
+msgid "Any load balancer rule defined in CloudStack can have a stickiness policy. The policy consists of a name, stickiness method, and parameters. The parameters are name-value pairs or flags, which are defined by the load balancer vendor. The stickiness method could be load balancer-generated cookie, application-generated cookie, or source-based. In the source-based method, the source IP address is used to identify the user and locate the user's stored data. In the other methods, cookies are used. The cookie generated by the load balancer or application is included in request and response URLs to create persistence. The cookie name can be specified by the administrator or automatically generated. A variety of options are provided to control the exact behavior of cookies, such as how they are generated and whether they are cached."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:352
+# bb05b34273814acfb053cac6ffdfe917
+msgid "For the most up to date list of available stickiness methods, see the CloudStack UI or call listNetworks and check the SupportedStickinessMethods capability."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:360
+# 35aba1c4298e4ecdaaa750f3375b4be2
+msgid "Health Checks for Load Balancer Rules"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:362
+# d9cc398640dc410ea5c44e614e8d82cd
+msgid "(NetScaler load balancer only; requires NetScaler version 10.0)"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:364
+# 13a5a45067f34a0b8387527dfaa9d0ce
+msgid "Health checks are used in load-balanced applications to ensure that requests are forwarded only to running, available services. When creating a load balancer rule, you can specify a health check policy. This is in addition to specifying the stickiness policy, algorithm, and other load balancer rule options. You can configure one health check policy per load balancer rule."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:371
+# 507b3dcc2fbd48a18c5ae46dcb37b341
+msgid "Any load balancer rule defined on a NetScaler load balancer in CloudStack can have a health check policy. The policy consists of a ping path, thresholds to define \"healthy\" and \"unhealthy\" states, health check frequency, and timeout wait interval."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:376
+# 35f78e270b3e47749e7a677486944ac1
+msgid "When a health check policy is in effect, the load balancer will stop forwarding requests to any resources that are found to be unhealthy. If the resource later becomes available again, the periodic health check will discover it, and the resource will once again be added to the pool of resources that can receive requests from the load balancer. At any given time, the most recent result of the health check is displayed in the UI. For any VM that is attached to a load balancer rule with a health check configured, the state will be shown as UP or DOWN in the UI depending on the result of the most recent health check."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:386
+# bdff04e42c3943e38c182443f757f743
+msgid "You can delete or modify existing health check policies."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:388
+# eef49f2114c344a58739dcf8f68aac70
+msgid "To configure how often the health check is performed by default, use the global configuration setting healthcheck.update.interval (default value is 600 seconds). You can override this value for an individual health check policy."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:393
+# 6f13b2ca1fd74ad2a09363a9de9dfa54
+msgid "For details on how to set a health check policy using the UI, see :ref:`adding-lb-rule`."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:400
+# 6f66a1def18847c0ba2eec5214f58bc4
+msgid "Configuring AutoScale"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:402
+# 1d10105f71d4436ca70e813d83aa587d
+msgid "AutoScaling allows you to scale your back-end services or application VMs up or down seamlessly and automatically according to the conditions you define. With AutoScaling enabled, you can ensure that the number of VMs you are using seamlessly scale up when demand increases, and automatically decreases when demand subsides. Thus it helps you save compute costs by terminating underused VMs automatically and launching new VMs when you need them, without the need for manual intervention."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:410
+# f916e1ba803d4d5f93f20a1fc650704f
+msgid "NetScaler AutoScaling is designed to seamlessly launch or terminate VMs based on user-defined conditions. Conditions for triggering a scaleup or scaledown action can vary from a simple use case like monitoring the CPU usage of a server to a complex use case of monitoring a combination of server's responsiveness and its CPU usage. For example, you can configure AutoScaling to launch an additional VM whenever CPU usage exceeds 80 percent for 15 minutes, or to remove a VM whenever CPU usage is less than 20 percent for 30 minutes."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:419
+# fa4167d0761945e6b5552ddc195aa1cb
+msgid "CloudStack uses the NetScaler load balancer to monitor all aspects of a system's health and work in unison with CloudStack to initiate scale-up or scale-down actions."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:424
+# 25cc6eeee03544bead38d29ffde91c33
+msgid "AutoScale is supported on NetScaler Release 10 Build 74.4006.e and beyond."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:428
+# f97b092a261142629f674c1cf40ee949
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:430
+# 0c697f756785488aaa591aa8b9a921cc
+msgid "Before you configure an AutoScale rule, consider the following:"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:432
+# 8229cf3ea2d24a22bc9707f8f142ca5e
+msgid "Ensure that the necessary template is prepared before configuring AutoScale. When a VM is deployed by using a template and when it comes up, the application should be up and running."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:437
+# a3b170baceb44749ba1bc8c05a2d5b1c
+msgid "If the application is not running, the NetScaler device considers the VM as ineffective and continues provisioning the VMs unconditionally until the resource limit is exhausted."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:441
+# df32d04c33ca462ea54e7d716b2d8ffe
+msgid "Deploy the templates you prepared. Ensure that the applications come up on the first boot and is ready to take the traffic. Observe the time requires to deploy the template. Consider this time when you specify the quiet time while configuring AutoScale."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:446
+# e416b95063a0497fa2b7ca6430c0957c
+msgid "The AutoScale feature supports the SNMP counters that can be used to define conditions for taking scale up or scale down actions. To monitor the SNMP-based counter, ensure that the SNMP agent is installed in the template used for creating the AutoScale VMs, and the SNMP operations work with the configured SNMP community and port by using standard SNMP managers. For example, see `\"Configuring SNMP Community String on a RHELServer\" <#configuring-snmp-community-string-on-a-rhel-server>`_ to configure SNMP on a RHEL machine."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:456
+# 0ac0707e74464bd0840f60e335716a25
+msgid "Ensure that the endpointe.url parameter present in the Global Settings is set to the Management Server API URL. For example, ``http://10.102.102.22:8080/client/api``. In a multi-node Management Server deployment, use the virtual IP address configured in the load balancer for the management server's cluster. Additionally, ensure that the NetScaler device has access to this IP address to provide AutoScale support."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:464
+# f8d93cd584a54fd8b2a72143d4107323
+msgid "If you update the endpointe.url, disable the AutoScale functionality of the load balancer rules in the system, then enable them back to reflect the changes. For more information see :ref:`update-autoscale`."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:468
+# f4e671d2a1814ee7936944319291f882
+msgid "If the API Key and Secret Key are regenerated for an AutoScale user, ensure that the AutoScale functionality of the load balancers that the user participates in are disabled and then enabled to reflect the configuration changes in the NetScaler."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:473
+# 1def24ca3fcf4a9984043a4339307137
+msgid "In an advanced Zone, ensure that at least one VM should be present before configuring a load balancer rule with AutoScale. Having one VM in the network ensures that the network is in implemented state for configuring AutoScale."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:480
+# d722fd21fbb64e1f8fe5c04b72d39a29
+msgid "Configuration"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:482
+# aa34165bbbed4360bb6cebfc7b978d91
+msgid "Specify the following:"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:484
+# 306046475ddb4e789bc88bc1633cdc73
+msgid "|autoscaleateconfig.png|"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:486
+# 951132877c0f4870b67560ae8035c8eb
+msgid "**Template**: A template consists of a base OS image and application. A template is used to provision the new instance of an application on a scaleup action. When a VM is deployed from a template, the VM can start taking the traffic from the load balancer without any admin intervention. For example, if the VM is deployed for a Web service, it should have the Web server running, the database connected, and so on."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:494
+# 313bdbb8a05e46239d80664ae76a92cf
+msgid "**Compute offering**: A predefined set of virtual hardware attributes, including CPU speed, number of CPUs, and RAM size, that the user can select when creating a new virtual machine instance. Choose one of the compute offerings to be used while provisioning a VM instance as part of scaleup action."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:500
+# cd0d1d8ce17d439eb9c360d182e61bc0
+msgid "**Min Instance**: The minimum number of active VM instances that is assigned to a load balancing rule. The active VM instances are the application instances that are up and serving the traffic, and are being load balanced. This parameter ensures that a load balancing rule has at least the configured number of active VM instances are available to serve the traffic."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:508
+# b883f060ac0a4b669952542845307113
+msgid "If an application, such as SAP, running on a VM instance is down for some reason, the VM is then not counted as part of Min Instance parameter, and the AutoScale feature initiates a scaleup action if the number of active VM instances is below the configured value. Similarly, when an application instance comes up from its earlier down state, this application instance is counted as part of the active instance count and the AutoScale process initiates a scaledown action when the active instance count breaches the Max instance value."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:518
+# 1062b529c80542fe9f49822dc8e1226b
+msgid "**Max Instance**: Maximum number of active VM instances that **should be assigned to**\\ a load balancing rule. This parameter defines the upper limit of active VM instances that can be assigned to a load balancing rule."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:523
+# 2f6f81ae0f294d00be1d4501c00d3ef4
+msgid "Specifying a large value for the maximum instance parameter might result in provisioning large number of VM instances, which in turn leads to a single load balancing rule exhausting the VM instances limit specified at the account or domain level."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:529
+# 80e14b2eba9f4b31bf0f73a8fb4665ac
+msgid "If an application, such as SAP, running on a VM instance is down for some reason, the VM is not counted as part of Max Instance parameter. So there may be scenarios where the number of VMs provisioned for a scaleup action might be more than the configured Max Instance value. Once the application instances in the VMs are up from an earlier down state, the AutoScale feature starts aligning to the configured Max Instance value."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:537
+# c05f5503e8994d1bbe38126fc1652574
+msgid "Specify the following scale-up and scale-down policies:"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:539
+# 8b8ee965cf5f45e4a993ef5a61584ee7
+msgid "**Duration**: The duration, in seconds, for which the conditions you specify must be true to trigger a scaleup action. The conditions defined should hold true for the entire duration you specify for an AutoScale action to be invoked."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:544
+# aef0e1b396cc4f4aa88ea919926bc457
+msgid "**Counter**: The performance counters expose the state of the monitored instances. By default, CloudStack offers four performance counters: Three SNMP counters and one NetScaler counter. The SNMP counters are Linux User CPU, Linux System CPU, and Linux CPU Idle. The NetScaler counter is ResponseTime. The root administrator can add additional counters into CloudStack by using the CloudStack API."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:551
+# e13329c9be684765967ad40f1ed75b4e
+msgid "**Operator**: The following five relational operators are supported in AutoScale feature: Greater than, Less than, Less than or equal to, Greater than or equal to, and Equal to."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:555
+# 736606eaa3ac4622b52ed0ab0545ba37
+msgid "**Threshold**: Threshold value to be used for the counter. Once the counter defined above breaches the threshold value, the AutoScale feature initiates a scaleup or scaledown action."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:559
+# e74122a065ed4373a7c1291eb1291e64
+msgid "**Add**: Click Add to add the condition."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:561
+# 7d05f0a9ea384a5790999dfcd7fd3647
+msgid "Additionally, if you want to configure the advanced settings, click Show advanced settings, and specify the following:"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:564
+# 9e8ccf2af53541eea6450c116ba10b0a
+msgid "**Polling interval**: Frequency in which the conditions, combination of counter, operator and threshold, are to be evaluated before taking a scale up or down action. The default polling interval is 30 seconds."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:569
+# 9a0a8077043d427ba02f39207e648c16
+msgid "**Quiet Time**: This is the cool down period after an AutoScale action is initiated. The time includes the time taken to complete provisioning a VM instance from its template and the time taken by an application to be ready to serve traffic. This quiet time allows the fleet to come up to a stable state before any action can take place. The default is 300 seconds."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:576
+# d562af8950534ba78cfad860812c91af
+msgid "**Destroy VM Grace Period**: The duration in seconds, after a scaledown action is initiated, to wait before the VM is destroyed as part of scaledown action. This is to ensure graceful close of any pending sessions or transactions being served by the VM marked for destroy. The default is 120 seconds."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:582
+# b74500ed7cdc4d5e984c9d01a17d6cae
+msgid "**Security Groups**: Security groups provide a way to isolate traffic to the VM instances. A security group is a group of VMs that filter their incoming and outgoing traffic according to a set of rules, called ingress and egress rules. These rules filter network traffic according to the IP address that is attempting to communicate with the VM."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:589
+# 6e921b5c683943bf8e306cb4cd731b76
+msgid "**Disk Offerings**: A predefined set of disk size for primary data storage."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:592
+# 8eeeb8c4bf1749e6b405081fce9318ca
+msgid "**SNMP Community**: The SNMP community string to be used by the NetScaler device to query the configured counter value from the provisioned VM instances. Default is public."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:596
+# 63d93ca18c5245e3aa630d743d5b1fff
+msgid "**SNMP Port**: The port number on which the SNMP agent that run on the provisioned VMs is listening. Default port is 161."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:599
+# 8e4ead8319ea470ba2e3a6183acf7ce2
+msgid "**User**: This is the user that the NetScaler device use to invoke scaleup and scaledown API calls to the cloud. If no option is specified, the user who configures AutoScaling is applied. Specify another user name to override."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:604
+# c5ab8b8578de4f5b8e2aa37c414525aa
+msgid "**Apply**: Click Apply to create the AutoScale configuration."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:608
+# 3d6ec42e045a4082a8798bec5791982a
+msgid "Disabling and Enabling an AutoScale Configuration"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:610
+# ec5c758cc62a40e587a4b6c4fddb434f
+msgid "If you want to perform any maintenance operation on the AutoScale VM instances, disable the AutoScale configuration. When the AutoScale configuration is disabled, no scaleup or scaledown action is performed. You can use this downtime for the maintenance activities. To disable the AutoScale configuration, click the Disable AutoScale |EnableDisable.png| button."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:616
+# 0a60f936b205455c98dceed77b11df3c
+msgid "The button toggles between enable and disable, depending on whether AutoScale is currently enabled or not. After the maintenance operations are done, you can enable the AutoScale configuration back. To enable, open the AutoScale configuration page again, then click the Enable AutoScale |EnableDisable.png| button."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:626
+# f4bb71e85bd344b89fdcb3239a0f51f8
+msgid "Updating an AutoScale Configuration"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:628
+# 3bf60f14a73d43869794736b33b5aa5b
+msgid "You can update the various parameters and add or delete the conditions in a scaleup or scaledown rule. Before you update an AutoScale configuration, ensure that you disable the AutoScale load balancer rule by clicking the Disable AutoScale button."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:633
+# f9665a6811b3410ba434ca755c6451f6
+msgid "After you modify the required AutoScale parameters, click Apply. To apply the new AutoScale policies, open the AutoScale configuration page again, then click the Enable AutoScale button."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:639
+# debb34a5766f45ca8759a81e6401dc05
+msgid "Runtime Considerations"
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:641
+# 57af5a07b00746d1b071d2eb6e80fea1
+msgid "An administrator should not assign a VM to a load balancing rule which is configured for AutoScale."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:644
+# 7df6035fc7ca442bbbb5d7bd0ea0428b
+msgid "Before a VM provisioning is completed if NetScaler is shutdown or restarted, the provisioned VM cannot be a part of the load balancing rule though the intent was to assign it to a load balancing rule. To workaround, rename the AutoScale provisioned VMs based on the rule name or ID so at any point of time the VMs can be reconciled to its load balancing rule."
+msgstr ""
+
+#: ../../networking/external_firewalls_and_load_balancers.rst:651
+# 0eca9ec603bb4fc28eaabd868afa3e27
+msgid "Making API calls outside the context of AutoScale, such as destroyVM, on an autoscaled VM leaves the load balancing configuration in an inconsistent state. Though VM is destroyed from the load balancer rule, NetScaler continues to show the VM as a service assigned to a rule."
+msgstr ""
+
diff --git a/source/locale/pot/networking/global_server_load_balancing.pot b/source/locale/pot/networking/global_server_load_balancing.pot
new file mode 100644
index 0000000..e9acc45
--- /dev/null
+++ b/source/locale/pot/networking/global_server_load_balancing.pot
@@ -0,0 +1,573 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/global_server_load_balancing.rst:18
+# dcd5b9f2eedc4d1682f64e174cd2cef7
+msgid "Global Server Load Balancing Support"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:20
+# 6cf6d74b4dde4e5fb05f41ae52822a4a
+msgid "CloudStack supports Global Server Load Balancing (GSLB) functionalities to provide business continuity, and enable seamless resource movement within a CloudStack environment. CloudStack achieve this by extending its functionality of integrating with NetScaler Application Delivery Controller (ADC), which also provides various GSLB capabilities, such as disaster recovery and load balancing. The DNS redirection technique is used to achieve GSLB in CloudStack."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:28
+# 7396fe0f91a94dcf8d73474623b3c975
+msgid "In order to support this functionality, region level services and service provider are introduced. A new service 'GSLB' is introduced as a region level service. The GSLB service provider is introduced that will provider the GSLB service. Currently, NetScaler is the supported GSLB provider in CloudStack. GSLB functionality works in an Active-Active data center environment."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:37
+# c1b8feb53b76438681b08acf77c25440
+msgid "About Global Server Load Balancing"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:39
+# e03a6a1a69b640308c22260d5737533b
+msgid "Global Server Load Balancing (GSLB) is an extension of load balancing functionality, which is highly efficient in avoiding downtime. Based on the nature of deployment, GSLB represents a set of technologies that is used for various purposes, such as load sharing, disaster recovery, performance, and legal obligations. With GSLB, workloads can be distributed across multiple data centers situated at geographically separated locations. GSLB can also provide an alternate location for accessing a resource in the event of a failure, or to provide a means of shifting traffic easily to simplify maintenance, or both."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:51
+# ba32175058a043b081e7045d04a34334
+msgid "Components of GSLB"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:53
+# 8282609b9ff24cd980a31ea858744fba
+msgid "A typical GSLB environment is comprised of the following components:"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:55
+# 0c4b0b08a37346789443744bef960c26
+msgid "**GSLB Site**: In CloudStack terminology, GSLB sites are represented by zones that are mapped to data centers, each of which has various network appliances. Each GSLB site is managed by a NetScaler appliance that is local to that site. Each of these appliances treats its own site as the local site and all other sites, managed by other appliances, as remote sites. It is the central entity in a GSLB deployment, and is represented by a name and an IP address."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:63
+# e6f8317f00944a5faf27bf059374e211
+msgid "**GSLB Services**: A GSLB service is typically represented by a load balancing or content switching virtual server. In a GSLB environment, you can have a local as well as remote GSLB services. A local GSLB service represents a local load balancing or content switching virtual server. A remote GSLB service is the one configured at one of the other sites in the GSLB setup. At each site in the GSLB setup, you can create one local GSLB service and any number of remote GSLB services."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:72
+# 0d6074d67e874afaafcced32aa2dcad8
+msgid "**GSLB Virtual Servers**: A GSLB virtual server refers to one or more GSLB services and balances traffic between traffic across the VMs in multiple zones by using the CloudStack functionality. It evaluates the configured GSLB methods or algorithms to select a GSLB service to which to send the client requests. One or more virtual servers from different zones are bound to the GSLB virtual server. GSLB virtual server does not have a public IP associated with it, instead it will have a FQDN DNS name."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:81
+# 25269a15ffaf4c48880b969ed8e8ff0b
+msgid "**Load Balancing or Content Switching Virtual Servers**: According to Citrix NetScaler terminology, a load balancing or content switching virtual server represents one or many servers on the local network. Clients send their requests to the load balancing or content switching virtual server's virtual IP (VIP) address, and the virtual server balances the load across the local servers. After a GSLB virtual server selects a GSLB service representing either a local or a remote load balancing or content switching virtual server, the client sends the request to that virtual server's VIP address."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:91
+# a4ae12735c574a18995202afba84a585
+msgid "**DNS VIPs**: DNS virtual IP represents a load balancing DNS virtual server on the GSLB service provider. The DNS requests for domains for which the GSLB service provider is authoritative can be sent to a DNS VIP."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:96
+# 18dae232ea054aad8beb56723f2e9d6d
+msgid "**Authoritative DNS**: ADNS (Authoritative Domain Name Server) is a service that provides actual answer to DNS queries, such as web site IP address. In a GSLB environment, an ADNS service responds only to DNS requests for domains for which the GSLB service provider is authoritative. When an ADNS service is configured, the service provider owns that IP address and advertises it. When you create an ADNS service, the NetScaler responds to DNS queries on the configured ADNS service IP and port."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:107
+# 9efb5a6ae20d45eab31e7fe7ffc87eab
+msgid "How Does GSLB Works in CloudStack?"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:109
+# daac6a57d97c4caebd3fa5d2f5f27324
+msgid "Global server load balancing is used to manage the traffic flow to a web site hosted on two separate zones that ideally are in different geographic locations. The following is an illustration of how GLSB functionality is provided in CloudStack: An organization, xyztelco, has set up a public cloud that spans two zones, Zone-1 and Zone-2, across geographically separated data centers that are managed by CloudStack. Tenant-A of the cloud launches a highly available solution by using xyztelco cloud. For that purpose, they launch two instances each in both the zones: VM1 and VM2 in Zone-1 and VM5 and VM6 in Zone-2. Tenant-A acquires a public IP, IP-1 in Zone-1, and configures a load balancer rule to load balance the traffic between VM1 and VM2 instances. CloudStack orchestrates setting up a virtual server on the LB service provider in Zone-1. Virtual server 1 that is set up on the LB service provider in Zone-1 represents a publicly accessible virtual server that client reaches at IP-1. The client traffic to virtual server 1 at IP-1 will be load balanced across VM1 and VM2 instances."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:126
+# ab85065c7a794a62bb64bb4d17ff62c9
+msgid "Tenant-A acquires another public IP, IP-2 in Zone-2 and sets up a load balancer rule to load balance the traffic between VM5 and VM6 instances. Similarly in Zone-2, CloudStack orchestrates setting up a virtual server on the LB service provider. Virtual server 2 that is setup on the LB service provider in Zone-2 represents a publicly accessible virtual server that client reaches at IP-2. The client traffic that reaches virtual server 2 at IP-2 is load balanced across VM5 and VM6 instances. At this point Tenant-A has the service enabled in both the zones, but has no means to set up a disaster recovery plan if one of the zone fails. Additionally, there is no way for Tenant-A to load balance the traffic intelligently to one of the zones based on load, proximity and so on. The cloud administrator of xyztelco provisions a GSLB service provider to both the zones. A GSLB provider is typically an ADC that has the ability to act as an ADNS (Authoritative Domain Name Server) and has the mechanism to monitor health of virtual servers both at local and remote sites. The cloud admin enables GSLB as a service to the tenants that use zones 1 and 2."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:144
+# 16e02bcf2da14fd48ec4af740ccfc445
+msgid "|gslb.png|"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:146
+# 7f93cb0f9f2e4bc58cfc7f308c019bda
+msgid "Tenant-A wishes to leverage the GSLB service provided by the xyztelco cloud. Tenant-A configures a GSLB rule to load balance traffic across virtual server 1 at Zone-1 and virtual server 2 at Zone-2. The domain name is provided as A.xyztelco.com. CloudStack orchestrates setting up GSLB virtual server 1 on the GSLB service provider at Zone-1. CloudStack binds virtual server 1 of Zone-1 and virtual server 2 of Zone-2 to GLSB virtual server 1. GSLB virtual server 1 is configured to start monitoring the health of virtual server 1 and 2 in Zone-1. CloudStack will also orchestrate setting up GSLB virtual server 2 on GSLB service provider at Zone-2. CloudStack will bind virtual server 1 of Zone-1 and virtual server 2 of Zone-2 to GLSB virtual server 2. GSLB virtual server 2 is configured to start monitoring the health of virtual server 1 and 2. CloudStack will bind the domain A.xyztelco.com to both the GSLB virtual server 1 and 2. At this point, Tenant-A service will be globally reachable at A.xyztelco.com. The private DNS server for the domain xyztelcom.com is configured by the admin out-of-band to resolve the domain A.xyztelco.com to the GSLB providers at both the zones, which are configured as ADNS for the domain A.xyztelco.com. A client when sends a DNS request to resolve A.xyztelcom.com, will eventually get DNS delegation to the address of GSLB providers at zone 1 and 2. A client DNS request will be received by the GSLB provider. The GSLB provider, depending on the domain for which it needs to resolve, will pick up the GSLB virtual server associated with the domain. Depending on the health of the virtual servers being load balanced, DNS request for the domain will be resolved to the public IP associated with the selected virtual server."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:175
+# dcd79b8e29a442d098cb8090a4527144
+msgid "Configuring GSLB"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:177
+# af3fb04e787447d9976ebb989e847e3d
+msgid "To configure a GSLB deployment, you must first configure a standard load balancing setup for each zone. This enables you to balance load across the different servers in each zone in the region. Then on the NetScaler side, configure both NetScaler appliances that you plan to add to each zone as authoritative DNS (ADNS) servers. Next, create a GSLB site for each zone, configure GSLB virtual servers for each site, create GLSB services, and bind the GSLB services to the GSLB virtual servers. Finally, bind the domain to the GSLB virtual servers. The GSLB configurations on the two appliances at the two different zones are identical, although each sites load-balancing configuration is specific to that site."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:189
+# f12e3e8dd3114cc6ab5febf7d770620a
+msgid "Perform the following as a cloud administrator. As per the example given above, the administrator of xyztelco is the one who sets up GSLB:"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:192
+# 9579cd3756414bb59e03052c3c4807de
+msgid "In the cloud.dns.name global parameter, specify the DNS name of your tenant's cloud that make use of the GSLB service."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:195
+# e675df400e4c40079a4b8ac2c3a3a007
+msgid "On the NetScaler side, configure GSLB as given in `Configuring Global Server Load Balancing (GSLB) <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-con.html>`_:"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:199
+# 8366d0a33b5d4328b32668eee7db43a7
+msgid "Configuring a standard load balancing setup."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:201
+# 652a6e0d3f25435bad8a3a37ff14f6de
+msgid "Configure Authoritative DNS, as explained in `Configuring an Authoritative DNS Service <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-adns-svc-tsk.html>`_."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:205
+# eb1be7170a664c05818eea4cebcd652c
+msgid "Configure a GSLB site with site name formed from the domain name details."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:208
+# af0e9c7b27f545b9a2532edf6109ddf3
+msgid "Configure a GSLB site with the site name formed from the domain name."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:211
+# 6c3c9b0f00314c219b51b9ea4a817b37
+msgid "As per the example given above, the site names are A.xyztelco.com and B.xyztelco.com."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:214
+# 8bc45e9126194d24824f0e0e2d92ca1b
+msgid "For more information, see `Configuring a Basic GSLB Site <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-basic-site-tsk.html>`_."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:217
+# 7276993a8c1f4f089886c5bfce5f4f6e
+msgid "Configure a GSLB virtual server."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:219
+# 8d0c82c139184d3992209af4d2e54a6c
+msgid "For more information, see `Configuring a GSLB Virtual Server <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-vsvr-tsk.html>`_."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:222
+# 7db75bd72fa44709ab7adb82ba26f318
+msgid "Configure a GSLB service for each virtual server."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:224
+# 7dd4d9aa1c394ed6859a00b0331f3e5b
+msgid "For more information, see `Configuring a GSLB Service <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-config-svc-tsk.html>`_."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:227
+# 30745365545f4cbca1a5ff6fa73a495f
+msgid "Bind the GSLB services to the GSLB virtual server."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:229
+# f5c32c764b0c44cc9b430cd2c74f5a0b
+msgid "For more information, see `Binding GSLB Services to a GSLB Virtual Server <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-bind-svc-vsvr-tsk.html>`_."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:232
+# 74f55b2693404f1d8b46b1960f0987db
+msgid "Bind domain name to GSLB virtual server. Domain name is obtained from the domain details."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:235
+# 012a1ab7ff7b422995e21b6709b4c6b3
+msgid "For more information, see `Binding a Domain to a GSLB Virtual Server <http://support.citrix.com/proddocs/topic/netscaler-traffic-management-10-map/ns-gslb-bind-dom-vsvr-tsk.html>`_."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:238
+# efe8d44a7dc84347bdc932507e0cf417
+msgid "In each zone that are participating in GSLB, add GSLB-enabled NetScaler device."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:241
+# b4176a11b248487686fbfb80d484f72d
+msgid "For more information, see :ref:`enabling-gslb-in-ns`."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:243
+# 8fc3da50593741b9863599aee89587e8
+msgid "As a domain administrator/ user perform the following:"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:245
+# 8c1293eb2d3746e8abb219c5c4cb7290
+msgid "Add a GSLB rule on both the sites."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:247
+# a78f47a38a364e859b24e482f8eab174
+msgid "See \":ref:`adding-gslb-rule`\"."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:249
+# 17e3b59ea95e4eb39b1290cea67e4801
+msgid "Assign load balancer rules."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:251
+# d37f5840c4d34fa9aa990a0bb0610af9
+msgid "See \":ref:`assigning-lb-rule-gslb`\"."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:255
+# 2553447c986746b582a9f8b495396c3b
+msgid "Prerequisites and Guidelines"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:257
+# 8627b5c519f04c4bb75b82af96f25418
+msgid "The GSLB functionality is supported both Basic and Advanced zones."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:259
+# c2b5f208b13f4b07b6755c0a53fa1104
+msgid "GSLB is added as a new network service."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:261
+# 3c6e0da5ecd148d599a35191c7e92678
+msgid "GSLB service provider can be added to a physical network in a zone."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:263
+# 6c159f1bc2224bb2b35dd03ec51bc6b1
+msgid "The admin is allowed to enable or disable GSLB functionality at region level."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:266
+# 6367e49f50d0418c92b7b6fc7cc91a39
+msgid "The admin is allowed to configure a zone as GSLB capable or enabled."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:268
+# a66b5c6d51534ab492d244d518221776
+msgid "A zone shall be considered as GSLB capable only if a GSLB service provider is provisioned in the zone."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:271
+# 0ea762e8718b465eaacf40a6118c8f7f
+msgid "When users have VMs deployed in multiple availability zones which are GSLB enabled, they can use the GSLB functionality to load balance traffic across the VMs in multiple zones."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:275
+# ed2130b4027e41e3833699a89ff82708
+msgid "The users can use GSLB to load balance across the VMs across zones in a region only if the admin has enabled GSLB in that region."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:278
+# 1b374fea614b459eb39cfbe4f20478c9
+msgid "The users can load balance traffic across the availability zones in the same region or different regions."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:281
+# 62da6f878356420f9becc6fffbe1ae6d
+msgid "The admin can configure DNS name for the entire cloud."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:283
+# 799fe9490296493e9d86d0ea8cdc9297
+msgid "The users can specify an unique name across the cloud for a globally load balanced service. The provided name is used as the domain name under the DNS name associated with the cloud."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:287
+# 1d6c20de63954971a720227985a74433
+msgid "The user-provided name along with the admin-provided DNS name is used to produce a globally resolvable FQDN for the globally load balanced service of the user. For example, if the admin has configured xyztelco.com as the DNS name for the cloud, and user specifies 'foo' for the GSLB virtual service, then the FQDN name of the GSLB virtual service is foo.xyztelco.com."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:294
+# a7817e36fe2c4ea58737d1a5ae3db30b
+msgid "While setting up GSLB, users can select a load balancing method, such as round robin, for using across the zones that are part of GSLB."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:297
+# 971bcd7f3cf24bbbb424a020cc7c06a4
+msgid "The user shall be able to set weight to zone-level virtual server. Weight shall be considered by the load balancing method for distributing the traffic."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:301
+# 6f3d31dca71d4b608fa90d1eb73ecee2
+msgid "The GSLB functionality shall support session persistence, where series of client requests for particular domain name is sent to a virtual server on the same zone."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:305
+# bfaf6196eae343259864ac2443ff5746
+msgid "Statistics is collected from each GSLB virtual server."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:311
+# d2f3468cd4ac44d58c53e731e50e35dd
+msgid "Enabling GSLB in NetScaler"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:313
+# d51d618416764b5c843fc13bfd2dfa6d
+msgid "In each zone, add GSLB-enabled NetScaler device for load balancing."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:315
+# 91d1d3b496c34b179f0b865500b6bf93
+msgid "Log in as administrator to the CloudStack UI."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:317
+# cc1ae38bffd84c058812510e8495b73f
+msgid "In the left navigation bar, click Infrastructure."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:319
+# 46ba7c7f81d04aa78f0c04d3d045bc8a
+msgid "In Zones, click View More."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:321
+# 1feb8d2e09014d9989264c48ece8fc81
+msgid "Choose the zone you want to work with."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:323
+# 82a50383b1124be48db8d0c5721e9f13
+msgid "Click the Physical Network tab, then click the name of the physical network."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:326
+# 75224089389e4bee8e89a1caf1dc5880
+msgid "In the Network Service Providers node of the diagram, click Configure."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:329
+# 410a9b626bf9412a9f482c2df1aac784
+msgid "You might have to scroll down to see this."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:331
+# 1d32a851fb92436c8e045ccc828641f4
+msgid "Click NetScaler."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:333
+# af72e8614fc44c60af3004624dba03b1
+msgid "Click Add NetScaler device and provide the following:"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:335
+# 6290f4f42d054ac28661b16c5366b62f
+msgid "For NetScaler:"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:337
+# 8e09b55d68a849d089029f2c893e3e97
+msgid "**IP Address**: The IP address of the SDX."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:339
+# 9b9b4165d2ee4e64b3b0b04390702686
+msgid "**Username/Password**: The authentication credentials to access the device. CloudStack uses these credentials to access the device."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:343
+# 212ab71ac16a49309da99e2870717faa
+msgid "**Type**: The type of device that is being added. It could be F5 Big Ip Load Balancer, NetScaler VPX, NetScaler MPX, or NetScaler SDX. For a comparison of the NetScaler types, see the CloudStack Administration Guide."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:348
+# 3d72c6cb5cbb49418002a5e3acf1617c
+msgid "**Public interface**: Interface of device that is configured to be part of the public network."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:351
+# 5bbed919dc2c45008af4312d028cfbd7
+msgid "**Private interface**: Interface of device that is configured to be part of the private network."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:354
+# fb82ba2e06e34aaf9ab8e8fa8362b43d
+msgid "**GSLB service**: Select this option."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:356
+# 8a1e3ad262934da086878740aefca5fc
+msgid "**GSLB service Public IP**: The public IP address of the NAT translator for a GSLB service that is on a private network."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:359
+# 5ca3fc19dd8e4706872b9e3af0652c2f
+msgid "**GSLB service Private IP**: The private IP of the GSLB service."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:361
+# 8f1a8fd9ec814e02970f7edf85c8fad1
+msgid "**Number of Retries**. Number of times to attempt a command on the device before considering the operation failed. Default is 2."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:364
+# 2416b7a9e5fa43fdb27834cb7e46253b
+msgid "**Capacity**: The number of networks the device can handle."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:366
+# c9166740fb2747a7abd4ae6c0851aabc
+msgid "**Dedicated**: When marked as dedicated, this device will be dedicated to a single account. When Dedicated is checked, the value in the Capacity field has no significance implicitly, its value is 1."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:371
+# e7f874eb36ba4cd380f7a50d5bff8909
+msgid "Click OK."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:377
+# d1556618bd5d4d18862c048d52694dd4
+msgid "Adding a GSLB Rule"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:379
+#: ../../networking/global_server_load_balancing.rst:423
+# c06bbbd0cb824ecc8ef3d7956571f739
+# 2b618c03ffb14afb99d7e63813820288
+msgid "Log in to the CloudStack UI as a domain administrator or user."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:381
+#: ../../networking/global_server_load_balancing.rst:425
+# 3b04d23a46774662bbca98318323a71e
+# 62eb7d6a5d9b4256bde0fcafb9f42b7f
+msgid "In the left navigation pane, click Region."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:383
+#: ../../networking/global_server_load_balancing.rst:427
+# 940f5610d0484910bf9e9ba31728be30
+# 581952b854514ed78884cc712ee4ec94
+msgid "Select the region for which you want to create a GSLB rule."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:385
+#: ../../networking/global_server_load_balancing.rst:429
+# fc1d362cc95a4668b2a24c7c0f488348
+# 8519e9d4ad6d46989865460e20b186b6
+msgid "In the Details tab, click View GSLB."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:387
+# f59a742f9f1b4f37b6f0bc0b062028d6
+msgid "Click Add GSLB."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:389
+# ca546577015a45af8ddcdc3d2ad22f3a
+msgid "The Add GSLB page is displayed as follows:"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:391
+# b0b6437c269342ff9099b6da9a6d5b9f
+msgid "|gslb-add.png|"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:393
+# 767ce39d9a094fda85465381d3a93bad
+msgid "Specify the following:"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:395
+# affa9e59440b4f4e9e6428e887d12582
+msgid "**Name**: Name for the GSLB rule."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:397
+# 82b72cbf0f8949fdab2de931138620c5
+msgid "**Description**: (Optional) A short description of the GSLB rule that can be displayed to users."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:400
+# 8a6b82bfcd3a469c838315b17f4cd014
+msgid "**GSLB Domain Name**: A preferred domain name for the service."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:402
+# ff5539d5f09f48bc80c0cf9dc83dcca0
+msgid "**Algorithm**: (Optional) The algorithm to use to load balance the traffic across the zones. The options are Round Robin, Least Connection, and Proximity."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:406
+# b07f4dffc105427389bb8e089a71f9f0
+msgid "**Service Type**: The transport protocol to use for GSLB. The options are TCP and UDP."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:409
+# 03ffe3890f5c4ea79836cfa0cc96986f
+msgid "**Domain**: (Optional) The domain for which you want to create the GSLB rule."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:412
+# 5d0367f6567241968e5d6cac6f8ab34b
+msgid "**Account**: (Optional) The account on which you want to apply the GSLB rule."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:415
+#: ../../networking/global_server_load_balancing.rst:439
+# 0161504934d746e39b05e6b50e264faf
+# 8c377e12f8494a009d5eed7e06824fe3
+msgid "Click OK to confirm."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:421
+# f61c6b78ef4940129243771e21d78f4c
+msgid "Assigning Load Balancing Rules to GSLB"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:431
+# 54cc7b916ceb420584020f5ff230b79c
+msgid "Select the desired GSLB."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:433
+# 5e2a1bf3adfc41bab4bea1a489f9bda1
+msgid "Click view assigned load balancing."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:435
+# 269db9ca8770495f9c5bc08491e61bc6
+msgid "Click assign more load balancing."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:437
+# eceeb5fccdfa4cac904ef8fb945242c9
+msgid "Select the load balancing rule you have created for the zone."
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:443
+# d8792daad4a94b4589452d5b61f75cd9
+msgid "Known Limitation"
+msgstr ""
+
+#: ../../networking/global_server_load_balancing.rst:445
+# 7424fdf000e3479c910e72fbbaaa0169
+msgid "Currently, CloudStack does not support orchestration of services across the zones. The notion of services and service providers in region are to be introduced."
+msgstr ""
+
diff --git a/source/locale/pot/networking/guest_ip_ranges.pot b/source/locale/pot/networking/guest_ip_ranges.pot
new file mode 100644
index 0000000..2e32f45
--- /dev/null
+++ b/source/locale/pot/networking/guest_ip_ranges.pot
@@ -0,0 +1,33 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/guest_ip_ranges.rst:18
+# c4f6e8eb1ed7428a8132309d84e4b1bf
+msgid "Guest IP Ranges"
+msgstr ""
+
+#: ../../networking/guest_ip_ranges.rst:20
+# ef6d3891253c4ed58a8a51c2f86b51dc
+msgid "The IP ranges for guest network traffic are set on a per-account basis by the user. This allows the users to configure their network in a fashion that will enable VPN linking between their guest network and their clients."
+msgstr ""
+
+#: ../../networking/guest_ip_ranges.rst:25
+# 943864c06f494d7ca4f4310246ba996a
+msgid "In shared networks in Basic zone and Security Group-enabled Advanced networks, you will have the flexibility to add multiple guest IP ranges from different subnets. You can add or remove one IP range at a time. For more information, see `\"About Multiple IP Ranges\" <#about-multiple-ip-ranges>`_."
+msgstr ""
+
diff --git a/source/locale/pot/networking/guest_traffic.pot b/source/locale/pot/networking/guest_traffic.pot
new file mode 100644
index 0000000..4cb5bbb
--- /dev/null
+++ b/source/locale/pot/networking/guest_traffic.pot
@@ -0,0 +1,53 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/guest_traffic.rst:18
+# 6a1d02b308ae4f228e4104aa95e39ee3
+msgid "Guest Traffic"
+msgstr ""
+
+#: ../../networking/guest_traffic.rst:20
+# 77e0128afe644aa9a04259e24cb22595
+msgid "A network can carry guest traffic only between VMs within one zone. Virtual machines in different zones cannot communicate with each other using their IP addresses; they must communicate with each other by routing through a public IP address."
+msgstr ""
+
+#: ../../networking/guest_traffic.rst:25
+# 79cb326a48f942949bf3dfe341a3664f
+msgid "See a typical guest traffic setup given below:"
+msgstr ""
+
+#: ../../networking/guest_traffic.rst:27
+# e0ac4742331840b89eef72912ffd2138
+msgid "|guest-traffic-setup.png|"
+msgstr ""
+
+#: ../../networking/guest_traffic.rst:29
+# 685689cd44444e13aefa015c58761ebb
+msgid "Typically, the Management Server automatically creates a virtual router for each network. A virtual router is a special virtual machine that runs on the hosts. Each virtual router in an isolated network has three network interfaces. If multiple public VLAN is used, the router will have multiple public interfaces. Its eth0 interface serves as the gateway for the guest traffic and has the IP address of 10.1.1.1. Its eth1 interface is used by the system to configure the virtual router. Its eth2 interface is assigned a public IP address for public traffic. If multiple public VLAN is used, the router will have multiple public interfaces."
+msgstr ""
+
+#: ../../networking/guest_traffic.rst:40
+# c07d5440a8e64d5b912e6e98e6f9d078
+msgid "The virtual router provides DHCP and will automatically assign an IP address for each guest VM within the IP range assigned for the network. The user can manually reconfigure guest VMs to assume different IP addresses."
+msgstr ""
+
+#: ../../networking/guest_traffic.rst:45
+# 360d9d124254479e85292973d6d8e7f9
+msgid "Source NAT is automatically configured in the virtual router to forward outbound traffic for all guest VMs"
+msgstr ""
+
diff --git a/source/locale/pot/networking/inter_vlan_routing.pot b/source/locale/pot/networking/inter_vlan_routing.pot
new file mode 100644
index 0000000..d7b6b80
--- /dev/null
+++ b/source/locale/pot/networking/inter_vlan_routing.pot
@@ -0,0 +1,118 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/inter_vlan_routing.rst:18
+# 536a6b6a19a04686832c0c8f3202472a
+msgid "About Inter-VLAN Routing (nTier Apps)"
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:20
+# 01903cae08524fb18fb51475e29cccc5
+msgid "Inter-VLAN Routing (nTier Apps) is the capability to route network traffic between VLANs. This feature enables you to build Virtual Private Clouds (VPC), an isolated segment of your cloud, that can hold multi-tier applications. These tiers are deployed on different VLANs that can communicate with each other. You provision VLANs to the tiers your create, and VMs can be deployed on different tiers. The VLANs are connected to a virtual router, which facilitates communication between the VMs. In effect, you can segment VMs by means of VLANs into different networks that can host multi-tier applications, such as Web, Application, or Database. Such segmentation by means of VLANs logically separate application VMs for higher security and lower broadcasts, while remaining physically connected to the same device."
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:33
+# d835d5a69985471085a5688b045c4e38
+msgid "This feature is supported on XenServer, KVM, and VMware hypervisors."
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:35
+# 7aecd1ac66b84f9cb92b03fea7d5edde
+msgid "The major advantages are:"
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:37
+# dca4c4be393c4d7bbcda75f49ffc8efc
+msgid "The administrator can deploy a set of VLANs and allow users to deploy VMs on these VLANs. A guest VLAN is randomly alloted to an account from a pre-specified set of guest VLANs. All the VMs of a certain tier of an account reside on the guest VLAN allotted to that account."
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:43
+# d5d8b41e126e4b38913d0cf7de1ec29d
+msgid "A VLAN allocated for an account cannot be shared between multiple accounts."
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:45
+# 4e04be2a6cef4fa8973d317232221018
+msgid "The administrator can allow users create their own VPC and deploy the application. In this scenario, the VMs that belong to the account are deployed on the VLANs allotted to that account."
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:49
+# 48018251e76046c4a606035de8d1b4d5
+msgid "Both administrators and users can create multiple VPCs. The guest network NIC is plugged to the VPC virtual router when the first VM is deployed in a tier."
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:53
+# cc50778ecfab43c38af3373511f47072
+msgid "The administrator can create the following gateways to send to or receive traffic from the VMs:"
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:56
+# 5d91169a83a5400b8408b6ce4ccb84f5
+msgid "**VPN Gateway**: For more information, see `\"Creating a VPN gateway for the VPC\" <#creating-a-vpn-gateway-for-the-vpc>`_."
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:59
+# 1f0ed1ecf964455ab40301bdf5ab2dc2
+msgid "**Public Gateway**: The public gateway for a VPC is added to the virtual router when the virtual router is created for VPC. The public gateway is not exposed to the end users. You are not allowed to list it, nor allowed to create any static routes."
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:64
+# b843201a793749bb924d48f21be04e09
+msgid "**Private Gateway**: For more information, see \":ref:`adding-priv-gw-vpc`\"."
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:66
+# a4ac63d4b99a4edd968087d0f622647a
+msgid "Both administrators and users can create various possible destinations-gateway combinations. However, only one gateway of each type can be used in a deployment."
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:70
+# 50735b7154a64b7880f5543c4792b1c0
+msgid "For example:"
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:72
+# bdd41dc64438436aac12d9f1c8d5a8bc
+msgid "**VLANs and Public Gateway**: For example, an application is deployed in the cloud, and the Web application VMs communicate with the Internet."
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:76
+# f2c3b70246534d5aabdd3954a25ba1eb
+msgid "**VLANs, VPN Gateway, and Public Gateway**: For example, an application is deployed in the cloud; the Web application VMs communicate with the Internet; and the database VMs communicate with the on-premise devices."
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:81
+# 7fb2fe01c3484b80a30d4c6edb0b5782
+msgid "The administrator can define Network Access Control List (ACL) on the virtual router to filter the traffic among the VLANs or between the Internet and a VLAN. You can define ACL based on CIDR, port range, protocol, type code (if ICMP protocol is selected) and Ingress/Egress type."
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:87
+# 95cd03acfa2948c682ec51eaf24346be
+msgid "The following figure shows the possible deployment scenarios of a Inter-VLAN setup:"
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:90
+# a9f3216208ba417681d8885848d2a414
+msgid "|mutltier.png|"
+msgstr ""
+
+#: ../../networking/inter_vlan_routing.rst:92
+# 785b1c5286424a3680f6ffa4fa40de5a
+msgid "To set up a multi-tier Inter-VLAN deployment, see \":ref:`configuring-vpc`\"."
+msgstr ""
+
diff --git a/source/locale/pot/networking/ip_forwarding_and_firewalling.pot b/source/locale/pot/networking/ip_forwarding_and_firewalling.pot
new file mode 100644
index 0000000..009b357
--- /dev/null
+++ b/source/locale/pot/networking/ip_forwarding_and_firewalling.pot
@@ -0,0 +1,393 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:18
+# 3ec46c2d67cb4acc87705b3f0985e5c8
+msgid "IP Forwarding and Firewalling"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:20
+# 5bb709bf233742ce8f3a83dc5ce7cf26
+msgid "By default, all incoming traffic to the public IP address is rejected. All outgoing traffic from the guests is also blocked by default."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:23
+# 83f985061e4e4301aa5ce50049ea4565
+msgid "To allow outgoing traffic, follow the procedure in :ref:`egress-fw-rules`."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:25
+# 1328a8040ae7487b8f7ed1dcaaf5a596
+msgid "To allow incoming traffic, users may set up firewall rules and/or port forwarding rules. For example, you can use a firewall rule to open a range of ports on the public IP address, such as 33 through 44. Then use port forwarding rules to direct traffic from individual ports within that range to specific ports on user VMs. For example, one port forwarding rule could route incoming traffic on the public IP's port 33 to port 100 on one user VM's private IP."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:35
+# 88ee727310bb4a5789291e8e48578dab
+msgid "Firewall Rules"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:37
+# 073cb21345c44ce2a3f2ce3446d4ad3a
+msgid "By default, all incoming traffic to the public IP address is rejected by the firewall. To allow external traffic, you can open firewall ports by specifying firewall rules. You can optionally specify one or more CIDRs to filter the source IPs. This is useful when you want to allow only incoming requests from certain IP addresses."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:43
+# b43e4fc4f43841c9aebd342bbd60b33d
+msgid "You cannot use firewall rules to open ports for an elastic IP address. When elastic IP is used, outside access is instead controlled through the use of security groups. See `\"Adding a Security Group\" <#adding-a-security-group>`_."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:48
+# 36b1e8acd3ef4b1cb7a7ffd1f60599c5
+msgid "In an advanced zone, you can also create egress firewall rules by using the virtual router. For more information, see \":ref:`egress-fw-rules`\"."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:51
+# 2aeb084c075b4451b0911c2a6baf0f84
+msgid "Firewall rules can be created using the Firewall tab in the Management Server UI. This tab is not displayed by default when CloudStack is installed. To display the Firewall tab, the CloudStack administrator must set the global configuration parameter firewall.rule.ui.enabled to \"true.\""
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:57
+# e1408eeb730f4709bbba8852f79807fd
+msgid "To create a firewall rule:"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:59
+#: ../../networking/ip_forwarding_and_firewalling.rst:132
+#: ../../networking/ip_forwarding_and_firewalling.rst:245
+# 098b22043ec643559c039b39aa24d618
+# f62479b013c241a791c42b8843bd140d
+# c384f1b44804485fba23fe018c16683e
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:61
+#: ../../networking/ip_forwarding_and_firewalling.rst:134
+# a633160d3ee343639365b9067af58eb1
+# c6c7495d464a4262ace3361c7cce9b5b
+msgid "In the left navigation, choose Network."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:63
+# ff56e69810c34ee4a08280a7ef06cfbb
+msgid "Click the name of the network where you want to work with."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:65
+# d546be88025a4254b8eecf1f0b16bdf0
+msgid "Click View IP Addresses."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:67
+# 0c60a7fde5644f9188c0bf190c166890
+msgid "Click the IP address you want to work with."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:69
+# 0e0775a902554fa68fc54157ed73ed0a
+msgid "Click the Configuration tab and fill in the following values."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:71
+# 8bb21f2deca7442683f782de4a83935f
+msgid "**Source CIDR**: (Optional) To accept only traffic from IP addresses within a particular address block, enter a CIDR or a comma-separated list of CIDRs. Example: 192.168.0.0/22. Leave empty to allow all CIDRs."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:76
+# 4cb05fbe28ae408a8df34014da711575
+msgid "**Protocol**: The communication protocol in use on the opened port(s)."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:79
+# e59d4d2a187f4510a91409fac5cfb51c
+msgid "**Start Port and End Port**: The port(s) you want to open on the firewall. If you are opening a single port, use the same number in both fields"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:83
+# 3274875afce44bbe9d7017bb4e2fc2b2
+msgid "**ICMP Type and ICMP Code**: Used only if Protocol is set to ICMP. Provide the type and code required by the ICMP protocol to fill out the ICMP header. Refer to ICMP documentation for more details if you are not sure what to enter"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:88
+#: ../../networking/ip_forwarding_and_firewalling.rst:163
+#: ../../networking/ip_forwarding_and_firewalling.rst:276
+# 41821a610d844daf8255026b71299059
+# 1d39fcb3a5e34d769f89885db9866836
+# 2319658c89b74a0294ce8f0a253a4d53
+msgid "Click Add."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:94
+# eec2e0a57feb4eca85c58ac1b58b228b
+msgid "Egress Firewall Rules in an Advanced Zone"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:96
+# 3bae6d1e0fb543beaeb466c40aeddfc3
+msgid "The egress traffic originates from a private network to a public network, such as the Internet. By default, the egress traffic is blocked in default network offerings, so no outgoing traffic is allowed from a guest network to the Internet. However, you can control the egress traffic in an Advanced zone by creating egress firewall rules. When an egress firewall rule is applied, the traffic specific to the rule is allowed and the remaining traffic is blocked. When all the firewall rules are removed the default policy, Block, is applied."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:107
+# 80fbdba2a681463894376f620458c160
+msgid "Prerequisites and Guidelines"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:109
+# 998ae537c5664319b836e769ab967fc3
+msgid "Consider the following scenarios to apply egress firewall rules:"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:111
+# 18a68e97f28f4f7898b92513d34e5e26
+msgid "Egress firewall rules are supported on Juniper SRX and virtual router."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:114
+# a4eaae6cb4474e5a8182092404f48116
+msgid "The egress firewall rules are not supported on shared networks."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:116
+# 85bdd2e7a708485bae147bfa93cdcb1b
+msgid "Allow the egress traffic from specified source CIDR. The Source CIDR is part of guest network CIDR."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:119
+# d9af348ce95e47a0bae91a55488b1155
+msgid "Allow the egress traffic with protocol TCP,UDP,ICMP, or ALL."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:121
+# 786d85af2e334cf5a8a25fc59dde7cb5
+msgid "Allow the egress traffic with protocol and destination port range. The port range is specified for TCP, UDP or for ICMP type and code."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:124
+# 8d9e5fa49cb648a6ad0b917f06176014
+msgid "The default policy is Allow for the new network offerings, whereas on upgrade existing network offerings with firewall service providers will have the default egress policy Deny."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:130
+# ee1ee0417255469abce66dbfd40f9611
+msgid "Configuring an Egress Firewall Rule"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:136
+# 4d43b047c25a4605acc888b025d376aa
+msgid "In Select view, choose Guest networks, then click the Guest network you want."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:139
+# 4c11dfc739f94ce0995b7c7bdf566e5d
+msgid "To add an egress rule, click the Egress rules tab and fill out the following fields to specify what type of traffic is allowed to be sent out of VM instances in this guest network:"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:143
+# a476fe8da41b43168b89c7b558afcb48
+msgid "|egress-firewall-rule.png|"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:145
+# d56527f1ac864c5c9d47df9e55c225cf
+msgid "**CIDR**: (Add by CIDR only) To send traffic only to the IP addresses within a particular address block, enter a CIDR or a comma-separated list of CIDRs. The CIDR is the base IP address of the destination. For example, 192.168.0.0/22. To allow all CIDRs, set to 0.0.0.0/0."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:151
+# c1e8fac9fa8046d8a9315511c011542e
+msgid "**Protocol**: The networking protocol that VMs uses to send outgoing traffic. The TCP and UDP protocols are typically used for data exchange and end-user communications. The ICMP protocol is typically used to send error messages or network monitoring data."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:156
+# 6b9d46d4c88d48c98d3fa4fcceb60e29
+msgid "**Start Port, End Port**: (TCP, UDP only) A range of listening ports that are the destination for the outgoing traffic. If you are opening a single port, use the same number in both fields."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:160
+# 17c266c56f194132a6fc948f3142e4bc
+msgid "**ICMP Type, ICMP Code**: (ICMP only) The type of message and error code that are sent."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:167
+# f0100304289f4a67b01e8f6c52976a10
+msgid "Configuring the Default Egress Policy"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:169
+# a802326f92404392beacd9675985c106
+msgid "The default egress policy for Isolated guest network is configured by using Network offering. Use the create network offering option to determine whether the default policy should be block or allow all the traffic to the public network from a guest network. Use this network offering to create the network. If no policy is specified, by default all the traffic is allowed from the guest network that you create by using this network offering."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:177
+# 9b5e480b6757449ab8272d3e7a691110
+msgid "You have two options: Allow and Deny."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:180
+# 9b8d4463d6024d8589cc801658fa7bab
+msgid "Allow"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:182
+# 01d29e0665f84d548d9f41399d9258d8
+msgid "If you select Allow for a network offering, by default egress traffic is allowed. However, when an egress rule is configured for a guest network, rules are applied to block the specified traffic and rest are allowed. If no egress rules are configured for the network, egress traffic is accepted."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:189
+# 63816b9551f04933aa99e27cc3dc34f1
+msgid "Deny"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:191
+# 1952d7735fb746a6834bbdeed4c1eaa9
+msgid "If you select Deny for a network offering, by default egress traffic for the guest network is blocked. However, when an egress rules is configured for a guest network, rules are applied to allow the specified traffic. While implementing a guest network, CloudStack adds the firewall egress rule specific to the default egress policy for the guest network."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:198
+# 238db98415e74782937deddd3970b285
+msgid "This feature is supported only on virtual router and Juniper SRX."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:200
+# e460df960d61405db56e64d21a8c43d7
+msgid "Create a network offering with your desirable default egress policy:"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:202
+# 5271ad0a1d4a4a27aa5597b044b42acf
+msgid "Log in with admin privileges to the CloudStack UI."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:204
+# fd49a59627284ffda66fef7096eaa709
+msgid "In the left navigation bar, click Service Offerings."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:206
+# 7fce8b96f6e64727bb6063766c828bdd
+msgid "In Select Offering, choose Network Offering."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:208
+# ef8895c197ff4343b04aecc73b5a9294
+msgid "Click Add Network Offering."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:210
+# abb73d0d766d4d32a4bbe32137193cad
+msgid "In the dialog, make necessary choices, including firewall provider."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:213
+# 932c30480a1f4e3ea92f06ba4296ae45
+msgid "In the Default egress policy field, specify the behaviour."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:215
+# 41d012a83e774bdeaeac42e5b44d851c
+msgid "Click OK."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:217
+# 5a1192bc5c8a4c3c930879e56c5d58bb
+msgid "Create an isolated network by using this network offering."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:219
+# 3918ff66d4914376a4707b9db470a027
+msgid "Based on your selection, the network will have the egress public traffic blocked or allowed."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:224
+# 29ffedbd547e431f95d82b075df5ea66
+msgid "Port Forwarding"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:226
+# d9efd9df178e4f7c8d81b2ba24a9fdbb
+msgid "A port forward service is a set of port forwarding rules that define a policy. A port forward service is then applied to one or more guest VMs. The guest VM then has its inbound network access managed according to the policy defined by the port forwarding service. You can optionally specify one or more CIDRs to filter the source IPs. This is useful when you want to allow only incoming requests from certain IP addresses to be forwarded."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:234
+# ae4f5d3e4bc24f8584c17c3057688144
+msgid "A guest VM can be in any number of port forward services. Port forward services can be defined but have no members. If a guest VM is part of more than one network, port forwarding rules will function only if they are defined on the default network"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:239
+# 89ce910349884d8ea8a7b4f6aee10613
+msgid "You cannot use port forwarding to open ports for an elastic IP address. When elastic IP is used, outside access is instead controlled through the use of security groups. See Security Groups."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:243
+# 263627f6e1de45999d0e9ab68c8a1a2d
+msgid "To set up port forwarding:"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:247
+# 41c9b9f2473e4b5aa0d8ea3c54e45b1b
+msgid "If you have not already done so, add a public IP address range to a zone in CloudStack. See Adding a Zone and Pod in the Installation Guide."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:251
+# 2c98fbd961df4ef28a276b3ccf1d53c0
+msgid "Add one or more VM instances to CloudStack."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:253
+# 17a544cc6c8a42cbaef47575f1029173
+msgid "In the left navigation bar, click Network."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:255
+# ade84b4f63694fadbe6c835b52ba796f
+msgid "Click the name of the guest network where the VMs are running."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:257
+# 48ab8bf9d7e04ca7a13eaf58eeead278
+msgid "Choose an existing IP address or acquire a new IP address. See `\"Acquiring a New IP Address\" <#acquiring-a-new-ip-address>`_. Click the name of the IP address in the list."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:261
+# da392889cd304ce8973c2b4b8341665b
+msgid "Click the Configuration tab."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:263
+# 4d02af0497b544d89616ff1ddf286767
+msgid "In the Port Forwarding node of the diagram, click View All."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:265
+# ee9101e2c97447d4b23f89177c60e7ab
+msgid "Fill in the following:"
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:267
+# e9d9402255ae405781f85b32409d3654
+msgid "**Public Port**: The port to which public traffic will be addressed on the IP address you acquired in the previous step."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:270
+# bf8d351e8ca649ca9931311f402ea7bc
+msgid "**Private Port**: The port on which the instance is listening for forwarded public traffic."
+msgstr ""
+
+#: ../../networking/ip_forwarding_and_firewalling.rst:273
+# 5140efc173fd46e194d6c4827a8a67fc
+msgid "**Protocol**: The communication protocol in use between the two ports"
+msgstr ""
+
diff --git a/source/locale/pot/networking/ip_load_balancing.pot b/source/locale/pot/networking/ip_load_balancing.pot
new file mode 100644
index 0000000..4d79eb1
--- /dev/null
+++ b/source/locale/pot/networking/ip_load_balancing.pot
@@ -0,0 +1,48 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/ip_load_balancing.rst:18
+# 974ac2a4e2dd4641920f5361833b3e12
+msgid "IP Load Balancing"
+msgstr ""
+
+#: ../../networking/ip_load_balancing.rst:20
+# 7eaede5161a04e0cbb6a4b15fc2de3b2
+msgid "The user may choose to associate the same public IP for multiple guests. CloudStack implements a TCP-level load balancer with the following policies."
+msgstr ""
+
+#: ../../networking/ip_load_balancing.rst:24
+# 8c044fa0f1714d63815a08d7a658b08d
+msgid "Round-robin"
+msgstr ""
+
+#: ../../networking/ip_load_balancing.rst:26
+# 6732c79a9ecf4eec91f6ddea4d55833a
+msgid "Least connection"
+msgstr ""
+
+#: ../../networking/ip_load_balancing.rst:28
+# 28c3b6fa228545e382ed84cceaf1666a
+msgid "Source IP"
+msgstr ""
+
+#: ../../networking/ip_load_balancing.rst:30
+# 0eac6f2afde349909f9ee8d0148a99b6
+msgid "This is similar to port forwarding but the destination may be multiple IP addresses."
+msgstr ""
+
diff --git a/source/locale/pot/networking/ip_reservation_in_guest_networks.pot b/source/locale/pot/networking/ip_reservation_in_guest_networks.pot
new file mode 100644
index 0000000..4d28e10
--- /dev/null
+++ b/source/locale/pot/networking/ip_reservation_in_guest_networks.pot
@@ -0,0 +1,238 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:18
+# 25e21d9bd50e4db29764c09ec3255ea1
+msgid "IP Reservation in Isolated Guest Networks"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:20
+# f043acb1e27b49aebecf48876dca90d4
+msgid "In isolated guest networks, a part of the guest IP address space can be reserved for non-CloudStack VMs or physical servers. To do so, you configure a range of Reserved IP addresses by specifying the CIDR when a guest network is in Implemented state. If your customers wish to have non-CloudStack controlled VMs or physical servers on the same network, they can share a part of the IP address space that is primarily provided to the guest network."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:28
+# fe77cb19c33a475f9389f57e62e466e0
+msgid "In an Advanced zone, an IP address range or a CIDR is assigned to a network when the network is defined. The CloudStack virtual router acts as the DHCP server and uses CIDR for assigning IP addresses to the guest VMs. If you decide to reserve CIDR for non-CloudStack purposes, you can specify a part of the IP address range or the CIDR that should only be allocated by the DHCP service of the virtual router to the guest VMs created in CloudStack. The remaining IPs in that network are called Reserved IP Range. When IP reservation is configured, the administrator can add additional VMs or physical servers that are not part of CloudStack to the same network and assign them the Reserved IP addresses. CloudStack guest VMs cannot acquire IPs from the Reserved IP Range."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:43
+# 9428ab05bfce48cb9dce92078998854c
+msgid "IP Reservation Considerations"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:45
+# 5780d0b48e6f44cbb972018a31489ebb
+msgid "Consider the following before you reserve an IP range for non-CloudStack machines:"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:48
+# cc50e370af0c450588c711e282c0ac93
+msgid "IP Reservation is supported only in Isolated networks."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:50
+# 9543f099f9de4fc3a8a815cd3cb04f40
+msgid "IP Reservation can be applied only when the network is in Implemented state."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:53
+# c7bc13975b37474299e4a7a65c56ed75
+msgid "No IP Reservation is done by default."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:55
+# f7a970b25ef94f48bc75a5c8a5fd0a0c
+msgid "Guest VM CIDR you specify must be a subset of the network CIDR."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:57
+# a96a64591c4d498ca7c95b1458def6f3
+msgid "Specify a valid Guest VM CIDR. IP Reservation is applied only if no active IPs exist outside the Guest VM CIDR."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:60
+# 0710411bb18c4764970dffcc49fe5dab
+msgid "You cannot apply IP Reservation if any VM is alloted with an IP address that is outside the Guest VM CIDR."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:63
+# ba005fe1c84e4e5d8d8b2f2cbd904deb
+msgid "To reset an existing IP Reservation, apply IP reservation by specifying the value of network CIDR in the CIDR field."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:66
+# 23bef4e190a54c2298a52b3acb439c57
+msgid "For example, the following table describes three scenarios of guest network creation:"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:70
+# fd80ccd9ee7947c6a41f35a77766ba87
+msgid "Case"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:70
+# 1b0d9124efce41c8bf2ff9c04f471053
+msgid "CIDR"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:70
+# 340cf6747d6449b09015c49437828468
+msgid "Network CIDR"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:70
+# ca9e89e3707343c6a6bb2e2c52dc4acd
+msgid "Reserved IP Range for Non-CloudStack VMs"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:70
+# e1395f7f735643f98e49f71acb302533
+msgid "Description"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:72
+# bfc721eb783042dbbd4049d97eeae50c
+msgid "1"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:72
+#: ../../networking/ip_reservation_in_guest_networks.rst:73
+#: ../../networking/ip_reservation_in_guest_networks.rst:76
+# 07110191079642298d8d53f83f4a6fe7
+# a0e61e48b84a4bb297fead377ce043cf
+# d64231917df74c5189732a5fedd1d141
+msgid "10.1.1.0/24"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:72
+#: ../../networking/ip_reservation_in_guest_networks.rst:72
+#: ../../networking/ip_reservation_in_guest_networks.rst:76
+#: ../../networking/ip_reservation_in_guest_networks.rst:76
+# 865ea8d88306424bab506a500520c22e
+# 184b1eac870b483f910546a5d5b37906
+# 70f4868471d54ac882b8093eb1db9f74
+# 3c040050888741f09b3cee5a8482aca4
+msgid "None"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:72
+# 24e526351c7b4686b16e030bc869d399
+msgid "No IP Reservation."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:73
+# 81f560cf3b4c47bbb2b781add102de88
+msgid "2"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:73
+# 725f92aed0d44be3bb5865f246acc29d
+msgid "10.1.1.0/26"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:73
+# 02e4012c8ce94d95a0c5e4d5088637fd
+msgid "10.1.1.64 to 10.1.1.254"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:73
+# 8fe36bed92d2475bbdd0fa903eb8c54b
+msgid "IP Reservation configured by the UpdateNetwork API with guestvmcidr=10.1.1.0/26 or enter 10.1.1.0/26 in the CIDR field in the UI."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:76
+# e2c363737b654228a0ac0581ba4c55c8
+msgid "3"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:76
+# 139e9ad2489d40738198ebfac4b14c45
+msgid "Removing IP Reservation by the UpdateNetwork API with guestvmcidr=10.1.1.0/24 or enter 10.1.1.0/24 in the CIDR field in the UI."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:83
+# 43bbd9a15792420cb8b1e694ad792cf2
+msgid "Limitations"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:85
+# 1ed6f796d3f04ed0b5c96512bc673c25
+msgid "The IP Reservation is not supported if active IPs that are found outside the Guest VM CIDR."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:88
+# 28ed30440a3543f6b7744261f3f5c2e0
+msgid "Upgrading network offering which causes a change in CIDR (such as upgrading an offering with no external devices to one with external devices) IP Reservation becomes void if any. Reconfigure IP Reservation in the new re-implemeted network."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:95
+# f9aacfd3f1a94c7c8d3ca0910da962a9
+msgid "Best Practices"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:97
+# c5d0950bef8a49ce9b373d64fcf22b86
+msgid "Apply IP Reservation to the guest network as soon as the network state changes to Implemented. If you apply reservation soon after the first guest VM is deployed, lesser conflicts occurs while applying reservation."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:104
+# 636d85b86d5a460788a233fd1cb49014
+msgid "Reserving an IP Range"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:106
+# 34eb58849cb141e9898291a434cc05ba
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:108
+# 3dc484e1bd5145259125fe0fcf8ccf8c
+msgid "In the left navigation, choose Network."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:110
+# e4559a4e7ddf4812890314b955dae344
+msgid "Click the name of the network you want to modify."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:112
+# 9119b8d7ea884da4b996f8a191d30e0b
+msgid "In the Details tab, click Edit. |ip-edit-icon.png|"
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:114
+# 31eaf6bfc27e465e950da4b920fbad80
+msgid "The CIDR field changes to editable one."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:116
+# f29831c8666d45218af0ae6769e46fff
+msgid "In CIDR, specify the Guest VM CIDR."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:118
+# 41acec1236df4ddbad427f23127244b1
+msgid "Click Apply."
+msgstr ""
+
+#: ../../networking/ip_reservation_in_guest_networks.rst:120
+# 8213a6fd8f414bd2b710a4ee77b167ae
+msgid "Wait for the update to complete. The Network CIDR and the Reserved IP Range are displayed on the Details page."
+msgstr ""
+
diff --git a/source/locale/pot/networking/isolation_in_advanced_zone_with_vlan.pot b/source/locale/pot/networking/isolation_in_advanced_zone_with_vlan.pot
new file mode 100644
index 0000000..1839104
--- /dev/null
+++ b/source/locale/pot/networking/isolation_in_advanced_zone_with_vlan.pot
@@ -0,0 +1,273 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:18
+# 2ce5e59640934ab387652df180ce1583
+msgid "Isolation in Advanced Zone Using Private VLAN"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:20
+# 813ada1771994469abac6b243cbc4ed6
+msgid "Isolation of guest traffic in shared networks can be achieved by using Private VLANs (PVLAN). PVLANs provide Layer 2 isolation between ports within the same VLAN. In a PVLAN-enabled shared network, a user VM cannot reach other user VM though they can reach the DHCP server and gateway, this would in turn allow users to control traffic within a network and help them deploy multiple applications without communication between application as well as prevent communication with other users' VMs."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:29
+# 1f6fb3f08ede4dbcbd7c9017afd047dd
+msgid "Isolate VMs in a shared networks by using Private VLANs."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:31
+# c578b86e668046b18652e81289fd1811
+msgid "Supported on KVM, XenServer, and VMware hypervisors"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:33
+# f410d2d58c4b4e91b95fec05d57cf0b8
+msgid "PVLAN-enabled shared network can be a part of multiple networks of a guest VM."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:38
+# 23d9d81e853644d8a8e311853c02a801
+msgid "About Private VLAN"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:40
+# a83e1c8b0ee2433b8776507d78fdd2b4
+msgid "In an Ethernet switch, a VLAN is a broadcast domain where hosts can establish direct communication with each another at Layer 2. Private VLAN is designed as an extension of VLAN standard to add further segmentation of the logical broadcast domain. A regular VLAN is a single broadcast domain, whereas a private VLAN partitions a larger VLAN broadcast domain into smaller sub-domains. A sub-domain is represented by a pair of VLANs: a Primary VLAN and a Secondary VLAN. The original VLAN that is being divided into smaller groups is called Primary, which implies that all VLAN pairs in a private VLAN share the same Primary VLAN. All the secondary VLANs exist only inside the Primary. Each Secondary VLAN has a specific VLAN ID associated to it, which differentiates one sub-domain from another."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:53
+# 4b8abf8fe1534c228333ad081037a150
+msgid "Three types of ports exist in a private VLAN domain, which essentially determine the behaviour of the participating hosts. Each ports will have its own unique set of rules, which regulate a connected host's ability to communicate with other connected host within the same private VLAN domain. Configure each host that is part of a PVLAN pair can be by using one of these three port designation:"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:60
+# d369217099d04739b0c778e20ac02897
+msgid "**Promiscuous**: A promiscuous port can communicate with all the interfaces, including the community and isolated host ports that belong to the secondary VLANs. In Promiscuous mode, hosts are connected to promiscuous ports and are able to communicate directly with resources on both primary and secondary VLAN. Routers, DHCP servers, and other trusted devices are typically attached to promiscuous ports."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:68
+# 1e0c762b123d404eaedebd33003ad75b
+msgid "**Isolated VLANs**: The ports within an isolated VLAN cannot communicate with each other at the layer-2 level. The hosts that are connected to Isolated ports can directly communicate only with the Promiscuous resources. If your customer device needs to have access only to a gateway router, attach it to an isolated port."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:74
+# 15e3128ebacd47afb6aa943d0f2a5df1
+msgid "**Community VLANs**: The ports within a community VLAN can communicate with each other and with the promiscuous ports, but they cannot communicate with the ports in other communities at the layer-2 level. In a Community mode, direct communication is permitted only with the hosts in the same community and those that are connected to the Primary PVLAN in promiscuous mode. If your customer has two devices that need to be isolated from other customers' devices, but to be able to communicate among themselves, deploy them in community ports."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:84
+# 6a977183f6864375ada79a287e63bab3
+msgid "For further reading:"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:86
+# ca791914bab54854b0b9c5cfdbb20be8
+msgid "`Understanding Private VLANs <http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/release/12.2_25_see/configuration/guide/swpvlan.html#wp1038379>`_"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:89
+# e676f05feb9a46d6974a4ed7048edad2
+msgid "`Cisco Systems' Private VLANs: Scalable Security in a Multi-Client Environment <http://tools.ietf.org/html/rfc5517>`_"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:92
+# d5429c82db8a47aa82c6bf7602605f93
+msgid "`Private VLAN (PVLAN) on vNetwork Distributed Switch - Concept Overview (1010691) <http://kb.vmware.com>`_"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:97
+# ad67b66852ee445b847bec89936c0d02
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:99
+# 1f2367cd590b456b9590a9b2616c8ad5
+msgid "Use a PVLAN supported switch."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:101
+# f2c1161babac465c93d8ff531d97174d
+msgid "See `Private VLAN Catalyst Switch Support Matrix <http://www.cisco.com/en/US/products/hw/switches/ps708/products_tech_note09186a0080094830.shtml>`_ for more information."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:105
+# d6805374b5244b3da5f5a39bbb521739
+msgid "All the layer 2 switches, which are PVLAN-aware, are connected to each other, and one of them is connected to a router. All the ports connected to the host would be configured in trunk mode. Open Management VLAN, Primary VLAN (public) and Secondary Isolated VLAN ports. Configure the switch port connected to the router in PVLAN promiscuous trunk mode, which would translate an isolated VLAN to primary VLAN for the PVLAN-unaware router."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:113
+# 3afd52bf2fa3442b8f0721d8bca53715
+msgid "Note that only Cisco Catalyst 4500 has the PVLAN promiscuous trunk mode to connect both normal VLAN and PVLAN to a PVLAN-unaware switch. For the other Catalyst PVLAN support switch, connect the switch to upper switch by using cables, one each for a PVLAN pair."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:118
+# 5ce2b463414844099564cd171152b994
+msgid "Configure private VLAN on your physical switches out-of-band."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:120
+# 2cd1aebdb79742a3ab786e439ef69d89
+msgid "Before you use PVLAN on XenServer and KVM, enable Open vSwitch (OVS)."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:123
+# 23029ff5d87847c3b9a551d1755aae1a
+msgid "OVS on XenServer and KVM does not support PVLAN natively. Therefore, CloudStack managed to simulate PVLAN on OVS for XenServer and KVM by modifying the flow table."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:129
+# 1ab529fe7a53485da31a8085c5fc8181
+msgid "Creating a PVLAN-Enabled Guest Network"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:131
+# 73811e0470e04b63a31d32549a8c882b
+msgid "Log in to the CloudStack UI as administrator."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:133
+# f987d4525be34ae986962e374a48197f
+msgid "In the left navigation, choose Infrastructure."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:135
+# 81a7cad61d0c43e3989e9742e6efb902
+msgid "On Zones, click View More."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:137
+# 62eb1c2209d34440987b38dc999dad75
+msgid "Click the zone to which you want to add a guest network."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:139
+# aeaece1bb557450383b2b0c0930b8d39
+msgid "Click the Physical Network tab."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:141
+# bdccf5bb73ce4a58b074c7db9f09db19
+msgid "Click the physical network you want to work with."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:143
+# d325d3d79e0e41fd9ce93131ae2ea76a
+msgid "On the Guest node of the diagram, click Configure."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:145
+# 3254ff32eecc4e9b9ac57fc4f2219acd
+msgid "Click the Network tab."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:147
+# fdd056f25bee447e98028c9301071fd7
+msgid "Click Add guest network."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:149
+# f58f17bd25284897abbe7df71fc2c3fb
+msgid "The Add guest network window is displayed."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:151
+# 5e421fb492504766a709b728f4fc51e5
+msgid "Specify the following:"
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:153
+# 606686347ca84fbc9a83c5f46c31d8ea
+msgid "**Name**: The name of the network. This will be visible to the user."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:156
+# 73bbe5e4075e43f39b388b8b267c5401
+msgid "**Description**: The short description of the network that can be displayed to users."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:159
+# 17a0fe7f48cc4af3bbe7b8e52b6f6d1b
+msgid "**VLAN ID**: The unique ID of the VLAN."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:161
+# 1656d47de54d42a788bc34e0a0c5f2e4
+msgid "**Secondary Isolated VLAN ID**: The unique ID of the Secondary Isolated VLAN."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:164
+# 22e09670bce14054b1c11ce5ff049ba5
+msgid "For the description on Secondary Isolated VLAN, see `About Private VLAN\" <#about-private-vlan>`_."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:167
+# 38765c8ae24048dba72826d07d096afe
+msgid "**Scope**: The available scopes are Domain, Account, Project, and All."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:170
+# 90706772c0084832b86742ce99f99d6e
+msgid "**Domain**: Selecting Domain limits the scope of this guest network to the domain you specify. The network will not be available for other domains. If you select Subdomain Access, the guest network is available to all the sub domains within the selected domain."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:176
+# 7e174e9b956f4f2784d5196f1a30439f
+msgid "**Account**: The account for which the guest network is being created for. You must specify the domain the account belongs to."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:180
+# d8216708afb2490c97e3cca13b2752dd
+msgid "**Project**: The project for which the guest network is being created for. You must specify the domain the project belongs to."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:184
+# 3aa0f96be4f84d1bae1f1744b108dff8
+msgid "**All**: The guest network is available for all the domains, account, projects within the selected zone."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:187
+# 339b47c6f0f94ca4a221c0f592e92d5b
+msgid "**Network Offering**: If the administrator has configured multiple network offerings, select the one you want to use for this network."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:191
+# ae2111debd664f179fe8eb3b251587ff
+msgid "**Gateway**: The gateway that the guests should use."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:193
+# df6c332c5f7e427d867dcef1784c0731
+msgid "**Netmask**: The netmask in use on the subnet the guests will use."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:195
+# 5331fd382d74450c957ad9e5fa46a095
+msgid "**IP Range**: A range of IP addresses that are accessible from the Internet and are assigned to the guest VMs."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:198
+# 6be7da6ede894331ad2082717f19c89d
+msgid "**Network Domain**: A custom DNS suffix at the level of a network. If you want to assign a special domain name to the guest VM network, specify a DNS suffix."
+msgstr ""
+
+#: ../../networking/isolation_in_advanced_zone_with_vlan.rst:202
+# 0f106d1db97249348138b9cf76182524
+msgid "Click OK to confirm."
+msgstr ""
+
diff --git a/source/locale/pot/networking/multiple_guest_networks.pot b/source/locale/pot/networking/multiple_guest_networks.pot
new file mode 100644
index 0000000..fa2f693
--- /dev/null
+++ b/source/locale/pot/networking/multiple_guest_networks.pot
@@ -0,0 +1,312 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/multiple_guest_networks.rst:18
+# cbc2c710bdfe4a52822f6acf8381d1dd
+msgid "Using Multiple Guest Networks"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:20
+# 43824860271641cabc92b4e2fea91b0d
+msgid "In zones that use advanced networking, additional networks for guest traffic may be added at any time after the initial installation. You can also customize the domain name associated with the network by specifying a DNS suffix for each network."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:25
+# e7a7a8ebce174e439d282d7c86c23ffc
+msgid "A VM's networks are defined at VM creation time. A VM cannot add or remove networks after it has been created, although the user can go into the guest and remove the IP address from the NIC on a particular network."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:30
+# c1facfd27f164a849bd7151e92129d58
+msgid "Each VM has just one default network. The virtual router's DHCP reply will set the guest's default gateway as that for the default network. Multiple non-default networks may be added to a guest in addition to the single, required default network. The administrator can control which networks are available as the default network."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:36
+# 008bbd9e609541888208d792dda845fd
+msgid "Additional networks can either be available to all accounts or be assigned to a specific account. Networks that are available to all accounts are zone-wide. Any user with access to the zone can create a VM with access to that network. These zone-wide networks provide little or no isolation between guests.Networks that are assigned to a specific account provide strong isolation."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:45
+# e8b12ba98b314fcca6f8659fdffe0e5a
+msgid "Adding an Additional Guest Network"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:47
+#: ../../networking/multiple_guest_networks.rst:97
+#: ../../networking/multiple_guest_networks.rst:135
+#: ../../networking/multiple_guest_networks.rst:153
+#: ../../networking/multiple_guest_networks.rst:173
+# fc94885acfb44c089b5b955040cda635
+# e90f66fa32fb4ac0bdd48def8833e52d
+# 443695bf438a4240b9c354d9c66f2292
+# dc150422f8d8498e81ccfa11cc7daf5f
+# f4162f2a3af54aee90b80a9efec6523f
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:49
+#: ../../networking/multiple_guest_networks.rst:179
+# e9d2f3becfba421592c540e757fe27e8
+# 1e2cad5b28aa4f56bfee80c03c969d5c
+msgid "In the left navigation, choose Network."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:51
+# 4e88ac1dcf2144278c13cac5cf518978
+msgid "Click Add guest network. Provide the following information:"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:53
+# 752dce8be6894794b7f10719d33214c9
+msgid "**Name**: The name of the network. This will be user-visible."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:55
+# 68d2d60b814f4b48805d73f511a0c3f4
+msgid "**Display Text**: The description of the network. This will be user-visible."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:58
+# 2e28d86b3670448ea924597e1a6eafbb
+msgid "**Zone**. The name of the zone this network applies to. Each zone is a broadcast domain, and therefore each zone has a different IP range for the guest network. The administrator must configure the IP range for each zone."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:63
+# 783fa5ad4bb94a898e27fb2fb400ce30
+msgid "**Network offering**: If the administrator has configured multiple network offerings, select the one you want to use for this network."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:67
+# e6d0251f520945198846d9589071d11c
+msgid "**Guest Gateway**: The gateway that the guests should use."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:69
+# 82e7d212928549ba947dfe5e04919372
+msgid "**Guest Netmask**: The netmask in use on the subnet the guests will use."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:72
+# 333d9595d92b4dbc9842d746d1dd8448
+msgid "Click Create."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:76
+# cadd27c83ef84c9e9ce49c9ce9e5d8ca
+msgid "Reconfiguring Networks in VMs"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:78
+# 38552d30397849ea975e0b5d28fd31a0
+msgid "CloudStack provides you the ability to move VMs between networks and reconfigure a VM's network. You can remove a VM from a network and add to a new network. You can also change the default network of a virtual machine. With this functionality, hybrid or traditional server loads can be accommodated with ease."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:84
+# 205bea0ed92e4de594873aa8e5ad9d45
+msgid "This feature is supported on XenServer, VMware, and KVM hypervisors."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:88
+# 7d8b8d41cfa04ea0b337a64b1206ae92
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:90
+# bd4145a5e8ae4ca29cd7bdd5b1aab637
+msgid "Ensure that vm-tools are running on guest VMs for adding or removing networks to work on VMware hypervisor."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:95
+# 42b8d9502ed54485bde4210b8fdbb499
+msgid "Adding a Network"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:99
+#: ../../networking/multiple_guest_networks.rst:137
+#: ../../networking/multiple_guest_networks.rst:155
+# c398a820cb1648bc8799135cbaa74b1b
+# d48f631728b44c90be3cb811c9cd0505
+# 37c98038af7f4dc6a120b05e4e13c555
+msgid "In the left navigation, click Instances."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:101
+#: ../../networking/multiple_guest_networks.rst:139
+#: ../../networking/multiple_guest_networks.rst:157
+# b25bff80ed07457f9b1f926c0a58cc6c
+# 39876863e78d47378acdd305a1e22606
+# 2f4e1895d207479597c89b7b137794df
+msgid "Choose the VM that you want to work with."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:103
+#: ../../networking/multiple_guest_networks.rst:141
+#: ../../networking/multiple_guest_networks.rst:159
+# 00b5baacd9084cd580b5fc02a2eb93fb
+# cd7d2fceff8d47d5b392be059b471ab9
+# 3f13993fdab542d6b8318cc2fe353acb
+msgid "Click the NICs tab."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:105
+# 47b1307c53ed41dfbe754e5141219451
+msgid "Click Add network to VM."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:107
+# ebd8002977894bed935a5229f868dc66
+msgid "The Add network to VM dialog is displayed."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:109
+# fa83b310f8904d8587c3dfdc52cacbad
+msgid "In the drop-down list, select the network that you would like to add this VM to."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:112
+# dd48bfa27d7345aa87c6b7e63a358160
+msgid "A new NIC is added for this network. You can view the following details in the NICs page:"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:115
+# 6463c065bc1943008470d1edad582974
+msgid "ID"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:117
+# 9420ad95bce443da9b81765885249155
+msgid "Network Name"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:119
+# f846a9f3d938451198081772cc74cb85
+msgid "Type"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:121
+# 8592916e5acf4e70bafbdbda7c00c614
+msgid "IP Address"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:123
+# c75427419ce04483b71df9bd261c2fbd
+msgid "Gateway"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:125
+# d008ddbc8a054a27ae521d3e3b8a4013
+msgid "Netmask"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:127
+# 41cff6439a0b42b5abab39913bc773bb
+msgid "Is default"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:129
+# cb23bf06693941579c5993219c416bb8
+msgid "CIDR (for IPv6)"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:133
+# bce02b8426584ab693112a2a3eaa69a4
+msgid "Removing a Network"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:143
+# ca1c1c7c1c9d4ff8aaca289a38a6f7c0
+msgid "Locate the NIC you want to remove."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:145
+# 85a4e2e7437642f18635fa647891d856
+msgid "Click Remove NIC button. |remove-nic.png|"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:147
+#: ../../networking/multiple_guest_networks.rst:165
+# ffa7cf9f06374be19a3b64261219cdc1
+# 5597778b6dec4d1fac608939422f4a00
+msgid "Click Yes to confirm."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:151
+# 78a6b76d558e43c18b80b80d9ae29567
+msgid "Selecting the Default Network"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:161
+# d548799e04664a74b122217c8b65678f
+msgid "Locate the NIC you want to work with."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:163
+# 43217c75ff3e4ac885b27d575f4c47ee
+msgid "Click the Set default NIC button. |set-default-nic.png|."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:168
+# fea27f4c1e3f45e89b4b9439c9affb16
+msgid "Changing the Network Offering on a Guest Network"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:170
+# 9de4858c24814a74a54559f2494b3a89
+msgid "A user or administrator can change the network offering that is associated with an existing guest network."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:175
+# 7c551d2e95a241b48be8ce6603506ab3
+msgid "If you are changing from a network offering that uses the CloudStack virtual router to one that uses external devices as network service providers, you must first stop all the VMs on the network."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:181
+# c67df95acd7f48b18f620634af845488
+msgid "Click the name of the network you want to modify."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:183
+# fb679c3a524c4c4a837fe24566e3a12b
+msgid "In the Details tab, click Edit. |edit-icon.png|"
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:185
+# 4afa43a2ac5b46f29ad42d421235b01d
+msgid "In Network Offering, choose the new network offering, then click Apply."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:188
+# 6a7280bbaba74bfb8b6622ac7832cf5c
+msgid "A prompt is displayed asking whether you want to keep the existing CIDR. This is to let you know that if you change the network offering, the CIDR will be affected."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:192
+# 42e2f2150b07464bbdf35bc0c30edd91
+msgid "If you upgrade between virtual router as a provider and an external network device as provider, acknowledge the change of CIDR to continue, so choose Yes."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:196
+# 3b240e38bc11456095069b1622cc917f
+msgid "Wait for the update to complete. Don't try to restart VMs until the network change is complete."
+msgstr ""
+
+#: ../../networking/multiple_guest_networks.rst:199
+# a6db1505b17b48e1ae1063872635e2bb
+msgid "If you stopped any VMs, restart them."
+msgstr ""
+
diff --git a/source/locale/pot/networking/multiple_ip_ranges.pot b/source/locale/pot/networking/multiple_ip_ranges.pot
new file mode 100644
index 0000000..1c2c968
--- /dev/null
+++ b/source/locale/pot/networking/multiple_ip_ranges.pot
@@ -0,0 +1,48 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/multiple_ip_ranges.rst:18
+# cea4bcb571304273bc04b67f139f0140
+msgid "About Multiple IP Ranges"
+msgstr ""
+
+#: ../../networking/multiple_ip_ranges.rst:20
+# fb1aec1297a645198cd0ecbc09f187eb
+msgid "The feature can only be implemented on IPv4 addresses."
+msgstr ""
+
+#: ../../networking/multiple_ip_ranges.rst:22
+# 3180ea2f13aa4565a8715d959ef1148d
+msgid "CloudStack provides you with the flexibility to add guest IP ranges from different subnets in Basic zones and security groups-enabled Advanced zones. For security groups-enabled Advanced zones, it implies multiple subnets can be added to the same VLAN. With the addition of this feature, you will be able to add IP address ranges from the same subnet or from a different one when IP address are exhausted. This would in turn allows you to employ higher number of subnets and thus reduce the address management overhead. To support this feature, the capability of ``createVlanIpRange`` API is extended to add IP ranges also from a different subnet."
+msgstr ""
+
+#: ../../networking/multiple_ip_ranges.rst:33
+# d1d9636b0fd14b508f2570b3d7f5b7a2
+msgid "Ensure that you manually configure the gateway of the new subnet before adding the IP range. Note that CloudStack supports only one gateway for a subnet; overlapping subnets are not currently supported."
+msgstr ""
+
+#: ../../networking/multiple_ip_ranges.rst:37
+# b1ed3bd81dfa4662bcf9ab17817d99e5
+msgid "Use the ``deleteVlanRange`` API to delete IP ranges. This operation fails if an IP from the remove range is in use. If the remove range contains the IP address on which the DHCP server is running, CloudStack acquires a new IP from the same subnet. If no IP is available in the subnet, the remove operation fails."
+msgstr ""
+
+#: ../../networking/multiple_ip_ranges.rst:43
+# 5c66e6ebd5cc42728bccf16a99764a94
+msgid "This feature is supported on KVM, xenServer, and VMware hypervisors."
+msgstr ""
+
diff --git a/source/locale/pot/networking/multiple_ips_on_single_nic.pot b/source/locale/pot/networking/multiple_ips_on_single_nic.pot
new file mode 100644
index 0000000..7919a5f
--- /dev/null
+++ b/source/locale/pot/networking/multiple_ips_on_single_nic.pot
@@ -0,0 +1,128 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/multiple_ips_on_single_nic.rst:18
+# 80e46ffc92914befa1e1b6bb37ae48e0
+msgid "Configuring Multiple IP Addresses on a Single NIC"
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:20
+# e552e4b860e64b83bd63e053002d0187
+msgid "CloudStack provides you the ability to associate multiple private IP addresses per guest VM NIC. In addition to the primary IP, you can assign additional IPs to the guest VM NIC. This feature is supported on all the network configurations: Basic, Advanced, and VPC. Security Groups, Static NAT and Port forwarding services are supported on these additional IPs."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:27
+# 37ec7f1162de4309afcd34ea7bc9af66
+msgid "As always, you can specify an IP from the guest subnet; if not specified, an IP is automatically picked up from the guest VM subnet. You can view the IPs associated with for each guest VM NICs on the UI. You can apply NAT on these additional guest IPs by using network configuration option in the CloudStack UI. You must specify the NIC to which the IP should be associated."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:34
+# 9a035e888c1245098bf6a6b97754c398
+msgid "This feature is supported on XenServer, KVM, and VMware hypervisors. Note that Basic zone security groups are not supported on VMware."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:39
+# e65e3e62dc4a4301b7c488f06bbe696d
+msgid "Use Cases"
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:41
+# 11ad1c7201dd4368b51c2686f4f6c436
+msgid "Some of the use cases are described below:"
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:43
+# bad26d93f70a454ea65fe8d314c5fb5f
+msgid "Network devices, such as firewalls and load balancers, generally work best when they have access to multiple IP addresses on the network interface."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:47
+# 95be93b5a22541cf8e3a65154ae683cc
+msgid "Moving private IP addresses between interfaces or instances. Applications that are bound to specific IP addresses can be moved between instances."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:51
+# 9ee757e7b88f4aa2a87ccd4771a324d2
+msgid "Hosting multiple SSL Websites on a single instance. You can install multiple SSL certificates on a single instance, each associated with a distinct IP address."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:57
+# 4edd1f589e2e49829a8738af942f1449
+msgid "Guidelines"
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:59
+# 54a52619c6484653a0d95be689657a85
+msgid "To prevent IP conflict, configure different subnets when multiple networks are connected to the same VM."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:64
+# 2e55027ec0ce4ce6b87130453ca2ea69
+msgid "Assigning Additional IPs to a VM"
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:66
+# 24aaa9f9fd734b1d9b775ad1342d31b2
+msgid "Log in to the CloudStack UI."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:68
+# 51fd921471ee488bb728f102e439c19e
+msgid "In the left navigation bar, click Instances."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:70
+# f0efc1c51c2a471498620eb3d6313aa6
+msgid "Click the name of the instance you want to work with."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:72
+# 17a62e09249f4a3fac5b78b1ee42aa11
+msgid "In the Details tab, click NICs."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:74
+# 815af55e9e6e475ea2139c0ee79838c8
+msgid "Click View Secondary IPs."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:76
+# edd4eb38ff964d91901201733864317e
+msgid "Click Acquire New Secondary IP, and click Yes in the confirmation dialog."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:79
+# a243effbef704447bf0f0a2d5bdc0a86
+msgid "You need to configure the IP on the guest VM NIC manually. CloudStack will not automatically configure the acquired IP address on the VM. Ensure that the IP address configuration persist on VM reboot."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:83
+# 92b50e481e5943af8db0036e562bcf45
+msgid "Within a few moments, the new IP address should appear with the state Allocated. You can now use the IP address in Port Forwarding or StaticNAT rules."
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:89
+# 8ce45ae597644592be9f68b1b9a50693
+msgid "Port Forwarding and StaticNAT Services Changes"
+msgstr ""
+
+#: ../../networking/multiple_ips_on_single_nic.rst:91
+# 707c305e2e104709866aebe9741b3891
+msgid "Because multiple IPs can be associated per NIC, you are allowed to select a desired IP for the Port Forwarding and StaticNAT services. The default is the primary IP. To enable this functionality, an extra optional parameter 'vmguestip' is added to the Port forwarding and StaticNAT APIs (enableStaticNat, createIpForwardingRule) to indicate on what IP address NAT need to be configured. If vmguestip is passed, NAT is configured on the specified private IP of the VM. if not passed, NAT is configured on the primary IP of the VM."
+msgstr ""
+
diff --git a/source/locale/pot/networking/multiple_subnets_in_shared_network.pot b/source/locale/pot/networking/multiple_subnets_in_shared_network.pot
new file mode 100644
index 0000000..ca77e68
--- /dev/null
+++ b/source/locale/pot/networking/multiple_subnets_in_shared_network.pot
@@ -0,0 +1,158 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:18
+# aaae14dc309846cf90268bd429550032
+msgid "Multiple Subnets in Shared Network"
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:20
+# e1e0546c06b44b948781bf1b155376b6
+msgid "CloudStack provides you with the flexibility to add guest IP ranges from different subnets in Basic zones and security groups-enabled Advanced zones. For security groups-enabled Advanced zones, it implies multiple subnets can be added to the same VLAN. With the addition of this feature, you will be able to add IP address ranges from the same subnet or from a different one when IP address are exhausted. This would in turn allows you to employ higher number of subnets and thus reduce the address management overhead. You can delete the IP ranges you have added."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:32
+# d651b6e4b73a4c8897943f492f553be4
+msgid "Prerequisites and Guidelines"
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:34
+# 321b92f77c9e47b581323b300949d477
+msgid "This feature can only be implemented:"
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:36
+# 693a867b887b40c39f9112ee79a514f3
+msgid "on IPv4 addresses"
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:38
+# d4bb9088f4ce439bb4aa86f2d6ca1226
+msgid "if virtual router is the DHCP provider"
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:40
+# b4bb01b3421b4a26af052b41ef2e9c74
+msgid "on KVM, xenServer, and VMware hypervisors"
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:42
+# 3ce0b6127bed4c878204268e02519b5f
+msgid "Manually configure the gateway of the new subnet before adding the IP range."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:45
+# 92e9da161e084fd09cbd7a34e3a8ea59
+msgid "CloudStack supports only one gateway for a subnet; overlapping subnets are not currently supported"
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:50
+# 0ccc8eb511c649519820d407c101fb3f
+msgid "Adding Multiple Subnets to a Shared Network"
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:52
+# 402388a40d1c4432adf97dcb94bc7e0a
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:54
+# c062e6ebc0b74be185c8e192c237a3d8
+msgid "In the left navigation, choose Infrastructure."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:56
+# 9d6f09662ceb452bb8bf26c21696a7ff
+msgid "On Zones, click View More, then click the zone to which you want to work with.."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:59
+# 9a6c131e8dee4829a34a534324f96d6a
+msgid "Click Physical Network."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:61
+# 412cf2ea6b7c4fc9a45dcfabca044210
+msgid "In the Guest node of the diagram, click Configure."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:63
+# 20271a4db3304ebd986eefb0dbe2304b
+msgid "Click Networks."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:65
+# d4d67c51b96a441984f094dad7440b53
+msgid "Select the networks you want to work with."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:67
+# dbda223b46514614bc24a96cbd967579
+msgid "Click View IP Ranges."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:69
+# fd40e95e0dcc4b37ac83ea1764ccd1c5
+msgid "Click Add IP Range."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:71
+# e57818339fdd4bea80a587551ff3bb27
+msgid "The Add IP Range dialog is displayed, as follows:"
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:73
+# 1adf38c68dd04551aeded2194d8d3bfb
+msgid "|add-ip-range.png|"
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:75
+# 8d5c0e4efe1742f7988a60fe55223d66
+msgid "Specify the following:"
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:77
+# c5bd70e2ab5748e18b8bc2840088a41e
+msgid "All the fields are mandatory."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:79
+# cefcd378eaf44ae5b0c6aaa2809a4fe4
+msgid "**Gateway**: The gateway for the tier you create. Ensure that the gateway is within the Super CIDR range that you specified while creating the VPC, and is not overlapped with the CIDR of any existing tier within the VPC."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:84
+# d63b707e5f374d5d807b5749f9cc44ad
+msgid "**Netmask**: The netmask for the tier you create."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:86
+# f5d499f2a9fa4a859f8563d9b68b29a3
+msgid "For example, if the VPC CIDR is 10.0.0.0/16 and the network tier CIDR is 10.0.1.0/24, the gateway of the tier is 10.0.1.1, and the netmask of the tier is 255.255.255.0."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:90
+# 4aeabf0b77244ea994e1c9a3587421a7
+msgid "**Start IP/ End IP**: A range of IP addresses that are accessible from the Internet and will be allocated to guest VMs. Enter the first and last IP addresses that define a range that CloudStack can assign to guest VMs ."
+msgstr ""
+
+#: ../../networking/multiple_subnets_in_shared_network.rst:95
+# c54dd19ac3fc4b1abe5c8e2ba6021969
+msgid "Click OK."
+msgstr ""
+
diff --git a/source/locale/pot/networking/networking_in_pod.pot b/source/locale/pot/networking/networking_in_pod.pot
new file mode 100644
index 0000000..47d6094
--- /dev/null
+++ b/source/locale/pot/networking/networking_in_pod.pot
@@ -0,0 +1,58 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/networking_in_pod.rst:18
+# 3d0c16ad63444261b9694623c2402727
+msgid "Networking in a Pod"
+msgstr ""
+
+#: ../../networking/networking_in_pod.rst:20
+# 6f94486d31ee45b8a15da0d2a1c080ca
+msgid "The figure below illustrates network setup within a single pod. The hosts are connected to a pod-level switch. At a minimum, the hosts should have one physical uplink to each switch. Bonded NICs are supported as well. The pod-level switch is a pair of redundant gigabit switches with 10 G uplinks."
+msgstr ""
+
+#: ../../networking/networking_in_pod.rst:26
+# d14ee305eeed479b95127d50242ce7f9
+msgid "|networksinglepod.png|"
+msgstr ""
+
+#: ../../networking/networking_in_pod.rst:28
+# 6c63d1a963fe4751bb6a3efcc28ec07b
+msgid "Servers are connected as follows:"
+msgstr ""
+
+#: ../../networking/networking_in_pod.rst:30
+# cab4d0a9b3874148b142ec81b8916ab3
+msgid "Storage devices are connected to only the network that carries management traffic."
+msgstr ""
+
+#: ../../networking/networking_in_pod.rst:33
+# a01f83aa00be44768e404b928746539d
+msgid "Hosts are connected to networks for both management traffic and public traffic."
+msgstr ""
+
+#: ../../networking/networking_in_pod.rst:36
+# 7cc32b192f154001a6b37b93bf141c79
+msgid "Hosts are also connected to one or more networks carrying guest traffic."
+msgstr ""
+
+#: ../../networking/networking_in_pod.rst:39
+# afe45e02d11f436b92bc4752de309aa2
+msgid "We recommend the use of multiple physical Ethernet cards to implement each network interface as well as redundant switch fabric in order to maximize throughput and improve reliability."
+msgstr ""
+
diff --git a/source/locale/pot/networking/networking_in_zone.pot b/source/locale/pot/networking/networking_in_zone.pot
new file mode 100644
index 0000000..377c408
--- /dev/null
+++ b/source/locale/pot/networking/networking_in_zone.pot
@@ -0,0 +1,43 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/networking_in_zone.rst:18
+# 3080bd3d63ce42f7970a7e111d5cc46b
+msgid "Networking in a Zone"
+msgstr ""
+
+#: ../../networking/networking_in_zone.rst:20
+# acc145c9dbbb43d0a4e7bcb5cdb804cb
+msgid "The following figure illustrates the network setup within a single zone."
+msgstr ""
+
+#: ../../networking/networking_in_zone.rst:22
+# a22b23e45435457b927cdcd248830e97
+msgid "|networksetupzone.png|"
+msgstr ""
+
+#: ../../networking/networking_in_zone.rst:24
+# 116d5e262cd547858fe9873be74c59da
+msgid "A firewall for management traffic operates in the NAT mode. The network typically is assigned IP addresses in the 192.168.0.0/16 Class B private address space. Each pod is assigned IP addresses in the 192.168.\\*.0/24 Class C private address space."
+msgstr ""
+
+#: ../../networking/networking_in_zone.rst:29
+# 7a1eee0be4da4ed3aa3c0854ab4c2230
+msgid "Each zone has its own set of public IP addresses. Public IP addresses from different zones do not overlap."
+msgstr ""
+
diff --git a/source/locale/pot/networking/palo_alto_config.pot b/source/locale/pot/networking/palo_alto_config.pot
new file mode 100644
index 0000000..6483dea
--- /dev/null
+++ b/source/locale/pot/networking/palo_alto_config.pot
@@ -0,0 +1,781 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/palo_alto_config.rst:18
+# f3d9b37c09d84940aa4c2fde3f9acd2a
+msgid "Setup a Palo Alto Networks Firewall"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:22
+# bf6ec115893747b1baf4957e9be35ff4
+msgid "Functionality Provided"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:24
+# c1f3ed83f8394089ab4694fe954e0195
+msgid "This implementation enables the orchestration of a Palo Alto Networks Firewall from within CloudStack UI and API."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:27
+# 4b1340d4e6f74cd39095e06ca20ccbdd
+msgid "**The following features are supported**:"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:29
+# e30f817e0e4d45ff8140a2bf41b86fb3
+msgid "List/Add/Delete Palo Alto Networks service provider"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:31
+# d027f8c0521d4e3c8659c5f89b010dc3
+msgid "List/Add/Delete Palo Alto Networks network service offering"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:33
+# d3c3bd36ca4744d68797f6bda8758efd
+msgid "List/Add/Delete Palo Alto Networks network using the above service offering"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:35
+# d4ba1563cd1a4efb8039895bd0fc4abc
+msgid "Add an instance to a Palo Alto Networks network"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:37
+# 095297003ef84ab4946859b93741650f
+msgid "Source NAT management on network create and delete"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:39
+# 83be5169430e457495da1faa61028b94
+msgid "List/Add/Delete Ingress Firewall rule"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:41
+# 934645096b2041c0892c5827ab0bae62
+msgid "List/Add/Delete Egress Firewall rule (both 'Allow' and 'Deny' default rules supported)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:44
+# b3d40e33e09544e892974a896c1c0f5e
+msgid "List/Add/Delete Port Forwarding rule"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:46
+# 2227e25f9e3e4cf19e34dd0deddbb404
+msgid "List/Add/Delete Static NAT rule"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:48
+# 64c598fbe2d04d368d5f30c35aa7f1d6
+msgid "Apply a Threat Profile to all firewall rules (more details in the Additional Features section)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:51
+# 6843739b321a4d828b6e9b17a9ef0fc8
+msgid "Apply a Log Forwarding profile to all firewall rules (more details in the Additional Features section)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:57
+# 90c46aad0abf4f3c9d84941828556629
+msgid "Initial Palo Alto Networks Firewall Configuration"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:60
+# 3404e87b314644c49c28a53bc5f5e6a0
+msgid "Anatomy of the Palo Alto Networks Firewall"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:62
+# a9c2ce1bfd05437a975c7cb37c0fba62
+msgid "In **'Network > Interfaces'** there is a list of physical interfaces as well as aggregated physical interfaces which are used for managing traffic in and out of the Palo Alto Networks Firewall device."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:66
+# 5ac5b705b6834ded91c030380797cbd2
+msgid "In **'Network > Zones'** there is a list of the different configuration zones.  This implementation will use two zones; a public (defaults to 'untrust') and private (defaults to 'trust') zone."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:70
+# eea4177c1fff4e099f0d3ed3d68ddfca
+msgid "In **'Network > Virtual Routers'** there is a list of VRs which handle traffic routing for the Palo Alto Firewall.  We only use a single Virtual Router on the firewall and it is used to handle all the routing to the next network hop."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:75
+# abd376e7380441f390cd90564d09d4c5
+msgid "In **'Objects > Security Profile Groups'** there is a list of profiles which can be applied to firewall rules.  These profiles are used to better understand the types of traffic that is flowing through your network. Configured when you add the firewall provider to CloudStack."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:80
+# 81bf3163d8e548f9827901650a45fa29
+msgid "In **'Objects > Log Forwarding'** there is a list of profiles which can be applied to firewall rules.  These profiles are used to better track the logs generated by the firewall.  Configured when you add the firewall provider to CloudStack."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:85
+# 3f1feff617394987a3e0e75b9098bdb8
+msgid "In **'Policies > Security'** there is a list of firewall rules that are currently configured.  You will not need to modify this section because it will be completely automated by CloudStack, but you can review the firewall rules which have been created here."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:90
+# 34e8e7a02d1a478d99e352c6a4dd825c
+msgid "In **'Policies > NAT'** there is a list of the different NAT rules.  You will not need to modify this section because it will be completely automated by CloudStack, but you can review the different NAT rules that have been created here.  Source NAT, Static NAT and Destination NAT (Port Forwarding) rules will show up in this list."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:99
+# 640e9e01bf184821b43d47005542f297
+msgid "Configure the Public / Private Zones on the firewall"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:101
+# dd1583c5eff3465b96b6e0e55da67a78
+msgid "No manual configuration is required to setup these zones because CloudStack will configure them automatically when you add the Palo Alto Networks firewall device to CloudStack as a service provider.  This implementation depends on two zones, one for the public side and one for the private side of the firewall."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:107
+# f247dae111a8455598a5509325f99b2d
+msgid "The public zone (defaults to 'untrust') will contain all of the public interfaces and public IPs."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:110
+# 3cc0d8d0cdd949bbae82f501193f7705
+msgid "The private zone (defaults to 'trust') will contain all of the private interfaces and guest network gateways."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:113
+# fffcd92335be420f92a7847a249b200c
+msgid "The NAT and firewall rules will be configured between these zones."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:118
+# 0f85059787c94c61b9cb4b39e5cb52c9
+msgid "Configure the Public / Private Interfaces on the firewall"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:120
+# c8c72310b2744d4caefb5b9575ee6e60
+msgid "This implementation supports standard physical interfaces as well as grouped physical interfaces called aggregated interfaces.  Both standard interfaces and aggregated interfaces are treated the same, so they can be used interchangeably. For this document, we will assume that we are using 'ethernet1/1' as the public interface and 'ethernet1/2' as the private interface.  If aggregated interfaces where used, you would use something like 'ae1' and 'ae2' as the interfaces."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:128
+# 2831a742f496425ba96db130e37c9fdf
+msgid "This implementation requires that the 'Interface Type' be set to 'Layer3' for both the public and private interfaces.  If you want to be able to use the 'Untagged' VLAN tag for public traffic in CloudStack, you will need to enable support for it in the public 'ethernet1/1' interface (details below)."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:133
+# 7c752ebb778a47f5ab20ddd8e7c2c88d
+msgid "**Steps to configure the Public Interface**:"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:135
+#: ../../networking/palo_alto_config.rst:171
+#: ../../networking/palo_alto_config.rst:228
+# 5700c7ece81b43cb98c6727c752735b2
+# e49c5cac5b754c67a068eb76b8f2b016
+# de7a1d67b1d944d9a9282e1481b27948
+msgid "Log into Palo Alto Networks Firewall"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:137
+#: ../../networking/palo_alto_config.rst:230
+# 084f3f60d58341c1bb8a4c5902758909
+# ef024b35b5944a84b02459069f6213a1
+msgid "Navigate to 'Network > Interfaces'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:139
+# f9c2ae1f0de249878828ead2f5703582
+msgid "Click on 'ethernet1/1' (for aggregated ethernet, it will probably be called 'ae1')"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:142
+#: ../../networking/palo_alto_config.rst:155
+# 04a63a60ad414b7e81b979d479bae1fd
+# 04da4ad3a88d4e6cba3ee5b4668f9ee2
+msgid "Select 'Layer3' from the 'Interface Type' list"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:144
+# ff872b1bbd2945db9cce189792e38246
+msgid "Click 'Advanced'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:146
+# 944d68b812d8463a87b69f9d882e8b28
+msgid "Check the 'Untagged Subinterface' check-box"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:148
+#: ../../networking/palo_alto_config.rst:157
+#: ../../networking/palo_alto_config.rst:193
+#: ../../networking/palo_alto_config.rst:195
+#: ../../networking/palo_alto_config.rst:265
+#: ../../networking/palo_alto_config.rst:339
+#: ../../networking/palo_alto_config.rst:388
+#: ../../networking/palo_alto_config.rst:426
+#: ../../networking/palo_alto_config.rst:455
+# 290ce1b89ac441bcbc6691b3a41534a6
+# ac12e64f14884682ba033e7f2177cc9b
+# 8f94cc2074684065a79e57cf90d6ab9a
+# 8a83b222380740918936aca1feee32b9
+# f18ef2d3aeac41389cdfd198b83c5467
+# 95a5afc210324dab8a21ba2da8e6801c
+# d765a343c5f146639728c4ea3493e250
+# 8b7efac976c241fe9f3fa33963361d5a
+# 8a61018dde394d37b9ca3df99d188ee5
+msgid "Click 'OK'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:150
+# 8b5c88e0cc8242a580db731046cce5d3
+msgid "**Steps to configure the Private Interface**:"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:152
+# a94612c3076e4722bd18904180a04114
+msgid "Click on 'ethernet1/2' (for aggregated ethernet, it will probably be called 'ae2')"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:162
+# 0beaed2fa39442e887eaca261cae62d7
+msgid "Configure a Virtual Router on the firewall"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:164
+# 22d2fb39f9f44f928787ed03f4aa558c
+msgid "The Virtual Router on the Palo Alto Networks Firewall is not to be confused with the Virtual Routers that CloudStack provisions.  For this implementation, the Virtual Router on the Palo Alto Networks Firewall will ONLY handle the upstream routing from the Firewall to the next hop."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:169
+# e11103f99e6d45d0bea4183b1cf60c98
+msgid "**Steps to configure the Virtual Router**:"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:173
+# d520996f46e84c8c94ce274dd654f3cb
+msgid "Navigate to 'Network > Virtual Routers'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:175
+# e966f3781b904686b55509eef9892346
+msgid "Select the 'default' Virtual Router or Add a new Virtual Router if there are none in the list"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:178
+# 9cbe5a8debc5407fb6918d33d5b71aab
+msgid "If you added a new Virtual Router, you will need to give it a 'Name'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:180
+# b6a107e3fda3444fbcc24365b6ee33ca
+msgid "Navigate to 'Static Routes > IPv4'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:182
+# 6efcbc75fe144976b8a75a2dd888c615
+msgid "'Add' a new static route"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:184
+# ed78234999764665912475eb992e6395
+msgid "**Name**: next_hop (you can name it anything you want)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:186
+# 47efb66b283043aa89a78ad4c6a87339
+msgid "**Destination**: 0.0.0.0/0 (send all traffic to this route)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:188
+# f9dde0e9e0534954bf1da5b6bf535824
+msgid "**Interface**: ethernet1/1 (or whatever you set your public interface as)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:191
+# 1e8a9818e50544a19445ee39589e5215
+msgid "**Next Hop**: (specify the gateway IP for the next hop in your network)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:200
+# f26446d9a67c4620a0f511145ecfde2b
+msgid "Configure the default Public Subinterface"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:202
+# 7225aebfeb604bd7ad6ffa6bd19425c3
+msgid "The current implementation of the Palo Alto Networks firewall integration uses CIDRs in the form of 'w.x.y.z/32' for the public IP addresses that CloudStack provisions.  Because no broadcast or gateway IPs are in this single IP range, there is no way for the firewall to route the traffic for these IPs.  To route the traffic for these IPs, we create a single subinterface on the public interface with an IP and a CIDR which encapsulates the CloudStack public IP range.  This IP will need to be inside the subnet defined by the CloudStack public range netmask, but outside the CloudStack public IP range.  The CIDR should reflect the same subnet defined by the CloudStack public range netmask. The name of the subinterface is determined by the VLAN configured for the public range in CloudStack."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:214
+# 3c781eec6bac4e599027b694351c3cd4
+msgid "To clarify this concept, we will use the following example."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:216
+# 9637f4b7396f4c51983c5bf87b43e912
+msgid "**Example CloudStack Public Range Configuration**:"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:218
+# 8a3070e081974ca68cc0375eca88007b
+msgid "**Gateway**: 172.30.0.1"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:220
+# 9f64613849464823b633f1d16645d42e
+msgid "**Netmask**: 255.255.255.0"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:222
+# 9330fe95cfaf44abbdb0d4f38e739dde
+msgid "**IP Range**: 172.30.0.100 - 172.30.0.199"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:224
+# 435b6fb99438485f877a6756893298bf
+msgid "**VLAN**: Untagged"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:226
+# eb956dfff226492fa1b0806cbbf743dc
+msgid "**Configure the Public Subinterface**:"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:232
+# 2c3eb0c3c7e642cbb78583a57bc43be3
+msgid "Select the 'ethernet1/1' line (not clicking on the name)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:234
+# 739221cdf0024efc9b93b1d76646825b
+msgid "Click 'Add Subinterface' at the bottom of the window"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:236
+# 6b8490f4a2684ca8ad9814a1461edaaa
+msgid "Enter 'Interface Name': 'ethernet1/1' . '9999'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:238
+# fb030c9c7b044a0185fe843def4a3bb5
+msgid "9999 is used if the CloudStack public range VLAN is 'Untagged'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:240
+# 912e1187e17b414f9493ddb7f368b068
+msgid "If the CloudStack public range VLAN is tagged (eg: 333), then the name will reflect that tag"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:243
+# 4472ddfa3e6f4c878a16d411cc343a7d
+msgid "The 'Tag' is the VLAN tag that the traffic is sent to the next hop with, so set it accordingly.  If you are passing 'Untagged' traffic from CloudStack to your next hop, leave it blank.  If you want to pass tagged traffic from CloudStack, specify the tag."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:248
+# f1ede2abd59c4fcc914acf233aa4b38c
+msgid "Select 'default' from the 'Config > Virtual Router' drop-down (assuming that is what your virtual router is called)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:251
+# 0d7f8743ae7e405c833390569c1a342c
+msgid "Click the 'IPv4' tab"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:253
+# 93bc9ae7b5f346f99a40644725c2ebc0
+msgid "Select 'Static' from the 'Type' radio options"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:255
+# 661bc9fb00f342d58bfd39624ff5f72a
+msgid "Click 'Add' in the 'IP' section"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:257
+# b3482058794d4e2abb1e0a1f41bee8fa
+msgid "Enter '172.30.0.254/24' in the new line"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:259
+# 02e03b2878504ed9a7ee888b36978cd4
+msgid "The IP can be any IP outside the CloudStack public IP range, but inside the CloudStack public range netmask (it can NOT be the gateway IP)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:262
+# 925fe2a4b10d4cb1ab438e2de318af0a
+msgid "The subnet defined by the CIDR should match the CloudStack public range netmask"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:269
+# 10d6dd9ed3af49ffad4020de805389de
+msgid "Commit configuration on the Palo Alto Networks Firewall"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:271
+# 89ac6f1b3c694a06b75008f8eec59b16
+msgid "In order for all the changes we just made to take effect, we need to commit the changes."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:274
+# 3137cac6d6e14fc9904a5fa154e3905d
+msgid "Click the 'Commit' link in the top right corner of the window"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:276
+# f3aaf9f819ef410fba6edbc621ea6a4d
+msgid "Click 'OK' in the commit window overlay"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:278
+# 3b4acc9911434ddc83362cedcacab668
+msgid "Click 'Close' to the resulting commit status window after the commit finishes"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:284
+# 6bb86113a96547538dbfd01db7c9e7ae
+msgid "Setup the Palo Alto Networks Firewall in CloudStack"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:287
+# b8515e0d94ef4d4a865f64f7bef85482
+msgid "Add the Palo Alto Networks Firewall as a Service Provider"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:289
+# 9b19a32893484d2fac28f3558f2643b5
+msgid "Navigate to 'Infrastructure > Zones > ZONE_NAME > Physical Network > NETWORK_NAME (guest) > Configure; Network Service Providers'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:292
+# 9bdf06473baa43cd9c6b8cb17a6313c3
+msgid "Click on 'Palo Alto' in the list"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:294
+# 8565a2ab22994798a9167083879136f7
+msgid "Click 'View Devices'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:296
+# d10162d1e53c40e6bd448e05bb8a3259
+msgid "Click 'Add Palo Alto Device'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:298
+# c6fcd95bacbf4675951227d95a5737fc
+msgid "Enter your configuration in the overlay.  This example will reflect the details previously used in this guide."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:301
+# 1d34f716f84e4296a01fd3f7afde7356
+msgid "**IP Address**: (the IP of the Palo Alto Networks Firewall)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:303
+# add3b3461b6b48d7b74f94961a7b26e1
+msgid "**Username**: (the admin username for the firewall)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:305
+# 708228ac2edb498f9fd079d05a8a7511
+msgid "**Password**: (the admin password for the firewall)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:307
+# b2a6f266de904ebe94805b3176617484
+msgid "**Type**: Palo Alto Firewall"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:309
+# 1cc218519592430f98cc8e009d0c8f2c
+msgid "**Public Interface**: ethernet1/1 (use what you setup earlier as the public interface if it is different from my examples)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:312
+# 5f1c1837d4df4e65a7a8abd05abd43ce
+msgid "**Private Interface**: ethernet1/2 (use what you setup earlier as the private interface if it is different from my examples)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:315
+# dd40b4143070449bb34ede04b3fe467e
+msgid "**Number of Retries**: 2 (the default is fine)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:317
+# 1d8080f41f894087b6e0a8c4c934dfe9
+msgid "**Timeout**: 300 (the default is fine)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:319
+# 876888b0168e496a897f306b246db971
+msgid "**Public Network**: untrust (this is the public zone on the firewall and did not need to be configured)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:322
+# 920274e528a341fb8962b73ff4b77179
+msgid "**Private Network**: trust (this is the private zone on the firewall and did not need to be configured)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:325
+# 2072277d3e14495aa762454838f72995
+msgid "**Virtual Router**: default (this is the name of the Virtual Router we setup on the firewall)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:328
+# 0376444c2cbd4404ad01b614aac5c07f
+msgid "**Palo Alto Threat Profile**: (not required.  name of the 'Security Profile Groups' to apply.  more details in the 'Additional Features' section)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:332
+# e649ac1802774500b5003c708987fe74
+msgid "**Palo Alto Log Profile**: (not required.  name of the 'Log Forwarding' profile to apply.  more details in the 'Additional Features' section)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:335
+# 32094fb7d72248d28b8f84e1fd56e988
+msgid "**Capacity**: (not required)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:337
+# 7e33721fb17a48e2ab7aa2d1b1dc460c
+msgid "**Dedicated**: (not required)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:341
+# dbef98d732fc4f7fbbad776d1b61f41e
+msgid "Click on 'Palo Alto' in the breadcrumbs to go back one screen."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:343
+# e499e22a30754ab4acfd6a779b03ea97
+msgid "Click on 'Enable Provider' |EnableDisableFeature.png|"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:347
+# b7b0fa1a4629430b839286b55162f882
+msgid "Add a Network Service Offering to use the new Provider"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:349
+# 1cc4ca671df7479c96ab873e7ae0cc68
+msgid "There are 6 'Supported Services' that need to be configured in the network service offering for this functionality.  They are DHCP, DNS, Firewall, Source NAT, Static NAT and Port Forwarding.  For the other settings, there are probably additional configurations which will work, but I will just document a common case."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:355
+# f406f98a91684fd1bd4947a0b06ed1a2
+msgid "Navigate to 'Service Offerings'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:357
+# 942ee3b426ba4d88acfbee186446dcaf
+msgid "In the drop-down at the top, select 'Network Offerings'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:359
+# 6d216de0290941758439b72593f8a6c8
+msgid "Click 'Add Network Offering'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:361
+# da673cd57e5d4dadaaa406cb5fa5ec13
+msgid "**Name**: (name it whatever you want)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:363
+# a59e3d821172494d9efb8de1253d352d
+msgid "**Description**: (again, can be whatever you want)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:365
+# bdb32fa4fdf545d2886707aa7ca1156d
+msgid "**Guest Type**: Isolated"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:367
+# ee73168cca234bf08581ec3131ec5bb8
+msgid "**Supported Services**:"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:369
+# 320e8c3f0b9b49ac8768926d267e94d7
+msgid "**DHCP**: Provided by 'VirtualRouter'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:371
+# 4c6b47d1b7b34586863177a90b865d85
+msgid "**DNS**: Provided by 'VirtualRouter'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:373
+# 56ac8260b8a3496ca38997dfc58dae3f
+msgid "**Firewall**: Provided by 'PaloAlto'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:375
+# fb63dd0553724890988f01e52cc9fb1a
+msgid "**Source NAT**: Provided by 'PaloAlto'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:377
+# 4cdf39f3041d47699f285f61fcf0ac95
+msgid "**Static NAT**: Provided by 'PaloAlto'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:379
+# bfbb888f85ab4e179965cac8c6d8dadb
+msgid "**Port Forwarding**: Provided by 'PaloAlto'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:381
+# 88e886aff4204f32811dff6e4d8ea019
+msgid "**System Offering for Router**: System Offering For Software Router"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:383
+# 8f0e43a7d0f34b9992263fdfdcfcd2d6
+msgid "**Supported Source NAT Type**: Per account (this is the only supported option)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:386
+# e06e5423d74c4f328eae1e741028734b
+msgid "**Default egress policy**: (both 'Allow' and 'Deny' are supported)"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:390
+# 59c525fe149a425098205f41b21a9cf1
+msgid "Click on the newly created service offering"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:392
+# 44fc81442fe34d68a2728f0ca0a160dc
+msgid "Click 'Enable network offering' |EnableDisableFeature.png|"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:394
+# 934d3259e9bf44c083323e6b2f2aa9bf
+msgid "When adding networks in CloudStack, select this network offering to use the Palo Alto Networks firewall."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:399
+# fae8d19c649e479f99c6b2edd49434eb
+msgid "Additional Features"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:401
+# 9dc0b83948d74e16b3ad351d1210f5b5
+msgid "In addition to the standard functionality exposed by CloudStack, we have added a couple additional features to this implementation.  We did not add any new screens to CloudStack, but we have added a couple fields to the 'Add Palo Alto Service Provider' screen which will add functionality globally for the device."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:408
+# 5af1e576fa7847f7b87eed5fe35e77b8
+msgid "Palo Alto Networks Threat Profile"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:410
+# 9070542c237349599f645efcd8a64128
+msgid "This feature allows you to specify a 'Security Profile Group' to be applied to all of the firewall rules which are created on the Palo Alto Networks firewall device."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:414
+# a4257973d0524640b7102968817ca7e5
+msgid "To create a 'Security Profile Group' on the Palo Alto Networks firewall, do the following:"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:417
+#: ../../networking/palo_alto_config.rst:446
+# 77a31bab19cd4e55b4cc13c92cb328bb
+# 92409a68a6f345c89e059f0a26e707ee
+msgid "Log into the Palo Alto Networks firewall"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:419
+# 2b0227f96b854d92bf96e91d9c17435c
+msgid "Navigate to 'Objects > Security Profile Groups'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:421
+# 2405f37aad834c34b4360f784ce6ec69
+msgid "Click 'Add' at the bottom of the page to add a new group"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:423
+# 7e5ffff8c26545c48b07a4921ca76a52
+msgid "Give the group a Name and specify the profiles you would like to include in the group"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:428
+#: ../../networking/palo_alto_config.rst:457
+# 3e3d4bfaa14c46c38499c68ce4f36095
+# 547b08aaaf164fb68c2b8f1b37d09793
+msgid "Click the 'Commit' link in the top right of the screen and follow the on screen instructions"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:431
+# a31ebe4cd3bf4bf9b7e3fe8d35c32f63
+msgid "Once you have created a profile, you can reference it by Name in the 'Palo Alto Threat Profile' field in the 'Add the Palo Alto Networks Firewall as a Service Provider' step."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:437
+# 735566ed2935434ea67f2e2595c3f686
+msgid "Palo Alto Networks Log Forwarding Profile"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:439
+# c229e4bdb0c04fac952295035d8afa6b
+msgid "This feature allows you to specify a 'Log Forwarding' profile to better manage where the firewall logs are sent to.  This is helpful for keeping track of issues that can arise on the firewall."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:443
+# 461ea8be12674fcd842217cf72c68f7f
+msgid "To create a 'Log Forwarding' profile on the Palo Alto Networks Firewall, do the following:"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:448
+# a61142f77e8941e9b976c01cd1aa9f89
+msgid "Navigate to 'Objects > Log Forwarding'"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:450
+# ea14dff9d3c448f0976b6aebe2d119cc
+msgid "Click 'Add' at the bottom of the page to add a new profile"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:452
+# 1352f9adcbd94a24a5429e2ed53caa48
+msgid "Give the profile a Name and specify the details you want for the traffic and threat settings"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:460
+# 6b304cde8312467ebef3f110a46fce1a
+msgid "Once you have created a profile, you can reference it by Name in the 'Palo Alto Log Profile' field in the 'Add the Palo Alto Networks Firewall as a Service Provider' step."
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:467
+# 7ba0d11bde5b4c3e97de4830b0aecc15
+msgid "Limitations"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:469
+# 796314d492b54823a652a3f50d430629
+msgid "The implementation currently only supports a single public IP range in CloudStack"
+msgstr ""
+
+#: ../../networking/palo_alto_config.rst:472
+# c8e8545461454cb9acf0a06bf42b95c0
+msgid "Usage tracking is not yet implemented"
+msgstr ""
+
diff --git a/source/locale/pot/networking/persistent_networks.pot b/source/locale/pot/networking/persistent_networks.pot
new file mode 100644
index 0000000..5db6bc1
--- /dev/null
+++ b/source/locale/pot/networking/persistent_networks.pot
@@ -0,0 +1,123 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/persistent_networks.rst:18
+# 4083b4f8962d4ce2add5a637beceaf4d
+msgid "Persistent Networks"
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:20
+# 5157cfe530594f5f954a8a8e1525ce10
+msgid "The network that you can provision without having to deploy any VMs on it is called a persistent network. A persistent network can be part of a VPC or a non-VPC environment."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:24
+# 469fa7c5517f4f82b49e9015b0027b0f
+msgid "When you create other types of network, a network is only a database entry until the first VM is created on that network. When the first VM is created, a VLAN ID is assigned and the network is provisioned. Also, when the last VM is destroyed, the VLAN ID is released and the network is no longer available. With the addition of persistent network, you will have the ability to create a network in CloudStack in which physical devices can be deployed without having to run any VMs. Additionally, you can deploy physical devices on that network."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:33
+# 87f88f46858c41ba96f785b7c3122342
+msgid "One of the advantages of having a persistent network is that you can create a VPC with a tier consisting of only physical devices. For example, you might create a VPC for a three-tier application, deploy VMs for Web and Application tier, and use physical machines for the Database tier. Another use case is that if you are providing services by using physical hardware, you can define the network as persistent and therefore even if all its VMs are destroyed the services will not be discontinued."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:44
+# 68622842a6474e23b5b4ace4928a7f02
+msgid "Persistent Network Considerations"
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:46
+# bd289a0ef0dc4ef1b5a6acb8b9ad0c38
+msgid "Persistent network is designed for isolated networks."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:48
+# 10b2b9266df84efcb8fb9002316e3f11
+msgid "All default network offerings are non-persistent."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:50
+# d9e8d354f6bc4b6f8194156ed112a537
+msgid "A network offering cannot be editable because changing it affects the behavior of the existing networks that were created using this network offering."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:54
+# 80b8615033b54141b06d3d7a311809bf
+msgid "When you create a guest network, the network offering that you select defines the network persistence. This in turn depends on whether persistent network is enabled in the selected network offering."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:58
+# 5e5d6fc784af4dec8e15481000f5125f
+msgid "An existing network can be made persistent by changing its network offering to an offering that has the Persistent option enabled. While setting this property, even if the network has no running VMs, the network is provisioned."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:63
+# 30e1aaa119a34adcb9a57e513d705745
+msgid "An existing network can be made non-persistent by changing its network offering to an offering that has the Persistent option disabled. If the network has no running VMs, during the next network garbage collection run the network is shut down."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:68
+# 1fafa4f8c2e8475e984703fe2e4c29ba
+msgid "When the last VM on a network is destroyed, the network garbage collector checks if the network offering associated with the network is persistent, and shuts down the network only if it is non-persistent."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:75
+# 6302571eba5d408687957bd3759816c3
+msgid "Creating a Persistent Guest Network"
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:77
+# c3876e9bd8d449b489101f5ac1bae458
+msgid "To create a persistent network, perform the following:"
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:79
+# 99fe5f5c722844089e5bdbcdadb22fc0
+msgid "Create a network offering with the Persistent option enabled."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:81
+# 16d2470643ab4777a40f35f26a9de70c
+msgid "See `\"Creating a New Network Offering\" <networking.html#creating-a-new-network-offering>`_."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:84
+# 267c8937d18548498e620897ef0e587e
+msgid "Select Network from the left navigation pane."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:86
+# bc4568a29a4149c797c11839057e9538
+msgid "Select the guest network that you want to offer this network service to."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:89
+# ecdb6f1a35444f46acd9620f3305b060
+msgid "Click the Edit button."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:91
+# 5bda22ffd010416cb80b2848179d18fa
+msgid "From the Network Offering drop-down, select the persistent network offering you have just created."
+msgstr ""
+
+#: ../../networking/persistent_networks.rst:94
+# fd7fed942171405cb30c3ea00f4111cb
+msgid "Click OK."
+msgstr ""
+
diff --git a/source/locale/pot/networking/portable_ips.pot b/source/locale/pot/networking/portable_ips.pot
new file mode 100644
index 0000000..d21b851
--- /dev/null
+++ b/source/locale/pot/networking/portable_ips.pot
@@ -0,0 +1,210 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/portable_ips.rst:18
+# 0d718ef9845940f3b45f93fdedd55a80
+msgid "Portable IPs"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:21
+# 7dbdc94b3c7148f3a67dd212137b1b78
+msgid "About Portable IP"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:23
+# a4b9041cb1da4c7c9185978b3bd46328
+msgid "Portable IPs in CloudStack are region-level pool of IPs, which are elastic in nature, that can be transferred across geographically separated zones. As an administrator, you can provision a pool of portable public IPs at region level and are available for user consumption. The users can acquire portable IPs if admin has provisioned portable IPs at the region level they are part of. These IPs can be use for any service within an advanced zone. You can also use portable IPs for EIP services in basic zones."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:32
+# 824ded2676d34d4b8d60fd93b08f58c8
+msgid "The salient features of Portable IP are as follows:"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:34
+# 1f57b59fbbbd426b9b2fd6f4dffaa0d2
+msgid "IP is statically allocated"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:36
+# 1759d65d5ed34db283d80b85d56f486a
+msgid "IP need not be associated with a network"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:38
+# 6826b76a9eea4332a6c068382f8b050c
+msgid "IP association is transferable across networks"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:40
+# ae7460bc9900474fbf94402165b9cb7e
+msgid "IP is transferable across both Basic and Advanced zones"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:42
+# 770563314c044da6acca6641fce5f500
+msgid "IP is transferable across VPC, non-VPC isolated and shared networks"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:44
+# ea55d3113555412f8f8a2bbf4f6b0846
+msgid "Portable IP transfer is available only for static NAT."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:48
+# 2ff5ef4c14bb4585a2e7c5c7458d25fe
+msgid "Guidelines"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:50
+# 662d9610efd3460aae2192eea97c7bd6
+msgid "Before transferring to another network, ensure that no network rules (Firewall, Static NAT, Port Forwarding, and so on) exist on that portable IP."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:56
+# d276865047e64a7f9cdddb63ad28d313
+msgid "Configuring Portable IPs"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:58
+#: ../../networking/portable_ips.rst:90
+# b085a9f5f2ce4744b86603f26196b283
+# a28f4db3b1734d3c9f0aa6cada34dab5
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:60
+# 2f850a50ddab404d9df06aa0338d6479
+msgid "In the left navigation, click Regions."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:62
+# 316a2bbd2c69469597356b663e5135ba
+msgid "Choose the Regions that you want to work with."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:64
+# c66c2dfa7575447e82396eeff33e1315
+msgid "Click View Portable IP."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:66
+# cd5798170b724d0abe4461ee8779eded
+msgid "Click Portable IP Range."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:68
+# 09d0a8e2201a44acbe61f89c2ebdba6b
+msgid "The Add Portable IP Range window is displayed."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:70
+# 9c9681bfaca543f09522720f86b05c3b
+msgid "Specify the following:"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:72
+# 2832d8a453bf4a27a01dfbe6ade2c252
+msgid "**Start IP/ End IP**: A range of IP addresses that are accessible from the Internet and will be allocated to guest VMs. Enter the first and last IP addresses that define a range that CloudStack can assign to guest VMs."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:77
+# ea589b30c39d429c86fd50fe49515dd7
+msgid "**Gateway**: The gateway in use for the Portable IP addresses you are configuring."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:80
+# 9d8360b75a254007b307c9ba1341550d
+msgid "**Netmask**: The netmask associated with the Portable IP range."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:82
+# 60ed534104ce48fdb9586f72c61b379f
+msgid "**VLAN**: The VLAN that will be used for public traffic."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:84
+# 8615e1020e2747f0ba31cd4cb186a010
+msgid "Click OK."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:88
+# d88ec64c255243049a67ed2616530031
+msgid "Acquiring a Portable IP"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:92
+# b933b6d78fe94153a35b24d2ccfd8e06
+msgid "In the left navigation, choose Network."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:94
+# 2f46ac57574a4ff3833cd3af46386463
+msgid "Click the name of the network where you want to work with."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:96
+# a7dc83315ae746af830094d45cfe7c11
+msgid "Click View IP Addresses."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:98
+# 64b8eac8ac21402293c2fff5d435a7eb
+msgid "Click Acquire New IP."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:100
+# 4a739787a6194df09e032797d1fe0911
+msgid "The Acquire New IP window is displayed."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:102
+# c8424da0e97a443f9d01fab04339184f
+msgid "Specify whether you want cross-zone IP or not."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:104
+# 222f964df0914c01bf92a5a5f461d4cc
+msgid "Click Yes in the confirmation dialog."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:106
+# 97dbf547785f4b1aaea165efca4b50a9
+msgid "Within a few moments, the new IP address should appear with the state Allocated. You can now use the IP address in port forwarding or static NAT rules."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:112
+# b84bba5db56047ba9dcd10cad9a14c3a
+msgid "Transferring Portable IP"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:114
+# f9ff7b7ea0d541a2bb6530a633a01f8b
+msgid "An IP can be transferred from one network to another only if Static NAT is enabled. However, when a portable IP is associated with a network, you can use it for any service in the network."
+msgstr ""
+
+#: ../../networking/portable_ips.rst:118
+# 2112dfc5676e4e7fbeb783e1bdbafb8d
+msgid "To transfer a portable IP across the networks, execute the following API:"
+msgstr ""
+
+#: ../../networking/portable_ips.rst:125
+# 794e73bb89214a29bc9257f2fc58c178
+msgid "Replace the UUID with appropriate UUID. For example, if you want to transfer a portable IP to network X and VM Y in a network, execute the following:"
+msgstr ""
+
diff --git a/source/locale/pot/networking/public_ips_and_vlans_for_accounts.pot b/source/locale/pot/networking/public_ips_and_vlans_for_accounts.pot
new file mode 100644
index 0000000..4d6abc6
--- /dev/null
+++ b/source/locale/pot/networking/public_ips_and_vlans_for_accounts.pot
@@ -0,0 +1,261 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:18
+# e16ce84ab27a470389c600bd7f1937e6
+msgid "Reserving Public IP Addresses and VLANs for Accounts"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:20
+# d20bf40a65964aee8e9477cfb99a8d76
+msgid "CloudStack provides you the ability to reserve a set of public IP addresses and VLANs exclusively for an account. During zone creation, you can continue defining a set of VLANs and multiple public IP ranges. This feature extends the functionality to enable you to dedicate a fixed set of VLANs and guest IP addresses for a tenant."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:26
+# e0cd381debc1495fa88b0bed963e8b16
+msgid "Note that if an account has consumed all the VLANs and IPs dedicated to it, the account can acquire two more resources from the system. CloudStack provides the root admin with two configuration parameter to modify this default behavior: use.system.public.ips and use.system.guest.vlans. These global parameters enable the root admin to disallow an account from acquiring public IPs and guest VLANs from the system, if the account has dedicated resources and these dedicated resources have all been consumed. Both these configurations are configurable at the account level."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:36
+# baef2538501f4f729cd5b4f69fbbefaa
+msgid "This feature provides you the following capabilities:"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:38
+# 4e16f6283a6e4f389b44d3af88cc4364
+msgid "Reserve a VLAN range and public IP address range from an Advanced zone and assign it to an account"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:41
+# c67672fcea6c4ae69a5c3c7d8fbd6a33
+msgid "Disassociate a VLAN and public IP address range from an account"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:43
+# 8451f0b840ab420cb1589fcc1572e6c0
+msgid "View the number of public IP addresses allocated to an account"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:45
+# 2a183b234d9c44b8b99fa31594f06e38
+msgid "Check whether the required range is available and is conforms to account limits."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:48
+# be8cff382a7748e4a75c68c3f8aa3dd7
+msgid "The maximum IPs per account limit cannot be superseded."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:52
+# 17f5e888607c4537816aa2f2e8b7c363
+msgid "Dedicating IP Address Ranges to an Account"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:54
+# 5409cfc1bd6f4b41bdd23eee4d6b9396
+msgid "Log in to the CloudStack UI as administrator."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:56
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:126
+# b8615267486a44ff8ee964b26529f16d
+# ba51a55851504a869dc0f28d293993ad
+msgid "In the left navigation bar, click Infrastructure."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:58
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:128
+# b1c57a90f0c843c4906f95e699dd7d13
+# 2a38ee721dc8442f850ff993fa52de59
+msgid "In Zones, click View All."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:60
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:130
+# defb870416a14ff0a7ea37bf68b8e890
+# 207025dba9b843299213868bf721e0d2
+msgid "Choose the zone you want to work with."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:62
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:132
+# 04eaa49757a64adf830002153cf8db20
+# cea8888967a844ccbb283c973f4b9482
+msgid "Click the Physical Network tab."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:64
+# fd016a6c74fa4aceb46c592a01f82621
+msgid "In the Public node of the diagram, click Configure."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:66
+# abe4deb76feb40fd9fa6dd1461e1dec3
+msgid "Click the IP Ranges tab."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:68
+# 3686de2bd0e24c578fb64abcd3b86fbc
+msgid "You can either assign an existing IP range to an account, or create a new IP range and assign to an account."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:71
+# 90bc5a3040c541cb95831323867cee7d
+msgid "To assign an existing IP range to an account, perform the following:"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:73
+# 196250a3ddc54abc978d437ea8ba3f96
+msgid "Locate the IP range you want to work with."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:75
+# 0a707d3297ad4ccfa38f80baa7690816
+msgid "Click Add Account |addAccount-icon.png| button."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:77
+# 3aaf2af3bb8f4c9485ae2e0ada7aee73
+msgid "The Add Account dialog is displayed."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:79
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:89
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:107
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:142
+# b99e236f412f4946af47669c8d62396e
+# eedc80b2aa5c4c8696da4d4b51a28179
+# 39b98908344542aeb2e40bdbf9550571
+# f6dc925b4c634b9fa0523254d12380bb
+msgid "Specify the following:"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:81
+# 64e4bf3c9f034ef4adb32087be1bc7aa
+msgid "**Account**: The account to which you want to assign the IP address range."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:84
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:112
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:150
+# d15ca620e8154bf9ad213a256496e6e0
+# 09ac68b8a6f24e84b36a726d6058809b
+# f8da528d9cdd447fb262d7ca5542308f
+msgid "**Domain**: The domain associated with the account."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:86
+# 06d6686b378e4a22a762e94353aee862
+msgid "To create a new IP range and assign an account, perform the following:"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:91
+# dd52a8808d1b44e7ba133f213439d71d
+msgid "**Gateway**"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:93
+# 781ca41349a949cca28101dfea1676d5
+msgid "**Netmask**"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:95
+# 1b745bfb0a6443e1a0f947860308e044
+msgid "**VLAN**"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:97
+# 9526ce220e2941459d408f259d6e9b30
+msgid "**Start IP**"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:99
+# a55c7588b51f4a84afa7fa78fc58ed5e
+msgid "**End IP**"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:101
+# 9282436854274ee485b8c2df6ba7f342
+msgid "**Account**: Perform the following:"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:103
+# 678fa43c9d524b8fbb3ca453d599d6f1
+msgid "Click Account."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:105
+# 58e785cf6c3f4544af852a60e9ff4639
+msgid "The Add Account page is displayed."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:109
+# c1b6c5a339b940b7907cfc3fd14b35d6
+msgid "**Account**: The account to which you want to assign an IP address range."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:115
+# e54b45158ec1469392091a64574cbb55
+msgid "Click OK."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:117
+# cbf3d4473399404684b33c48a92e0148
+msgid "Click Add."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:121
+# 8d933442217c4288b95b7ed71f57b95f
+msgid "Dedicating VLAN Ranges to an Account"
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:123
+# d7e1ce8c0be24d57b606cd1a7b4ac29e
+msgid "After the CloudStack Management Server is installed, log in to the CloudStack UI as administrator."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:134
+# 68317dc975da4182878b75c19ec73b1e
+msgid "In the Guest node of the diagram, click Configure."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:136
+# de0ffdc9f48d4d068a50a53f85c49cea
+msgid "Select the Dedicated VLAN Ranges tab."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:138
+# d7319cdb148746849dba29b0a020ce01
+msgid "Click Dedicate VLAN Range."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:140
+# 6037b47944d9429aad5df0dd7981dace
+msgid "The Dedicate VLAN Range dialog is displayed."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:144
+# 564cf1e324b54969924910efd7c3f00b
+msgid "**VLAN Range**: The VLAN range that you want to assign to an account."
+msgstr ""
+
+#: ../../networking/public_ips_and_vlans_for_accounts.rst:147
+# b2c4b566d49c4a3b99b3268f4e867233
+msgid "**Account**: The account to which you want to assign the selected VLAN range."
+msgstr ""
+
diff --git a/source/locale/pot/networking/releasing_an_ip_address.pot b/source/locale/pot/networking/releasing_an_ip_address.pot
new file mode 100644
index 0000000..0a982ef
--- /dev/null
+++ b/source/locale/pot/networking/releasing_an_ip_address.pot
@@ -0,0 +1,58 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/releasing_an_ip_address.rst:18
+# c50d06f60c5d483ba5f4799c50384e9c
+msgid "Releasing an IP Address"
+msgstr ""
+
+#: ../../networking/releasing_an_ip_address.rst:20
+# 3a245bdefb444425ad5f7bd6a1ea5de2
+msgid "When the last rule for an IP address is removed, you can release that IP address. The IP address still belongs to the VPC; however, it can be picked up for any guest network again."
+msgstr ""
+
+#: ../../networking/releasing_an_ip_address.rst:24
+# 99e24197740148e683aa3ffad5870800
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr ""
+
+#: ../../networking/releasing_an_ip_address.rst:26
+# da80f79b21a846878018930987c87ffd
+msgid "In the left navigation, choose Network."
+msgstr ""
+
+#: ../../networking/releasing_an_ip_address.rst:28
+# 24863c020eb04ba9808fc2e0f24e0760
+msgid "Click the name of the network where you want to work with."
+msgstr ""
+
+#: ../../networking/releasing_an_ip_address.rst:30
+# 1e70144ba5394954a2c92850335b7555
+msgid "Click View IP Addresses."
+msgstr ""
+
+#: ../../networking/releasing_an_ip_address.rst:32
+# 3f542514484849b1bfde31aa95ec3a25
+msgid "Click the IP address you want to release."
+msgstr ""
+
+#: ../../networking/releasing_an_ip_address.rst:34
+# 7851cee0ec9c4ea3a8d5309aa5f84d40
+msgid "Click the Release IP button. |ReleaseIPButton.png|"
+msgstr ""
+
diff --git a/source/locale/pot/networking/remote_access_vpn.pot b/source/locale/pot/networking/remote_access_vpn.pot
new file mode 100644
index 0000000..b7806e1
--- /dev/null
+++ b/source/locale/pot/networking/remote_access_vpn.pot
@@ -0,0 +1,997 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/remote_access_vpn.rst:18
+# 037fa60a2e2f4601bf22e714a97fe0fd
+msgid "Remote Access VPN"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:20
+# 8202b8f150584992995c6c6f69a2c907
+msgid "CloudStack account owners can create virtual private networks (VPN) to access their virtual machines. If the guest network is instantiated from a network offering that offers the Remote Access VPN service, the virtual router (based on the System VM) is used to provide the service. CloudStack provides a L2TP-over-IPsec-based remote access VPN service to guest virtual networks. Since each network gets its own virtual router, VPNs are not shared across the networks. VPN clients native to Windows, Mac OS X and iOS can be used to connect to the guest networks. The account owner can create and manage users for their VPN. CloudStack does not use its account database for this purpose but uses a separate table. The VPN user database is shared across all the VPNs created by the account owner. All VPN users get access to all VPNs created by the account owner."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:35
+# a8a54e6134ab4ebaae71aeb42d0ad32b
+msgid "Make sure that not all traffic goes through the VPN. That is, the route installed by the VPN should be only for the guest network and not for all traffic."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:39
+# a107bc4ab6624b839681adafc00d60e1
+msgid "**Road Warrior / Remote Access**. Users want to be able to connect securely from a home or office to a private network in the cloud. Typically, the IP address of the connecting client is dynamic and cannot be preconfigured on the VPN server."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:44
+# 7b5e742bfe7f429794320cf1c32ffdfc
+msgid "**Site to Site**. In this scenario, two private subnets are connected over the public Internet with a secure VPN tunnel. The cloud user's subnet (for example, an office network) is connected through a gateway to the network in the cloud. The address of the user's gateway must be preconfigured on the VPN server in the cloud. Note that although L2TP-over-IPsec can be used to set up Site-to-Site VPNs, this is not the primary intent of this feature. For more information, see \":ref:`setting-s2s-vpn-conn`\"."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:55
+# 3411c8387ca84f18bd032795907f4585
+msgid "Configuring Remote Access VPN"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:57
+# b5e1d88079c447ba9d2baa0e3f5cf685
+msgid "To set up VPN for the cloud:"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:59
+#: ../../networking/remote_access_vpn.rst:301
+#: ../../networking/remote_access_vpn.rst:411
+#: ../../networking/remote_access_vpn.rst:431
+#: ../../networking/remote_access_vpn.rst:493
+#: ../../networking/remote_access_vpn.rst:624
+# 85153916f2a94aeb80faa2c9f22cfcea
+# e7cff502f3494c00b665a1b732e05fb1
+# 7fd5ac75573d435b8c164435b6b50404
+# ab1f2323529a48e8a071e9baa44284e3
+# 6dfbddbad973426b8d6704da05fb2166
+# ce7c03a477b84c029914728fac5f85d5
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:61
+# ef4d98e4df0149d797b4aebfc0dbdc03
+msgid "In the left navigation, click Global Settings."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:63
+# 6915f23eef3f4ddfaf19ba566058535d
+msgid "Set the following global configuration parameters."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:65
+# b46467b5e34e436389d14380f0094d63
+msgid "remote.access.vpn.client.ip.range - The range of IP addresses to be allocated to remote access VPN clients. The first IP in the range is used by the VPN server."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:69
+# ad4d961d0bf3453ebc21a59b09ad0207
+msgid "remote.access.vpn.psk.length - Length of the IPSec key."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:71
+# a89aef80d75a49a9bf21eed458b3a570
+msgid "remote.access.vpn.user.limit - Maximum number of VPN users per account."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:74
+# 115f9b2e63704bd7b8d0880401243098
+msgid "To enable VPN for a particular network:"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:76
+#: ../../networking/remote_access_vpn.rst:101
+# 1cbcce1e10884bc0906f10625b02b967
+# d3065ab6ac634b4ab6d37d5cc5f6b0f8
+msgid "Log in as a user or administrator to the CloudStack UI."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:78
+#: ../../networking/remote_access_vpn.rst:103
+# 911488c63a744096b46e3c6ffffb13be
+# d221bc15811f454fbe75a5f60599eddf
+msgid "In the left navigation, click Network."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:80
+# 6c20446c6a1442f5997a8515ffe0e2b7
+msgid "Click the name of the network you want to work with."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:82
+# a23f38b6e2c8464bb754dcb7965bd45e
+msgid "Click View IP Addresses."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:84
+# ddf12be035374568a290af5640b40e74
+msgid "Click one of the displayed IP address names."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:86
+#: ../../networking/remote_access_vpn.rst:140
+# 41e32709f78944188aa733087e185747
+# 29b34df35b844a28a5c4da345fb4deca
+msgid "Click the Enable VPN button. |vpn-icon.png|"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:88
+# 2721223cf47046fa977985536715b7f7
+msgid "The IPsec key is displayed in a popup window."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:92
+# 4837a25ffda64a66818f80b1160c7cd2
+msgid "Configuring Remote Access VPN in VPC"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:94
+# c157c1f5cdd34780971c2d08fa7c492c
+msgid "On enabling Remote Access VPN on a VPC, any VPN client present outside the VPC can access VMs present in the VPC by using the Remote VPN connection. The VPN client can be present anywhere except inside the VPC on which the user enabled the Remote Access VPN service."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:99
+# 5254f550923d4da39985b04b9a5b5054
+msgid "To enable VPN for a VPC:"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:105
+#: ../../networking/remote_access_vpn.rst:435
+#: ../../networking/remote_access_vpn.rst:497
+#: ../../networking/remote_access_vpn.rst:628
+# 12f54511f47d449693acfea97e8d4600
+# 435bbd53f5414d84ba589387bf3fdce6
+# b89124caf1504a709e89424403a433ed
+# 7f0dcc6104d34e828aed248a3d1e5382
+msgid "In the Select view, select VPC."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:107
+#: ../../networking/remote_access_vpn.rst:437
+#: ../../networking/remote_access_vpn.rst:630
+# 7febfd652a0f4a4a9e44f110742bf34a
+# f923f2ca6046405ab0c396e3ca9d07ec
+# 07d5aa607fb94d8b9968b055618eea1c
+msgid "All the VPCs that you have created for the account is listed in the page."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:110
+# 9c932fa1898c4fef97f99b0535e90a08
+msgid "Click the Configure button of the VPC."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:112
+#: ../../networking/remote_access_vpn.rst:446
+#: ../../networking/remote_access_vpn.rst:509
+#: ../../networking/remote_access_vpn.rst:641
+# 83859c50046f48e4b614cd9f79148c16
+# 15f6f70e22df4f90868d62f6c93d09f7
+# 22a5c413786843acb09faad526a6e8e0
+# b4e49b76aea54ad6a1b5116db84dd6d6
+msgid "For each tier, the following options are displayed:"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:114
+#: ../../networking/remote_access_vpn.rst:448
+#: ../../networking/remote_access_vpn.rst:511
+#: ../../networking/remote_access_vpn.rst:643
+# f709cfb9270544caa350d3649e206913
+# 1e135a9023a3449996277c5654e0ffe8
+# 36d751e518594344814cd905fce95167
+# 5f29611ae8024e66a507590e86ca1301
+msgid "Internal LB"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:116
+#: ../../networking/remote_access_vpn.rst:450
+#: ../../networking/remote_access_vpn.rst:513
+#: ../../networking/remote_access_vpn.rst:645
+# 38b29ff504c24ecc8d7d54f35ab29998
+# d744448419454b5ba7aae6c638c1f8fd
+# 7e6e21ff676c435d902e75134d2341e5
+# b7dd123eea7d460aa99844bad34e0f91
+msgid "Public LB IP"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:118
+#: ../../networking/remote_access_vpn.rst:452
+#: ../../networking/remote_access_vpn.rst:515
+#: ../../networking/remote_access_vpn.rst:647
+# 74d00e17afdf47d8a79f5c8f0a90a214
+# 404668f335f04d41947db0129e79e65f
+# bee509b27e7c4c9985f5bd7c9169ecaf
+# 7f14717fbb6e471c9e00e2f7622cfa7b
+msgid "Static NAT"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:120
+#: ../../networking/remote_access_vpn.rst:454
+#: ../../networking/remote_access_vpn.rst:517
+#: ../../networking/remote_access_vpn.rst:649
+# 6fd6582e4c7d47019c91a20d69646e3a
+# e333c5792fca4359b9348192f5918984
+# bdf83d752fbc42ef93ab96051cdf7700
+# 30265536e81c46c2879ee0cca63d1297
+msgid "Virtual Machines"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:122
+#: ../../networking/remote_access_vpn.rst:456
+#: ../../networking/remote_access_vpn.rst:519
+#: ../../networking/remote_access_vpn.rst:651
+# 8696dd08ef2d4b6a816ecd0095cdf602
+# f1f39145e71e46b09b4c26ce0175e5b8
+# fe3c8f334ef04b4aa83e3850c9666137
+# 54ff7edf855e482da2b26688c543effe
+msgid "CIDR"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:124
+#: ../../networking/remote_access_vpn.rst:458
+#: ../../networking/remote_access_vpn.rst:521
+#: ../../networking/remote_access_vpn.rst:653
+# 1bd24a8501fd4efd8cd4d0eba492ce37
+# e7a3e4a10b2e484f8b311cdb938a0e47
+# 95e13a760c004dc9a119ddf73d83d0fa
+# 5605be5958c24cb5a0f534dbdecdfa40
+msgid "The following router information is displayed:"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:126
+#: ../../networking/remote_access_vpn.rst:460
+#: ../../networking/remote_access_vpn.rst:523
+#: ../../networking/remote_access_vpn.rst:655
+# 8d80f7dd9bcc41f38e801ab022f3fa7d
+# 5c726601395a427e9f541bf544194e40
+# 8b623ab0e8764c58bad6a828685b3cce
+# 71bcceb5de54474b88583e11b88f962e
+msgid "Private Gateways"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:128
+#: ../../networking/remote_access_vpn.rst:462
+#: ../../networking/remote_access_vpn.rst:525
+#: ../../networking/remote_access_vpn.rst:657
+# 0b3d0e7c6eac4b83b9912d3af84c76b3
+# 582728e1b1c043f0bde4a3c35e0ebaba
+# df66b830cc464227ab4da8790a6275bf
+# 4055bdef61d847dc91261a6fc6346d1d
+msgid "Public IP Addresses"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:130
+#: ../../networking/remote_access_vpn.rst:464
+#: ../../networking/remote_access_vpn.rst:527
+#: ../../networking/remote_access_vpn.rst:659
+# 9ce2994577cc43f9bd1f86225e23149e
+# fbf89a2ae9534ea18fb4673230aa75fb
+# 0720a5b1037e49ffbf44a70beacd5c9b
+# 3ade6e74142f446c9bea2329e2828be8
+msgid "Site-to-Site VPNs"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:132
+#: ../../networking/remote_access_vpn.rst:466
+#: ../../networking/remote_access_vpn.rst:529
+#: ../../networking/remote_access_vpn.rst:661
+# 8c10e84bb92143eb918356bda1b0e7e5
+# 376033730f8d4e0b88fc25e1b6fdea80
+# a7e9c55327984532a4460a2b4ba05bb4
+# cd29b4ee7b0c4da0aec784bb04dce7e6
+msgid "Network ACL Lists"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:134
+# c45c88d1e8af4023bd23142b7397edd5
+msgid "In the Router node, select Public IP Addresses."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:136
+# 2334ea7959384b2bbf5138eb8c7aaf78
+msgid "The IP Addresses page is displayed."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:138
+# 31440b2a6daa47d2a5ff458a51ca81cc
+msgid "Click Source NAT IP address."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:142
+# 8cf058b60a184e129abe4d2bc8ade840
+msgid "Click OK to confirm. The IPsec key is displayed in a pop-up window."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:144
+# 36c398fbda5b45599ac36f3b5b77e97d
+msgid "Now, you need to add the VPN users."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:146
+# a6d5430b813547dabde217104eba046a
+msgid "Click the Source NAT IP."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:148
+# 88ac91cdca464aa8a924d7cbca73f3df
+msgid "Select the VPN tab."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:150
+# 76a034604e9a4113a46051cde33b0cd8
+msgid "Add the username and the corresponding password of the user you wanted to add."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:153
+# f388fc2f4f0749f5bbb9e062d57f1137
+msgid "Click Add."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:155
+# c491f786e1874564b25032b670c35f98
+msgid "Repeat the same steps to add the VPN users."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:159
+# d3c8df533b2c4e659158e77c8669a813
+msgid "Using Remote Access VPN with Windows"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:161
+# d03485e36a8744758782e81ab88041d1
+msgid "The procedure to use VPN varies by Windows version. Generally, the user must edit the VPN properties and make sure that the default route is not the VPN. The following steps are for Windows L2TP clients on Windows Vista. The commands should be similar for other Windows versions."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:166
+# 98196e5429de407da75adf5f3ce7cf8d
+msgid "Log in to the CloudStack UI and click on the source NAT IP for the account. The VPN tab should display the IPsec preshared key. Make a note of this and the source NAT IP. The UI also lists one or more users and their passwords. Choose one of these users, or, if none exists, add a user and password."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:172
+# 6a896fa8431d479195d161efebf56672
+msgid "On the Windows box, go to Control Panel, then select Network and Sharing center. Click Setup a connection or network."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:175
+# 8e983aa928b444228e689749e8fc0801
+msgid "In the next dialog, select No, create a new connection."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:177
+# 98f484c7652c45d2ae57690d719610ed
+msgid "In the next dialog, select Use my Internet Connection (VPN)."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:179
+# 784c5c041ba94caea475a667add0adcd
+msgid "In the next dialog, enter the source NAT IP from step #1 and give the connection a name. Check Don't connect now."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:183
+# 41d1540c0a7d401a9c549bd5304f18ce
+msgid "In the next dialog, enter the user name and password selected in step #1."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:186
+# 3cbbd674fd8d412c90bfbbeb8f607ea0
+msgid "Click Create."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:188
+# 85a9ef6f201e47f584255229980b3d87
+msgid "Go back to the Control Panel and click Network Connections to see the new connection. The connection is not active yet."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:191
+# 1d169d66dd744654bd8ea7dd62a677a6
+msgid "Right-click the new connection and select Properties. In the Properties dialog, select the Networking tab."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:196
+# a191730de1684f06a3d729e5cde2e487
+msgid "In Type of VPN, choose L2TP IPsec VPN, then click IPsec settings. Select Use preshared key. Enter the preshared key from step #1."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:199
+# 343858b6c3e5498fad0bd34b503e792d
+msgid "The connection is ready for activation. Go back to Control Panel -> Network Connections and double-click the created connection."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:202
+# e60c05ee4aef40d38a3a0b01aade9b5e
+msgid "Enter the user name and password from step #1."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:206
+# d1cfefca174a4554a0c4170ec0c49f9b
+msgid "Using Remote Access VPN with Mac OS X"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:208
+# 728cc61e43c440459c1ad6252a2f6b97
+msgid "First, be sure you've configured the VPN settings in your CloudStack install. This section is only concerned with connecting via Mac OS X to your VPN."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:212
+# b3185af9f4534991ad3e3e5b66f47da2
+msgid "Note, these instructions were written on Mac OS X 10.7.5. They may differ slightly in older or newer releases of Mac OS X."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:215
+# 6f2aaf1e33d6421db0f521c5820d02c8
+msgid "On your Mac, open System Preferences and click Network."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:217
+# 26e7088ea9494f94922f1a8f5e0ad753
+msgid "Make sure Send all traffic over VPN connection is not checked."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:219
+# 8e0600ca2c9546a2b3905659b64a835b
+msgid "If your preferences are locked, you'll need to click the lock in the bottom left-hand corner to make any changes and provide your administrator credentials."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:223
+# da1ba33a066b4415a728d14ab936780c
+msgid "You will need to create a new network entry. Click the plus icon on the bottom left-hand side and you'll see a dialog that says \"Select the interface and enter a name for the new service.\" Select VPN from the Interface drop-down menu, and \"L2TP over IPSec\" for the VPN Type. Enter whatever you like within the \"Service Name\" field."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:229
+# b96bb5f3c9534d3384752b6c652405b5
+msgid "You'll now have a new network interface with the name of whatever you put in the \"Service Name\" field. For the purposes of this example, we'll assume you've named it \"CloudStack.\" Click on that interface and provide the IP address of the interface for your VPN under the Server Address field, and the user name for your VPN under Account Name."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:236
+# db5b3b2b72e449368be600488d32a212
+msgid "Click Authentication Settings, and add the user's password under User Authentication and enter the pre-shared IPSec key in the Shared Secret field under Machine Authentication. Click OK."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:240
+# 79ff11baad9844c9a7bb84f19aac4703
+msgid "You may also want to click the \"Show VPN status in menu bar\" but that's entirely optional."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:243
+# 74b926642e7d49ca925804a4d6d99abc
+msgid "Now click \"Connect\" and you will be connected to the CloudStack VPN."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:249
+# fb0aef197790435d95971b0006f98a9d
+msgid "Setting Up a Site-to-Site VPN Connection"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:251
+# b113a5a8546b4ce8b1a7507f2b860ad7
+msgid "A Site-to-Site VPN connection helps you establish a secure connection from an enterprise datacenter to the cloud infrastructure. This allows users to access the guest VMs by establishing a VPN connection to the virtual router of the account from a device in the datacenter of the enterprise. You can also establish a secure connection between two VPC setups or high availability zones in your environment. Having this facility eliminates the need to establish VPN connections to individual VMs."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:260
+# ec0ce935716740158c031ebf544b7294
+msgid "The difference from Remote VPN is that Site-to-site VPNs connects entire networks to each other, for example, connecting a branch office network to a company headquarters network. In a site-to-site VPN, hosts do not have VPN client software; they send and receive normal TCP/IP traffic through a VPN gateway."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:266
+# 79120b77963b4f77afa51573e6ad1ca7
+msgid "The supported endpoints on the remote datacenters are:"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:268
+# 34aba4dd56884ad3871e85272aab2acf
+msgid "Cisco ISR with IOS 12.4 or later"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:270
+# 95978dcfdbf34c2886952ee16cb6e16d
+msgid "Juniper J-Series routers with JunOS 9.5 or later"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:272
+# 272a2a827c494e90a6b2d52dc96b7f0b
+msgid "CloudStack virtual routers"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:275
+# 8c16297c0eab4c72b6a2a29b0f4866d1
+msgid "In addition to the specific Cisco and Juniper devices listed above, the expectation is that any Cisco or Juniper device running on the supported operating systems are able to establish VPN connections."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:279
+# eb701cb20d40405b9ca1d79ce15b681f
+msgid "To set up a Site-to-Site VPN connection, perform the following:"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:281
+# b5f397a7a64b47168a74fb1618810e5c
+msgid "Create a Virtual Private Cloud (VPC)."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:283
+# 1d44be641cf042b99841b146bb055956
+msgid "See \":ref:`configuring-vpc`\"."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:285
+# f1ff67e23d7d4eaeb81c1b5686399942
+msgid "Create a VPN Customer Gateway."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:287
+# e3425171b9504f5b958d0802ca1a55ce
+msgid "Create a VPN gateway for the VPC that you created."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:289
+# 6d0964544a6944f39ec8eafdaf587428
+msgid "Create VPN connection from the VPC VPN gateway to the customer VPN gateway."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:294
+# 3d85874020904fbdb261885b5e2f05ce
+msgid "Creating and Updating a VPN Customer Gateway"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:297
+# 9b0857af13544aaebee5984422c93195
+msgid "A VPN customer gateway can be connected to only one VPN gateway at a time."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:299
+# 1a951a0ee8d54164b9b99ff9cd080e58
+msgid "To add a VPN Customer Gateway:"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:303
+#: ../../networking/remote_access_vpn.rst:413
+#: ../../networking/remote_access_vpn.rst:433
+#: ../../networking/remote_access_vpn.rst:495
+#: ../../networking/remote_access_vpn.rst:626
+# 6a26e636eb224d1eb75c9782de7c830d
+# affc98b5cd4b401086e5e00f9e69ac90
+# 23c81aa674f64826830390c49839730c
+# 98dc2f6f69d341b0b1867f35102e20ff
+# d4efd83e728b439eaa8408bd783d0c11
+msgid "In the left navigation, choose Network."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:305
+#: ../../networking/remote_access_vpn.rst:415
+# b0e99af0f0014e1aa156dd7f2644f23a
+# cf4e8a6aa8be4c3e9c92bd5f84e9b571
+msgid "In the Select view, select VPN Customer Gateway."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:307
+# 51d8e12e75dd47e4b2d4a9c52da89be9
+msgid "Click Add VPN Customer Gateway."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:309
+# e72b7822c85649f99f01e845e1418844
+msgid "|addvpncustomergateway.png|"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:311
+# 0810d2cb133043b4858badbc2e4ac704
+msgid "Provide the following information:"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:313
+# 372ec8983a514ad3b0927d01bc30fae6
+msgid "**Name**: A unique name for the VPN customer gateway you create."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:315
+# 0cd283ba65a241cf97d90b2c5f04c36f
+msgid "**Gateway**: The IP address for the remote gateway."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:317
+# 0e3f2efe75f7454e9f2ac706604f832d
+msgid "**CIDR list**: The guest CIDR list of the remote subnets. Enter a CIDR or a comma-separated list of CIDRs. Ensure that a guest CIDR list is not overlapped with the VPC's CIDR, or another guest CIDR. The CIDR must be RFC1918-compliant."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:322
+# 929c5f444fae4aee88faa98a926d0f52
+msgid "**IPsec Preshared Key**: Preshared keying is a method where the endpoints of the VPN share a secret key. This key value is used to authenticate the customer gateway and the VPC VPN gateway to each other."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:328
+# 171abb6f27ef471eae87fd0718d714af
+msgid "The IKE peers (VPN end points) authenticate each other by computing and sending a keyed hash of data that includes the Preshared key. If the receiving peer is able to create the same hash independently by using its Preshared key, it knows that both peers must share the same secret, thus authenticating the customer gateway."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:335
+# a4553b53ccb04b358a278545e87eb9bd
+msgid "**IKE Encryption**: The Internet Key Exchange (IKE) policy for phase-1. The supported encryption algorithms are AES128, AES192, AES256, and 3DES. Authentication is accomplished through the Preshared Keys."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:341
+# 3bb40218a4db49e0aa09d5983d57a8fa
+msgid "The phase-1 is the first phase in the IKE process. In this initial negotiation phase, the two VPN endpoints agree on the methods to be used to provide security for the underlying IP traffic. The phase-1 authenticates the two VPN gateways to each other, by confirming that the remote gateway has a matching Preshared Key."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:347
+# a5e3619f28fb487987386ff3359d079b
+msgid "**IKE Hash**: The IKE hash for phase-1. The supported hash algorithms are SHA1 and MD5."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:350
+# 998f798e068147c69b96d5332181acdd
+msgid "**IKE DH**: A public-key cryptography protocol which allows two parties to establish a shared secret over an insecure communications channel. The 1536-bit Diffie-Hellman group is used within IKE to establish session keys. The supported options are None, Group-5 (1536-bit) and Group-2 (1024-bit)."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:356
+# 34c98169c2dd4375a23dff45d764590d
+msgid "**ESP Encryption**: Encapsulating Security Payload (ESP) algorithm within phase-2. The supported encryption algorithms are AES128, AES192, AES256, and 3DES."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:361
+# c61b40cf82de4f9fb6c45b8e0172b4b4
+msgid "The phase-2 is the second phase in the IKE process. The purpose of IKE phase-2 is to negotiate IPSec security associations (SA) to set up the IPSec tunnel. In phase-2, new keying material is extracted from the Diffie-Hellman key exchange in phase-1, to provide session keys to use in protecting the VPN data flow."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:367
+# 71d47a66a42f4a04b2540e69eba4cdd9
+msgid "**ESP Hash**: Encapsulating Security Payload (ESP) hash for phase-2. Supported hash algorithms are SHA1 and MD5."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:370
+# 2378eab3a19b42cda0e954ae2c70bb38
+msgid "**Perfect Forward Secrecy**: Perfect Forward Secrecy (or PFS) is the property that ensures that a session key derived from a set of long-term public and private keys will not be compromised. This property enforces a new Diffie-Hellman key exchange. It provides the keying material that has greater key material life and thereby greater resistance to cryptographic attacks. The available options are None, Group-5 (1536-bit) and Group-2 (1024-bit). The security of the key exchanges increase as the DH groups grow larger, as does the time of the exchanges."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:381
+# de12259eb62f48c294bc324395468d43
+msgid "When PFS is turned on, for every negotiation of a new phase-2 SA the two gateways must generate a new set of phase-1 keys. This adds an extra layer of protection that PFS adds, which ensures if the phase-2 SA's have expired, the keys used for new phase-2 SA's have not been generated from the current phase-1 keying material."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:387
+# c29472e88000476ea8eb3f3165f58da4
+msgid "**IKE Lifetime (seconds)**: The phase-1 lifetime of the security association in seconds. Default is 86400 seconds (1 day). Whenever the time expires, a new phase-1 exchange is performed."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:391
+# c05a91d5e2b44d7a9ea842e762a6f4a0
+msgid "**ESP Lifetime (seconds)**: The phase-2 lifetime of the security association in seconds. Default is 3600 seconds (1 hour). Whenever the value is exceeded, a re-key is initiated to provide a new IPsec encryption and authentication session keys."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:396
+# 9afba73f17a3471faa8cff978bb64495
+msgid "**Dead Peer Detection**: A method to detect an unavailable Internet Key Exchange (IKE) peer. Select this option if you want the virtual router to query the liveliness of its IKE peer at regular intervals. It's recommended to have the same configuration of DPD on both side of VPN connection."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:402
+#: ../../networking/remote_access_vpn.rst:425
+# 4d12f59b777c48e98fb18ab2bace355d
+# a65f0ba427b04b6da2bdc39a05acba02
+msgid "Click OK."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:406
+# 460983ec4dd64370b650944e21d45b75
+msgid "Updating and Removing a VPN Customer Gateway"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:408
+# 47640086ca6e4122a862027f6e528af6
+msgid "You can update a customer gateway either with no VPN connection, or related VPN connection is in error state."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:417
+# eee4a55897da4f06b44795327c878110
+msgid "Select the VPN customer gateway you want to work with."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:419
+# 9dc617447a9c48df92819b996a8e3b39
+msgid "To modify the required parameters, click the Edit VPN Customer Gateway button |vpn-edit-icon.png|"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:422
+# 0c3c4beedfb2453cb03958649454d3d2
+msgid "To remove the VPN customer gateway, click the Delete VPN Customer Gateway button |delete.png|"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:429
+# ae45fd8564384b9a8682a662011196da
+msgid "Creating a VPN gateway for the VPC"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:440
+#: ../../networking/remote_access_vpn.rst:501
+#: ../../networking/remote_access_vpn.rst:633
+# addf23d2b2b14d9c80370bc70f64ec94
+# 8ab2d3e53e83433ab4cf699e916d89d9
+# 5ece94a59df34ecdb036ac45fc49bd06
+msgid "Click the Configure button of the VPC to which you want to deploy the VMs."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:443
+#: ../../networking/remote_access_vpn.rst:504
+#: ../../networking/remote_access_vpn.rst:636
+# af1a9268a6da4a45922589c847776234
+# 1ccf3bf911414951aeb77508e82aa992
+# 433faedb39a3413c8ce1f220f5e22560
+msgid "The VPC page is displayed where all the tiers you created are listed in a diagram."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:468
+#: ../../networking/remote_access_vpn.rst:531
+#: ../../networking/remote_access_vpn.rst:663
+# 3152bcd237704f96b4a1b897b801f81b
+# 5a72231d602e4625acd0cbd4b0af4f7e
+# 243047505a8c40e1aadfa9dfbc091f0c
+msgid "Select Site-to-Site VPN."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:470
+# 626b08a7444c4baeb387b316fcf8921d
+msgid "If you are creating the VPN gateway for the first time, selecting Site-to-Site VPN prompts you to create a VPN gateway."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:473
+# c46b3f642ec240738664d6765c1d736f
+msgid "In the confirmation dialog, click Yes to confirm."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:475
+# 6dbf5c6dc5984bc896785e8d81f1fa0d
+msgid "Within a few moments, the VPN gateway is created. You will be prompted to view the details of the VPN gateway you have created. Click Yes to confirm."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:479
+# 62c9ff637a9c46beb4a187d9d333e711
+msgid "The following details are displayed in the VPN Gateway page:"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:481
+#: ../../networking/remote_access_vpn.rst:561
+# 202a6b9a51f3470d89bb84bb2c9579a8
+# 47435eb81ccf40eab149e9b0abb9213e
+msgid "IP Address"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:483
+# 46f2ea07f3744ac381add8029488f5d3
+msgid "Account"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:485
+# bad02846a1ee4160a278abb51303de1f
+msgid "Domain"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:489
+# b0b08d6daddb48409f581811786b76cf
+msgid "Creating a VPN Connection"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:491
+# 596c1d39f0fe47fa8b05ff9b321ae507
+msgid "CloudStack supports creating up to 8 VPN connections."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:499
+# a61e029b8b514adfa93c97620ffff95f
+msgid "All the VPCs that you create for the account are listed in the page."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:507
+#: ../../networking/remote_access_vpn.rst:639
+# 690702b545754083adec40f20d69acb4
+# 614430ff17c8485fae7ddb094273ef06
+msgid "Click the Settings icon."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:533
+#: ../../networking/remote_access_vpn.rst:665
+# 86dbf74b2c6e4f0aab3f252fafd89f2c
+# fab72af09a284fd2800ff51645f071bf
+msgid "The Site-to-Site VPN page is displayed."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:535
+#: ../../networking/remote_access_vpn.rst:667
+# db4dc2719dd6405eb250f62908eef010
+# 207bfc2acd9e434887770513a245873b
+msgid "From the Select View drop-down, ensure that VPN Connection is selected."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:538
+# 950eac49657f4a29a9fba1b973577867
+msgid "Click Create VPN Connection."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:540
+# 916fc10dd39346ada9828e3a2a80ffda
+msgid "The Create VPN Connection dialog is displayed:"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:542
+# 87888fff4a5f4664be5c4c03fc2ecf6a
+msgid "|createvpnconnection.png|"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:544
+# 4b6cc407b8bc4a728fb3328f0ce53f3f
+msgid "Select the desired customer gateway."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:546
+# 6776ab8d9fad4c2d8956d78ff11ab998
+msgid "Select Passive if you want to establish a connection between two VPC virtual routers."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:549
+# 513eee2d7f8745a4b338c8ea142fae05
+msgid "If you want to establish a connection between two VPC virtual routers, select Passive only on one of the VPC virtual routers, which waits for the other VPC virtual router to initiate the connection. Do not select Passive on the VPC virtual router that initiates the connection."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:555
+# dd03407d4f064ec99ea68bb066d2289e
+msgid "Click OK to confirm."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:557
+# d4c274e9cecb44bcad1ba67ed65069e4
+msgid "Within a few moments, the VPN Connection is displayed."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:559
+# 42dd7918225d458f980e458924b262f3
+msgid "The following information on the VPN connection is displayed:"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:563
+# 64fdbdcdfac148dea0883db2615bf0ed
+msgid "Gateway"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:565
+# 8ac547f2f1574131adc8c69d4e3c30ef
+msgid "State"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:567
+# d2a5bd51a6e347e89857750706114fc9
+msgid "IPSec Preshared Key"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:569
+# ccfea0cb9ae34777990aa348b7a9c23f
+msgid "IKE Policy"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:571
+# bc29ecfda06848f78a8cc694b3f6d47b
+msgid "ESP Policy"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:575
+# 57cee5dc2eed4f6a9164c4838ebdc9d6
+msgid "Site-to-Site VPN Connection Between VPC Networks"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:577
+# d8f9f929fafd40e6895122549b022754
+msgid "CloudStack provides you with the ability to establish a site-to-site VPN connection between CloudStack virtual routers. To achieve that, add a passive mode Site-to-Site VPN. With this functionality, users can deploy applications in multiple Availability Zones or VPCs, which can communicate with each other by using a secure Site-to-Site VPN Tunnel."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:583
+# 2fb087843cd04fafa3beba95a3ae2af1
+msgid "This feature is supported on all the hypervisors."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:585
+# 217a4da322cc4f8caa7e04c029779c8b
+msgid "Create two VPCs. For example, VPC A and VPC B."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:587
+# a78d89e3621346c8a11277927e8dc502
+msgid "For more information, see \":ref:`configuring-vpc`\"."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:589
+# 09b752dc4d4e4cd29912fcbe352309fa
+msgid "Create VPN gateways on both the VPCs you created."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:591
+# b9af87b346ef40889104b5a1f40c7702
+msgid "For more information, see `\"Creating a VPN gateway for the VPC\" <#creating-a-vpn-gateway-for-the-vpc>`_."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:594
+# 29d8db01114c458e8d855996c22e0664
+msgid "Create VPN customer gateway for both the VPCs."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:596
+# 1a50b7ef681f4cb48c15d30e08dfd1e7
+msgid "For more information, see `\"Creating and Updating a VPN Customer Gateway\" <#creating-and-updating-a-vpn-customer-gateway>`_."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:599
+# c9013d4ec4c74444a40bf745ae0a5544
+msgid "Enable a VPN connection on VPC A in passive mode."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:601
+# 8fb700491eeb4156a1c7549d81a78346
+msgid "For more information, see `\"Creating a VPN Connection\" <#creating-a-vpn-connection>`_."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:604
+# e8dd1dd51dd34f57ac10161220734be4
+msgid "Ensure that the customer gateway is pointed to VPC B. The VPN connection is shown in the Disconnected state."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:607
+# eca76af9d9304b17982a0bb977a12547
+msgid "Enable a VPN connection on VPC B."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:609
+# 79e9417cc7294b70bd95236d9c2c80ac
+msgid "Ensure that the customer gateway is pointed to VPC A. Because virtual router of VPC A, in this case, is in passive mode and is waiting for the virtual router of VPC B to initiate the connection, VPC B virtual router should not be in passive mode."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:614
+# cf0657024acb43ea8028262bf74a9848
+msgid "The VPN connection is shown in the Disconnected state."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:616
+# 4c18218889914f65b2fe355d4568b407
+msgid "Creating VPN connection on both the VPCs initiates a VPN connection. Wait for few seconds. The default is 30 seconds for both the VPN connections to show the Connected state."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:622
+# 84118e99c0b14f49b14160c3975dad17
+msgid "Restarting and Removing a VPN Connection"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:670
+# 090940869ab44e80b8e9c4ea04fa48ec
+msgid "All the VPN connections you created are displayed."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:672
+# b921e72e9ca74e75b9c515a87f105b9a
+msgid "Select the VPN connection you want to work with."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:674
+# 2387d86e243f469f84a0cee989324610
+msgid "The Details tab is displayed."
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:676
+# 345c5bfe23d84fd09f56e0e34de09e29
+msgid "To remove a VPN connection, click the Delete VPN connection button |remove-vpn.png|"
+msgstr ""
+
+#: ../../networking/remote_access_vpn.rst:679
+# 8d1a3cf378554f51a5702b0710c331f2
+msgid "To restart a VPN connection, click the Reset VPN connection button present in the Details tab. |reset-vpn.png|"
+msgstr ""
+
diff --git a/source/locale/pot/networking/security_groups.pot b/source/locale/pot/networking/security_groups.pot
new file mode 100644
index 0000000..d52a4a3
--- /dev/null
+++ b/source/locale/pot/networking/security_groups.pot
@@ -0,0 +1,265 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/security_groups.rst:18
+# b67087ae536e4b77ac5668f8f3f73ba8
+msgid "Security Groups"
+msgstr ""
+
+#: ../../networking/security_groups.rst:21
+# 1397d3fadf7d45779a890fb7156cf142
+msgid "About Security Groups"
+msgstr ""
+
+#: ../../networking/security_groups.rst:23
+# 965e0935679141b0bc89e0d82dc1cff8
+msgid "Security groups provide a way to isolate traffic to VMs. A security group is a group of VMs that filter their incoming and outgoing traffic according to a set of rules, called ingress and egress rules. These rules filter network traffic according to the IP address that is attempting to communicate with the VM. Security groups are particularly useful in zones that use basic networking, because there is a single guest network for all guest VMs. In advanced zones, security groups are supported only on the KVM hypervisor."
+msgstr ""
+
+#: ../../networking/security_groups.rst:33
+# 7cc1c024596546c4837b5e09cef7f7db
+msgid "In a zone that uses advanced networking, you can instead define multiple guest networks to isolate traffic to VMs."
+msgstr ""
+
+#: ../../networking/security_groups.rst:36
+# bd8429af9a564cd398104231d1bfc2d9
+msgid "Each CloudStack account comes with a default security group that denies all inbound traffic and allows all outbound traffic. The default security group can be modified so that all new VMs inherit some other desired set of rules."
+msgstr ""
+
+#: ../../networking/security_groups.rst:41
+# 3eb3f0e93cf04d8a9c2a967e8ff3a11c
+msgid "Any CloudStack user can set up any number of additional security groups. When a new VM is launched, it is assigned to the default security group unless another user-defined security group is specified. A VM can be a member of any number of security groups. Once a VM is assigned to a security group, it remains in that group for its entire lifetime; you can not move a running VM from one security group to another."
+msgstr ""
+
+#: ../../networking/security_groups.rst:48
+# 1d91c7babdd54f38b62e9e65788a8a7c
+msgid "You can modify a security group by deleting or adding any number of ingress and egress rules. When you do, the new rules apply to all VMs in the group, whether running or stopped."
+msgstr ""
+
+#: ../../networking/security_groups.rst:52
+# f705f2a195b240f49ffc0cbe9aaa253a
+msgid "If no ingress rules are specified, then no traffic will be allowed in, except for responses to any traffic that has been allowed out through an egress rule."
+msgstr ""
+
+#: ../../networking/security_groups.rst:58
+# 7fa1798aea704a55b545171eb64a16bd
+msgid "Adding a Security Group"
+msgstr ""
+
+#: ../../networking/security_groups.rst:60
+# f7cc763899ad4df99b9e927ef37eabb4
+msgid "A user or administrator can define a new security group."
+msgstr ""
+
+#: ../../networking/security_groups.rst:62
+#: ../../networking/security_groups.rst:124
+# a026f1875e7f4cec8447b013bf2d7a78
+# 27e30ee65cbe485bb8e7370a38b75281
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr ""
+
+#: ../../networking/security_groups.rst:64
+# 344ee6a79a674e88a4a61b24b0a01b42
+msgid "In the left navigation, choose Network."
+msgstr ""
+
+#: ../../networking/security_groups.rst:66
+# 07579af87ecd4f1d8bd6e66835cb2958
+msgid "In Select view, choose Security Groups."
+msgstr ""
+
+#: ../../networking/security_groups.rst:68
+# 23507439460f427cb5be523f65e254fb
+msgid "Click Add Security Group."
+msgstr ""
+
+#: ../../networking/security_groups.rst:70
+# a530b7d59d194fb18081a92d396a272a
+msgid "Provide a name and description."
+msgstr ""
+
+#: ../../networking/security_groups.rst:72
+# 237fc184482448589b8a2eb7c3c70e76
+msgid "Click OK."
+msgstr ""
+
+#: ../../networking/security_groups.rst:74
+# 34ea82240e9c456ab55ff2f0d5756566
+msgid "The new security group appears in the Security Groups Details tab."
+msgstr ""
+
+#: ../../networking/security_groups.rst:76
+# df20adfc9c2e43b9b56c6f1119a9d73f
+msgid "To make the security group useful, continue to Adding Ingress and Egress Rules to a Security Group."
+msgstr ""
+
+#: ../../networking/security_groups.rst:81
+# 0a506fc7186b4a0c8a15ae463c4793e1
+msgid "Security Groups in Advanced Zones (KVM Only)"
+msgstr ""
+
+#: ../../networking/security_groups.rst:83
+# b2a6fb8be2384189ae73c2430ce94159
+msgid "CloudStack provides the ability to use security groups to provide isolation between guests on a single shared, zone-wide network in an advanced zone where KVM is the hypervisor. Using security groups in advanced zones rather than multiple VLANs allows a greater range of options for setting up guest isolation in a cloud."
+msgstr ""
+
+#: ../../networking/security_groups.rst:91
+# 180782afad3643f1ba9672b7f6da72b3
+msgid "Limitations"
+msgstr ""
+
+#: ../../networking/security_groups.rst:93
+# 133ba38a19484e2e9122631ab38446fa
+msgid "The following are not supported for this feature:"
+msgstr ""
+
+#: ../../networking/security_groups.rst:95
+# 7c46f4b3ab9f405b8ba2b599ffc1985e
+msgid "Two IP ranges with the same VLAN and different gateway or netmask in security group-enabled shared network."
+msgstr ""
+
+#: ../../networking/security_groups.rst:98
+# 25d83dec92f045bda786a85257b3e1d1
+msgid "Two IP ranges with the same VLAN and different gateway or netmask in account-specific shared networks."
+msgstr ""
+
+#: ../../networking/security_groups.rst:101
+# 529f72b64c464f0cbbe8b287e8258f1a
+msgid "Multiple VLAN ranges in security group-enabled shared network."
+msgstr ""
+
+#: ../../networking/security_groups.rst:103
+# c9ffb5f82e6b45778e4e1b83b29ed310
+msgid "Multiple VLAN ranges in account-specific shared networks."
+msgstr ""
+
+#: ../../networking/security_groups.rst:105
+# 8488c958047d450bb250b38d098bc214
+msgid "Security groups must be enabled in the zone in order for this feature to be used."
+msgstr ""
+
+#: ../../networking/security_groups.rst:110
+# 6c5be222e8184b8ab28d3019648e9990
+msgid "Enabling Security Groups"
+msgstr ""
+
+#: ../../networking/security_groups.rst:112
+# b6b2af559254408ba42336e7fddf32e6
+msgid "In order for security groups to function in a zone, the security groups feature must first be enabled for the zone. The administrator can do this when creating a new zone, by selecting a network offering that includes security groups. The procedure is described in Basic Zone Configuration in the Advanced Installation Guide. The administrator can not enable security groups for an existing zone, only when creating a new zone."
+msgstr ""
+
+#: ../../networking/security_groups.rst:122
+# e09d51e1a259488eab79d1fb28954b59
+msgid "Adding Ingress and Egress Rules to a Security Group"
+msgstr ""
+
+#: ../../networking/security_groups.rst:126
+# b24e5ca705b84ea4a6c0511ef2244936
+msgid "In the left navigation, choose Network"
+msgstr ""
+
+#: ../../networking/security_groups.rst:128
+# e6e52ad277a249ebb052f48c14687e98
+msgid "In Select view, choose Security Groups, then click the security group you want."
+msgstr ""
+
+#: ../../networking/security_groups.rst:131
+# 4563cb9609194e7b8bfe401fa3b6219e
+msgid "To add an ingress rule, click the Ingress Rules tab and fill out the following fields to specify what network traffic is allowed into VM instances in this security group. If no ingress rules are specified, then no traffic will be allowed in, except for responses to any traffic that has been allowed out through an egress rule."
+msgstr ""
+
+#: ../../networking/security_groups.rst:137
+# a4934e5b794b41469ff66677df530f64
+msgid "**Add by CIDR/Account**. Indicate whether the source of the traffic will be defined by IP address (CIDR) or an existing security group in a CloudStack account (Account). Choose Account if you want to allow incoming traffic from all VMs in another security group"
+msgstr ""
+
+#: ../../networking/security_groups.rst:143
+# 38c863d52b6c4f3b900f9268d71a3167
+msgid "**Protocol**. The networking protocol that sources will use to send traffic to the security group. TCP and UDP are typically used for data exchange and end-user communications. ICMP is typically used to send error messages or network monitoring data."
+msgstr ""
+
+#: ../../networking/security_groups.rst:148
+# bcb96d430c8649f483335f10c670e649
+msgid "**Start Port, End Port**. (TCP, UDP only) A range of listening ports that are the destination for the incoming traffic. If you are opening a single port, use the same number in both fields."
+msgstr ""
+
+#: ../../networking/security_groups.rst:152
+# 6c1ac4c3fb7e476a8eba891bbf1fa14e
+msgid "**ICMP Type, ICMP Code**. (ICMP only) The type of message and error code that will be accepted."
+msgstr ""
+
+#: ../../networking/security_groups.rst:155
+# 6d982263975e486e8e1b13fe56a83ed0
+msgid "**CIDR**. (Add by CIDR only) To accept only traffic from IP addresses within a particular address block, enter a CIDR or a comma-separated list of CIDRs. The CIDR is the base IP address of the incoming traffic. For example, 192.168.0.0/22. To allow all CIDRs, set to 0.0.0.0/0."
+msgstr ""
+
+#: ../../networking/security_groups.rst:161
+# 10e7f63d3cf94152a51416bc737199ed
+msgid "**Account, Security Group**. (Add by Account only) To accept only traffic from another security group, enter the CloudStack account and name of a security group that has already been defined in that account. To allow traffic between VMs within the security group you are editing now, enter the same name you used in step 7."
+msgstr ""
+
+#: ../../networking/security_groups.rst:167
+# 9d70746377c24fdb80bdb73145dda1fe
+msgid "The following example allows inbound HTTP access from anywhere:"
+msgstr ""
+
+#: ../../networking/security_groups.rst:169
+# f1fa895a70e745a182f076db946d9d16
+msgid "|httpaccess.png|"
+msgstr ""
+
+#: ../../networking/security_groups.rst:171
+# 25c1f9eee689482ab0a99049e45c6ceb
+msgid "To add an egress rule, click the Egress Rules tab and fill out the following fields to specify what type of traffic is allowed to be sent out of VM instances in this security group. If no egress rules are specified, then all traffic will be allowed out. Once egress rules are specified, the following types of traffic are allowed out: traffic specified in egress rules; queries to DNS and DHCP servers; and responses to any traffic that has been allowed in through an ingress rule"
+msgstr ""
+
+#: ../../networking/security_groups.rst:180
+# 83bfb97418d545549c3ea5c0a17c5985
+msgid "**Add by CIDR/Account**. Indicate whether the destination of the traffic will be defined by IP address (CIDR) or an existing security group in a CloudStack account (Account). Choose Account if you want to allow outgoing traffic to all VMs in another security group."
+msgstr ""
+
+#: ../../networking/security_groups.rst:186
+# f175b78e34494795b301760a7fd5168f
+msgid "**Protocol**. The networking protocol that VMs will use to send outgoing traffic. TCP and UDP are typically used for data exchange and end-user communications. ICMP is typically used to send error messages or network monitoring data."
+msgstr ""
+
+#: ../../networking/security_groups.rst:191
+# 31089018bb9f47e4941651c91b2bd90c
+msgid "**Start Port, End Port**. (TCP, UDP only) A range of listening ports that are the destination for the outgoing traffic. If you are opening a single port, use the same number in both fields."
+msgstr ""
+
+#: ../../networking/security_groups.rst:195
+# 96661f61b9b54d448e5e7be7ba933296
+msgid "**ICMP Type, ICMP Code**. (ICMP only) The type of message and error code that will be sent"
+msgstr ""
+
+#: ../../networking/security_groups.rst:198
+# 7e52dd9e52524ea98f0bcf7ff00116ac
+msgid "**CIDR**. (Add by CIDR only) To send traffic only to IP addresses within a particular address block, enter a CIDR or a comma-separated list of CIDRs. The CIDR is the base IP address of the destination. For example, 192.168.0.0/22. To allow all CIDRs, set to 0.0.0.0/0."
+msgstr ""
+
+#: ../../networking/security_groups.rst:204
+# 40e0b1515ef948adb1a42642f73f490d
+msgid "**Account, Security Group**. (Add by Account only) To allow traffic to be sent to another security group, enter the CloudStack account and name of a security group that has already been defined in that account. To allow traffic between VMs within the security group you are editing now, enter its name."
+msgstr ""
+
+#: ../../networking/security_groups.rst:210
+# 39febf06883a4d248d1ac5ad19510065
+msgid "Click Add."
+msgstr ""
+
diff --git a/source/locale/pot/networking/static_nat.pot b/source/locale/pot/networking/static_nat.pot
new file mode 100644
index 0000000..20773ee
--- /dev/null
+++ b/source/locale/pot/networking/static_nat.pot
@@ -0,0 +1,83 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/static_nat.rst:18
+# 89295dfc645a421eac4401834f1b5564
+msgid "Static NAT"
+msgstr ""
+
+#: ../../networking/static_nat.rst:20
+# c3b2d053fab944578298ac1adf46e76e
+msgid "A static NAT rule maps a public IP address to the private IP address of a VM in order to allow Internet traffic into the VM. The public IP address always remains the same, which is why it is called static NAT. This section tells how to enable or disable static NAT for a particular IP address."
+msgstr ""
+
+#: ../../networking/static_nat.rst:28
+# ffe605639e6844fa8170c65805372b4c
+msgid "Enabling or Disabling Static NAT"
+msgstr ""
+
+#: ../../networking/static_nat.rst:30
+# 311e1bb870dd43bb98cd7ee6a01f42ca
+msgid "If port forwarding rules are already in effect for an IP address, you cannot enable static NAT to that IP."
+msgstr ""
+
+#: ../../networking/static_nat.rst:33
+# b89fc2e081874b24b0ad50ed843837e9
+msgid "If a guest VM is part of more than one network, static NAT rules will function only if they are defined on the default network."
+msgstr ""
+
+#: ../../networking/static_nat.rst:36
+# e6dabe6070464d23926137799673505a
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr ""
+
+#: ../../networking/static_nat.rst:38
+# 726614a43cbf4c448770c40822676059
+msgid "In the left navigation, choose Network."
+msgstr ""
+
+#: ../../networking/static_nat.rst:40
+# 71505d3318714907a3abd5319833b78e
+msgid "Click the name of the network where you want to work with."
+msgstr ""
+
+#: ../../networking/static_nat.rst:42
+# 0898722d18384a89a217a7a8e7cb6fbf
+msgid "Click View IP Addresses."
+msgstr ""
+
+#: ../../networking/static_nat.rst:44
+# 5e916ccbf7c94237b104827f38f2ca6a
+msgid "Click the IP address you want to work with."
+msgstr ""
+
+#: ../../networking/static_nat.rst:46
+# 4f5018aad8f14212a2d0c17d955b197a
+msgid "Click the Static NAT |enabledisablenat.png| button."
+msgstr ""
+
+#: ../../networking/static_nat.rst:48
+# 001cc2e543c345afb265ff300a5435ca
+msgid "The button toggles between Enable and Disable, depending on whether static NAT is currently enabled for the IP address."
+msgstr ""
+
+#: ../../networking/static_nat.rst:51
+# 91178f93f90f4135b40823266a6ecb4e
+msgid "If you are enabling static NAT, a dialog appears where you can choose the destination VM and click Apply."
+msgstr ""
+
diff --git a/source/locale/pot/networking/virtual_private_cloud_config.pot b/source/locale/pot/networking/virtual_private_cloud_config.pot
new file mode 100644
index 0000000..e589c54
--- /dev/null
+++ b/source/locale/pot/networking/virtual_private_cloud_config.pot
@@ -0,0 +1,2019 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 
+# This file is distributed under the same license as the Apache CloudStack Administration Documentation package.
+# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Administration Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-06-30 12:52+0200\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
+"Language-Team: LANGUAGE <LL@li.org>\n"
+"MIME-Version: 1.0\n"
+"Content-Type: text/plain; charset=UTF-8\n"
+"Content-Transfer-Encoding: 8bit\n"
+
+#: ../../networking/virtual_private_cloud_config.rst:20
+# 4425df0b51c64a33802d59f9f7eb5bd8
+msgid "Configuring a Virtual Private Cloud"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:23
+# 60b4e45448554da0a9df907a8e700391
+msgid "About Virtual Private Clouds"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:25
+# 9caa2b864b03431aae6a6f47aa583653
+msgid "CloudStack Virtual Private Cloud is a private, isolated part of CloudStack. A VPC can have its own virtual network topology that resembles a traditional physical network. You can launch VMs in the virtual network that can have private addresses in the range of your choice, for example: 10.0.0.0/16. You can define network tiers within your VPC network range, which in turn enables you to group similar kinds of instances based on IP address range."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:33
+# e8c6a442ed744a6c96df83edc8c28763
+msgid "For example, if a VPC has the private range 10.0.0.0/16, its guest networks can have the network ranges 10.0.1.0/24, 10.0.2.0/24, 10.0.3.0/24, and so on."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:39
+# d7dd703816c14c8ab823fc4ac5ee3c02
+msgid "Major Components of a VPC"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:41
+# c50712e0b85b4e8d8a37c525dc8f77d0
+msgid "A VPC is comprised of the following network components:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:43
+# 7805e308c7f14ae4b5bf6813c742fd84
+msgid "**VPC**: A VPC acts as a container for multiple isolated networks that can communicate with each other via its virtual router."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:46
+# 6837ce595efa433cb0a4eeef3c61bd86
+msgid "**Network Tiers**: Each tier acts as an isolated network with its own VLANs and CIDR list, where you can place groups of resources, such as VMs. The tiers are segmented by means of VLANs. The NIC of each tier acts as its gateway."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:51
+# eaa3327f752e430ba437d3048c8cd517
+msgid "**Virtual Router**: A virtual router is automatically created and started when you create a VPC. The virtual router connect the tiers and direct traffic among the public gateway, the VPN gateways, and the NAT instances. For each tier, a corresponding NIC and IP exist in the virtual router. The virtual router provides DNS and DHCP services through its IP."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:58
+# 2922aef73276424d86c458cab53d05d6
+msgid "**Public Gateway**: The traffic to and from the Internet routed to the VPC through the public gateway. In a VPC, the public gateway is not exposed to the end user; therefore, static routes are not support for the public gateway."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:63
+# 417e8d202f044580b6bef8868a97493b
+msgid "**Private Gateway**: All the traffic to and from a private network routed to the VPC through the private gateway. For more information, see \":ref:`adding-priv-gw-vpc`\"."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:67
+# 4776de29b7b1471084bbdc0a5fd8257d
+msgid "**VPN Gateway**: The VPC side of a VPN connection."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:69
+# 208527258e274b0ea77846c710ba8258
+msgid "**Site-to-Site VPN Connection**: A hardware-based VPN connection between your VPC and your datacenter, home network, or co-location facility. For more information, see \":ref:`setting-s2s-vpn-conn`\"."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:73
+# 3b96c83ddcc34269896e5573992e31b5
+msgid "**Customer Gateway**: The customer side of a VPN Connection. For more information, see `\"Creating and Updating a VPN Customer Gateway\" <#creating-and-updating-a-vpn-customer-gateway>`_."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:77
+# bfadc68d3fbe458bb82d6692306f1319
+msgid "**NAT Instance**: An instance that provides Port Address Translation for instances to access the Internet via the public gateway. For more information, see \":ref:`enabling-disabling-static-nat-on-vpc`\"."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:81
+# aa7430e86dde41ea828ef58fdc9a2616
+msgid "**Network ACL**: Network ACL is a group of Network ACL items. Network ACL items are nothing but numbered rules that are evaluated in order, starting with the lowest numbered rule. These rules determine whether traffic is allowed in or out of any tier associated with the network ACL. For more information, see \":ref:`conf-net-acl`\"."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:89
+# 3248944cfc5a49b7a0c47f7fe13a0385
+msgid "Network Architecture in a VPC"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:91
+# 5f310f0748274a1a9d0a095aec7c9c2b
+msgid "In a VPC, the following four basic options of network architectures are present:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:94
+# 7cb03da5ae0b478690c6ab442164a344
+msgid "VPC with a public gateway only"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:96
+# ea9f2145319e406e957665bb7b53123c
+msgid "VPC with public and private gateways"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:98
+# 2b4f4b4fbf46434c8e5534d0631bca33
+msgid "VPC with public and private gateways and site-to-site VPN access"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:100
+# 45b4489a9fcc4360a6d5b2719a77dc79
+msgid "VPC with a private gateway only and site-to-site VPN access"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:104
+# b702ceb782244642b4369af267ce81d8
+msgid "Connectivity Options for a VPC"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:106
+# 6b1ff95952fe4ccbba871b1f5d84e8d8
+msgid "You can connect your VPC to:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:108
+# 65aa43fb551b4f999e9e48eb5960893d
+msgid "The Internet through the public gateway."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:110
+# 09137011988c4abebde330c2201cbfe4
+msgid "The corporate datacenter by using a site-to-site VPN connection through the VPN gateway."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:113
+# 7a7466064859416c9bf3d5f6fb2828fa
+msgid "Both the Internet and your corporate datacenter by using both the public gateway and a VPN gateway."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:118
+# c4053fc0a35c4c30b312bd50f3cc946e
+msgid "VPC Network Considerations"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:120
+# f884bf37cfa444299fac3dd70425950c
+msgid "Consider the following before you create a VPC:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:122
+# 3d67118ab9e24f4d861c4b78cd07fe86
+msgid "A VPC, by default, is created in the enabled state."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:124
+# 64f62904ffbf4d0998ef58a29ec39785
+msgid "A VPC can be created in Advance zone only, and can't belong to more than one zone at a time."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:127
+# 146628ae783e4af79b8cdd56694e87b3
+msgid "The default number of VPCs an account can create is 20. However, you can change it by using the max.account.vpcs global parameter, which controls the maximum number of VPCs an account is allowed to create."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:131
+# 548f4246178a412ba72c20238355c619
+msgid "The default number of tiers an account can create within a VPC is 3. You can configure this number by using the vpc.max.networks parameter."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:135
+# 8f4ab58bb2db48e7ab28e709ee99c791
+msgid "Each tier should have an unique CIDR in the VPC. Ensure that the tier's CIDR should be within the VPC CIDR range."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:138
+# a3ab5225e8e649a38b583c6dfa85dd0b
+msgid "A tier belongs to only one VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:140
+# cbf79c1dbbb04abeb940ac4a4e63693b
+msgid "All network tiers inside the VPC should belong to the same account."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:142
+# 4697685b3c1c4f75888b23d1f474ad37
+msgid "When a VPC is created, by default, a SourceNAT IP is allocated to it. The Source NAT IP is released only when the VPC is removed."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:145
+# f790d826d90d4341885a39022d276efc
+msgid "A public IP can be used for only one purpose at a time. If the IP is a sourceNAT, it cannot be used for StaticNAT or port forwarding."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:148
+# cccc0c77482c4721a48a8e3eee6370e0
+msgid "The instances can only have a private IP address that you provision. To communicate with the Internet, enable NAT to an instance that you launch in your VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:152
+# b833eb4050c145869c7a419c8f37aee9
+msgid "Only new networks can be added to a VPC. The maximum number of networks per VPC is limited by the value you specify in the vpc.max.networks parameter. The default value is three."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:156
+# 1180f413398548729b7198559dc5eb33
+msgid "The load balancing service can be supported by only one tier inside the VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:159
+# 1d6388d964364caa8d134f7673bfa2dd
+msgid "If an IP address is assigned to a tier:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:161
+# 92d15597ceda4a5383fd25cb566b47c7
+msgid "That IP can't be used by more than one tier at a time in the VPC. For example, if you have tiers A and B, and a public IP1, you can create a port forwarding rule by using the IP either for A or B, but not for both."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:166
+# a92e77fa9415458b960baded020a27ac
+msgid "That IP can't be used for StaticNAT, load balancing, or port forwarding rules for another guest network inside the VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:169
+# e138623610a449e8a6fd5bb3f4a2ab3f
+msgid "Remote access VPN is not supported in VPC networks."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:173
+# 02efff273d294762ad189c6d19730f71
+msgid "Adding a Virtual Private Cloud"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:175
+# d1100a2ab1a54454bece6b2f5a47e4f8
+msgid "When creating the VPC, you simply provide the zone and a set of IP addresses for the VPC network address space. You specify this set of addresses in the form of a Classless Inter-Domain Routing (CIDR) block."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:179
+#: ../../networking/virtual_private_cloud_config.rst:223
+#: ../../networking/virtual_private_cloud_config.rst:331
+#: ../../networking/virtual_private_cloud_config.rst:380
+#: ../../networking/virtual_private_cloud_config.rst:492
+#: ../../networking/virtual_private_cloud_config.rst:662
+#: ../../networking/virtual_private_cloud_config.rst:729
+#: ../../networking/virtual_private_cloud_config.rst:788
+#: ../../networking/virtual_private_cloud_config.rst:848
+#: ../../networking/virtual_private_cloud_config.rst:1014
+#: ../../networking/virtual_private_cloud_config.rst:1227
+#: ../../networking/virtual_private_cloud_config.rst:1282
+#: ../../networking/virtual_private_cloud_config.rst:1360
+#: ../../networking/virtual_private_cloud_config.rst:1388
+# 27c90db3b2d846b58c9abf075735077b
+# 23214314bc4c40d3bc784cf8b99c1273
+# 06da644a106746d9b22320df5442e7eb
+# 8292048a7bd74adeae7e3b6677cc7dc8
+# fb4e97f30b554d92af68a1e9d1886576
+# ceaea70c95b1422597606b789f77fae7
+# c80fe5feb23443ab8e81a05534c38d15
+# 612a8d98561a4b08824d22d8ab9cd815
+# 3d9f5b1f4cf7497ebaa39f40d2b7d3fb
+# 7af40adf2d7f49ee82115cf17558f076
+# 54efcc991da44e5b87cab339063f09cc
+# 98308f9c7c7e4548b3e6ef0828178c9d
+# b16c2e02fd8e42a1aacb687d60b4fb46
+# 1d2a5b77246843818d6d6cc8fd7482ae
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:181
+#: ../../networking/virtual_private_cloud_config.rst:225
+#: ../../networking/virtual_private_cloud_config.rst:333
+#: ../../networking/virtual_private_cloud_config.rst:382
+#: ../../networking/virtual_private_cloud_config.rst:494
+#: ../../networking/virtual_private_cloud_config.rst:664
+#: ../../networking/virtual_private_cloud_config.rst:731
+#: ../../networking/virtual_private_cloud_config.rst:790
+#: ../../networking/virtual_private_cloud_config.rst:850
+#: ../../networking/virtual_private_cloud_config.rst:1016
+#: ../../networking/virtual_private_cloud_config.rst:1229
+#: ../../networking/virtual_private_cloud_config.rst:1284
+#: ../../networking/virtual_private_cloud_config.rst:1362
+#: ../../networking/virtual_private_cloud_config.rst:1390
+# 25aa9d2390434c03a89b6b16c9b69fe9
+# 6e8e81dbb9f447c3aaabac12cbbebc79
+# 7daeed72e5de4f68b5d3fec3deae5a12
+# ad50664f103d4bc3b95d04f0c6891395
+# b462daef366f4f119997d229bdcd4fde
+# cbb8c618e79f4f5bb024ac637c94f155
+# d418a0fbecc7474d89b0c7122cb9f046
+# c1602cd2089a4465bb64a310c84582ae
+# 692a153c672746fa937e636f18024241
+# f2241fbd031643a498b64bc52bc9a3ed
+# 35b9e68484d140e1813335d0a33c68d1
+# bb61fadd006d4624a91bb45665efac73
+# 0cdbc29c89c540c08fa87bd601f4976c
+# 2706338d19fe43d589acd0c274b932c0
+msgid "In the left navigation, choose Network."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:183
+#: ../../networking/virtual_private_cloud_config.rst:227
+#: ../../networking/virtual_private_cloud_config.rst:335
+#: ../../networking/virtual_private_cloud_config.rst:384
+#: ../../networking/virtual_private_cloud_config.rst:496
+#: ../../networking/virtual_private_cloud_config.rst:666
+#: ../../networking/virtual_private_cloud_config.rst:733
+#: ../../networking/virtual_private_cloud_config.rst:792
+#: ../../networking/virtual_private_cloud_config.rst:852
+#: ../../networking/virtual_private_cloud_config.rst:1018
+#: ../../networking/virtual_private_cloud_config.rst:1231
+#: ../../networking/virtual_private_cloud_config.rst:1286
+#: ../../networking/virtual_private_cloud_config.rst:1364
+#: ../../networking/virtual_private_cloud_config.rst:1392
+# 4a2df6815f134b918345eaf3d39193fa
+# a59b8d1dfb334d948ed4ad0764ce5b84
+# 12b0ac2563474462b71654534aba088a
+# 08995e8ef0484b879f2982b11278720c
+# 0913e0292efb41c284ad04d0d8ec0c1d
+# f66916dd15334247bb50483cd9c296b7
+# d34dad2acbce43aa9f28ce7014089f24
+# 50500a3f8df347e19b005d01525ac7e1
+# c538254df2644b7fb6e4aa16f80f84a6
+# 92649f86d20849b498765a29fd1d7973
+# 9528e3d88e224cacb28e4e204ddab6a7
+# 934c19367f124113b2d3d8f8aabab4a6
+# cd85c04d5e0b4e7c901b189b7ab5e96e
+# 2028f717603c4390944c6c6cb703af37
+msgid "In the Select view, select VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:185
+# 03b833a9bbc14d2f8ccd0561f8bac779
+msgid "Click Add VPC. The Add VPC page is displayed as follows:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:187
+# 007c69b8b7c640d2a9dd08b2b4a86102
+msgid "|add-vpc.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:189
+# 7bd4344fc68d4e6c8939286640c64ff6
+msgid "Provide the following information:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:191
+# fecc1622a73f4e299c4fe16149ef3c1e
+msgid "**Name**: A short name for the VPC that you are creating."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:193
+# 9fe964ec13864d159f7f9fe45e612351
+msgid "**Description**: A brief description of the VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:195
+# 75bab09118a641cd94d798e0450bb114
+msgid "**Zone**: Choose the zone where you want the VPC to be available."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:197
+# 38e1b19b64074aebbc448d4398522e6a
+msgid "**Super CIDR for Guest Networks**: Defines the CIDR range for all the tiers (guest networks) within a VPC. When you create a tier, ensure that its CIDR is within the Super CIDR value you enter. The CIDR must be RFC1918 compliant."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:202
+# 2b3cb992f4d9418699ec71ad0d7892b7
+msgid "**DNS domain for Guest Networks**: If you want to assign a special domain name, specify the DNS suffix. This parameter is applied to all the tiers within the VPC. That implies, all the tiers you create in the VPC belong to the same DNS domain. If the parameter is not specified, a DNS domain name is generated automatically."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:208
+# ae282958b5fb4ea594fe92f009ca5f46
+msgid "**Public Load Balancer Provider**: You have two options: VPC Virtual Router and Netscaler."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:211
+#: ../../networking/virtual_private_cloud_config.rst:281
+#: ../../networking/virtual_private_cloud_config.rst:455
+#: ../../networking/virtual_private_cloud_config.rst:479
+# f0a8bdb0febf4b97879a69db489ba8b8
+# a37c6acaf1254a6f818d9f64ae0960aa
+# 677238e0e48a40898578fd007249ecaa
+# 650c882688974599ba5c3660d14f2838
+msgid "Click OK."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:215
+# 83d71b83ff1b413187423073f1a1c957
+msgid "Adding Tiers"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:217
+# 8202063e990e4086bb8c476cfa8f2650
+msgid "Tiers are distinct locations within a VPC that act as isolated networks, which do not have access to other tiers by default. Tiers are set up on different VLANs that can communicate with each other by using a virtual router. Tiers provide inexpensive, low latency network connectivity to other tiers within the VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:229
+#: ../../networking/virtual_private_cloud_config.rst:1366
+# 6f156f2256294f94a48422c02a2a33f1
+# 91fdfd64076446a1af782ea3021c6911
+msgid "All the VPC that you have created for the account is listed in the page."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:233
+# 98e3757975184289b5414253c54bd6c9
+msgid "The end users can see their own VPCs, while root and domain admin can see any VPC they are authorized to see."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:236
+#: ../../networking/virtual_private_cloud_config.rst:1369
+# 3293738bea7a4e3c97fc6b8cd60f65ba
+# 4c89fd343c734f5cabc8cb26dd48bf94
+msgid "Click the Configure button of the VPC for which you want to set up tiers."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:239
+# a3b02bf28e484233b337b84341a2f39e
+msgid "Click Create network."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:241
+# e8b22e1b54b84b1e9945e0c94e3fd069
+msgid "The Add new tier dialog is displayed, as follows:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:243
+# 1f18a2fd76094e94947690c4064b2a75
+msgid "|add-tier.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:245
+# 830f50fe9c8041c9821f1cf9b94f87bd
+msgid "If you have already created tiers, the VPC diagram is displayed. Click Create Tier to add a new tier."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:248
+#: ../../networking/virtual_private_cloud_config.rst:539
+#: ../../networking/virtual_private_cloud_config.rst:1062
+#: ../../networking/virtual_private_cloud_config.rst:1330
+# b372cab6baf04844a5ff7a1611d1d5b6
+# 4bc6b0a5224f4b8383ff3c5322dc34c6
+# 95ebee159c7a49d6a38872dfbba22963
+# 1490eec9177146d0bb7ef70ee1896fb9
+msgid "Specify the following:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:250
+# 07194bca2d77463fb722f6b3a2d51fd6
+msgid "All the fields are mandatory."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:252
+# 26b1c6c9cd4747a0b399711d03ee9f7f
+msgid "**Name**: A unique name for the tier you create."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:254
+# b4b14e979a074d9fbdd39309629f1524
+msgid "**Network Offering**: The following default network offerings are listed: Internal LB, DefaultIsolatedNetworkOfferingForVpcNetworksNoLB, DefaultIsolatedNetworkOfferingForVpcNetworks"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:259
+# 54126af9bcfb4590a766f2324d72f790
+msgid "In a VPC, only one tier can be created by using LB-enabled network offering."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:262
+# 083df7653efc42938c67b7537bbc4bc3
+msgid "**Gateway**: The gateway for the tier you create. Ensure that the gateway is within the Super CIDR range that you specified while creating the VPC, and is not overlapped with the CIDR of any existing tier within the VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:267
+# abb381823abe42c78600368125e95a5a
+msgid "**VLAN**: The VLAN ID for the tier that the root admin creates."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:269
+# e6585788ce994cfba6fa7581d88af8df
+msgid "This option is only visible if the network offering you selected is VLAN-enabled."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:272
+# 383ce12e9bc44d939d3ae386c0ca42aa
+msgid "For more information, see `\"Assigning VLANs to Isolated Networks\" <hosts.html#assigning-vlans-to-isolated-networks>`_."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:275
+# 88877f2edc5f40a9949cf663c7c306a0
+msgid "**Netmask**: The netmask for the tier you create."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:277
+# 25897e33d08b4bedb702059f77e2f09e
+msgid "For example, if the VPC CIDR is 10.0.0.0/16 and the network tier CIDR is 10.0.1.0/24, the gateway of the tier is 10.0.1.1, and the netmask of the tier is 255.255.255.0."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:283
+# 6da01b412d664e3baa5324abd03955b7
+msgid "Continue with configuring access control list for the tier."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:289
+# dc2a5ea9afaf4bb8b1d188b3cadc5fb2
+msgid "Configuring Network Access Control List"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:291
+# 79dbace67e0b4872ba1da3458f8ccb16
+msgid "Define Network Access Control List (ACL) on the VPC virtual router to control incoming (ingress) and outgoing (egress) traffic between the VPC tiers, and the tiers and Internet. By default, all incoming traffic to the guest networks is blocked and all outgoing traffic from guest networks is allowed, once you add an ACL rule for outgoing traffic, then only outgoing traffic specified in this ACL rule is allowed, the rest is blocked. To open the ports, you must create a new network ACL. The network ACLs can be created for the tiers only if the NetworkACL service is supported."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:303
+# c9d908950964474eb10940d7ba15e7ba
+msgid "About Network ACL Lists"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:305
+# c28b7fe0e1f04f65ad1968b74ca91f03
+msgid "In CloudStack terminology, Network ACL is a group of Network ACL items. Network ACL items are nothing but numbered rules that are evaluated in order, starting with the lowest numbered rule. These rules determine whether traffic is allowed in or out of any tier associated with the network ACL. You need to add the Network ACL items to the Network ACL, then associate the Network ACL with a tier. Network ACL is associated with a VPC and can be assigned to multiple VPC tiers within a VPC. A Tier is associated with a Network ACL at all the times. Each tier can be associated with only one ACL."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:315
+# e213818eed1947258f8bcb2896c4b24a
+msgid "The default Network ACL is used when no ACL is associated. Default behavior is all the incoming traffic is blocked and outgoing traffic is allowed from the tiers. Default network ACL cannot be removed or modified. Contents of the default Network ACL is:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:321
+# e7163daf40764297bb4c9256f9b0db76
+msgid "Rule"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:321
+# 8c0f119efb90499885ad10d74e32f699
+msgid "Protocol"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:321
+# 6a4e95a5005949559075e58b104e8b1e
+msgid "Traffic type"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:321
+# db7f138ccd254efda3045d28c44e5ebd
+msgid "Action"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:321
+#: ../../networking/virtual_private_cloud_config.rst:352
+#: ../../networking/virtual_private_cloud_config.rst:519
+#: ../../networking/virtual_private_cloud_config.rst:754
+#: ../../networking/virtual_private_cloud_config.rst:812
+#: ../../networking/virtual_private_cloud_config.rst:873
+#: ../../networking/virtual_private_cloud_config.rst:1039
+#: ../../networking/virtual_private_cloud_config.rst:1307
+# 51c0d62f36c143a5baf332fb86f16b96
+# d597d570fbfc4080b2ea3998fa7d939e
+# eff385663f0941d4b6809c0c182cfaf2
+# 2599fa667bce44d7b2c977f4d835a98e
+# bc9aa77c4f984714a6cead0bf43281ad
+# a2e2cc9d31f448ecab07fc456663f5bd
+# d849de055dcd46a29493cd6942aa2cae
+# 7d80106d48c4421190d8c55e7ddd2f90
+msgid "CIDR"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:323
+# fc484eb64ca04d1b8fed82414583e90a
+msgid "1"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:323
+#: ../../networking/virtual_private_cloud_config.rst:324
+# c40bf7c2103d4006b064570d67b6b324
+# 8f113663532445cbb46226109e68fc87
+msgid "All"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:323
+# cd3fb0b3957f47a7b32acd1b403d5f55
+msgid "Ingress"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:323
+#: ../../networking/virtual_private_cloud_config.rst:324
+# e166cc8cfc04481391575caea5841312
+# d259eeaee8994ad79d0143e92a5fe39a
+msgid "Deny"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:323
+#: ../../networking/virtual_private_cloud_config.rst:324
+# acedcca878414c89b67e3f7e98d67e02
+# c2f3ea9812544c20a6fc02ac9aad34f0
+msgid "0.0.0.0/0"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:324
+# dd6e16cde8494347a2e77ca176fd8a0c
+msgid "2"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:324
+# 23726ba83ae748468e32ef14a54d573b
+msgid "Egress"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:329
+# 464f3ed7f4f24169b73210972956651a
+msgid "Creating ACL Lists"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:337
+#: ../../networking/virtual_private_cloud_config.rst:386
+#: ../../networking/virtual_private_cloud_config.rst:498
+#: ../../networking/virtual_private_cloud_config.rst:668
+#: ../../networking/virtual_private_cloud_config.rst:735
+#: ../../networking/virtual_private_cloud_config.rst:794
+#: ../../networking/virtual_private_cloud_config.rst:854
+#: ../../networking/virtual_private_cloud_config.rst:1020
+#: ../../networking/virtual_private_cloud_config.rst:1233
+#: ../../networking/virtual_private_cloud_config.rst:1288
+#: ../../networking/virtual_private_cloud_config.rst:1394
+# b4c82d1c9112484d92153e98ab6a2d33
+# 473281bb899a4393b7cf08840e8c8fde
+# 96a686680e5647d1b47c4067236c664f
+# a790843b311f4f1a9cd8d8d1ee5257a0
+# 4b114128189141c284315e2473ddc438
+# eee54cf82c9f4083b3ad53bb800a3bb4
+# 5c27b5d189844a82a379bc064c2b337e
+# 24808f02d0764c739d4aad58f9e15037
+# 1b11a2ac4b0e47ee9fc8a3f367edea68
+# 100ab8e1140f431bb36c49295576da40
+# 3ed6090af9fa4e238cf801269c4c072d
+msgid "All the VPCs that you have created for the account is listed in the page."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:340
+#: ../../networking/virtual_private_cloud_config.rst:389
+# 6aa87599a443418889e9db15cc500f7d
+# 0bb74bee4b2d4d6da70d6240c47afe8f
+msgid "Click the Configure button of the VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:342
+#: ../../networking/virtual_private_cloud_config.rst:1029
+#: ../../networking/virtual_private_cloud_config.rst:1297
+# a7a5868fc1c545d8b40456b1836b9ddc
+# 62d64d7c737248d3b49d2cfcf91ab9ea
+# a7576a24a2874ab89a29f6d0b1528bac
+msgid "For each tier, the following options are displayed:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:344
+#: ../../networking/virtual_private_cloud_config.rst:511
+#: ../../networking/virtual_private_cloud_config.rst:746
+#: ../../networking/virtual_private_cloud_config.rst:804
+#: ../../networking/virtual_private_cloud_config.rst:865
+#: ../../networking/virtual_private_cloud_config.rst:1031
+#: ../../networking/virtual_private_cloud_config.rst:1299
+# c84c70798b73443ba7f00b174398ed30
+# 2b1209152c06414c809dd9cbe8e873f6
+# 2d40227490424cf0b08f531835947150
+# 5d234a982f1c449bb04697d7e629b3d7
+# b35cbc7845ed400cb02bd71b07eac64e
+# 68ca9e9b2011446da7adcef0d83d05ee
+# edde5a9896f94691829221191ccf24ca
+msgid "Internal LB"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:346
+#: ../../networking/virtual_private_cloud_config.rst:513
+#: ../../networking/virtual_private_cloud_config.rst:748
+#: ../../networking/virtual_private_cloud_config.rst:806
+#: ../../networking/virtual_private_cloud_config.rst:867
+#: ../../networking/virtual_private_cloud_config.rst:1033
+#: ../../networking/virtual_private_cloud_config.rst:1301
+# 840747d13a8548c3a1ed1cfa7aec94d8
+# 2cebf679ea3c44cea4495a0da3fdede4
+# 171baf1d98124ad5a9e0e93348d43959
+# 60793fb25c274674a39f4d6ca1d6f5e8
+# cdafdf21344242e391e50189def8e3f7
+# 22aed14946de415e844a06a396d14413
+# d215b78e0acd4886aaae10e01da3539a
+msgid "Public LB IP"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:348
+#: ../../networking/virtual_private_cloud_config.rst:515
+#: ../../networking/virtual_private_cloud_config.rst:750
+#: ../../networking/virtual_private_cloud_config.rst:808
+#: ../../networking/virtual_private_cloud_config.rst:869
+#: ../../networking/virtual_private_cloud_config.rst:1035
+#: ../../networking/virtual_private_cloud_config.rst:1303
+# 503c7c6831eb4f5ca96c64c2b8328442
+# b565e6a4cff8412f9d1c9032ea24e848
+# 749694902cf440fea4b8315f93dddf91
+# 0b5fb5da84014d7680951915cb26b0a8
+# f8fa3d05ec454df1abf7f6a5079c965b
+# 43f4ab42a09a499783f95aba183bd8a7
+# 88e9603df37e4eacb36619474a076744
+msgid "Static NAT"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:350
+#: ../../networking/virtual_private_cloud_config.rst:517
+#: ../../networking/virtual_private_cloud_config.rst:752
+#: ../../networking/virtual_private_cloud_config.rst:810
+#: ../../networking/virtual_private_cloud_config.rst:871
+#: ../../networking/virtual_private_cloud_config.rst:1037
+#: ../../networking/virtual_private_cloud_config.rst:1305
+# c7d592104fa6447da1b9471822e82ec8
+# 714747328af148798be74203cc3ea72e
+# 86f01795bd5c488fb9cbffd13a3b84a0
+# 1a4d0e4cefc648188e4e0d1e3f5f813f
+# 7df65f6c728842c680faa985c0d2b934
+# 0caa2b61a0d14a3893de13c06290cb7a
+# 8adba6b367094ad4bd769cc0a7ae13a8
+msgid "Virtual Machines"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:354
+#: ../../networking/virtual_private_cloud_config.rst:521
+#: ../../networking/virtual_private_cloud_config.rst:756
+#: ../../networking/virtual_private_cloud_config.rst:814
+#: ../../networking/virtual_private_cloud_config.rst:875
+#: ../../networking/virtual_private_cloud_config.rst:1041
+#: ../../networking/virtual_private_cloud_config.rst:1309
+# 2e579cf3f90345feb4b8edc18f78fd8d
+# 600d551d0f114e47a420f1c86cd445f4
+# 485eb313498a44e2ab1906012a044734
+# 92f01bcc2bcd45919753fcbc87f143c3
+# e6be963a127340ba88d4e76482c44368
+# e48b3a02fdbf4c1aab3e5704df727b54
+# 0a61a781736c436c9379e115fd3df3cb
+msgid "The following router information is displayed:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:356
+#: ../../networking/virtual_private_cloud_config.rst:523
+#: ../../networking/virtual_private_cloud_config.rst:758
+#: ../../networking/virtual_private_cloud_config.rst:816
+#: ../../networking/virtual_private_cloud_config.rst:877
+#: ../../networking/virtual_private_cloud_config.rst:1043
+#: ../../networking/virtual_private_cloud_config.rst:1311
+# 4ed3754e8e014af2a5af0fb4036eeef2
+# 3d5c5cdec63d4e90aee5f9c884e80a5d
+# dcf31b093d01445ebfad5a3769f1a716
+# 4e06d785ce264f838a57f818a5eb51de
+# 33fd1f6f2fe94fbb8fcebb54432f6db5
+# 920576fcde1e43f5a7d673e3fc8c3961
+# 8d9aac57476145b98417e24b78edbee1
+msgid "Private Gateways"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:358
+#: ../../networking/virtual_private_cloud_config.rst:525
+#: ../../networking/virtual_private_cloud_config.rst:760
+#: ../../networking/virtual_private_cloud_config.rst:818
+#: ../../networking/virtual_private_cloud_config.rst:879
+#: ../../networking/virtual_private_cloud_config.rst:1045
+#: ../../networking/virtual_private_cloud_config.rst:1313
+# 0f79101b541d4297ad26fb3125843df6
+# 4e977612c45648cd8858b2f415c8d338
+# 764c6f4d2f214c1f9d33d36fec4bc931
+# 9ed4d3258aec4c01a9d1d7ab9ee6584a
+# 6210247a7c834558b9caf3e695d10eeb
+# b44f415f26cd49dcb58c424bce136a67
+# db0357d3ac9a479698e479d686e8cd9c
+msgid "Public IP Addresses"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:360
+#: ../../networking/virtual_private_cloud_config.rst:527
+#: ../../networking/virtual_private_cloud_config.rst:762
+#: ../../networking/virtual_private_cloud_config.rst:820
+#: ../../networking/virtual_private_cloud_config.rst:881
+#: ../../networking/virtual_private_cloud_config.rst:1047
+#: ../../networking/virtual_private_cloud_config.rst:1315
+# 70abe760545c42d0a794c6ce16a6c288
+# 0c346db4251b43b3a80a084bfd310d80
+# e6e45a6bac434db8b588e5a74c0902b8
+# d682a97cc5f14a0e801c4858edf11f48
+# 29fa45fc941945f891cbf96f6478db82
+# 941bc49890ae411aa05236d0e5102149
+# 3800a9e49a3b4745b17c1769febf9383
+msgid "Site-to-Site VPNs"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:362
+#: ../../networking/virtual_private_cloud_config.rst:529
+#: ../../networking/virtual_private_cloud_config.rst:764
+#: ../../networking/virtual_private_cloud_config.rst:822
+#: ../../networking/virtual_private_cloud_config.rst:883
+#: ../../networking/virtual_private_cloud_config.rst:1049
+#: ../../networking/virtual_private_cloud_config.rst:1317
+# ba528c5024fa489689b4d8ce0c1a0d85
+# 9b993afc4ad845f081de9838ee06ba00
+# 64ec433ac68146178442d14772e8ef45
+# 5a1b96032f234dbc85b6c87e45c31b31
+# c6f194d9a94a415a914fccd54dd4cffa
+# 1148599659df40fc8189b9aaf51587de
+# 5ae9778ec74a46dca0c4191ae03ecbb0
+msgid "Network ACL Lists"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:364
+#: ../../networking/virtual_private_cloud_config.rst:391
+# a3498a3bc728411aa4d5a7313f8d1fca
+# 1fd8c162a2124419bfff5003f1d58fe3
+msgid "Select Network ACL Lists."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:366
+# 9a1064fed3e342afb4b08a5d9e4ba3f9
+msgid "The following default rules are displayed in the Network ACLs page: default\\_allow, default\\_deny."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:369
+# eee1fde55c454e4ba76e51f7c0073681
+msgid "Click Add ACL Lists, and specify the following:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:371
+# 0019e51fcb5d4b609e3dfc8a2f798182
+msgid "**ACL List Name**: A name for the ACL list."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:373
+# 545d7afa82d944fc932e088624630881
+msgid "**Description**: A short description of the ACL list that can be displayed to users."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:378
+# 0eef9c80eb244e469737b6dbfed09ee5
+msgid "Creating an ACL Rule"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:393
+# 9ec1bad501f2492c875359dee57af36c
+msgid "In addition to the custom ACL lists you have created, the following default rules are displayed in the Network ACLs page: default\\_allow, default\\_deny."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:397
+#: ../../networking/virtual_private_cloud_config.rst:477
+# 56fa96725745426090705b3dea696c75
+# a5a846532a7f4d51b3b4ad850b809ffc
+msgid "Select the desired ACL list."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:399
+# 9b8b87a05d164a1e9388a9e96455c916
+msgid "Select the ACL List Rules tab."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:401
+# a35e39faa5504d4a939aa4cbc70ebd47
+msgid "To add an ACL rule, fill in the following fields to specify what kind of network traffic is allowed in the VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:404
+# 09875f1f997e40c78467e4afbfd008a0
+msgid "**Rule Number**: The order in which the rules are evaluated."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:406
+# 718a86130cf84374b39ef695d7c0319f
+msgid "**CIDR**: The CIDR acts as the Source CIDR for the Ingress rules, and Destination CIDR for the Egress rules. To accept traffic only from or to the IP addresses within a particular address block, enter a CIDR or a comma-separated list of CIDRs. The CIDR is the base IP address of the incoming traffic. For example, 192.168.0.0/22. To allow all CIDRs, set to 0.0.0.0/0."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:413
+# 5e7871dde2bc4878b9630e4f89ef78a5
+msgid "**Action**: What action to be taken. Allow traffic or block."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:415
+# 960f6ba511804daf84bb14b0ee7d9fcb
+msgid "**Protocol**: The networking protocol that sources use to send traffic to the tier. The TCP and UDP protocols are typically used for data exchange and end-user communications. The ICMP protocol is typically used to send error messages or network monitoring data. All supports all the traffic. Other option is Protocol Number."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:422
+# f8c920b2724240f7bcce7a3ffa539142
+msgid "**Start Port**, **End Port** (TCP, UDP only): A range of listening ports that are the destination for the incoming traffic. If you are opening a single port, use the same number in both fields."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:426
+# 6354d433a9d14d5aac441bc824aa18d8
+msgid "**Protocol Number**: The protocol number associated with IPv4 or IPv6. For more information, see `Protocol Numbers <http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xml>`_."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:430
+# 07c3ccfb6e804b7b9f9c6ee3e97baab6
+msgid "**ICMP Type**, **ICMP Code** (ICMP only): The type of message and error code that will be sent."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:433
+# fcf4685a451c434fa979261a9f4a989a
+msgid "**Traffic Type**: The type of traffic: Incoming or outgoing."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:435
+# 4cb2859d5c494c07a39e4f7f9c8b316d
+msgid "Click Add. The ACL rule is added."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:437
+# 6a1dc858d8f64fc4b59744f3ce271735
+msgid "You can edit the tags assigned to the ACL rules and delete the ACL rules you have created. Click the appropriate button in the Details tab."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:443
+# f116157c2cc3452d9381d88f34e5edcc
+msgid "Creating a Tier with Custom ACL List"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:445
+#: ../../networking/virtual_private_cloud_config.rst:461
+# a6dcc18dbcf14658bbe49913ec9d7258
+# a9d8c9ab4785456fa3b539a958e0a391
+msgid "Create a VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:447
+#: ../../networking/virtual_private_cloud_config.rst:467
+# c46ed610d0de4aabb7a66be1bc38b59c
+# 0eba50fd6c8241ce8c46b4f22adac8ce
+msgid "Create a custom ACL list."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:449
+#: ../../networking/virtual_private_cloud_config.rst:469
+# d641158411d6429aa58b99856ae3aa3e
+# ee2e3bb2bdcf4ae6ac56d960eb5c8414
+msgid "Add ACL rules to the ACL list."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:451
+#: ../../networking/virtual_private_cloud_config.rst:463
+# 1b9144de1d7c42478e9bcc5e58e8ad8b
+# 6416990ed47a46299ea5a399d45a25e5
+msgid "Create a tier in the VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:453
+# d7313c7f5dc741be9cab74d4cc465987
+msgid "Select the desired ACL list while creating a tier."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:459
+# a2518e7f8c9347b1b2c5d2a4575170df
+msgid "Assigning a Custom ACL List to a Tier"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:465
+# 67c4657175a040149f04332d949d57bf
+msgid "Associate the tier with the default ACL rule."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:471
+# b83eff10b1ce44d2bcfae9e1e8920b6f
+msgid "Select the tier for which you want to assign the custom ACL."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:473
+# a44330dc8018442bb213f335afaab969
+msgid "Click the Replace ACL List icon. |replace-acl-icon.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:475
+# dd9f88e9651f45199d45d102228e2574
+msgid "The Replace ACL List dialog is displayed."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:485
+# 51a9c7e87c8c46bc8c2d01f1c70b1b5e
+msgid "Adding a Private Gateway to a VPC"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:487
+# 5bb03fe2db6344479a16781735c33d36
+msgid "A private gateway can be added by the root admin only. The VPC private network has 1:1 relationship with the NIC of the physical network. You can configure multiple private gateways to a single VPC. No gateways with duplicated VLAN and IP are allowed in the same data center."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:501
+# 56d5e3ac03e0437e95ee0073c44b19dd
+msgid "Click the Configure button of the VPC to which you want to configure load balancing rules."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:504
+#: ../../networking/virtual_private_cloud_config.rst:741
+#: ../../networking/virtual_private_cloud_config.rst:799
+#: ../../networking/virtual_private_cloud_config.rst:860
+#: ../../networking/virtual_private_cloud_config.rst:1294
+# 142dc427cda8454c943c18bb8066cbea
+# 508dbf4fb717460bbb35c009061f7564
+# fb95c3660854480db28704507ed4b900
+# 21eb0af33be64ade85d894838188a330
+# 75579da7cb264f9b80565e8bc7ef99b4
+msgid "The VPC page is displayed where all the tiers you created are listed in a diagram."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:507
+# 57a669215b0c459babdfa0f7477512bb
+msgid "Click the Settings icon."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:509
+#: ../../networking/virtual_private_cloud_config.rst:744
+#: ../../networking/virtual_private_cloud_config.rst:802
+# 27df09e575754d0bb04ff268ac13cd85
+# aec57c8f590a41ea9f3c4002d2bb2082
+# c83fad1cd6a74d3ba7da7551441402ad
+msgid "The following options are displayed."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:531
+# c22be90142b04c5483ec525bb576d2c3
+msgid "Select Private Gateways."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:533
+# 2902accc6b5b49a1b204fd3fd16b1f5e
+msgid "The Gateways page is displayed."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:535
+# 92c2f2f09846411594265950bf78b9e4
+msgid "Click Add new gateway:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:537
+# 2c2c653d4d9d4521b4a7eb5c0e19f64c
+msgid "|add-new-gateway-vpc.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:541
+# 891ea4ddb15443e5ab8f32c8088c452f
+msgid "**Physical Network**: The physical network you have created in the zone."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:544
+# ca06b3e4deaf4ce3a02322454f78ed68
+msgid "**IP Address**: The IP address associated with the VPC gateway."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:546
+# a5410ac8843e4c719973edf2d9bab4e0
+msgid "**Gateway**: The gateway through which the traffic is routed to and from the VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:549
+# 955c1cc8e0f847408e1bd7754afbe13b
+msgid "**Netmask**: The netmask associated with the VPC gateway."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:551
+# 852f638bb7234dc1a27dc43b5e016322
+msgid "**VLAN**: The VLAN associated with the VPC gateway."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:553
+# 6f6c910aeb6d4ee29cfd16a8f169801a
+msgid "**Source NAT**: Select this option to enable the source NAT service on the VPC private gateway."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:556
+# ca50f58a899f498d80e5d3cfaddc4e56
+msgid "See \":ref:`source-nat-priv-gw`\"."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:558
+# 4004b1c124dc41d7afca981bfc6aa29d
+msgid "**ACL**: Controls both ingress and egress traffic on a VPC private gateway. By default, all the traffic is blocked."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:561
+# e0641473896e4fc4abe0e8d8f6500ad5
+msgid "See \":ref:`acl-priv-gw`\"."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:563
+# c748dfb7b8764ed2b63524e27be99156
+msgid "The new gateway appears in the list. You can repeat these steps to add more gateway for this VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:570
+# 67cc2c7079b445b1aa5c3f8d7b0ff2bf
+msgid "Source NAT on Private Gateway"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:572
+# 2a8f60c14ac64d6e8d87dbce76bedb16
+msgid "You might want to deploy multiple VPCs with the same super CIDR and guest tier CIDR. Therefore, multiple guest VMs from different VPCs can have the same IPs to reach a enterprise data center through the private gateway. In such cases, a NAT service need to be configured on the private gateway to avoid IP conflicts. If Source NAT is enabled, the guest VMs in VPC reaches the enterprise network via private gateway IP address by using the NAT service."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:580
+# 13ba311a60ee4d00b7c597fafb945d0b
+msgid "The Source NAT service on a private gateway can be enabled while adding the private gateway. On deletion of a private gateway, source NAT rules specific to the private gateway are deleted."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:584
+# d8e4c7cc999e4730ad5bf6aa6f1b810f
+msgid "To enable source NAT on existing private gateways, delete them and create afresh with source NAT."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:591
+# 8c1553f72c3d4599892c402b65672931
+msgid "ACL on Private Gateway"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:593
+# 7a5729fff5c74521a2455b4e2b885a0f
+msgid "The traffic on the VPC private gateway is controlled by creating both ingress and egress network ACL rules. The ACLs contains both allow and deny rules. As per the rule, all the ingress traffic to the private gateway interface and all the egress traffic out from the private gateway interface are blocked."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:599
+# a7c844a5b9594a8c9090ef0fb4c815ac
+msgid "You can change this default behaviour while creating a private gateway. Alternatively, you can do the following:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:602
+#: ../../networking/virtual_private_cloud_config.rst:633
+# ce82be93f3014dafa0618abed1ddbc56
+# cf4dffd32e4045a0809d358aa5c89b4e
+msgid "In a VPC, identify the Private Gateway you want to work with."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:604
+# d931e9176936499f8a82583a1141f759
+msgid "In the Private Gateway page, do either of the following:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:606
+# df22ccb2fc4a4d4cbc59a8eced7cdd99
+msgid "Use the Quickview. See 3."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:608
+# 2e88948ffe35436398eb3dcc24a068a1
+msgid "Use the Details tab. See 4 through ."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:610
+# a6b863b1326a484080f38c0d2fffe32e
+msgid "In the Quickview of the selected Private Gateway, click Replace ACL, select the ACL rule, then click OK"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:613
+# 393090f44f4e449480ae7b9cd7171e2e
+msgid "Click the IP address of the Private Gateway you want to work with."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:615
+# 175a8bc977814206b1b438e55d487d9d
+msgid "In the Detail tab, click the Replace ACL button. |replace-acl-icon.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:618
+# cb57cf7f56bd4ab7b815980fd401d492
+msgid "The Replace ACL dialog is displayed."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:620
+# 52fd814724fc4614a6513bc716822b2e
+msgid "select the ACL rule, then click OK."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:622
+# 0594c5c95e77436b9fba83680438d29f
+msgid "Wait for few seconds. You can see that the new ACL rule is displayed in the Details page."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:627
+# ab277710c8d843ae81e757e3336317d0
+msgid "Creating a Static Route"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:629
+# 941e24b2fbef4bb7a3938f2fc6fb31ba
+msgid "CloudStack enables you to specify routing for the VPN connection you create. You can enter one or CIDR addresses to indicate which traffic is to be routed back to the gateway."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:635
+# 6a994cb0af754d01bd335367a6f9d4f9
+msgid "In the Private Gateway page, click the IP address of the Private Gateway you want to work with."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:638
+# ed8760a26f62434da30f3b3d3094da23
+msgid "Select the Static Routes tab."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:640
+# dc6e78e20d8a49b18b1c7b68fc53d28f
+msgid "Specify the CIDR of destination network."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:642
+# a267ec664f35442db0c8d33d273ec07a
+msgid "Click Add."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:644
+# 0b06e4ce11114d68a1d616162a29b46b
+msgid "Wait for few seconds until the new route is created."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:648
+# f66d2b908d63453ba9331658c3105974
+msgid "Blacklisting Routes"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:650
+# 5e262d8f57f94df080de1ebfd57089c5
+msgid "CloudStack enables you to block a list of routes so that they are not assigned to any of the VPC private gateways. Specify the list of routes that you want to blacklist in the ``blacklisted.routes`` global parameter. Note that the parameter update affects only new static route creations. If you block an existing static route, it remains intact and continue functioning. You cannot add a static route if the route is blacklisted for the zone."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:660
+# c95c27354e2b4308b6fe6cd594b07c4b
+msgid "Deploying VMs to the Tier"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:671
+#: ../../networking/virtual_private_cloud_config.rst:738
+#: ../../networking/virtual_private_cloud_config.rst:857
+#: ../../networking/virtual_private_cloud_config.rst:1291
+# d912fb084257494b9ea49a22d2952df6
+# 6a271ec843964a2392c14ea15bebcab2
+# 2db0b4a30faa4d2486de8987dc035b35
+# 42de70c0e3314b3b9312103ccf0318a3
+msgid "Click the Configure button of the VPC to which you want to deploy the VMs."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:674
+# a10f32d36f52426288a9a524c7034bde
+msgid "The VPC page is displayed where all the tiers you have created are listed."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:677
+# e8a7f18c2c2443b8afb0ba68b10df211
+msgid "Click Virtual Machines tab of the tier to which you want to add a VM."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:679
+# 2021d183ee7640019cdf5bdbfe5498f3
+msgid "|add-vm-vpc.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:681
+# 2d48018b840946fd8af8d726d139f5d0
+msgid "The Add Instance page is displayed."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:683
+# 3090bc6cae14453a973abac600b9c2cf
+msgid "Follow the on-screen instruction to add an instance. For information on adding an instance, see the Installation Guide."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:688
+# dcd8e45c721b400eaba7cde1328bdc81
+msgid "Deploying VMs to VPC Tier and Shared Networks"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:690
+# 17212685c197411da69afebe1fd43553
+msgid "CloudStack allows you deploy VMs on a VPC tier and one or more shared networks. With this feature, VMs deployed in a multi-tier application can receive monitoring services via a shared network provided by a service provider."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:695
+# fc5a14ca00a74032a5a578f32fe13799
+msgid "Log in to the CloudStack UI as an administrator."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:697
+# 32b36a6c72fa45f99cc16fe65842edb4
+msgid "In the left navigation, choose Instances."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:699
+# 2f251266e8f84c3bb1eb88f9cbf3421b
+msgid "Click Add Instance."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:701
+# e9423e60b1d047809ea35f96287dc4cb
+msgid "Select a zone."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:703
+# 270e50111a9d4c328ccfd3e302a1712c
+msgid "Select a template or ISO, then follow the steps in the wizard."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:705
+# b9f9249e068d492a89e876e8d5282100
+msgid "Ensure that the hardware you have allows starting the selected service offering."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:708
+# 646cca07fc3241d9bdcb00578a77e3e3
+msgid "Under Networks, select the desired networks for the VM you are launching."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:711
+# c5f162c06a0641cf8ca1c4ee6f54f651
+msgid "You can deploy a VM to a VPC tier and multiple shared networks."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:713
+# edcfad81a1b04c068848242fac9adfac
+msgid "|addvm-tier-sharednw.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:715
+# efc4e3cc0b2843ccb58ccc673b8f20cd
+msgid "Click Next, review the configuration and click Launch."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:717
+# 34b1022eb48b4dbf92712eb65b1308c8
+msgid "Your VM will be deployed to the selected VPC tier and shared network."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:721
+# e75183b01c2e4d9a87561e256f60760d
+msgid "Acquiring a New IP Address for a VPC"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:723
+# 8712a3a4537f4038a9703ae12a15da40
+msgid "When you acquire an IP address, all IP addresses are allocated to VPC, not to the guest networks within the VPC. The IPs are associated to the guest network only when the first port-forwarding, load balancing, or Static NAT rule is created for the IP or the network. IP can't be associated to more than one network at a time."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:766
+# f3548df663fd4502b857204d85782486
+msgid "Select IP Addresses."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:768
+# 8b29cfd1cdcd4018ae63dfe1624f5e58
+msgid "The Public IP Addresses page is displayed."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:770
+# b571bcf25fd64067a9bc6c684f923ef4
+msgid "Click Acquire New IP, and click Yes in the confirmation dialog."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:772
+# 5bc9804e2b3a444c9eca95b480c5247e
+msgid "You are prompted for confirmation because, typically, IP addresses are a limited resource. Within a few moments, the new IP address should appear with the state Allocated. You can now use the IP address in port forwarding, load balancing, and static NAT rules."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:779
+# f14eea7624044595966630cad5fb25a4
+msgid "Releasing an IP Address Alloted to a VPC"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:781
+# a32c2ee15c7f41209d11d1460881df99
+msgid "The IP address is a limited resource. If you no longer need a particular IP, you can disassociate it from its VPC and return it to the pool of available addresses. An IP address can be released from its tier, only when all the networking ( port forwarding, load balancing, or StaticNAT ) rules are removed for this IP address. The released IP address will still belongs to the same VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:797
+# cff29ec3366646748c80c78ae0b21df3
+msgid "Click the Configure button of the VPC whose IP you want to release."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:824
+# e61ac663ca83460e902eb75be8323c7b
+msgid "Select Public IP Addresses."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:826
+#: ../../networking/virtual_private_cloud_config.rst:887
+#: ../../networking/virtual_private_cloud_config.rst:1053
+#: ../../networking/virtual_private_cloud_config.rst:1321
+# d6214f88ed8e46abb807a2b8e2f87bf7
+# fee8b392a6654e98b2a92ed46a6a1d09
+# 86b1ba91303847249fe71e091aa53075
+# e80daef3c8c548fe905c71e3888d9d35
+msgid "The IP Addresses page is displayed."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:828
+# 7100a75c5b7f4e94af12eba67cc769d7
+msgid "Click the IP you want to release."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:830
+# 5d08cda75ef64158bc169fa0b4d55bfd
+msgid "In the Details tab, click the Release IP button |release-ip-icon.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:836
+# 66b58ca8d7e8481184b5f30fb10aeb3a
+msgid "Enabling or Disabling Static NAT on a VPC"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:838
+# 5ffcce98eb5341c4815405feb3f45e3d
+msgid "A static NAT rule maps a public IP address to the private IP address of a VM in a VPC to allow Internet traffic to it. This section tells how to enable or disable static NAT for a particular IP address in a VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:842
+# 3a033892a74543d4a655001ee01f7102
+msgid "If port forwarding rules are already in effect for an IP address, you cannot enable static NAT to that IP."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:845
+# 3ced6dfc6cda40c59a7663608968ae25
+msgid "If a guest VM is part of more than one network, static NAT rules will function only if they are defined on the default network."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:863
+# a101d2d938bd44ef8b442c2dd878803b
+msgid "For each tier, the following options are displayed."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:885
+#: ../../networking/virtual_private_cloud_config.rst:1051
+#: ../../networking/virtual_private_cloud_config.rst:1319
+# 2aa87b8efca045199c60a69232f4100c
+# f29854dbe679478497f195c125c70fc3
+# 0ca75518c2c1401bada82a5f5b3953b2
+msgid "In the Router node, select Public IP Addresses."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:889
+# ecb19327446e44f7a44f71eaef9cc73a
+msgid "Click the IP you want to work with."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:891
+# 54b9ba8fad964d51a0442fc5838ba574
+msgid "In the Details tab,click the Static NAT button. |enable-disable.png| The button toggles between Enable and Disable, depending on whether static NAT is currently enabled for the IP address."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:896
+# ee96b8eeef6f44169338cbec4bd552e2
+msgid "If you are enabling static NAT, a dialog appears as follows:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:898
+# 2934b5d934b343aab14d143fb537ce07
+msgid "|select-vmstatic-nat.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:900
+# ba4894eec4ee4f8ab908308bf7f2b682
+msgid "Select the tier and the destination VM, then click Apply."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:904
+# 6bc44c698b784002948ea93ac931ccb3
+msgid "Adding Load Balancing Rules on a VPC"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:906
+# d55b224d3d4d427da85774962a911e9b
+msgid "In a VPC, you can configure two types of load balancing: external LB and internal LB. External LB is nothing but a LB rule created to redirect the traffic received at a public IP of the VPC virtual router. The traffic is load balanced within a tier based on your configuration. Citrix NetScaler and VPC virtual router are supported for external LB. When you use internal LB service, traffic received at a tier is load balanced across different VMs within that tier. For example, traffic reached at Web tier is redirected to another VM in that tier. External load balancing devices are not supported for internal LB. The service is provided by a internal LB VM configured on the target tier."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:919
+# 40e935f35e0c40ada19216e535aa1258
+msgid "Load Balancing Within a Tier (External LB)"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:921
+# f415c289521945488fc0ee0094a1dab0
+msgid "A CloudStack user or administrator may create load balancing rules that balance traffic received at a public IP to one or more VMs that belong to a network tier that provides load balancing service in a VPC. A user creates a rule, specifies an algorithm, and assigns the rule to a set of VMs within a tier."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:929
+# 3e4fdfab26c8433f985733abf6b8fab2
+msgid "Enabling NetScaler as the LB Provider on a VPC Tier"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:931
+# f4009b64ee9a4abc935568ba00072b14
+msgid "Add and enable Netscaler VPX in dedicated mode."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:933
+# 11c807f9e62a4acb9f8b3ef0d007c2c9
+msgid "Netscaler can be used in a VPC environment only if it is in dedicated mode."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:936
+# 57a85fbc857449ee89781dd4fce1788c
+msgid "Create a network offering, as given in \":ref:`create-net-offering-ext-lb`\"."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:938
+# 08a0f277fc3f43b694322360de337dfc
+msgid "Create a VPC with Netscaler as the Public LB provider."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:940
+# ecc067da6bf9448587d900d0602ecacd
+msgid "For more information, see `\"Adding a Virtual Private Cloud\" <#adding-a-virtual-private-cloud>`_."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:943
+# aa3b5b48c05343338d0ee08f3382b40d
+msgid "For the VPC, acquire an IP."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:945
+# 7c4c3743af9240d882f3ba1d438b3bd8
+msgid "Create an external load balancing rule and apply, as given in :ref:`create-ext-lb-rule`."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:952
+# 65a1193d54904d989149249c4257b9c1
+msgid "Creating a Network Offering for External LB"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:954
+# e69c20a921124dc7b5ac28a8bc23f254
+msgid "To have external LB support on VPC, create a network offering as follows:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:957
+#: ../../networking/virtual_private_cloud_config.rst:1163
+# 27d475982a384fed8f13220941eded23
+# 2da0ddfe20c0412a9dc8725da9ebfb08
+msgid "Log in to the CloudStack UI as a user or admin."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:959
+#: ../../networking/virtual_private_cloud_config.rst:1165
+# 2e6d402ef3d044488597c6501ca6749d
+# f974a014675745ceae4ebb19113bc49e
+msgid "From the Select Offering drop-down, choose Network Offering."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:961
+#: ../../networking/virtual_private_cloud_config.rst:1167
+# 08107e25d3ae4ed5a4e72a9ef68249af
+# f88397d4525c49d4b10ca8f6d24c5999
+msgid "Click Add Network Offering."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:963
+#: ../../networking/virtual_private_cloud_config.rst:1169
+# 0b77090696474c0a9cab45f79b1c7986
+# e1cffd47fe2e4f3089c2620a68b839a1
+msgid "In the dialog, make the following choices:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:965
+#: ../../networking/virtual_private_cloud_config.rst:1171
+# 60d2abd68eb948dbaba04e1ac5723b86
+# 2e15e5f8b3704612a4d58813e4d32f6b
+msgid "**Name**: Any desired name for the network offering."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:967
+#: ../../networking/virtual_private_cloud_config.rst:1173
+# 3959d6091cd747cb937e8f842088c32e
+# 5f694898705c49328c1a2e142eb14d1f
+msgid "**Description**: A short description of the offering that can be displayed to users."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:970
+#: ../../networking/virtual_private_cloud_config.rst:1176
+# 2e0e45c2f8604206ab9ab52b64e032e0
+# 40a66509e3424c24bb6186610a441bac
+msgid "**Network Rate**: Allowed data transfer rate in MB per second."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:972
+#: ../../networking/virtual_private_cloud_config.rst:1178
+# 33f13b044bc94b5b8696d75ddf4b8bc3
+# a160a569847143f797400c4ff977efdf
+msgid "**Traffic Type**: The type of network traffic that will be carried on the network."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:975
+#: ../../networking/virtual_private_cloud_config.rst:1181
+# aaf9ff68483341d98ede19f290845e4d
+# c3356024660a4455a0ceac2dcae5caee
+msgid "**Guest Type**: Choose whether the guest network is isolated or shared."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:978
+#: ../../networking/virtual_private_cloud_config.rst:1184
+# 78da437179454d2e9bb2b2566016b345
+# 8e43b8eb7620486dafe2037f9644fc74
+msgid "**Persistent**: Indicate whether the guest network is persistent or not. The network that you can provision without having to deploy a VM on it is termed persistent network."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:982
+#: ../../networking/virtual_private_cloud_config.rst:1188
+# b8efdabd98ae4986a6423993e842848f
+# a09dbae19ba24a44abe4d1e06d94391d
+msgid "**VPC**: This option indicate whether the guest network is Virtual Private Cloud-enabled. A Virtual Private Cloud (VPC) is a private, isolated part of CloudStack. A VPC can have its own virtual network topology that resembles a traditional physical network. For more information on VPCs, see `\"About Virtual Private Clouds\" <#about-virtual-private-clouds>`_."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:988
+#: ../../networking/virtual_private_cloud_config.rst:1195
+# f833921e66e7405e90b64ecab4f06585
+# 60780dc0b1414010b97ef9ee9fdf6896
+msgid "**Specify VLAN**: (Isolated guest networks only) Indicate whether a VLAN should be specified when this offering is used."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:991
+# c39ddc76ab104334a4dc179d2666185f
+msgid "**Supported Services**: Select Load Balancer. Use Netscaler or VpcVirtualRouter."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:994
+# 0f2a2787484945d4893a95c93e013659
+msgid "**Load Balancer Type**: Select Public LB from the drop-down."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:996
+# 012d5de507d14d86a63f00c612267262
+msgid "**LB Isolation**: Select Dedicated if Netscaler is used as the external LB provider."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:999
+#: ../../networking/virtual_private_cloud_config.rst:1203
+# 32714ec60c95462a86fad6f4ea8a389f
+# 6d1b55437586405195f96d4e1901a030
+msgid "**System Offering**: Choose the system service offering that you want virtual routers to use in this network."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1002
+#: ../../networking/virtual_private_cloud_config.rst:1206
+# ccddc4e596ac4b9590b1e89143679f4c
+# 5b0c2de816bb4f3489ea6c0aaf56dd92
+msgid "**Conserve mode**: Indicate whether to use conserve mode. In this mode, network resources are allocated only when the first virtual machine starts in the network."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1006
+#: ../../networking/virtual_private_cloud_config.rst:1210
+# 64b8ac5900b040949abdbe1be369798e
+# 86eacc968b5642af9d7708d20b05fa0b
+msgid "Click OK and the network offering is created."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1012
+# 7d8aa307714e45a48e2b8a026f88ecd5
+msgid "Creating an External LB Rule"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1023
+# ec858cbb6d054d82b7344347f3d1f80a
+msgid "Click the Configure button of the VPC, for which you want to configure load balancing rules."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1026
+#: ../../networking/virtual_private_cloud_config.rst:1239
+# 24c4acc56c8546b48b0d1ba8225aa2c3
+# 8623ea1fa5f64fc882bc161a00e0de31
+msgid "The VPC page is displayed where all the tiers you created listed in a diagram."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1055
+#: ../../networking/virtual_private_cloud_config.rst:1323
+# faa2aca06f244ec79e1495f403d60fba
+# f6b4d72a1ace463aaeae65e85f5351fe
+msgid "Click the IP address for which you want to create the rule, then click the Configuration tab."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1058
+# 05fb941cda1540a6ae76a68c80d28164
+msgid "In the Load Balancing node of the diagram, click View All."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1060
+#: ../../networking/virtual_private_cloud_config.rst:1328
+# a68bbaad32ad4fb1a32434a21627c7df
+# 513eb1682d554f15af9624073505f185
+msgid "Select the tier to which you want to apply the rule."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1064
+#: ../../networking/virtual_private_cloud_config.rst:1249
+# 48072a5bd67b4fc2b091903b2930ef20
+# 23e879002b734874bb3fb8648d82ec9f
+msgid "**Name**: A name for the load balancer rule."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1066
+# 035ce1c6b7094ddfb03cf84e79fe13fb
+msgid "**Public Port**: The port that receives the incoming traffic to be balanced."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1069
+# 95e57b758d354580b0723b1cf69b1ad9
+msgid "**Private Port**: The port that the VMs will use to receive the traffic."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1072
+#: ../../networking/virtual_private_cloud_config.rst:1268
+# 9401419db1ac40dd8912809bfb47d5fa
+# c29c451e2c474605af3093430f4fe416
+msgid "**Algorithm**. Choose the load balancing algorithm you want CloudStack to use. CloudStack supports the following well-known algorithms:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1076
+#: ../../networking/virtual_private_cloud_config.rst:1272
+# 45872bf350da46e8915a4c200e500d47
+# 2fe10525962546129f438019ddb43570
+msgid "Round-robin"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1078
+#: ../../networking/virtual_private_cloud_config.rst:1274
+# b89b8c35da0e4067aa0e2dfc46507db4
+# 384c8fd5fe8049389138586119a8e392
+msgid "Least connections"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1080
+#: ../../networking/virtual_private_cloud_config.rst:1276
+# 75b481e88cb749ee9744fa2d4153d658
+# a656566824f644a7a9bf0c5aa7f7ce82
+msgid "Source"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1082
+# 156eaabf00d6402fb1a6f26cdc8bdc3a
+msgid "**Stickiness**. (Optional) Click Configure and choose the algorithm for the stickiness policy. See Sticky Session Policies for Load Balancer Rules."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1086
+# 5a609fc01f0c442fbaa6859f3c48de9d
+msgid "**Add VMs**: Click Add VMs, then select two or more VMs that will divide the load of incoming traffic, and click Apply."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1089
+# 227920ab85304ccd9ef2ff2fcc816394
+msgid "The new load balancing rule appears in the list. You can repeat these steps to add more load balancing rules for this IP address."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1094
+# 9e2c252f60374e98b336b982bdb5a807
+msgid "Load Balancing Across Tiers"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1096
+# b0b3d2bc1154428ea7aa2a73ccf65ca9
+msgid "CloudStack supports sharing workload across different tiers within your VPC. Assume that multiple tiers are set up in your environment, such as Web tier and Application tier. Traffic to each tier is balanced on the VPC virtual router on the public side, as explained in `\"Adding Load Balancing Rules on a VPC\" <#adding-load-balancing-rules-on-a-vpc>`_. If you want the traffic coming from the Web tier to the Application tier to be balanced, use the internal load balancing feature offered by CloudStack."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1107
+# fbb2a59a26334767857dae55b7dd76d2
+msgid "How Does Internal LB Work in VPC?"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1109
+# 9f3100aad1e345bb8ac547e9ff36084f
+msgid "In this figure, a public LB rule is created for the public IP 72.52.125.10 with public port 80 and private port 81. The LB rule, created on the VPC virtual router, is applied on the traffic coming from the Internet to the VMs on the Web tier. On the Application tier two internal load balancing rules are created. An internal LB rule for the guest IP 10.10.10.4 with load balancer port 23 and instance port 25 is configured on the VM, InternalLBVM1. Another internal LB rule for the guest IP 10.10.10.4 with load balancer port 45 and instance port 46 is configured on the VM, InternalLBVM1. Another internal LB rule for the guest IP 10.10.10.6, with load balancer port 23 and instance port 25 is configured on the VM, InternalLBVM2."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1121
+# c94baade36ca41029339b5771845f6eb
+msgid "|vpc-lb.png|"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1125
+# 6b5c736fe39c453f9df86d49e415bb0d
+msgid "Guidelines"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1127
+# f48db5cf237f48c1b83470d2b3619c89
+msgid "Internal LB and Public LB are mutually exclusive on a tier. If the tier has LB on the public side, then it can't have the Internal LB."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1130
+# 39c3726d0f1e417ba4856caefdc69c5f
+msgid "Internal LB is supported just on VPC networks in CloudStack 4.2 release."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1133
+# c9b5009bd45949ca9adfe8bad469126e
+msgid "Only Internal LB VM can act as the Internal LB provider in CloudStack 4.2 release."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1136
+# f0db26b4389241deb62e3e62af4ae108
+msgid "Network upgrade is not supported from the network offering with Internal LB to the network offering with Public LB."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1139
+# cdacc61443a24192b33aa89bf454081d
+msgid "Multiple tiers can have internal LB support in a VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1141
+# 08ebb9d7ed624f58a875207bb6be9859
+msgid "Only one tier can have Public LB support in a VPC."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1145
+# 0cf099b085094a858d1b083c8e2f72f6
+msgid "Enabling Internal LB on a VPC Tier"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1147
+# 381918d116bf406189b9d4dd38f04f33
+msgid "Create a network offering, as given in :ref:`creating-net-offering-internal-lb`."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1150
+# f09e6b3612574602ae51429ca4126c05
+msgid "Create an internal load balancing rule and apply, as given in :ref:`create-int-lb-rule`."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1157
+# 25a70af8ca1e41f18f48eb08ef5d850a
+msgid "Creating a Network Offering for Internal LB"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1159
+# 08c27533594e44e582e605b3e9b3df6a
+msgid "To have internal LB support on VPC, either use the default offering, DefaultIsolatedNetworkOfferingForVpcNetworksWithInternalLB, or create a network offering as follows:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1198
+# a41f382608f64d309fbe464cf7137a17
+msgid "**Supported Services**: Select Load Balancer. Select ``InternalLbVM`` from the provider list."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1201
+# 163583059e0b4dc38ec9a9324be12914
+msgid "**Load Balancer Type**: Select Internal LB from the drop-down."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1216
+# c468f85bcd804f59b3e50b6395b59e2a
+msgid "Creating an Internal LB Rule"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1218
+# 97768defcebc48e484aca56eed453215
+msgid "When you create the Internal LB rule and applies to a VM, an Internal LB VM, which is responsible for load balancing, is created."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1221
+# 68b5cb10c6e7463690bbeefba32870fb
+msgid "You can view the created Internal LB VM in the Instances page if you navigate to **Infrastructure** > **Zones** > <zone\\_ name> > <physical\\_network\\_name> > **Network Service Providers** > **Internal LB VM**. You can manage the Internal LB VMs as and when required from the location."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1236
+# 3df2a5995876429facf54c5a8446811d
+msgid "Locate the VPC for which you want to configure internal LB, then click Configure."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1242
+# 6f207d8e5df84a4b8c67c56fd431c1d7
+msgid "Locate the Tier for which you want to configure an internal LB rule, click Internal LB."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1245
+# 3d886b162d3b4cb78187e716d7935265
+msgid "In the Internal LB page, click Add Internal LB."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1247
+# f08b145932924c3caba6b02b3e38b19a
+msgid "In the dialog, specify the following:"
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1251
+# 551399e510014c7fbc3cf5f1a0110627
+msgid "**Description**: A short description of the rule that can be displayed to users."
+msgstr ""
+
+#: ../../networking/virtual_private_cloud_config.rst:1254
+# 6cf0e4a86d4043878ef3a656833ff790
+msgid "**Source IP Address**: (Optional) The source IP from which traffic originates. The IP is acquired from the CIDR of that particular tier on which you want to create the Internal LB rule. If not specified, the IP address is automatically allocated from the network CIDR."