Hi Alex, thanks a lot for the detailed explanations :-)
Best regards, Christian -----Ursprüngliche Nachricht----- Von: Alex Mattioli [mailto:alex.matti...@shapeblue.com] Gesendet: Montag, 4. November 2024 16:29 An: users@cloudstack.apache.org Betreff: RE: CloudStack is creating several PortGroups on DSwitch for the same VLAN Hi Christian, The number after vlan ID is the bandwidth allowed, which can be set in a network offering level, compute offering level, global, etc... So it might happen that the bandwidth allowed for the network is, for example, 300mbps. But for the compute offering of a certain VM it is 200mbps, in that case you'll end up with two port groups in the same vlan, but different bandwidth shaping, in this case: cloud.guest.VLAN-ID.200.1-DSwitch-Service and cloud.guest.VLAN-ID.300.1-DSwitch-Service Check the Traffic shaping of those portgroups and it will make more sense :) In order to ensure all VMs are in the same portgroup you need to set the same bandwidth for the compute offering, or leave it blank so the global setting is used. You'd also need to match the bandwidth of the compute offerings (or global setting) with the bandwidth of the network offering. Hope that explains what you need Cheers Alex From: Christian Reichert <christian.reich...@scsynergy.com.INVALID> Sent: 04 November 2024 16:02 To: 'users@cloudstack.apache.org' <users@cloudstack.apache.org> Subject: CloudStack is creating several PortGroups on DSwitch for the same VLAN Hi all, we are running CloudStack on vmware ESXi Hypervisor. Sometimes CloudStack is creating several port groups for the same VLAN-ID. Always end on cloud.guest.VLAN-ID.200.1-DSwitch-Service, .300 .500 The instances belong not all to the same Port-Group depending on when they were created. No we noticed some communication problems between the instances. If I change the NIC in the vCeneter to the same port group for all instances, the communication works. My question, why is this happening and how can I get CloudStack to connect all VMs to the same port group? CS 4.18.2.3 and vCenter 7.0.3 I look forward to every hint Best regards, Christian
smime.p7s
Description: S/MIME cryptographic signature
