Hi Keith, my nested vcenter does not participate in the management network unless I enable Promiscuous mode on the port groups? But you have it disabled why is that?
Thank you for the question. @bluesblue6453 In my nested lab I am using the 192.168.1.0/24 network (all in the same VLAN) for the management PC, physical server iDRAC, ESXi physical server management IP, Nested ESXi servers management IPs, as well as both the parent and nested vCenter management IPs. As a result, shouldn't need to have promiscuous ports anywhere. let me know if that helps.
I would prefer to deploy the second Vcenter server on the physical host instead of the nested environment. Just easier and will most likely have better performance than the nested one
Amazing content. Thank you Keith 😎
Thank you @7onysWorld!
Hi Keith, I had the same problem as Bluesblue, In order to pass all the traffic I have enable Promiscuous mode
Thank you @alaindjite9776! Interesting. I'm not sure why that would be required.
Hi Keith, my nested vcenter does not participate in the management network unless I enable Promiscuous mode on the port groups? But you have it disabled why is that?
Thank you for the question. @bluesblue6453
In my nested lab I am using the 192.168.1.0/24 network (all in the same VLAN) for the management PC, physical server iDRAC, ESXi physical server management IP, Nested ESXi servers management IPs, as well as both the parent and nested vCenter management IPs.
As a result, shouldn't need to have promiscuous ports anywhere.
let me know if that helps.
I would prefer to deploy the second Vcenter server on the physical host instead of the nested environment. Just easier and will most likely have better performance than the nested one
Thank you @Nimitz_oceo!
I agree! Later in the series, I did a cross-vCenter migration of the nested vCSA to get it 1 level closer to the hardware.