This content has been marked as final. Show 1 reply
I assume you're talking about the "Virtualized Network Expansion Module" (HXGE). The system is not a Layer 2 switch, as you're describing. Rather, it merely shares PHY connections to individual MACs on each blade (provided you have the right Fabric Expansion Module on the blade). So, any packets you receive on one of the VNEM's uplink ports is seen by every blade, according to the "failover" settings of the VNEM (e.g. if both uplinks are active, blades 0 - 4 see VNEM uplink 0 and blades 5-9 see uplink 1). There's no way to "filter" packets based on VLAN via the VNEM.
To answer your questions:
1) If you want every blade to see traffic from a particular VLAN and only that VLAN, then you do not want a trunk port. You want an "access" port, and assign the default VLAN accordingly. If you intend to do any VLAN based networking on any of the blades, then yes, you want a 802.1q trunk port. At that point, it depends on the OS layer on each blade to deal with VLAN tagging appropriately. Solaris 10 and VMware seem to handle this just fine, but I've had issues with WIndows Server 2008 R2 (but possibly only because I'm new to Hyper-V networking).
2) I assume you're talking about configuring VLAN tagging in Solaris 10. That's easy. You just multiply the VLAN ID number by 1000, then add the device ordinal. For example, with two VNEMs in our chassis, each blade will see /dev/hxge0 and /dev/hxge1. To assign an IP to VLAN 11 on hxge1, you plumb hxge11001. For VLAN 5 on hxge0, you would plumb hxge5000, etc. Note that if you do not use VLAN tagging in the OS (i.e. hxge0 or hxge1), all traffic will be sent on the default VLAN assigned by the switch.
3) I just did :)