怎样在xenserver中设置没有默认网关的ip.docVIP

How to Set up XenServer in a Routed Network Document ID: CTX121169 ??/?? Created On: 2010-2-4 ??/?? Updated On: 2010-2-4 Average Rating: (2 ratings) View products this document applies to? Summary In some cases (such as hosting environments), multiple subnets of IP addresses are provided on a single interface where subnets other than the original are not assigned a default gateway. This configuration works when an IP interface exists within the same subnet as the default gateway from the primary subnet, however this is not always possible. The diagram below depicts this scenario: In this case, if a VM is configured within the 172.16.20.0/24 subnet, the customer’s default gateway (172.16.1.1) cannot be used and connectivity to subnets other than 172.16.20.0/24 isn not possible. Whenever possible, you should configure the default gateway for the secondary subnets as secondary IP addresses on the VLAN. This action completely avoids the need for complex workarounds. Notice This article makes changes to the XenServer configuration which, if made improperly, might prevent network access to the host or compromise security. These changes might also be overwritten after updates or upgrades between XenServer releases. Requirements One or more XenServer hosts configured with an existing management IP address in the same subnet as the default gateway. To implement this procedure, it is assumed that you have basic Linux (such as editing files) and networking knowledge. Background XenServer is designed to allow a single IP address per management interface. In addition, XenServer does not by default facilitate routing between IP interfaces as this can compromise system security if not implemented properly. For XenServer to work effectively in this type of environment, it must be configured to: 1. Allow one or more secondary IP addresses to be configured on a given management interface. 2. Enable forwarding between IP interfaces. 3. Configure the in-built IPTables firewall to