I have a second pod in the same zone and this pod has a separate subnet for its 
management network. In the settings for the management network I have a VLAN 
assigned.

However, when a system VM is placed on the cluster in this pod, such as a 
console proxy, it pulls the appropriate private IP address for the pod, but it 
does not do it as a VLAN interface.  Since this pod requires tagging for some 
of the functions, The console proxy cannot get to the management server, since 
it's interface is not tagged with the appropriate VLAN for the management 
network on that pod.

Am I missing something? Should it not create a VLAN interface on the console 
proxy VM if the pod has a VLAN tag set for it in the zone settings? I don't 
have the little check box that says system VMS checked for that IP range of the 
second pod. So why would it put it there in the 1st place if that is not 
checked?

As always thank you for the help.

Marty


Reply via email to