BladeSystem Virtual Connect
cancel
Showing results for 
Search instead for 
Did you mean: 

VCEM 1.30 - VC 2.10 - Multiple Networks with 1 native - Odd behaviour

 
Alex Haddock
Occasional Advisor

VCEM 1.30 - VC 2.10 - Multiple Networks with 1 native - Odd behaviour

Hi all, may need to log a call for this but just in case anyone has seen it before. Chassis#1 not managed by VCEM. Shared Uplink set. Mapped. I can go in to the server profile, choose multiple networks and set one to untagged. Once I've clicked apply everything is green, all connections work as expected down to the ESX hosts. I then have a production group imported in to VCEM (same hardware, firmware, networks as the unmanaged one above). When I follow the same process as Chassis#1 (but through VCEM this time) I can apply the profile but the network is dropped. Looking in the server profile it now reads as unassigned. Removing the untagged VLAN flag results in it taking correctly and being assigned. So it seems that for some reason I can't apply a native VLAN on a multiple network using VCEM 1.30 but I can on a standalone chassis with the same config. Any ideas? Cheers [Updated on 6/23/2009 11:38 AM]