[
https://issues.apache.org/jira/browse/CLOUDSTACK-7364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14235434#comment-14235434
]
Francois Gaudreault commented on CLOUDSTACK-7364:
-------------------------------------------------
Thanks for reopening the case Rajesh.
There is a functionality impact, the ability to efficiently dedicate public
subnet. As soon as you have to manage more than 1 public VLAN on a zone, you
have to make sure each Netscaler has an interface on each public VLAN. Also,
when you add new VLANs after you provisioned the NetScaler, these old
NetScalers also need to have that new interface added, and that causes downtime
because they need a reboot.
I think it's fair to say it impacts functionality.
> NetScaler won't create the Public VLAN and Bind the IP to it
> ------------------------------------------------------------
>
> Key: CLOUDSTACK-7364
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7364
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.3.0, 4.4.0, 4.4.1
> Reporter: Francois Gaudreault
> Assignee: Rajesh Battala
> Priority: Critical
> Fix For: 4.6.0
>
> Attachments: 10_1NS_vlan_ip_if.png, 10_5_NS_vlan_ip_if.png,
> management-server.log.debug.gz, screenshot-1.png, screenshot-2.png
>
>
> When adding a Load Balancing rule with the NetScaler, the provider will tag
> and bind the private IP to the appropriate interface. However, the behaviour
> for the Public Interface is different. It simply adds the IP untagged on all
> interfaces. This is wrong.
> The public VLAN should be tagged, and the VIP bound to the right VLAN tag to
> avoid unnecessary ARP on other VLANs.
> NS Version tested: 123,11, 127.10, 128.8
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
