[
https://issues.apache.org/jira/browse/CLOUDSTACK-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13680010#comment-13680010
]
Venkata Siva Vijayendra Bhamidipati commented on CLOUDSTACK-2888:
-----------------------------------------------------------------
Angie, whether or not the svlan and pvlan IDs are configured correctly on the
underlying infrastructure is irrelevant to cloudstack. As far as cloudstack is
concerned, the pvlan and svlan IDs are acceptable as long as they are valid
vlan IDs. Having two secondary VLAN IDs associated with the same promiscuous
VLAN ID is valid. Our aim in using PVLAN is basically to seal off VMs belonging
to the same isolated VLAN from each other. If they're in different isolated
VLANs, they will be able to talk to each other via the router VM, regardless of
the promiscuous VLAN they are associated with.
> PVLAN - Ubuntu 13.04 vmware - should not allow networks with different
> primary VLAN with same Secondary VLAN, same primary VLAN with different
> Secondary VLAN
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-2888
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2888
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.2.0
> Environment: MS ASF 4.2 build
> CloudStack-non-OSS-MASTER-452-rhel6.3.tar.gz
> vmware ESXi 5.0 hosts
> ubuntu 13.04 hosts
> Reporter: angeline shen
> Assignee: Venkata Siva Vijayendra Bhamidipati
> Fix For: 4.2.0
>
> Attachments: management-server.log.gz
>
>
> Given:
> pvlan1 = 1611 svlan1 = 998
> pvlan2 = 1612 svlan2 = 997
> nonexistent svlan3 = 999
> Following PVLAN networks SHOULD NOT HAVE BEEN ALLOWED to be created :
> pvlan1 , svlan2
> pvlan1 , svlan3
> pvlan2 , svlan1
> pvlan2 , svlan3
> Result: Above PVLAN networks were allowed to be created
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
