cloudstack/docs/en-US/multiple-ip-range.xml

42 lines
2.4 KiB
XML

<?xml version='1.0' encoding='utf-8' ?>
<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN" "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
<!ENTITY % BOOK_ENTITIES SYSTEM "cloudstack.ent">
%BOOK_ENTITIES;
]>
<!-- Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements. See the NOTICE file
distributed with this work for additional information
regarding copyright ownership. The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied. See the License for the
specific language governing permissions and limitations
under the License.
-->
<section id="multiple-ip-range">
<title>About Multiple IP Ranges</title>
<note>
<para>The feature can only be implemented on IPv4 addresses.</para>
</note>
<para>&PRODUCT; provides you with the flexibility to add guest IP ranges from different subnets in
Basic zones and security groups-enabled Advanced zones. What it implies in the case of security
groups-enabled Advanced zones is 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 during IP address exhaustion. To support this feature, the capability of
<code>createVlanIpRange</code> API is extended to add IP ranges also from a different
subnet.</para>
<para>As an admin, you should manually configure the gateway of the new subnet before adding the
IP range. &PRODUCT; supports only one gateway for a subnet; overlapping subnets are not
currently supported.</para>
<para>Use the <code>deleteVlanRange</code> 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, &PRODUCT; acquires a new IP from the same subnet. If no IP is available in
the subnet, the remove operation fails.</para>
<para>This feature is supported on KVM, xenServer, and VMware hypervisors.</para>
</section>