[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Murali Reddy reassigned CLOUDSTACK-5611:
----------------------------------------

    Assignee: Murali Reddy

> Can't create shared network with the same vlan being userd for Public Traffic 
> but  with different IP range
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5611
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5611
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Hypervisor Controller, Management Server
>    Affects Versions: 4.3.0
>         Environment: Latest build from 4.3 branch with 
> commit:d462db4ae5c30e677d5810111f9ea5ca6812bce2
>            Reporter: Sanjeev N
>            Assignee: Murali Reddy
>            Priority: Critical
>             Fix For: 4.3.0
>
>
> Can't create shared network with the same vlan being userd for Public Traffic 
> but  with different IP range
> Steps to Reproduce:
> =================
> 1.Bring up CS in advanced zone with Hypev cluster
> 2.Use tagged vlan ip range say: 10.147.48.0/24 with range 10.147.48.3-20 for 
> public traffic with vlan id 48.
> 3.Deploy couple of guest vms.
> 4.Try to create a shared network with vlan 48 with ip range from 10.147.48.30 
> to 10.147.48.40.
> Expected Result:
> ===============
> Should be allowed to create shared network with the vlan same as public 
> traffic.
> Actual Result:
> ===========
> Shared network creation failed with the following error:
> The IP range with tag: vlan://48 in zone Adv has overlapped with the subnet. 
> Please specify a different gateway/netmask.
> CS should not allow to create multiple shared networks with CIDR/subnet, but 
> should be ok to allow shared network and public traffic in the same subnet 
> without overlapping IP ranges.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to