You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Andrija Panic (JIRA)" <ji...@apache.org> on 2014/10/13 14:09:33 UTC
[jira] [Commented] (CLOUDSTACK-6814) Detected overlapping subnets
in differents vlans
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14169213#comment-14169213 ]
Andrija Panic commented on CLOUDSTACK-6814:
-------------------------------------------
Hi,
any update on this ? True, this is similar issue, but it says in https://issues.apache.org/jira/browse/CLOUDSTACK-4282 that it is resolved in 4.2 verisons, which, for my case is not true - this is overlaping IP range between guest and Public network, not between 2 guest networks...
Any plan on fixing this, or not - I would really appreciate info, to be able to proceed with another Cloudstack deployment...
> Detected overlapping subnets in differents vlans
> ------------------------------------------------
>
> Key: CLOUDSTACK-6814
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6814
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server, Network Controller
> Affects Versions: 4.3.0
> Environment: not relevant
> Reporter: Andrija Panic
> Priority: Critical
> Labels: guestnetwork, network, overlap, publicip
>
> I have both Public IP(untagged) and Guest IP range (vlan 500) on same physical network device eth1 (infrastrucure-zones-physical network-eth1public tag...) Don't ask me how/why, but it works and it had worked from CS 4.0.0 till now...
> In previous versions I was able to add few additional IP addresses from the /24 subnet to Guest IP range..
> In 4.3, there is an error message saying that Guest IP range and Public IP range has overlaping subnets - which IS true - but since those networks ARE on different vlans completely, I'm not sure why there is such check at all (overlaping subnet check). Different vlans means different broadcast domains, why checking IP parameters across different vlans...
> Existing database records - first row is Public IP range, rest is all smaller ranges of IP addresses added few times for Guest IP range.
> mysql> select id,uuid,vlan_id,vlan_gateway,vlan_netmask,description from cloud.vlan;
> +----+--------------------------------------+-----------------+--------------+---------------+-------------------------------+
> | id | uuid | vlan_id | vlan_gateway | vlan_netmask | description |
> +----+--------------------------------------+-----------------+--------------+---------------+-------------------------------+
> | 1 | 10a1e453-7369-4645-9e0f-4936c18bfeac | vlan://untagged | 46.232.xxx.1 | 255.255.255.0 | 46.232.xxx.240-46.232.xxx.248 |
> | 3 | 76c30667-e4c9-4bfe-84cc-3c8e5c608770 | 500 | 46.232.xxx.1 | 255.255.255.0 | 46.232.xxx.220-46.232.xxx.238 |
> | 4 | e2b2b09b-81f2-4ec0-9323-b4c626fcd63b | 500 | 46.232.xxx.1 | 255.255.255.0 | 46.232.xxx.210-46.232.xxx.219 |
> | 5 | f810fd59-ea8a-44fb-850e-58eb791191f0 | 500 | 46.232.xxx.1 | 255.255.255.0 | 46.232.xxx.202-46.232.xxx.209 |
> | 8 | f0bec296-3ac8-483c-a23a-b36213fdf846 | 500 | 46.232.xxx.1 | 255.255.255.0 | 46.232.xxx.131-46.232.xxx.201 |
> +----+--------------------------------------+-----------------+--------------+---------------+-------------------------------+
> Now when I want to add new range 46.232.xxx.100-46.232.xxx.130 to eather Public or Guest network - I can't do that and getting folowing error (tried adding it to Public range here):
> "The IP range with tag: 500 in zone DC-ZURICH-GLATTBRUGG has overlapped with the subnet. Please specify a different gateway/netmask."
> This subnet check across differenet vlans should be removed, and I'm stuck with over 90% used IP addresses, and can't add more from same /24 range that we got...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)