You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cloudstack.apache.org by se...@apache.org on 2014/03/31 20:07:02 UTC
[3/7] setup i18n with transifex and sphinx-intl

http://git-wip-us.apache.org/repos/asf/cloudstack-docs-install/blob/bd81bcc4/source/locale/pot/managing_networks.pot
----------------------------------------------------------------------
diff --git a/source/locale/pot/managing_networks.pot b/source/locale/pot/managing_networks.pot
new file mode 100644
index 0000000..d8ac813
--- /dev/null
+++ b/source/locale/pot/managing_networks.pot
@@ -0,0 +1,6769 @@
+# SOME DESCRIPTIVE TITLE.
+# Copyright (C) 2014, Apache Software Foundation
+# This file is distributed under the same license as the Apache CloudStack Installation Documentation package.
+# FIRST AUTHOR <EM...@ADDRESS>, YEAR.
+#
+#, fuzzy
+msgid ""
+msgstr ""
+"Project-Id-Version: Apache CloudStack Installation Documentation 4\n"
+"Report-Msgid-Bugs-To: \n"
+"POT-Creation-Date: 2014-03-31 14:02-0400\n"
+"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
+"Last-Translator: FULL NAME <EM...@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"
+
+#: ../../managing_networks.rst:17
+# fc6be4b2a5ef4daab75e0149886b57ab
+msgid "Managing Networks and Traffic"
+msgstr ""
+
+#: ../../managing_networks.rst:19
+# e6e873bbde6b490a93904226a79e35e7
+msgid "In a CloudStack, guest VMs can communicate with each other using shared infrastructure with the security and user perception that the guests have a private LAN. The CloudStack virtual router is the main component providing networking features for guest traffic."
+msgstr ""
+
+#: ../../managing_networks.rst:25
+# 158d9384502741139d4db7ad5d35f129
+msgid "Guest Traffic"
+msgstr ""
+
+#: ../../managing_networks.rst:27
+# 79038a2139e34806a98fb5dd5d6b1380
+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 ""
+
+#: ../../managing_networks.rst:32
+# 23f28e25661d4e449f0498521ff811f4
+msgid "See a typical guest traffic setup given below:"
+msgstr ""
+
+#: ../../managing_networks.rst:34
+# 3e47df0ab4fe4f7994d946a031909210
+msgid "|guest-traffic-setup.png: Depicts a guest traffic setup|"
+msgstr ""
+
+#: ../../managing_networks.rst:36
+# 4ddddc3fc73a4867a25fc49b035a99b7
+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 ""
+
+#: ../../managing_networks.rst:47
+# 32df6f633baa46de8a08df89b547bf68
+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 ""
+
+#: ../../managing_networks.rst:52
+# 037184db1823493ab1584e55b5275584
+msgid "Source NAT is automatically configured in the virtual router to forward outbound traffic for all guest VMs"
+msgstr ""
+
+#: ../../managing_networks.rst:56
+# d2daf1fae25745c0a829cd52009d5ac3
+msgid "Networking in a Pod"
+msgstr ""
+
+#: ../../managing_networks.rst:58
+# 3574c26b40ab456e8286506f92bca83c
+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 ""
+
+#: ../../managing_networks.rst:64
+# 35d1da6e0db343f2ae916ce0be527d56
+msgid "|networksinglepod.png: diagram showing logical view of network in a pod|"
+msgstr ""
+
+#: ../../managing_networks.rst:66
+# b7c71c1045954931b9d89bd5843e0306
+msgid "Servers are connected as follows:"
+msgstr ""
+
+#: ../../managing_networks.rst:70
+# 09e404c4512e44e59345fa1f14899f3d
+msgid "Storage devices are connected to only the network that carries management traffic."
+msgstr ""
+
+#: ../../managing_networks.rst:75
+# a3a5ebaa022e413da0ffc6bdae7b6465
+msgid "Hosts are connected to networks for both management traffic and public traffic."
+msgstr ""
+
+#: ../../managing_networks.rst:80
+# bd0d953a458e41eea4bf15edbfb12b2a
+msgid "Hosts are also connected to one or more networks carrying guest traffic."
+msgstr ""
+
+#: ../../managing_networks.rst:83
+# 28c5e92ff62f49bba80dace0b3ae2fb0
+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 ""
+
+#: ../../managing_networks.rst:88
+# d85d232eadb24f49a48d499c5adf81e7
+msgid "Networking in a Zone"
+msgstr ""
+
+#: ../../managing_networks.rst:90
+# 45168de567df49238a394803bce5aacc
+msgid "The following figure illustrates the network setup within a single zone."
+msgstr ""
+
+#: ../../managing_networks.rst:92
+# 29289f73fcf54224bc331c5454378f15
+msgid "|networksetupzone.png: Depicts network setup in a single zone|"
+msgstr ""
+
+#: ../../managing_networks.rst:94
+# df4e8223cc9c4409adf7cc8c71e7a98e
+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 ""
+
+#: ../../managing_networks.rst:99
+# 9886368af88c424183304a4eb31ab641
+msgid "Each zone has its own set of public IP addresses. Public IP addresses from different zones do not overlap."
+msgstr ""
+
+#: ../../managing_networks.rst:103
+# e924366efd4241009758e8896b3e6669
+msgid "Basic Zone Physical Network Configuration"
+msgstr ""
+
+#: ../../managing_networks.rst:105
+# 99801fc2693a463386163a5ba924265b
+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 ""
+
+#: ../../managing_networks.rst:111
+# 4794c328db1440609a15296cef16b874
+msgid "Advanced Zone Physical Network Configuration"
+msgstr ""
+
+#: ../../managing_networks.rst:113
+# 627040abff364b5ea8314a3426b65674
+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 ""
+
+#: ../../managing_networks.rst:118
+# 7d82c9b8761a46dda119e356cf26d478
+msgid "Configure Guest Traffic in an Advanced Zone"
+msgstr ""
+
+#: ../../managing_networks.rst:120
+# 1744b57706544187ae3a8c396a505bf1
+msgid "These steps assume you have already logged in to the CloudStack UI. To configure the base guest network:"
+msgstr ""
+
+#: ../../managing_networks.rst:125
+# 5aecf3d836d747a884b554bca3fbb83d
+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 ""
+
+#: ../../managing_networks.rst:130
+#: ../../managing_networks.rst:214
+#: ../../managing_networks.rst:1585
+# 0cbb909f14cb492385ca0848aa144676
+# ae580367a0aa4a1186f4e67538afff94
+# af249bda556241b28af1cd321cc15602
+msgid "Click the Network tab."
+msgstr ""
+
+#: ../../managing_networks.rst:134
+#: ../../managing_networks.rst:218
+#: ../../managing_networks.rst:1589
+# 7c7e182828424070b9c41369469b65f0
+# 2e538d60fc224c08a46491e983daca7e
+# 44ba62fc316b4753a5d2655c5c666a98
+msgid "Click Add guest network."
+msgstr ""
+
+#: ../../managing_networks.rst:136
+# 15e6873aadaf411c83caf85f0a01dd5e
+msgid "The Add guest network window is displayed:"
+msgstr ""
+
+#: ../../managing_networks.rst:138
+# 0d02390e218c427e9a53bf85ca53de51
+msgid "|addguestnetwork.png: Add guest network setup in a single zone|"
+msgstr ""
+
+#: ../../managing_networks.rst:142
+#: ../../managing_networks.rst:4111
+#: ../../managing_networks.rst:4979
+# 0800e2f4123c4dd9a3cf88e6df107406
+# 9e8f926d35dd4062a29482a8ac99cbde
+# 30dd4c879c8f431d96a1941eb88e5443
+msgid "Provide the following information:"
+msgstr ""
+
+#: ../../managing_networks.rst:146
+# 7604500c996c439089ccdde1d7c025b4
+msgid "**Name**. The name of the network. This will be user-visible"
+msgstr ""
+
+#: ../../managing_networks.rst:150
+# 360746c957d54a70bd23064f9714bf87
+msgid "**Display Text**: The description of the network. This will be user-visible"
+msgstr ""
+
+#: ../../managing_networks.rst:155
+# 4c0edf7e62fb438f9f48989672721586
+msgid "**Zone**: The zone in which you are configuring the guest network."
+msgstr ""
+
+#: ../../managing_networks.rst:159
+# d0157a715ff0417e968114b1c345ed05
+msgid "**Network offering**: If the administrator has configured multiple network offerings, select the one you want to use for this network"
+msgstr ""
+
+#: ../../managing_networks.rst:164
+# 8821fdb0e3e34d4eb2d879f89ef8265f
+msgid "**Guest Gateway**: The gateway that the guests should use"
+msgstr ""
+
+#: ../../managing_networks.rst:168
+# 4dc47880e5f541529ad13f5cf0ca522f
+msgid "**Guest Netmask**: The netmask in use on the subnet the guests will use"
+msgstr ""
+
+#: ../../managing_networks.rst:173
+#: ../../managing_networks.rst:870
+#: ../../managing_networks.rst:1242
+#: ../../managing_networks.rst:1419
+#: ../../managing_networks.rst:1742
+#: ../../managing_networks.rst:3064
+#: ../../managing_networks.rst:3578
+#: ../../managing_networks.rst:4209
+#: ../../managing_networks.rst:4245
+#: ../../managing_networks.rst:5015
+#: ../../managing_networks.rst:5106
+#: ../../managing_networks.rst:5352
+#: ../../managing_networks.rst:5394
+#: ../../managing_networks.rst:6843
+# 84368ab7e8384ed2ae5ecece5835bf18
+# 40ef14b296d343928f7b1af29927beba
+# fd54e59b59e34039ba86fdf384b32bb4
+# d595b9b3106b4a93b86dc8def713e6cf
+# 946c5d37563d43f98c6f39734828f252
+# 8969b38d8d954135bd6fd49ba48540a2
+# 96826bee1eba4ea1bbc5592ab0c19d71
+# b886d197d674421586d115da68f6e823
+# 8a1b58cd366c4d22a2a0ef021bf5439a
+# 8873118788c94bcc91cdcb0412e1f3a9
+# 067481ecae7e42a691ed616190af998f
+# 26e33f314996484ab84cff370047c483
+# 7d0cd95d267b472fb4b0dda772ffc2bc
+# 6ada6497acc04627b1750ff39f3e3b89
+msgid "Click OK."
+msgstr ""
+
+#: ../../managing_networks.rst:176
+# 92ed55846f3943a0899c3de25a023050
+msgid "Configure Public Traffic in an Advanced Zone"
+msgstr ""
+
+#: ../../managing_networks.rst:178
+# 915dafcef9e741c2a3aa241af4f416bf
+msgid "In a zone that uses advanced networking, you need to configure at least one range of IP addresses for Internet traffic."
+msgstr ""
+
+#: ../../managing_networks.rst:182
+# 38eed1230b0548409982c02a9e02c83e
+msgid "Configuring a Shared Guest Network"
+msgstr ""
+
+#: ../../managing_networks.rst:186
+#: ../../managing_networks.rst:760
+#: ../../managing_networks.rst:1557
+# 029160365cb44beeabf86951b8cabbac
+# 5709f6a0aa4d4e87afbf1cd833e9b2f3
+# 390b3883b39c4ad585199248f00069c2
+msgid "Log in to the CloudStack UI as administrator."
+msgstr ""
+
+#: ../../managing_networks.rst:190
+#: ../../managing_networks.rst:1354
+#: ../../managing_networks.rst:1561
+# 6b9a0641eccf4c888cb21525be4ed4c4
+# 25eb0f7c27f44e2983c3f49702a6d79b
+# 10241f1af1c84aa7a72d15d48b14b3e9
+msgid "In the left navigation, choose Infrastructure."
+msgstr ""
+
+#: ../../managing_networks.rst:194
+#: ../../managing_networks.rst:1565
+# 72ac0f8a684a418aa1a522b990724f3c
+# fcdd5db0bcf7487fb69abb38b182c87c
+msgid "On Zones, click View More."
+msgstr ""
+
+#: ../../managing_networks.rst:198
+#: ../../managing_networks.rst:1569
+# 15ee52a81be94e849e9aebbffd80f86e
+# 572f3b0de37d4cde8ee922ca57357102
+msgid "Click the zone to which you want to add a guest network."
+msgstr ""
+
+#: ../../managing_networks.rst:202
+#: ../../managing_networks.rst:776
+#: ../../managing_networks.rst:898
+#: ../../managing_networks.rst:1573
+# c8621ca1f0014cab8a2df11d16b6e23b
+# b0ac7488089d4de49ab63d4714a358d1
+# 67983bfccffe4126b74f01d74445a757
+# c54cc238e91a40e88ebec6ac9a67c3b9
+msgid "Click the Physical Network tab."
+msgstr ""
+
+#: ../../managing_networks.rst:206
+#: ../../managing_networks.rst:1577
+# 819adbe3002443ac81418804a6524958
+# 4f1ac1f461d24c96aac89732394faeb4
+msgid "Click the physical network you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:210
+#: ../../managing_networks.rst:1581
+# bf5520949d574c33956b419b623300af
+# a5e3c030c17040fd843946f7acd71beb
+msgid "On the Guest node of the diagram, click Configure."
+msgstr ""
+
+#: ../../managing_networks.rst:220
+#: ../../managing_networks.rst:1591
+# 3a1c06a1806443829aced440705c6ebb
+# 035fafb19b594767b275df96c08bffd8
+msgid "The Add guest network window is displayed."
+msgstr ""
+
+#: ../../managing_networks.rst:224
+#: ../../managing_networks.rst:806
+#: ../../managing_networks.rst:822
+#: ../../managing_networks.rst:856
+#: ../../managing_networks.rst:916
+#: ../../managing_networks.rst:1218
+#: ../../managing_networks.rst:1391
+#: ../../managing_networks.rst:1595
+#: ../../managing_networks.rst:3095
+#: ../../managing_networks.rst:5061
+#: ../../managing_networks.rst:5485
+#: ../../managing_networks.rst:6237
+#: ../../managing_networks.rst:6629
+# 2f740f3f23ab48a29ae3adbaf94c9a76
+# 342b53e57638424dbd3fc25b5de444cc
+# 81cc7e7f5132410a85166b44099c4efd
+# 433cd273bd454f109daafe4144bedce4
+# fbc94c5a87b34f69a0b7ccd2ec2961b8
+# 49a60cbb39104498a256acb82fa540bc
+# d93b5e9a682247d09575b8fed78e8419
+# 17f3af10510b469ab4fa599fdeca5e84
+# 147594fd9398446a9bffe7aa89aa42ae
+# 9d0d76a77389406aa54c77270247fb68
+# 0d313bd3accd40bba047ccbf1b35d224
+# 3daf7170c2984410906999b0b0fa4f3c
+# 2240e232e86f4b3ca8ab2960be6c573b
+msgid "Specify the following:"
+msgstr ""
+
+#: ../../managing_networks.rst:228
+#: ../../managing_networks.rst:1599
+# 14a5b53bcd874033a8eaa789e7c562d1
+# 2f405f166fd04a0bacf050bb1f4f4250
+msgid "**Name**: The name of the network. This will be visible to the user."
+msgstr ""
+
+#: ../../managing_networks.rst:233
+#: ../../managing_networks.rst:1604
+# 0f8d2c8170fd4b98bf717c87aef34378
+# 7585c82a0ece4f368233e94f9d3dfa64
+msgid "**Description**: The short description of the network that can be displayed to users."
+msgstr ""
+
+#: ../../managing_networks.rst:238
+#: ../../managing_networks.rst:1609
+# 99429451759a40f7ba18b278914e39f0
+# 88da596b302847b090b03d4973e86bfd
+msgid "**VLAN ID**: The unique ID of the VLAN."
+msgstr ""
+
+#: ../../managing_networks.rst:242
+# 00c2912dbf2443aa9b3241c8c5676742
+msgid "**Isolated VLAN ID**: The unique ID of the Secondary Isolated VLAN."
+msgstr ""
+
+#: ../../managing_networks.rst:247
+#: ../../managing_networks.rst:1621
+# 6d2136a01445425e94f1ff5205af5c28
+# f35050303cac4011bb97763f32382baf
+msgid "**Scope**: The available scopes are Domain, Account, Project, and All."
+msgstr ""
+
+#: ../../managing_networks.rst:252
+#: ../../managing_networks.rst:1626
+# fe3608c2f3b3416aa62072104aa0fa8e
+# 21c43e42d8d34b4c97f8065f32bdae9e
+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 ""
+
+#: ../../managing_networks.rst:260
+#: ../../managing_networks.rst:1634
+# 5703f6a9a2db4216aca3b448df168a2a
+# a98df446d79849acbcf910ae486f9f24
+msgid "**Account**: The account for which the guest network is being created for. You must specify the domain the account belongs to."
+msgstr ""
+
+#: ../../managing_networks.rst:266
+#: ../../managing_networks.rst:1640
+# a1006b86f9414bee862542a9fe33ea89
+# 7431a628570b4f8f941f22c0dbca0d10
+msgid "**Project**: The project for which the guest network is being created for. You must specify the domain the project belongs to."
+msgstr ""
+
+#: ../../managing_networks.rst:272
+#: ../../managing_networks.rst:1646
+# 8b76a654149140adb4fb77dc2eaa7f03
+# 86babff897704393a7a47fac16fdb6da
+msgid "**All**: The guest network is available for all the domains, account, projects within the selected zone."
+msgstr ""
+
+#: ../../managing_networks.rst:277
+#: ../../managing_networks.rst:1651
+# abea434f07f34363afcd9c5acb702a37
+# 1367c8fe48974b6b8fcef96e9154b1f5
+msgid "**Network Offering**: If the administrator has configured multiple network offerings, select the one you want to use for this network."
+msgstr ""
+
+#: ../../managing_networks.rst:283
+#: ../../managing_networks.rst:1657
+# 699e9d5856cb463885a05f687b080247
+# 433ee2c2a4084f46956487e77324431b
+msgid "**Gateway**: The gateway that the guests should use."
+msgstr ""
+
+#: ../../managing_networks.rst:287
+#: ../../managing_networks.rst:1661
+# ce51526eaf0744f69498878264436b85
+# 45bbdda7a102498a9f476b2cdb175fd2
+msgid "**Netmask**: The netmask in use on the subnet the guests will use."
+msgstr ""
+
+#: ../../managing_networks.rst:291
+#: ../../managing_networks.rst:1665
+# 6dbeaf06a3e14f82aa81cb65f66d29f5
+# 4eec9a4a29fa4d52a6b4337a8a50155c
+msgid "**IP Range**: A range of IP addresses that are accessible from the Internet and are assigned to the guest VMs."
+msgstr ""
+
+#: ../../managing_networks.rst:294
+# 6136c512a7fd43cf949e71c315564e8e
+msgid "If one NIC is used, these IPs should be in the same CIDR in the case of IPv6."
+msgstr ""
+
+#: ../../managing_networks.rst:299
+# 2049d251d6d24864be2401aae7d15eda
+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 ""
+
+#: ../../managing_networks.rst:306
+#: ../../managing_networks.rst:1670
+# 2eb61bdd6e2e4d0fb52eb0f2ab77e5c3
+# eb07ff88c573443cbf65bd9790a02d7e
+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 ""
+
+#: ../../managing_networks.rst:312
+#: ../../managing_networks.rst:1676
+#: ../../managing_networks.rst:3133
+#: ../../managing_networks.rst:3172
+#: ../../managing_networks.rst:4450
+# 01a5c1ddc4284bf7bb918c2924b99144
+# 29e37ee9c31a42b3b19bbd29b62699db
+# 5b8546575cc143e6aa6df3a739ec2dd4
+# c9c0a1842e2243cbbfbdd7bda9f8c173
+# 62ad85eee39c492e951ac8ef8cc0f1de
+msgid "Click OK to confirm."
+msgstr ""
+
+#: ../../managing_networks.rst:315
+# 0ba3f54aff874d7eb78409feb3e574cb
+msgid "Using Multiple Guest Networks"
+msgstr ""
+
+#: ../../managing_networks.rst:317
+# 9ee699c8fe6347568730b54b7737afe5
+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 ""
+
+#: ../../managing_networks.rst:322
+# cb2cfc8f5dd14b6a8d4c568329b1bc9e
+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 ""
+
+#: ../../managing_networks.rst:327
+# 044af5c71d054ac780d922e821f138a2
+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 ""
+
+#: ../../managing_networks.rst:333
+# 0adbfc444f2b4c1db5edbdd5b7d6bbea
+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 ""
+
+#: ../../managing_networks.rst:341
+# b7306772cd68452da7fcba1da1f76cb7
+msgid "Adding an Additional Guest Network"
+msgstr ""
+
+#: ../../managing_networks.rst:345
+#: ../../managing_networks.rst:412
+#: ../../managing_networks.rst:477
+#: ../../managing_networks.rst:508
+#: ../../managing_networks.rst:543
+#: ../../managing_networks.rst:686
+#: ../../managing_networks.rst:1196
+#: ../../managing_networks.rst:1249
+#: ../../managing_networks.rst:1350
+#: ../../managing_networks.rst:1722
+#: ../../managing_networks.rst:1799
+#: ../../managing_networks.rst:2157
+#: ../../managing_networks.rst:3200
+#: ../../managing_networks.rst:3243
+#: ../../managing_networks.rst:3286
+#: ../../managing_networks.rst:3362
+#: ../../managing_networks.rst:3464
+#: ../../managing_networks.rst:3611
+#: ../../managing_networks.rst:3743
+#: ../../managing_networks.rst:4095
+#: ../../managing_networks.rst:4219
+#: ../../managing_networks.rst:4252
+#: ../../managing_networks.rst:4349
+#: ../../managing_networks.rst:4542
+#: ../../managing_networks.rst:4963
+#: ../../managing_networks.rst:5028
+#: ../../managing_networks.rst:5156
+#: ../../managing_networks.rst:5238
+#: ../../managing_networks.rst:5406
+#: ../../managing_networks.rst:5643
+#: ../../managing_networks.rst:5735
+#: ../../managing_networks.rst:5823
+#: ../../managing_networks.rst:5913
+#: ../../managing_networks.rst:6155
+#: ../../managing_networks.rst:6463
+#: ../../managing_networks.rst:6547
+#: ../../managing_networks.rst:6672
+#: ../../managing_networks.rst:6711
+# bbfccf4187ee4d4fbf07e7f4bb88a635
+# 55b4e0f4a10d435781dc67f60c289bcc
+# 448e46420df84abe9fd5e0a98622bd8a
+# 7045e9260e2b41ac88aea79006e38ad5
+# c94a526c0dc04ebba1a701bb33b34bd3
+# 5878e84a00674d17980caa25c5845868
+# 21870457e3e743f78d2afa2427544010
+# c407b2aceffd487888c468b506ec84f2
+# be7946dbd37144e8a9a120d588d4ed8d
+# 57c820671f3e472e80e9758a6875049d
+# 7effce72473246f583a2c6706cf7ae8b
+# 10a47885bc344872bb68acaa38950c56
+# 0e16e2897c2541bdb9a9fe44c7c8c314
+# 69c641cc9e5745699a855b095a3f4234
+# 682913d951a64d7a9672b6c2d8ce61ec
+# b507fdb77c914103931f4382f7e94b6f
+# 69bf185d9530474e9d1e3ac4caccde82
+# 3a12fbb150d4405283cf759bdc0f579c
+# ce1e6561910a4f9b92872de6c4f0fe75
+# 8e6a2cd4f9da4a7da14bd4ff19517c5c
+# 0c0a9fa95a2c4c23affeb329bc18b9cd
+# ba5dc11cd6054bb0842bd0c996926273
+# 0383bb7ab57f403bb4dfdfd3cbe56bad
+# 0ce64e2cda5f451f939117bb581125bb
+# 2e7c7ca911564fd0b55e438fbf85b707
+# 724f938759144bca86466d021cded7cb
+# 3eb23b8ca60f439097e03d61faefe36b
+# a1e4d7e27f0a4bfd89398d6c8e268485
+# 4fdda4830b1d407b8baa1d170ccbd0f5
+# c1fe8cc9534f44f1825f02b028eda7ff
+# 1c6cfb5f62e947c8a05df1bdbca53570
+# 797717e559d24b03951f25f843042245
+# e1e46b9e3b67432eba081e3fa0b0b179
+# 7b6bd9d6ebe042aa817672a63cbdfa37
+# c7d9f6a38d724a9aa8a5caa76ed2d848
+# e6c130b9b73f4034b0e9d9c8a3aaa8dd
+# bdc2624551194b9eadb9cdfdf7403a02
+# c7ca24ebec074700a533736638fefcc0
+msgid "Log in to the CloudStack UI as an administrator or end user."
+msgstr ""
+
+#: ../../managing_networks.rst:349
+#: ../../managing_networks.rst:553
+#: ../../managing_networks.rst:690
+#: ../../managing_networks.rst:1253
+#: ../../managing_networks.rst:2161
+#: ../../managing_networks.rst:3204
+#: ../../managing_networks.rst:3247
+#: ../../managing_networks.rst:3290
+#: ../../managing_networks.rst:3366
+#: ../../managing_networks.rst:3468
+#: ../../managing_networks.rst:4099
+#: ../../managing_networks.rst:4223
+#: ../../managing_networks.rst:4256
+#: ../../managing_networks.rst:4353
+#: ../../managing_networks.rst:4546
+#: ../../managing_networks.rst:4967
+#: ../../managing_networks.rst:5032
+#: ../../managing_networks.rst:5160
+#: ../../managing_networks.rst:5242
+#: ../../managing_networks.rst:5410
+#: ../../managing_networks.rst:5647
+#: ../../managing_networks.rst:5739
+#: ../../managing_networks.rst:5827
+#: ../../managing_networks.rst:5917
+#: ../../managing_networks.rst:6159
+#: ../../managing_networks.rst:6467
+#: ../../managing_networks.rst:6551
+#: ../../managing_networks.rst:6676
+#: ../../managing_networks.rst:6715
+# 542d2aed321d47bdabd1fca487ffd35e
+# e9aad32ba9934dfabf895d86886307b4
+# a64380da9ffa4f209568917d3e2f7ae6
+# f6467d352c5441f3aac59ff1a7e5751e
+# 489eb5a18ecf487089f92e974e4004b2
+# b77e8c3076474667a41f9c643cfb8921
+# 53f468b814a14dc7bc2846e0bb679713
+# b20083aec91a49e38ba1bd1bbd5ca432
+# cc62da2d87294fe59e75b03eab0b30de
+# 89a49e650a154374ac569bb05b88d91f
+# 230865dbd3c4443cb426bb570ee13485
+# 774f364202474a70b77a8561495b3245
+# 0ad7189c21294ef0b43aba32a8bafb7d
+# 726205f734c447d48af0ecd790bd238a
+# fdade5ad8a554d8897cc4e6c27dbc34e
+# 749f818fe9a349f9bb8cb7538cde74f8
+# b444a52f1dd14725bbd9f33966b9b508
+# bdcf2c42e7064f82ade52bd341621f2e
+# b1f4a91afafd4f6e84df0723ead48206
+# 541424f9e38a42d983bb27f87dcd3225
+# b5e9e12abba44624b3b74fc09e0f77fc
+# f392c162ed3241f09fc16f75065cd789
+# 2cd0df6af7ef4a7f9bad72059870b57b
+# e7d42493086e4c04a6545951d4c1ce5b
+# 3f34c206961e4a239714abc14d945f2c
+# d874094ea72f43988a5a4da919c3aae1
+# 0107854a76984dd18cc4256511f643fb
+# 399088fe7776424c8455730cb62a2f94
+# 9eaf23c1feb144f1b0cd1227b0b9ddd1
+msgid "In the left navigation, choose Network."
+msgstr ""
+
+#: ../../managing_networks.rst:353
+# ffe816f2fabe4d698bc426a2756acbe6
+msgid "Click Add guest network. Provide the following information:"
+msgstr ""
+
+#: ../../managing_networks.rst:357
+# e493749a1b58441b9f26c0ff3b13b9a7
+msgid "**Name**: The name of the network. This will be user-visible."
+msgstr ""
+
+#: ../../managing_networks.rst:361
+# e6573973726c48d1a6ddd47d98dfc7d4
+msgid "**Display Text**: The description of the network. This will be user-visible."
+msgstr ""
+
+#: ../../managing_networks.rst:366
+# 12ce0885bb7f4c36890123d1bdbd6b6d
+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 ""
+
+#: ../../managing_networks.rst:373
+# 6a5f82ef524445d184e3c139994c446f
+msgid "**Network offering**: If the administrator has configured multiple network offerings, select the one you want to use for this network."
+msgstr ""
+
+#: ../../managing_networks.rst:379
+# d63cb3347919412cb5652d167f3198a0
+msgid "**Guest Gateway**: The gateway that the guests should use."
+msgstr ""
+
+#: ../../managing_networks.rst:383
+# 1da6215b19f84083aeac888d2ef3bff1
+msgid "**Guest Netmask**: The netmask in use on the subnet the guests will use."
+msgstr ""
+
+#: ../../managing_networks.rst:388
+#: ../../managing_networks.rst:3947
+# 4a768d89236c43fd9f2c33eab727c4e8
+# a127adae4308423cb1caf2db8966bdc4
+msgid "Click Create."
+msgstr ""
+
+#: ../../managing_networks.rst:391
+# 21b37eb5b7fe40bd99e0910a9f2bb75a
+msgid "Reconfiguring Networks in VMs"
+msgstr ""
+
+#: ../../managing_networks.rst:393
+# 476864eb3c9c4bccb394ef84b6e0c94b
+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 ""
+
+#: ../../managing_networks.rst:399
+# 9e97bafcd742424d921d811f3230a213
+msgid "This feature is supported on XenServer, VMware, and KVM hypervisors."
+msgstr ""
+
+#: ../../managing_networks.rst:402
+#: ../../managing_networks.rst:1517
+# f34aa270088a4613b0a44df4357afc8f
+# 8bd7a92ac32d4a2a929c8af17d3fb170
+msgid "Prerequisites"
+msgstr ""
+
+#: ../../managing_networks.rst:404
+# 145ab5ecce044608b4b9656676c6cfc7
+msgid "Ensure that vm-tools are running on guest VMs for adding or removing networks to work on VMware hypervisor."
+msgstr ""
+
+#: ../../managing_networks.rst:408
+# 5a51c1312ebb4557a8603954294917c7
+msgid "Adding a Network"
+msgstr ""
+
+#: ../../managing_networks.rst:416
+#: ../../managing_networks.rst:481
+#: ../../managing_networks.rst:512
+# ecf6574c795f4768b731ef450b7ae607
+# 3b1c880a36ab4788a672d34d01ef6a4c
+# 49f1a64bc600489b90f669ff77ba9059
+msgid "In the left navigation, click Instances."
+msgstr ""
+
+#: ../../managing_networks.rst:420
+#: ../../managing_networks.rst:485
+#: ../../managing_networks.rst:516
+# 338fcbaeb8724ead9106c34112c862d9
+# bca3b4caf62d4663b33417eb7edaf223
+# f31277b33b9e4e2f9793e5a8ca4d7bb5
+msgid "Choose the VM that you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:424
+#: ../../managing_networks.rst:489
+#: ../../managing_networks.rst:520
+# 156d65dc581c4df498395e309bc7cbde
+# e5d8801dfa004ca1b93351677c983d89
+# 469dea7ab2094639b3d9a2299529fc07
+msgid "Click the NICs tab."
+msgstr ""
+
+#: ../../managing_networks.rst:428
+# 1bd7e90630f144b2b08248a827e64b0b
+msgid "Click Add network to VM."
+msgstr ""
+
+#: ../../managing_networks.rst:430
+# 049059a7b43d4efc989e4fcd813e6e1c
+msgid "The Add network to VM dialog is displayed."
+msgstr ""
+
+#: ../../managing_networks.rst:434
+# 5c99fc8205ef493dbab49c0599061a45
+msgid "In the drop-down list, select the network that you would like to add this VM to."
+msgstr ""
+
+#: ../../managing_networks.rst:437
+# 901988536d184641ac9d5ecaaee03ee2
+msgid "A new NIC is added for this network. You can view the following details in the NICs page:"
+msgstr ""
+
+#: ../../managing_networks.rst:442
+# 8d071d6df54845d6a56e7d96321dd7e8
+msgid "ID"
+msgstr ""
+
+#: ../../managing_networks.rst:446
+# ba92b68db3fc48ae810bd43616abc87a
+msgid "Network Name"
+msgstr ""
+
+#: ../../managing_networks.rst:450
+# eefe16e33001458591bb721f9e964a32
+msgid "Type"
+msgstr ""
+
+#: ../../managing_networks.rst:454
+#: ../../managing_networks.rst:4332
+#: ../../managing_networks.rst:4458
+# ce7e7d2354fc48ccb97e1c2917007397
+# 35a3d8a7cc444f7289fff5b3f02731e3
+# 906d6bce91f745de9cc8eb362260b17b
+msgid "IP Address"
+msgstr ""
+
+#: ../../managing_networks.rst:458
+#: ../../managing_networks.rst:4462
+# 07c404d90b444084935108a2905f8147
+# aa4cc5b288b14a26b34b3cd819e6be4e
+msgid "Gateway"
+msgstr ""
+
+#: ../../managing_networks.rst:462
+# da3675e2aed24eb681d8601910102496
+msgid "Netmask"
+msgstr ""
+
+#: ../../managing_networks.rst:466
+# 48374307b68a4eff88c1778ea7bd9380
+msgid "Is default"
+msgstr ""
+
+#: ../../managing_networks.rst:470
+# 2777d60a7bf14a35bd37af5f0ac55458
+msgid "CIDR (for IPv6)"
+msgstr ""
+
+#: ../../managing_networks.rst:473
+# 84f9d9b60c4e4ce4a509cad5b0900a5b
+msgid "Removing a Network"
+msgstr ""
+
+#: ../../managing_networks.rst:493
+# 707d137eb0aa4adaa497aff9a413ad06
+msgid "Locate the NIC you want to remove."
+msgstr ""
+
+#: ../../managing_networks.rst:497
+# c2a07f20886b47be83f065291dfee6fb
+msgid "Click Remove NIC button. |remove-nic.png: button to remove a NIC|"
+msgstr ""
+
+#: ../../managing_networks.rst:501
+#: ../../managing_networks.rst:533
+# b23abd4aac6242bdbc3f97acc2666a90
+# 8f8b04c7921a441ba8480683014b9864
+msgid "Click Yes to confirm."
+msgstr ""
+
+#: ../../managing_networks.rst:504
+# 4f9e35dc3f614384a7505c4161fffaac
+msgid "Selecting the Default Network"
+msgstr ""
+
+#: ../../managing_networks.rst:524
+# 40b332e2efca44c092058585a0004200
+msgid "Locate the NIC you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:528
+# 3d3dc6ede8e440efab9778ab27669811
+msgid "Click the Set default NIC button. |set-default-nic.png: button to set a NIC as default one.|"
+msgstr ""
+
+#: ../../managing_networks.rst:536
+# f0c74bc7df3d400bac208e03ca7e454d
+msgid "Changing the Network Offering on a Guest Network"
+msgstr ""
+
+#: ../../managing_networks.rst:538
+# bd0f96f469b24f7cb9efc0e11835fc56
+msgid "A user or administrator can change the network offering that is associated with an existing guest network."
+msgstr ""
+
+#: ../../managing_networks.rst:547
+# 746637ea703149eab979289dea055956
+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 ""
+
+#: ../../managing_networks.rst:557
+#: ../../managing_networks.rst:694
+# b06f831436614c7799e92f02062dd02e
+# b2aef771f9cb4102849882e08921deda
+msgid "Click the name of the network you want to modify."
+msgstr ""
+
+#: ../../managing_networks.rst:561
+# 8fe0c8047dd941648bdb27d5c4d46d64
+msgid "In the Details tab, click Edit. |EditButton.png: button to edit a network|"
+msgstr ""
+
+#: ../../managing_networks.rst:566
+# 38ce91cfac534d3d8ce2d2be8ac4d9db
+msgid "In Network Offering, choose the new network offering, then click Apply."
+msgstr ""
+
+#: ../../managing_networks.rst:569
+# 0c9082cd84904f30a842d0296519899f
+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 ""
+
+#: ../../managing_networks.rst:573
+# 395368811c93495691bd4e308ae0bbc4
+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 ""
+
+#: ../../managing_networks.rst:579
+# ee09bef0f4f84d41a949984dce97934e
+msgid "Wait for the update to complete. Don’t try to restart VMs until the network change is complete."
+msgstr ""
+
+#: ../../managing_networks.rst:584
+# 7c315c696ed54f5197595376cdd7d0c0
+msgid "If you stopped any VMs, restart them."
+msgstr ""
+
+#: ../../managing_networks.rst:587
+# 92b286db05494a3f9d6591a9f2ccfc6a
+msgid "IP Reservation in Isolated Guest Networks"
+msgstr ""
+
+#: ../../managing_networks.rst:589
+# 67ed578463354e849af5ed40418159aa
+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 ""
+
+#: ../../managing_networks.rst:597
+# d38381f1dad148afb7aeed5ee6e6db41
+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 ""
+
+#: ../../managing_networks.rst:611
+# 3031b1a715ff422bad8de1f97adc2db7
+msgid "IP Reservation Considerations"
+msgstr ""
+
+#: ../../managing_networks.rst:613
+# c57c48d3a65e474c89a99952e65a6a40
+msgid "Consider the following before you reserve an IP range for non-CloudStack machines:"
+msgstr ""
+
+#: ../../managing_networks.rst:618
+# 05c140f272754cfb9d21597b9c778fc5
+msgid "IP Reservation is supported only in Isolated networks."
+msgstr ""
+
+#: ../../managing_networks.rst:622
+# f5211c450a014b0a8d335434d84aa391
+msgid "IP Reservation can be applied only when the network is in Implemented state."
+msgstr ""
+
+#: ../../managing_networks.rst:627
+# 6add1277df044450bce332b364de119b
+msgid "No IP Reservation is done by default."
+msgstr ""
+
+#: ../../managing_networks.rst:631
+# 0847da9c049c4c0da2a6eac963931b02
+msgid "Guest VM CIDR you specify must be a subset of the network CIDR."
+msgstr ""
+
+#: ../../managing_networks.rst:635
+# 36a9bbd09feb416ca7f9ccca3c54eefb
+msgid "Specify a valid Guest VM CIDR. IP Reservation is applied only if no active IPs exist outside the Guest VM CIDR."
+msgstr ""
+
+#: ../../managing_networks.rst:638
+# 191010bd30424f3aa12cf309a48dcfc4
+msgid "You cannot apply IP Reservation if any VM is alloted with an IP address that is outside the Guest VM CIDR."
+msgstr ""
+
+#: ../../managing_networks.rst:643
+# e4b8dc3735d4441ebf832418538d5833
+msgid "To reset an existing IP Reservation, apply IP reservation by specifying the value of network CIDR in the CIDR field."
+msgstr ""
+
+#: ../../managing_networks.rst:646
+# 8281e4ae0c6a4374b25bfef4f7e74405
+msgid "For example, the following table describes three scenarios of guest network creation:"
+msgstr ""
+
+#: ../../managing_networks.rst:650
+# 9f714ae7b5f346bc87da5182136d41e5
+msgid "Case"
+msgstr ""
+
+#: ../../managing_networks.rst:650
+#: ../../managing_networks.rst:3846
+#: ../../managing_networks.rst:4293
+#: ../../managing_networks.rst:4393
+#: ../../managing_networks.rst:4587
+#: ../../managing_networks.rst:5144
+#: ../../managing_networks.rst:5193
+#: ../../managing_networks.rst:5451
+#: ../../managing_networks.rst:5776
+#: ../../managing_networks.rst:5863
+#: ../../managing_networks.rst:5954
+#: ../../managing_networks.rst:6196
+#: ../../managing_networks.rst:6588
+# 43eb64da7dd14977948b1fd136c81c4f
+# ba69ebf50fa04e628494a63c71ee09be
+# 6e509570aefc4ed58372df0bae71f59e
+# e02ce26c53d447cab48c5987becb6178
+# 372de59b30db4b00a1a4a4503aecb29d
+# 0efc90dc789a42219e0e1821921c3a3b
+# 2f722e4bc54941bf9ac18e34ec89ea21
+# 0f4f84fccf1c4879a9ec6691a4abb447
+# 04c82a1485db4a52a0c4fae3e4018e41
+# 8788d910542844b09ae66506304063dc
+# e65e4e6cdcba4f138e43047ff9d3bed6
+# 23d809b6aa20458dacb898b0e8b4d1da
+# cd520efc8baa4344b57bd33b0fa5254d
+msgid "CIDR"
+msgstr ""
+
+#: ../../managing_networks.rst:650
+# 63125858003344c0b965da2ac922cf02
+msgid "Network CIDR"
+msgstr ""
+
+#: ../../managing_networks.rst:650
+# c3c99ba5184c4c9194605bb04a547f39
+msgid "Reserved IP Range for Non-CloudStack VMs"
+msgstr ""
+
+#: ../../managing_networks.rst:650
+# 0e5c1cae0f4d4f06851e27a50273b95c
+msgid "Description"
+msgstr ""
+
+#: ../../managing_networks.rst:652
+#: ../../managing_networks.rst:5146
+# 2e71a7acd08543168d74d2c0d03e0c39
+# d06565ec0d634d848669aa19d123d59a
+msgid "1"
+msgstr ""
+
+#: ../../managing_networks.rst:652
+#: ../../managing_networks.rst:653
+#: ../../managing_networks.rst:654
+# bd4f28e5c83943d8882e2012659415bf
+# 249137a9387145d0ac514e9000be76cd
+# d7c4b09246fb4bfeb5649c2cf6e23d30
+msgid "10.1.1.0/24"
+msgstr ""
+
+#: ../../managing_networks.rst:652
+#: ../../managing_networks.rst:652
+#: ../../managing_networks.rst:654
+#: ../../managing_networks.rst:654
+# 2f9cc88264fb4285bfa3149ea04b26a5
+# d74122c1ce754a1999acc721dfe12491
+# 3e1cad272521413bb73ebf025861f357
+# c9bd04abf9984e3d82a008b15823df6f
+msgid "None"
+msgstr ""
+
+#: ../../managing_networks.rst:652
+# 672d94082a534891849650884d4c25d0
+msgid "No IP Reservation."
+msgstr ""
+
+#: ../../managing_networks.rst:653
+#: ../../managing_networks.rst:5147
+# 7f31ca61138545d19f53bfea0156930f
+# f11cfcf719bc4813a691abc48eef0c50
+msgid "2"
+msgstr ""
+
+#: ../../managing_networks.rst:653
+# 8e804381dca64c3ab199583ca238a7e8
+msgid "10.1.1.0/26"
+msgstr ""
+
+#: ../../managing_networks.rst:653
+# 042cf084bef6418fa9d8ee1a00593e8a
+msgid "10.1.1.64 to 10.1.1.254"
+msgstr ""
+
+#: ../../managing_networks.rst:653
+# 2094d73c4b004d18b9b1c3be4ac72e10
+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 ""
+
+#: ../../managing_networks.rst:654
+# 769561dd7e454a58b571d069407bc84f
+msgid "3"
+msgstr ""
+
+#: ../../managing_networks.rst:654
+# 99819f9f881049da88cf236d227fbcce
+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 ""
+
+#: ../../managing_networks.rst:659
+# af64fa9a0d594bf6aba58e557fb64ef2
+msgid "Limitations"
+msgstr ""
+
+#: ../../managing_networks.rst:663
+# b133ecb14f0743c5aad172cbec921f69
+msgid "The IP Reservation is not supported if active IPs that are found outside the Guest VM CIDR."
+msgstr ""
+
+#: ../../managing_networks.rst:668
+# 9c8183bbe2aa4950a96b3f707269281c
+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 ""
+
+#: ../../managing_networks.rst:674
+# a6037f7354694b7fa3df7eab35ce68a3
+msgid "Best Practices"
+msgstr ""
+
+#: ../../managing_networks.rst:676
+# 1402bdfed0e642a5bc411cad728d629f
+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 ""
+
+#: ../../managing_networks.rst:682
+# 9d8b936d8d924b3e9610e79cea49d7ed
+msgid "Reserving an IP Range"
+msgstr ""
+
+#: ../../managing_networks.rst:698
+# 43313d5d032c4bc1ae00497086042bf1
+msgid "In the Details tab, click Edit. |edit-icon.png: button to edit a network|"
+msgstr ""
+
+#: ../../managing_networks.rst:701
+# 4b6443793ca64ed7b71e9dacebc772c6
+msgid "The CIDR field changes to editable one."
+msgstr ""
+
+#: ../../managing_networks.rst:705
+# 170900f4419c40d3ae77ba9cee3b6fff
+msgid "In CIDR, specify the Guest VM CIDR."
+msgstr ""
+
+#: ../../managing_networks.rst:709
+# 1fccea99506b441bba9fd6fbc76dd995
+msgid "Click Apply."
+msgstr ""
+
+#: ../../managing_networks.rst:711
+# c0734e33a8844d90aac6295573540aee
+msgid "Wait for the update to complete. The Network CIDR and the Reserved IP Range are displayed on the Details page."
+msgstr ""
+
+#: ../../managing_networks.rst:715
+# aad0613e9913469fb756198fc0170632
+msgid "Reserving Public IP Addresses and VLANs for Accounts"
+msgstr ""
+
+#: ../../managing_networks.rst:717
+# 6e44df38576d4f5e99903f26a9db1253
+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 ""
+
+#: ../../managing_networks.rst:723
+# 8da4bb7270e845baa41435d7a8dc2897
+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 ""
+
+#: ../../managing_networks.rst:733
+# 37e6f49f8b53452a8036407ad381ea12
+msgid "This feature provides you the following capabilities:"
+msgstr ""
+
+#: ../../managing_networks.rst:737
+# 671086ca87b14ae28c39b69fd8046953
+msgid "Reserve a VLAN range and public IP address range from an Advanced zone and assign it to an account"
+msgstr ""
+
+#: ../../managing_networks.rst:742
+# 404fcaa9d1b848d2ab247cce5350c281
+msgid "Disassociate a VLAN and public IP address range from an account"
+msgstr ""
+
+#: ../../managing_networks.rst:746
+# bd85bcf3d9394066af54e1e703ae3cf7
+msgid "View the number of public IP addresses allocated to an account"
+msgstr ""
+
+#: ../../managing_networks.rst:750
+# 01799c3a9b364c51b97d539c849d3394
+msgid "Check whether the required range is available and is conforms to account limits."
+msgstr ""
+
+#: ../../managing_networks.rst:753
+# 7716c7ee6e9a4c68bacaaafbba51a78c
+msgid "The maximum IPs per account limit cannot be superseded."
+msgstr ""
+
+#: ../../managing_networks.rst:756
+# 8f2fa2619671428980abde283469e00d
+msgid "Dedicating IP Address Ranges to an Account"
+msgstr ""
+
+#: ../../managing_networks.rst:764
+#: ../../managing_networks.rst:886
+#: ../../managing_networks.rst:2974
+# d7a82a1208db4208961df5b2bda98eb3
+# 3ac411dc4da74e0689c3e931f08d5c59
+# c74ad6e9cbee4ff685cef4af6c1a1c8a
+msgid "In the left navigation bar, click Infrastructure."
+msgstr ""
+
+#: ../../managing_networks.rst:768
+#: ../../managing_networks.rst:890
+# ad2d0d358fab46f69cc0e2834d1025b5
+# 06d4cbfaa106459eb58d6d9bb34a92a1
+msgid "In Zones, click View All."
+msgstr ""
+
+#: ../../managing_networks.rst:772
+#: ../../managing_networks.rst:894
+#: ../../managing_networks.rst:2982
+# 04e17439a9d04d8c92bace413127ce77
+# e40c006773b9414cbe8dd42bb69472d4
+# 03828d4d48bf4770bdc2328f34b55100
+msgid "Choose the zone you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:780
+# b2f55880ae154ea5a38880eeeb515690
+msgid "In the Public node of the diagram, click Configure."
+msgstr ""
+
+#: ../../managing_networks.rst:784
+# 790579c6465f4bf88b03caf31b04e907
+msgid "Click the IP Ranges tab."
+msgstr ""
+
+#: ../../managing_networks.rst:786
+# 9136b3e4ca934c23806bbc7ca0ff01e5
+msgid "You can either assign an existing IP range to an account, or create a new IP range and assign to an account."
+msgstr ""
+
+#: ../../managing_networks.rst:791
+# be977158780a4bfca4232fc7d2573dd7
+msgid "To assign an existing IP range to an account, perform the following:"
+msgstr ""
+
+#: ../../managing_networks.rst:795
+# c85643e60bae4ce7a7341f72ed356343
+msgid "Locate the IP range you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:799
+# 8c760073c6e140c98957ae64117cd375
+msgid "Click Add Account |addAccount-icon.png: button to assign an IP range to an account.| button."
+msgstr ""
+
+#: ../../managing_networks.rst:802
+# 5907d0ab73b04589b7fba68c857ad361
+msgid "The Add Account dialog is displayed."
+msgstr ""
+
+#: ../../managing_networks.rst:810
+# d84f7b0e62b043939a4656f457f829e7
+msgid "**Account**: The account to which you want to assign the IP address range."
+msgstr ""
+
+#: ../../managing_networks.rst:815
+# 54ea232ef7544939989c85cf78823ab4
+msgid "**Domain**: The domain associated with the account."
+msgstr ""
+
+#: ../../managing_networks.rst:817
+# cac430d036924f38a9290dde3665c841
+msgid "To create a new IP range and assign an account, perform the following:"
+msgstr ""
+
+#: ../../managing_networks.rst:826
+# d50191ed42ad44ee95f6167032a30c65
+msgid "**Gateway**"
+msgstr ""
+
+#: ../../managing_networks.rst:830
+# 13d287dfefa145e3bf443ca11ed78fa2
+msgid "**Netmask**"
+msgstr ""
+
+#: ../../managing_networks.rst:834
+# 2e49c1a58f4a4bfa87d30c1c449df1e3
+msgid "**VLAN**"
+msgstr ""
+
+#: ../../managing_networks.rst:838
+# 8ebc180647e6488db6d7419f0c96d969
+msgid "**Start IP**"
+msgstr ""
+
+#: ../../managing_networks.rst:842
+# 39bbcd6bce9c4acdb1dde4c134d36aee
+msgid "**End IP**"
+msgstr ""
+
+#: ../../managing_networks.rst:846
+# c9ff42e89acd482b839c78ede4bf72a2
+msgid "**Account**: Perform the following:"
+msgstr ""
+
+#: ../../managing_networks.rst:850
+# 4e8c15e78f4040da8818c60242a385f7
+msgid "Click Account."
+msgstr ""
+
+#: ../../managing_networks.rst:852
+# 4d16eeb78e534a4aba7b7c05c335d94a
+msgid "The Add Account page is displayed."
+msgstr ""
+
+#: ../../managing_networks.rst:860
+# 4fcbdb024f3c4d0e916309194ccf9796
+msgid "****Account****: The account to which you want to assign an IP address range."
+msgstr ""
+
+#: ../../managing_networks.rst:865
+#: ../../managing_networks.rst:930
+# 5dd4ec70717a455cb3eae0f191b2c338
+# e1b99db893e94523a9c9c6c2dca5e50a
+msgid "****Domain****: The domain associated with the account."
+msgstr ""
+
+#: ../../managing_networks.rst:874
+#: ../../managing_networks.rst:1919
+#: ../../managing_networks.rst:3411
+#: ../../managing_networks.rst:3511
+#: ../../managing_networks.rst:3667
+#: ../../managing_networks.rst:3899
+#: ../../managing_networks.rst:5623
+# 222bcd68057f4097804636cc658bae40
+# 583b09f47740445cae14b167a426c0d5
+# d8184c325cbe4e2989e1772dd91acd0b
+# b8bdf6dd077f48bab5be9a342447e9d8
+# 221e41362cdb48c1b692cef19b0a8218
+# f241bee872c34bcfa7d43b4601e1cb48
+# 95df29e50c984e798847dc985a455395
+msgid "Click Add."
+msgstr ""
+
+#: ../../managing_networks.rst:877
+# 6f5ed4ecaf104ec089964163e1e6884f
+msgid "Dedicating VLAN Ranges to an Account"
+msgstr ""
+
+#: ../../managing_networks.rst:881
+# 1d96f022bb0641f591f869dcdef945de
+msgid "After the CloudStack Management Server is installed, log in to the CloudStack UI as administrator."
+msgstr ""
+
+#: ../../managing_networks.rst:902
+#: ../../managing_networks.rst:1367
+# b7387ff7ac314fabb59c5c8adb95d64c
+# 09557ffae33041df84505184339ead4d
+msgid "In the Guest node of the diagram, click Configure."
+msgstr ""
+
+#: ../../managing_networks.rst:906
+# fcf27305c8cf42bcaea54b6e0d583e74
+msgid "Select the Dedicated VLAN Ranges tab."
+msgstr ""
+
+#: ../../managing_networks.rst:910
+# 67395673dcac45fd95c09509e40ab195
+msgid "Click Dedicate VLAN Range."
+msgstr ""
+
+#: ../../managing_networks.rst:912
+# ab0efa84cce7484aa1483aa86e7458e3
+msgid "The Dedicate VLAN Range dialog is displayed."
+msgstr ""
+
+#: ../../managing_networks.rst:920
+# 79112ed3b43d4ac9b8ffd92e5be692f1
+msgid "****VLAN Range****: The VLAN range that you want to assign to an account."
+msgstr ""
+
+#: ../../managing_networks.rst:925
+# a99491d184b347ae9692f3140f8507e1
+msgid "****Account****: The account to which you want to assign the selected VLAN range."
+msgstr ""
+
+#: ../../managing_networks.rst:933
+# fcc09f716f8d4237b77cc161171a4261
+msgid "Configuring Multiple IP Addresses on a Single NIC"
+msgstr ""
+
+#: ../../managing_networks.rst:935
+# a94a3710f1234c97836f59a5a07db667
+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 ""
+
+#: ../../managing_networks.rst:942
+# 494be8c0259840fb84fb26e96d13a908
+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 ""
+
+#: ../../managing_networks.rst:949
+# 925a5eb75fe04c35bfd19b1ac2f44b7e
+msgid "This feature is supported on XenServer, KVM, and VMware hypervisors. Note that Basic zone security groups are not supported on VMware."
+msgstr ""
+
+#: ../../managing_networks.rst:953
+# 5ac573ae5f4345aeb143a5fcc101524d
+msgid "Use Cases"
+msgstr ""
+
+#: ../../managing_networks.rst:955
+# 872874841bbe414a88684eb2a0045657
+msgid "Some of the use cases are described below:"
+msgstr ""
+
+#: ../../managing_networks.rst:959
+# d5c27060797b4aee9174ebb56ffef918
+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 ""
+
+#: ../../managing_networks.rst:965
+# 24ce123387844169a49487bc30845b7a
+msgid "Moving private IP addresses between interfaces or instances. Applications that are bound to specific IP addresses can be moved between instances."
+msgstr ""
+
+#: ../../managing_networks.rst:971
+# 0c37cb7a4c434f399e9d45b1c2e472e9
+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 ""
+
+#: ../../managing_networks.rst:976
+#: ../../managing_networks.rst:6315
+# d4f7b4962530468a906a498acca4bae2
+# 3da7bf4ad1544749bab36764d2d447ef
+msgid "Guidelines"
+msgstr ""
+
+#: ../../managing_networks.rst:978
+# d6caf12c9309436d9de8f99f9c7543c3
+msgid "To prevent IP conflict, configure different subnets when multiple networks are connected to the same VM."
+msgstr ""
+
+#: ../../managing_networks.rst:982
+# 16aeec8d7d974a11ab5270669432a394
+msgid "Assigning Additional IPs to a VM"
+msgstr ""
+
+#: ../../managing_networks.rst:986
+# 034b4e6e920d4b1b819935e74e2b858c
+msgid "Log in to the CloudStack UI."
+msgstr ""
+
+#: ../../managing_networks.rst:990
+# 6a36c11f314b4a73ae436cedecc70f5e
+msgid "In the left navigation bar, click Instances."
+msgstr ""
+
+#: ../../managing_networks.rst:994
+# a8208d3a66ae4646bb1c56d1ecb10311
+msgid "Click the name of the instance you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:998
+# 3614c5b73e634141848b9ffd09823e34
+msgid "In the Details tab, click NICs."
+msgstr ""
+
+#: ../../managing_networks.rst:1002
+# 9ddaf912d7f64aa791244c3f89f4f87e
+msgid "Click View Secondary IPs."
+msgstr ""
+
+#: ../../managing_networks.rst:1006
+# 41a35e39fad3445a94b912212054ec76
+msgid "Click Acquire New Secondary IP, and click Yes in the confirmation dialog."
+msgstr ""
+
+#: ../../managing_networks.rst:1009
+# 966f02979ce94ebfad48594d314843e6
+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 ""
+
+#: ../../managing_networks.rst:1013
+# 6f93e046959a4ebd9133806cbf00c179
+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 ""
+
+#: ../../managing_networks.rst:1018
+# 584ea105deaf4c149e1f4a22e7c76f9c
+msgid "Port Forwarding and StaticNAT Services Changes"
+msgstr ""
+
+#: ../../managing_networks.rst:1020
+# 66fa989a4cf444159810d5b86fe29d71
+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 ""
+
+#: ../../managing_networks.rst:1030
+# d56668f88c1b4778956f3e78eb0af4f3
+msgid "About Multiple IP Ranges"
+msgstr ""
+
+#: ../../managing_networks.rst:1032
+# a425fadff6f24df8a703773e76e1da84
+msgid "The feature can only be implemented on IPv4 addresses."
+msgstr ""
+
+#: ../../managing_networks.rst:1034
+# 085d7bcb306c4df9b4bcb062fa965779
+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 ""
+
+#: ../../managing_networks.rst:1045
+# a916ea5fa2a3442cac9346d464c33b3c
+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 ""
+
+#: ../../managing_networks.rst:1049
+# 0cb128b2b4964c4c94d50a7d4f4c113d
+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 ""
+
+#: ../../managing_networks.rst:1055
+# 5c50556940324ae1a2c2f33b4e3be74c
+msgid "This feature is supported on KVM, xenServer, and VMware hypervisors."
+msgstr ""
+
+#: ../../managing_networks.rst:1058
+# 86f5b04f9bf84ff4a0162e548a43ed45
+msgid "About Elastic IP"
+msgstr ""
+
+#: ../../managing_networks.rst:1060
+# 1abc932ae33e4097ad9d5a7c01466858
+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 ""
+
+#: ../../managing_networks.rst:1069
+# 6f92b16714d4455c9c0d07422b7a5278
+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 ""
+
+#: ../../managing_networks.rst:1077
+# 1917b806df094374b24b204ab96801f8
+msgid "|eip-ns-basiczone.png: Elastic IP in a NetScaler-enabled Basic Zone.|"
+msgstr ""
+
+#: ../../managing_networks.rst:1079
+# 3b1d323c9feb4e9ba7ca76be6aaad6b2
+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 ""
+
+#: ../../managing_networks.rst:1088
+# d73486cd06ff42a3b7ae00d650f94b85
+msgid "The EIP work flow is as follows:"
+msgstr ""
+
+#: ../../managing_networks.rst:1092
+# c76961037d5e4684aae701d14e8628ef
+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 ""
+
+#: ../../managing_networks.rst:1098
+# 113a0b56fa5c4d588763310f3344c045
+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 ""
+
+#: ../../managing_networks.rst:1103
+# 26464e6616334eba867bfbedcd8b9b32
+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 ""
+
+#: ../../managing_networks.rst:1107
+# c24df2c0e244417bac058ee69288159e
+msgid "This default public IP will be released in two cases:"
+msgstr ""
+
+#: ../../managing_networks.rst:1111
+# e69a190aa6ff4094a1376bbd1a48c806
+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 ""
+
+#: ../../managing_networks.rst:1117
+# ae09bc75005442799a101c13ee164cfe
+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 ""
+
+#: ../../managing_networks.rst:1125
+# 85b2631843ed40888b2ca7fe400962fd
+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 ""
+
+#: ../../managing_networks.rst:1134
+# 94a57e6c08fb4beeb2cc92ada6ed0e19
+msgid "For more information on the Associate Public IP option, see the Administration Guide."
+msgstr ""
+
+#: ../../managing_networks.rst:1137
+# 51ff3fc654054203b273f9c148ae18b5
+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 ""
+
+#: ../../managing_networks.rst:1139
+# 83364c7e0dd94f759842ac386a8cac79
+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 ""
+
+#: ../../managing_networks.rst:1144
+# 342239c2715c475b88c10804e3612a51
+msgid "Portable IPs"
+msgstr ""
+
+#: ../../managing_networks.rst:1147
+# dd5fc98d73bc4d75beeb09ce0439d181
+msgid "About Portable IP"
+msgstr ""
+
+#: ../../managing_networks.rst:1149
+# 89820f26aa2645078ccb72b82efc9dfe
+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 ""
+
+#: ../../managing_networks.rst:1158
+# bd4cf0b29f8b41b3b03e37f656c52501
+msgid "The salient features of Portable IP are as follows:"
+msgstr ""
+
+#: ../../managing_networks.rst:1162
+# 855ab24aced14fa18033b90699abf066
+msgid "IP is statically allocated"
+msgstr ""
+
+#: ../../managing_networks.rst:1166
+# 7e45d53e50814ec584c37135e430715f
+msgid "IP need not be associated with a network"
+msgstr ""
+
+#: ../../managing_networks.rst:1170
+# f4869a8c48e8434ea57e20c6cc65cf55
+msgid "IP association is transferable across networks"
+msgstr ""
+
+#: ../../managing_networks.rst:1174
+# 2f9e4bbd9a5c4a61957b15982551f2e9
+msgid "IP is transferable across both Basic and Advanced zones"
+msgstr ""
+
+#: ../../managing_networks.rst:1178
+# ea6d679d393d4bcfa494249d365ba374
+msgid "IP is transferable across VPC, non-VPC isolated and shared networks"
+msgstr ""
+
+#: ../../managing_networks.rst:1182
+# afa26b14dffe40119ee655d8132db452
+msgid "Portable IP transfer is available only for static NAT."
+msgstr ""
+
+#: ../../managing_networks.rst:1187
+# 671509538e074821aee5d282b4fd3822
+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 ""
+
+#: ../../managing_networks.rst:1192
+# a10fe6016ca4432d9466323adc5feafa
+msgid "Configuring Portable IPs"
+msgstr ""
+
+#: ../../managing_networks.rst:1200
+# 323070f73d46451b97228b1b4aadaa54
+msgid "In the left navigation, click Regions."
+msgstr ""
+
+#: ../../managing_networks.rst:1204
+# 428125e4de8d4140af2bbdfcd4ecc332
+msgid "Choose the Regions that you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:1208
+# eed1d708ff224966a3d021ab2bc33aa6
+msgid "Click View Portable IP."
+msgstr ""
+
+#: ../../managing_networks.rst:1212
+# abc03c1eb418441fb10a7cf6beb37fea
+msgid "Click Portable IP Range."
+msgstr ""
+
+#: ../../managing_networks.rst:1214
+# 595f33e914024c0a86540527bc370258
+msgid "The Add Portable IP Range window is displayed."
+msgstr ""
+
+#: ../../managing_networks.rst:1222
+# ca11f239cc8449a6817014a3adcd61a0
+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 ""
+
+#: ../../managing_networks.rst:1229
+# 6c64c167231b40a68bfe26799c8054c3
+msgid "**Gateway**: The gateway in use for the Portable IP addresses you are configuring."
+msgstr ""
+
+#: ../../managing_networks.rst:1234
+# 83455a09e71a4eccb3755e02bd14515c
+msgid "**Netmask**: The netmask associated with the Portable IP range."
+msgstr ""
+
+#: ../../managing_networks.rst:1238
+# 7b8fbceeaf074302abbd838f0e2849bf
+msgid "**VLAN**: The VLAN that will be used for public traffic."
+msgstr ""
+
+#: ../../managing_networks.rst:1245
+# d850eac9d4014f0dab3417fab28601f7
+msgid "Acquiring a Portable IP"
+msgstr ""
+
+#: ../../managing_networks.rst:1257
+#: ../../managing_networks.rst:3208
+#: ../../managing_networks.rst:3251
+#: ../../managing_networks.rst:3294
+#: ../../managing_networks.rst:3370
+# 3262a0725955438a99e78981176d092f
+# 701bcf108f834cdc9c4ea748e804dab0
+# 2859adde9cb44f6e970e1a0651717bed
+# e93c68f572f04989afefcb87f1716ec4
+# 5efad310be724f029a2e40ffd479c432
+msgid "Click the name of the network where you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:1261
+#: ../../managing_networks.rst:2170
+#: ../../managing_networks.rst:3212
+#: ../../managing_networks.rst:3255
+#: ../../managing_networks.rst:3298
+#: ../../managing_networks.rst:3374
+#: ../../managing_networks.rst:3784
+# 305ab6c53fda46d8adf4a49df4f72b73
+# 3186a0f1dbbd4b36afd65ce287083ef4
+# 77cf6faa7c404c33bddce8721952e2e2
+# 6fbd7a5b4b7e4fe684956b795c3516f8
+# 6662b46aca0349ffb4f7db65473cf5a4
+# e6ede01e32f44d8d9eb51185ac8cca93
+# c003065bf88441dc838fb6ff067c1d46
+msgid "Click View IP Addresses."
+msgstr ""
+
+#: ../../managing_networks.rst:1265
+#: ../../managing_networks.rst:3216
+# 3cb9985604264815812c496744d99e7a
+# b3b02650cb5849d29899feb56b041267
+msgid "Click Acquire New IP."
+msgstr ""
+
+#: ../../managing_networks.rst:1267
+#: ../../managing_networks.rst:3218
+# 0fd88d76e0454a0aafadff6be75ab526
+# 25404011fc7044529f48e7fb157f04ed
+msgid "The Acquire New IP window is displayed."
+msgstr ""
+
+#: ../../managing_networks.rst:1271
+#: ../../managing_networks.rst:3222
+# ead81d2ea1984be4874b71915d73fe10
+# 6fe5747d6b7547a8918070f73c52cc78
+msgid "Specify whether you want cross-zone IP or not."
+msgstr ""
+
+#: ../../managing_networks.rst:1275
+# d4620b5751e246e48d4c00aca1d4a8f3
+msgid "Click Yes in the confirmation dialog."
+msgstr ""
+
+#: ../../managing_networks.rst:1277
+#: ../../managing_networks.rst:3230
+# 99771ddd9716455ba6a961284174f20b
+# 1ff8f2a384d445a8ba816f2443f9a096
+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 ""
+
+#: ../../managing_networks.rst:1282
+# e9a2afafc0df48bcba35924913d45e73
+msgid "Transferring Portable IP"
+msgstr ""
+
+#: ../../managing_networks.rst:1284
+# 65ca926473184157a1cfd41612675661
+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 ""
+
+#: ../../managing_networks.rst:1288
+# 8afb23c700a44791bb6a9fa4690d1649
+msgid "To transfer a portable IP across the networks, execute the following API:"
+msgstr ""
+
+#: ../../managing_networks.rst:1295
+# 55a1869308ee4aed849674dc2535b805
+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 ""
+
+#: ../../managing_networks.rst:1304
+# 3afd351582954a49b746d509abba4eac
+msgid "Multiple Subnets in Shared Network"
+msgstr ""
+
+#: ../../managing_networks.rst:1306
+# 9a2eae7b8f84440f90cd0402d4ed0d76
+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 ""
+
+#: ../../managing_networks.rst:1317
+#: ../../managing_networks.rst:2885
+#: ../../managing_networks.rst:3426
+# 344b838f0b0841728cb18a682c1962e2
+# ca130580b3e848d59bbd0823702a71ad
+# 9d4bbe7d6b854394bcbb260e68f1226a
+msgid "Prerequisites and Guidelines"
+msgstr ""
+
+#: ../../managing_networks.rst:1321
+# 231696a9da0c47e5be1d4fec098a8b7f
+msgid "This feature can only be implemented:"
+msgstr ""
+
+#: ../../managing_networks.rst:1325
+# e11af27c4f9b4a68aa2b824c8d51ef26
+msgid "on IPv4 addresses"
+msgstr ""
+
+#: ../../managing_networks.rst:1329
+# 89a310c9cc9a4cc0b046da60d4db626f
+msgid "if virtual router is the DHCP provider"
+msgstr ""
+
+#: ../../managing_networks.rst:1333
+# 2f901469d8a547669181457a79ea3825
+msgid "on KVM, xenServer, and VMware hypervisors"
+msgstr ""
+
+#: ../../managing_networks.rst:1337
+# 07ac9be1fbd949109da3f8269a75cd31
+msgid "Manually configure the gateway of the new subnet before adding the IP range."
+msgstr ""
+
+#: ../../managing_networks.rst:1342
+# fd0dee06ed544e709ea404a01e2141a4
+msgid "CloudStack supports only one gateway for a subnet; overlapping subnets are not currently supported"
+msgstr ""
+
+#: ../../managing_networks.rst:1346
+# cfe0f1c81e094655b1cf2158397f8beb
+msgid "Adding Multiple Subnets to a Shared Network"
+msgstr ""
+
+#: ../../managing_networks.rst:1358
+# 2239434247834913b8b23dab3f7f896d
+msgid "On Zones, click View More, then click the zone to which you want to work with.."
+msgstr ""
+
+#: ../../managing_networks.rst:1363
+# 52b4f5c3dc6c4c96a91c21e53b5f6ba7
+msgid "Click Physical Network."
+msgstr ""
+
+#: ../../managing_networks.rst:1371
+# d545de9168774122b8d39fe9b88db0f9
+msgid "Click Networks."
+msgstr ""
+
+#: ../../managing_networks.rst:1375
+# 201b95be96f741419b7a53c915e3da38
+msgid "Select the networks you want to work with."
+msgstr ""
+
+#: ../../managing_networks.rst:1379
+# b1dafa11c6dd48aaba7215933fc61640
+msgid "Click View IP Ranges."
+msgstr ""
+
+#: ../../managing_networks.rst:1383
+# 962df84772504a178c0760d6862328be
+msgid "Click Add IP Range."
+msgstr ""
+
+#: ../../managing_networks.rst:1385
+# a8c9f66de4e84e56882ecb276ca04e41
+msgid "The Add IP Range dialog is displayed, as follows:"
+msgstr ""
+
+#: ../../managing_networks.rst:1387
+# ae7f538d814144019a90e1b0ac6f4a3d
+msgid "|add-ip-range.png: adding an IP range to a network.|"
+msgstr ""
+
+#: ../../managing_networks.rst:1393
+#: ../../managing_networks.rst:5063
+# 0884d274eba74f889ae1c3abffff98dd
+# 03a1c57fd13d4fdb9f6c63ec4afcc907
+msgid "All the fields are mandatory."
+msgstr ""
+
+#: ../../managing_networks.rst:1397
+#: ../../managing_networks.rst:5081
+# 8da5ac3902824555b54847009a765ed7
+# fe107d12592248a982087f39da19a41a
+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 ""
+
+#: ../../managing_networks.rst:1404
+#: ../../managing_networks.rst:5098
+# d23bd452fc4d46579356f5ede9152d95
+# af646832ee3f44ebaa1213c5db09bb4a
+msgid "**Netmask**: The netmask for the tier you create."
+msgstr ""
+
+#: ../../managing_networks.rst:1406
+#: ../../managing_networks.rst:5100
+# 86f10e90777a4711964d8a8df3a0e45c
+# 04b52f8b675747ee8a9c73e86c123710
+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 ""
+
+#: ../../managing_networks.rst:1412
+# 3bdc377e66c842a4a3f09450a0832e67
+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 ""
+
+#: ../../managing_networks.rst:1422
+# b6a0de7ae6b643a3b425583d43f6163e
+msgid "Isolation in Advanced Zone Using Private VLAN"
+msgstr ""
+
+#: ../../managing_networks.rst:1424
+# 4f75858c33ec4279a864c4b208e29b2b
+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 ""
+
+#: ../../managing_networks.rst:1435
+# 2b100ae9fa4e4eaea15ed0c9c965697f
+msgid "Isolate VMs in a shared networks by using Private VLANs."
+msgstr ""
+
+#: ../../managing_networks.rst:1439
+# 72cb21f4bdaa4f6c88f7f1253969f497
+msgid "Supported on KVM, XenServer, and VMware hypervisors"
+msgstr ""
+
+#: ../../managing_networks.rst:1443
+# 64e4f6f904e145cc94c88300b2f6f1ec
+msgid "PVLAN-enabled shared network can be a part of multiple networks of a guest VM."
+msgstr ""
+
+#: ../../managing_networks.rst:1447
+# 39b527fd98914ef4ae1f7cd5d5a083c3
+msgid "About Private VLAN"
+msgstr ""
+
+#: ../../managing_networks.rst:1449
+# ffcf29c6500a4e3a897fefd357efafa1
+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 ""
+
+#: ../../managing_networks.rst:1462
+# dadf77ad95da46d29d655fa1b5c88836
+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 ""
+
+#: ../../managing_networks.rst:1471
+# 338ab35c29694e549d0f63e57cf3ecfc
+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 ""
+
+#: ../../managing_networks.rst:1481
+# 1eb75b61178b4a8da29196b19e0755f1
+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 ""
+
+#: ../../managing_networks.rst:1489
+# 3c344baffb3649a3a99b4762947818ae
+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 ""
+
+#: ../../managing_networks.rst:1499
+# a10ac6622d024e57899b845f7e847140
+msgid "For further reading:"
+msgstr ""
+
+#: ../../managing_networks.rst:1503
+# 5efde3c2b6894bd387b0f388d8bdeae3
+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 ""
+
+#: ../../managing_networks.rst:1508
+# 02596ab9a4bd47daaed6a4272e786d9a
+msgid "`Cisco Systems' Private VLANs: Scalable Security in a Multi-Client Environment <http://tools.ietf.org/html/rfc5517>`__"
+msgstr ""
+
+#: ../../managing_networks.rst:1513
+# 886e828c09384218b5bd4f8cd224d968
+msgid "`Private VLAN (PVLAN) on vNetwork Distributed Switch - Concept Overview (1010691) <http://kb.vmware.com>`__"
+msgstr ""
+
+#: ../../managing_networks.rst:1521
+# 6cb7c445963a491caff15981fe0b4ce4
+msgid "Use a PVLAN supported switch."
+msgstr ""
+
+#: ../../managing_networks.rst:1523
+# f7f97cd16eb24ff588d513c2d34ff289
+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 ""
+
+#: ../../managing_networks.rst:1529
+# 09e5467647fd4eb6af74a6c1cb65b159
+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 ""
+
+#: ../../managing_networks.rst:1537
+# 3eb08525c8114e1fade9c52b44c14c59
+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 ""
+
+#: ../../managing_networks.rst:1544
+# e9c74dd366ef45f1be1d0793986d7f73
+msgid "Configure private VLAN on your physical switches out-of-band."
+msgstr ""
+
+#: ../../managing_networks.rst:1548
+# 2ecc130e165749aba238d52a9a7f2486
+msgid "Before you use PVLAN on XenServer and KVM, enable Open vSwitch (OVS)."
+msgstr ""
+
+#: ../../managing_networks.rst:1550
+# 030698129200435e9f708d7cb120c98b
+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 ""
+
+#: ../../managing_networks.rst:1553
+# f6a73d4d4c73444dbf0a403921b5aa74
+msgid "Creating a PVLAN-Enabled Guest Network"
+msgstr ""
+
+#: ../../managing_networks.rst:1613
+# 740911b6b7d14c93bb243f861cbde303
+msgid "**Secondary Isolated VLAN ID**: The unique ID of the Secondary Isolated VLAN."
+msgstr ""
+
+#: ../../managing_networks.rst:1616
+# 33d01a6c72b3484991970c439ebe1b80
+msgid "For the description on Secondary Isolated VLAN, see `Section 15.14.1, “About Private VLAN” <#about-pvlan>`__."
+msgstr ""
+
+#: ../../managing_networks.rst:1679
+# 2c24eb1bc100495989166e76788319c0
+msgid "Security Groups"
+msgstr ""
+
+#: ../../managing_networks.rst:1682
+# d331348078ea4de8a8dc8471c9cc3cce
+msgid "About Security Groups"
+msgstr ""
+
+#: ../../managing_networks.rst:1684
+# f34bf064d0114b288f2f55f17a25f84a
+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 ""
+
+#: ../../managing_networks.rst:1693
+# 5e82a09d657a4767acec9f22d782de51
+msgid "In a zone that uses advanced networking, you can instead define multiple guest networks to isolate traffic to VMs."
+msgstr ""
+
+#: ../../managing_networks.rst:1695
+# 79f27644dfcf4cf788bba960a7f3b5bf
+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 ""
+
+#: ../../managing_networks.rst:1700
+# baa28941d5194fae811bbd88c61df125
+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 ""
+
+#: ../../managing_networks.rst:1707
+# de98d0c1571a4cc18032b6472947663b
+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 ""
+
+#: ../../managing_networks.rst:1711
+# 6e7dbedd8ee140e1ad567e65c7ff552d
+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 ""
+
+#: ../../managing_networks.rst:1716
+# 50b80901d7c24d66a23e838b0f4293d3
+msgid "Adding a Security Group"
+msgstr ""
+
+#: ../../managing_networks.rst:1718
+# f870c727a4ba4b5fafdca88cc7a4b660
+msgid "A user or administrator can define a new security group."
+msgstr ""
+
+#: ../../managing_networks.rst:1726
+#: ../../managing_networks.rst:1803
+# 2bd568db435b4894a6594bdabb71b71f
+# ec651383a1084a9bb247059b0cb38cc8
+msgid "In the left navigation, choose Network"
+msgstr ""
+
+#: ../../managing_networks.rst:1730
+# 20641ac9b26d48a8a2af8025a38b3550
+msgid "In Select view, choose Security Groups."
+msgstr ""
+
+#: ../../managing_networks.rst:1734
+# 3b8b48dea99749bf821c45bf85f5edce
+msgid "Click Add Security Group."
+msgstr ""
+
+#: ../../managing_networks.rst:1738
+# da5c74165969469d9c2395eaaa3f94e6
+msgid "Provide a name and description."
+msgstr ""
+
+#: ../../managing_networks.rst:1744
+# cebb13c23de64a278615d79e7d92b3bc
+msgid "The new security group appears in the Security Groups Details tab."
+msgstr ""
+
+#: ../../managing_networks.rst:1748
+# b0f1a7c4f9d74d0cbf905c6ce03546b8
+msgid "To make the security group useful, continue to Adding Ingress and Egress Rules to a Security Group."
+msgstr ""
+
+#: ../../managing_networks.rst:1752
+# 0c59765ee0c64629952434a87beb9d81
+msgid "Security Groups in Advanced Zones (KVM Only)"
+msgstr ""
+
+#: ../../managing_networks.rst:1754
+# 33c22ff2d84d4c149fb2a3ba75f8689f
+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 ""
+
+#: ../../managing_networks.rst:1760
+# 0d98099524ba4909b604a7399ffc1bd8
+msgid "Limitations: The following are not supported for this feature:"
+msgstr ""
+
+#: ../../managing_networks.rst:1764
+# cfee500d52ad40699096b1a8e4e389c1
+msgid "Two IP ranges with the same VLAN and different gateway or netmask in security group-enabled shared network."
+msgstr ""
+
+#: ../../managing_networks.rst:1769
+# 6246185f1f154f93875963e698243930
+msgid "Two IP ranges with the same VLAN and different gateway or netmask in account-specific shared networks."
+msgstr ""
+
+#: ../../managing_networks.rst:1774
+# 1d7c154fd0c34eaf9711d6ec05f84dee
+msgid "Multiple VLAN ranges in security group-enabled shared network."
+msgstr ""
+
+#: ../../managing_networks.rst:1778
+# d31b3ceda7e84ff09119957ddcbbdf2b
+msgid "Multiple VLAN ranges in account-specific shared networks."
+msgstr ""
+
+#: ../../managing_networks.rst:1780
+# 6eeb1f2182894bc383d39cb1f701fb27
+msgid "Security groups must be enabled in the zone in order for this feature to be used."
+msgstr ""
+
+#: ../../managing_networks.rst:1784
+# d9c879f6880c426dbe5cc14699e86c87
+msgid "Enabling Security Groups"
+msgstr ""
+
+#: ../../managing_networks.rst:1786
+# 6038307bd32f4032b2cf2283627e5084
+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 ""
+
+#: ../../managing_networks.rst:1795
+# 9239428930ac475c8787a1fa5c7b5852
+msgid "Adding Ingress and Egress Rules to a Security Group"
+msgstr ""
+
+#: ../../managing_networks.rst:1807
+# 1dabe90dfbf742b1ad863dda6a7370cf
+msgid "In Select view, choose Security Groups, then click the security group you want ."
+msgstr ""
+
+#: ../../managing_networks.rst:1812
+# 14c6cdb0f76f4e5bafb8a8247c89a3f5
+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 ""
+
+#: ../../managing_networks.rst:1820
+# dbc6db6a8f164564b90b36fb8600f6c4
+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 ""
+
+#: ../../managing_networks.rst:1828
+# c7404bcf0635456b924a7d4461860444
+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 ""
+
+#: ../../managing_networks.rst:1835
+# 553fb9fc05c647d38e4c15f2ccbb5123
+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 ""
+
+#: ../../managing_networks.rst:1841
+# f1ac0dd3df2a46ad8b321cc49981a565
+msgid "**ICMP Type, ICMP Code**. (ICMP only) The type of message and error code that will be accepted."
+msgstr ""
+
+#: ../../managing_networks.rst:1846
+# 4b14903d5adb4c9a8301a393218c0fe9
+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 ""
+
+#: ../../managing_networks.rst:1854
+# c1561e01a67747a699e6e8f0b8d265a1
+msgid "**Account, Security Group**. (Add by Account only) To accept only traffic from an

<TRUNCATED>