Community
 
 
 

CloudPlatform 3.x

343 abonnés
 
Avatar
Pankaj Paliwal

Bizzare Networking with VMWare

Avatar

Bizzare Networking with VMWare

Hello All,

I seem to be banging my head against a wall with the way Cloud Platform deals with networking, so I'm hoping you lovely people can help me shed some light on the issues?

I am trying to add vCentre to my cloud platform installation and am using the Advanced Networking options when I add my zone. However, the vSwitch configuration doesn't seem to make sense. Before going into the issue, it may help that I run through my configuration:

Required Networks:

Public:
This is basically my DMZ for all clients (their virtual routers will recieve an IP on this network)

IP Range: 192.168.10.191 to 192.168.10.250
Default Gateway: 192.168.10.254 (currently a Cisco Device)
vlan: 13
VMWare Tag: vSwitch0

Private - Management
I believe this is used for CloudPlatform management tasks.

IP Range: 192.168.15.191 to 192.168.15.250
Default Gateway: 192.168.15.254 (currently a Cisco Device)
vlan: 815
VMWare Tag: vSwitch1

I also have a Netapp vfiler that has exported my secondary storage.

Private - Guest Traffic
This will be the guest network switch.

vlan Range: 500 to 900
VMWare Tag: vswitch0

Management Server:
I have my management server that is has two NICS, one is in both the management and public networks (this in in seperate PortGroups on a dedicated vswitch).

The Issue:

So this is all well and good. At the moment, I can ping between my Management and Public vlans (bear in mind this is a lab) from my Management Server.

So when I add the zone, pod, cluster and storage the process starts to build my System VMs. The first steps to this will create me the following PortGroups:

cloud.public.13.0.1-vSwitch0
cloud.private.untagged.0.1-vSwtich0
cloud.storage.untagged.0.1-vSwitch1
cloud.private.untagged.0.1-vSiwtch1

The ones that are in italic do not have a vlan tag. This is causing the management server to loose touch with the system VMs. If I manually tag the port group or reconnect my management server/VMs to a port group with the correct tags, it all works.

So here is my question, am I setting everything up correctly, and this is just how cloudstack does it?

Is there a way I can force my portgroup for Management/Storage to use a dedicated vlan (815 in this case)?

Thanks

Paul


Paul Sanders MEMBERS
2 commentaires
0

Vous devez vous connecter pour laisser un commentaire.

 
 

Previous 2 commentaires

Avatar
Pankaj Paliwal
Avatar

Bizzare Networking with VMWare

I have managed to work around this by setting the native vlan to my management network. Is there another way?

Thanks

Paul


Paul Sanders MEMBERS
Actions pour les commentaires Permalien
Avatar
Pankaj Paliwal
Avatar

Hi, Paul. It looks like you did not configure the traffic label for the management (private) network. You should input the traffic label as "vswitchname,vlanid" if you want the management network on a VLAN in vSphere. For example, to put the management traffic on a port group with VLAN 815 on vSwitch0, use "vSwitch0,815". The management network traffic label is configured in Infrastructure > Zones (select the zone) > Physical Network tab (select the physical network with management traffic) > Management (click Configure). See the attached screen shot.

Best regards,

{color:#555555}Kirk Kosinski{color} !http://www.linkedin.com/favicon.ico!
{color:#999999}MCITP: EA / VA / EDA7, VCP 4 / 5, CCA{color}

Attached Files


Kirk Kosinski CITRIX EMPLOYEES
Actions pour les commentaires Permalien

Top Contributors