You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/07/29 10:21:48 UTC

[jira] [Commented] (CLOUDSTACK-3870) [VMware] Management traffic network over a VLAN is not working

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-3870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722258#comment-13722258 ] 

ASF subversion and git services commented on CLOUDSTACK-3870:
-------------------------------------------------------------

Commit 460fe86eb52beba2cf00b9d8ed339821c0ca67a9 in branch refs/heads/4.2 from [~sateeshc]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=460fe86 ]

CLOUDSTACK-3870 [VMware] Management traffic network over a VLAN is not working

CLOUDSTACK-3437 In case of multiple physical network setup we see log message "can't get physical network"

CloudStack's control network is management network in case of VMware.
Processing management VLAN id provided in zone traffic label for management traffic.`

Signed-off-by: Sateesh Chodapuneedi <sa...@apache.org>

                
> [VMware] Management traffic network over a VLAN is not working
> --------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3870
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3870
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: VMware
>    Affects Versions: 4.2.0
>            Reporter: Sateesh Chodapuneedi
>            Assignee: Sateesh Chodapuneedi
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> Cloudstack picks up management traffic information from network label specified in zone creation wizard. If user specifies "<vswitchname>,<vlanid>" it has to be picked up. It's not working right now.

--
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