Using Multiple VLANs with HP Virtual Connect Flex-10

In this article on using VMware ESX Virtual Switch Tagging (VST) with HP Virtual Connect, I showed you how to use the Multiple VLANs setting to map multiple VLANs onto a network connection so that the VLAN tags would pass all the way up to the VMware ESX/ESXi host—a necessary prerequisite for making VST work.

However, there is a key caveat to this approach that applies when using HP Virtual Connect Flex-10 and HP blades that have Flex-10 LOM (LAN on Motherboard) interfaces. As you might already know, Flex-10 LOMs have the ability to “subdivide” themselves into four logical instances, each of them a valid PCIe function, which are called FlexNICs. These FlexNICs appear as real, actual, physical NICs to the operating system installed on the blades. This includes VMware ESX/ESXi. In the Virtual Connect Manager, though, you have the ability to fine-tune the amount of bandwidth allocated to each of these FlexNICs, up to the shared maximum of 10Gbps.

This is pretty cool, but there is one limitation of which you must be aware—a limitation that is particularly significant in VMware ESX/ESXi environments. When you use the Multiple Networks option to map multiple VLANs onto a FlexNIC, you can’t map the same VLAN onto two different FlexNICs from the same LOM.

The FlexNICs are noted as LOM 1:a, LOM 1:b, LOM 2:a, etc. Again, as noted earlier, up to four FlexNICs are presented to the operating system on the blade. When you start assigning network connections in a Server Profile in Virtual Connect Manager, these network connections will bounce back and forth between the LOMs (assuming there are no other network interface cards in the server blade):

First network connection > LOM 1:a
Second network connection > LOM 2:a
Third network connection > LOM 1:b
Fourth network connection > LOM 2:b

Seventh network connection > LOM 1:d
Eighth network connection > LOM 2:d

As far as I know, there is no way to change this behavior.

With that in mind, what this means is that you can’t map the same VLANs to the first, third, fifth, and seventh network connections, or to the second, fourth, sixth, or eighth network connections. Why? Because each of these connections are logical FlexNICs on the same LOM, and you can’t map the same VLANs to more than one FlexNIC on the same LOM.

Perhaps an example would help. Consider the configuration shown in this figure, in which multiple VLANs are mapped to all eight connections in Virtual Connect Manager:

hp-flex10-vlans-incorrect.png

This screenshot shows how the VLANs are mapped for each of those eight network connections:

hp-flex10-vlan-mapping.png

As you can see, I have the same set of five VLANs mapped onto all eight network connections (all eight logical FlexNIC instances). But only the first two show OK—the rest show Critical. Why? Because these logical FlexNICs have the same VLANs mapped to them as were mapped to the first FlexNIC, and therefore Virtual Connect Manager has placed them into a Critical state (they’ll be reported as “Down” to an operating system on the blade).

This behavior is the strange behavior I tweeted about a few days ago, where I couldn’t figure out why Virtual Connect was behaving in the way that it was. Now I know why!

Contrast that first configuration with the configuration shown in this screenshot:

hp-flex10-vlans-correct.png

In this case, you’ll note that I do not have the same VLANs mapped to more than one FlexNIC on the same LOM. As a result, Virtual Connect Manager does not place any of the FlexNICs into a Critical state, and all eight show OK (and will be reported as Up to an operating system on the blade).

So what does this mean? In its simplest terms, it means you can’t use VST on all the FlexNICs—some of the FlexNICs will have to carry “ordinary” traffic to VMware ESX/ESXi port groups that have no VLAN ID specified. In the image above, you can see that the first three pairs of FlexNICs each carry a specific type of traffic. The matching output of esxcfg-vswitch --list for this VMware ESX host shows that the port groups on each of the three matching vSwitches do not have any VLAN IDs specified. This is because, in this configuration, these three pairs of FlexNICs carry only a single type of traffic, and that single type of traffic has no VLAN tags attached. Therefore, the VMware ESX/ESXi port groups must not have a VLAN ID specified in order for traffic to flow.

But it also presents some other interesting design considerations. If your VMware ESX Service Console (or VMware ESXi Management interface) is on the same VLAN as some of your virtual machines, you’ll run into an issue—you won’t be able to map the VLAN to one set of FlexNICs for Service Console traffic and then map that same VLAN to another set of FlexNICs for other virtual machine traffic. In effect, it greatly reduces the extent to which you can use VST on VMware ESX/ESXi hosts.

Of course, the other way of handling it is to assign only two network connections, map multiple VLANs to those network connections, assign the full 10Gbps of throughput to those two FlexNICs (network connections), and use a single vSwitch design.

As far as I can tell, this is not documented by HP in the Virtual Connect (or Flex-10) documentation. So, you might want to bookmark this article, or post it to Delicious.com or similar. Finally, as always, I’d love to hear any feedback or clarifications in the comments. Thanks!

Tags: , , ,

  1. Rob L.’s avatar

    Scott,

    Let me fill you in on a few other limitations of Virtual Connect and Flex-10 right now.

    If you need to make any changes to a server profile like adding a VLAN or adjusting the bandwidth of the Flex NICs you have to reboot the host. It is an issue in our environment where we have many VLANs and having to add one to an ESX host to support a new VM is not unusual.

    The previous Virtual Connect firmware version had a limitation that you could only map up to 32 VLANs from an uplink set. Again we use many VLANs and were bordering on this limit. The new firmware has increased this to 64. But the other limitation of the previous firmware is that you could map up to 28 vNetworks(VLANs) to a single FlexNIC. We have not got confirmation from HP that this number has increased with the latest firmware.

    Virtual Connect can’t take down the link of an individual FlexNIC, it can only take down the link of the whole physical NIC(all 4 FlexNICs). This is a problem if you use link status to do ESX network fault tolerance. Virtual Connect has a feature called Smart Link that if a Virtual Connect uplink goes down it will take down the server links. But again it can only take down the whole physical NIC and only if the all uplinks for all the vNetworks that are mapped to all 4 FlexNICs go down.

    I know HP is aware of some of these limitations and has stated they will be addressed in future firmware releases.

  2. slowe’s avatar

    Rob L,

    Thanks for the additional information. I was already aware of the need to have a server powered down in order to modify the Server Profile, but it is helpful to point that out again. If there is one limitation that HP most needs to address, it’s this one, IMHO.

    Similarly, the limitations on the number of VLANs and the number of VLANs that can be mapped to a single FlexNIC could similarly be problems for larger environments.

    As for the Smart Link limitation (not being able to take down a single FlexNIC), I don’t see that as a limitation–that makes sense to me. If an uplink goes down, you would WANT all four FlexNICs to go down because they all ride the same uplink (or same set of uplinks).

    Thanks for your comment!

  3. Matt’s avatar

    Thanks for taking the time to write this article, very useful as we are deploying vSphere on BL685s with Flex-10 VC modules.

    Does this scenario only happen with VLAN mapping or does it apply to VLAN tunelling as well?

  4. slowe’s avatar

    Matt,

    I do not know if there are similar limitations with VLAN tunneling. That is on my test plan, so I’ll post results here as soon as I have more information.

  5. Chris B (HP)’s avatar

    Scott,

    Thanks for taking the time to evaluate Virtual Connect. HP’s Virtual Connect with Flex-10 enables our customers to use VST on all FlexNICs providing they use different VLANs on each FlexNIC LOM. Replicating FlexNIC configurations between LOMs allows for teaming and chip-level redundancy. There is no advantage to using the same VLANs one each FlexNIC beyond the additional bandwidth; something easily tuned using the bandwidth parameter on each individual FlexNIC.

    Another alternative to mapping a VLAN to independent sets of FlexNICs for Console traffic and VM traffic would be to define two different Virtual Connect networks, one for service console traffic, and the other for the VM traffic. Virtual Connect will keep these two networks completely isolated, but you can bridge them externally. In many cases, it is desirable to keep those two separate anyway.

    Thanks again, we look forward to more insight.

    Chris

  6. slowe’s avatar

    Chris B,

    Thanks for adding your comments! I appreciate it. To help further drive home your point about presenting multiple VLANs to the FlexNICs, I’ve posted this follow-up:

    http://blog.scottlowe.org/2009/07/09/follow-up-about-multiple-vlans-virtual-connect-and-flex-10/

    Thanks again!

  7. Matt’s avatar

    I’m implimenting Flex-10 on BL460-G6 blades. I really don’t need the Flex-NICs, I’m just tunneling all the VLANs to the ESx servers. What I find anoying is the 6 dead links with no links, it is two bad there isn’t a way to make the unused Fle-NICs to go away. The bigger problem I have is a poorly documented problem, you can mix Virtual connect modules in one chassis, but a Flex-10 can not be in a slot next to a VC ethernet module. Anybody want to swap a VC ethernet for a Flex-10 module?

  8. Brad Hedlund’s avatar

    Scott,

    In this article you said: “you have the ability to fine-tune the amount of bandwidth allocated to each of these FlexNICs, up to the shared maximum of 10Gbps.”

    Question: Is the “Allocated” bandwidth for a FlexNIC a maximum not-to-exceed bandwidth? Or, is “Allocated” bandwidth a minimum guaranteed bandwidth with the ability to go higher if bandwidth is unused/available?

    In other words, suppose I have (2) FlexNICs on the same LOM port, each with an “Allocated” bandwidth setting of 5Gbps. If FlexNIC #1 is idle, not using any bandwidth, is FlexNIC #2 able to use 10Gbps? Or, in this scenario, is FlexNIC #2 still limited to a maximum of 5Gbps?

    Thanks,
    Brad

  9. Carl S.’s avatar

    There is a lot of meat in this post, so I am guessing it will take a bit of time to tackle specifics. If you do have Flex10 technical questions, posting them on the HP Blade Connect community is the best way to get a direct response from an HP resource.
    http://h18006.www1.hp.com/products/blades/components/bladeconnect.html

    I can’t comment on specific feature enhancements or firmware updates, so I will try to address your comments as best possible in those areas.

    Yes, there are some profile related annoyances noted by Rob and Scott. Originally Virtual Connect had the ability to change network mappings on the fly without powering off the blade. But with a recent flurry of Virtual Connect enhancements including Flex10, some of those features were temporarily disabled. We have added tons of enhancements over the last 2+ years, and I expect that you will see positive changes in the areas you noted.

    With regard to VLAN tunneling (multiple networks per FlexNIC), I have worked with VC and Flex10 extensively but have not come across many customers interested in tunneling large numbers of VLANs across a single FlexNIC. Obviously there is nothing wrong with doing that, just that experience has shown limited interest in that type of design. It would help to understand that VLAN strategy a little better to be able to comment more appropriately.

    Experience with VMware customers using Flex10 has shown that most are using a smaller number of VLANs to support VMs running on an ESX farm, and that Flex10 provides greater bandwidth and better LAN fault tolerance for VMware environments than was previously available. The big thing here was increasing the number of physical NICs presented to the OS and simultaneously increasing bandwidth (regardless of OS or application) – and at the same time lowering core uplink and edge interconnect costs.

    With respect to the limitations on SmartLink, there is logic there which requires a more detailed design discussion to fully address. Suffice to say that rules/reactions are different for FlexNICs with mapped (Single VLAN) and tunneled FlexNICs (Multiple networks). The SmartLink rules depend specifically on how your uplinks to the data center are configured, in addition to your VLAN selection on the FlexNIC. These need to be planned for on a customer by customer basis.

    I will keep posting as time allows.

  10. Daniel’s avatar

    Scott,

    We have our SC, Vmotion, and VM Traffic all on the same VLAN and you suggested “…assign the full 10Gbps of throughput to those two FlexNICs (network connections), and use a single vSwitch design.” as an alternate design. With 10Gbps, I don’t see a bandwidth issue. Are there any drawbacks to using a single vSwitch design for all 3 networks besides possible security risks with vMotion sent clear?

  11. geeko71’s avatar

    Hi

    Thanks for this Informations, this confirmes my findings.

    In my particular enviorement (vShpere Cluster, lot of Hosts, Nexus 1000v DVSwitch) i would like to realize the following configuration:

    2 x 4 x 10GbE Uplinks (vPC, LACP, all ports active)
    LOM 1a: mapped VLAN 2000 – 2050 for Management Stuff
    LOM 2a: mapped VLAN 2000 – 2050 for Management Stuff
    LOM 1b: trunk port (all VLANs from Uplink)
    LOM 2b: trunk port (all VLANs from Uplink)
    LOM 1c: mapped VLAN 2100, 2101, 2102, 2103
    LOM 2c: mapped VLAN 2100, 2101, 2102, 2103
    LOM 1d: mapped VLAN 2199
    LOM 2d: mapped VLAN 2199

    but im not able to realize this… neither in mapped mode nor in tunnel mode… :(

    can you coufirm thats no way for this config?

  12. geeko71’s avatar

    just found this dokument from HP…

    http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01990371/c01990371.pdf

    Page 156
    It seems that the only solution is to split the Uplinks in 2 Groups…

  13. Chris C’s avatar

    geeko71, that is the exact solution that i ended up with.

    hosts have to do active/passive interfaces if uplinks are on different physical switches. etherchannels cannot span multiple devices by default. if uplinks are on the same switch or cisco vss is implemented (etherchannel spanning) then you can do mode 4 bonding or lacp on os’s.

    we have two hp c7000 chassis with two flex10 modules with one uplink per module. one uplink goes to 6500 A and the second goes to 6500 B. i have two vnet’s defined in VC on each chassis. this config is cumbersome but its the only way without having to purchase 4 more sfp’s for module interconnects which i cannot do at this time. all vlan are configured as smartlink and natve vlan is set. all flexnic’s are set up as multiple networks type interfaces. this allows for kickstart/jumpstart via rarpd or dhcpd which are untagged broadcast type traffic. this type of traffic will be dropped if native vlan isn’t set. os’s are then configured to do mode 1 active/passive bonding or ipmp and vlan tagging. this keeps things very simple.

    great article btw.

    /C

  14. Sam’s avatar

    We have an performance issue when using flex 10 with Nexus 7k or 5k
    we have latest firmware on VC 3.15 and OA 3.21 and we ran a backup on one of our blade that connected to flex 10 and Nexus 7k it will ran about 2 or 3 hours more, but if we bypass the flex 10 and go from cisco 3120 to Nexus 7k or 5k this will be much faster. Has anyone seen any issue between flex 10 talking to nexus 7k or 5k please let me know

    Thanks

  15. slowe’s avatar

    Sam, I have not personally seen this behavior, but perhaps other readers can weigh in and let us know if anyone has a solution.

  16. Jeremy Pack’s avatar

    >>If you need to make any changes to a server profile like adding a VLAN or adjusting the bandwidth of the Flex NICs you have to reboot the host

    I’m not an expert on this but from my own personal experience in July2011
    This restriction has gone away. (At least for Hyper-V) As I have seen repeated changes to the VC configuration immediately visible in the OS, with out the need for a reboot.

  17. Bestin’s avatar

    Hi,
    we can see that NICs are not going down on HP UX 11.3 on Bl 860s with smart link enabled feature eventhough the uplink is down.
    any suggestion

  18. Basheer’s avatar

    Thanks for sharing this info.

    Since I have a large ENV, I have more than 28 VLANIDs.

    Maximum vNets you can choose is 28.

    Any improvements on this ?

  19. Rob Yeichner’s avatar

    Basheer, the maximum amount of VLANs you can select for a particular Flex-10 NIC, is 28. I have seen environments with many more VLANs than this – you simply pass one set of VLANs up through one NIC, a second set of VLANs through a second, etc.

    With up to date firmware on your Virtual Connects – this configuration maximum gets a boost to 162 VLANs per Flex-10 NIC. The latest firmware is 3.30 as of this date.

  20. tayo dada’s avatar

    hi scott,
    please clarify how one is able to have vlan tagging on a virtual switch in esx out to the flexnic and onto a physical switch.

  21. slowe’s avatar

    Tayo, I’m not 100% sure I understand your question. If you designate the physical switch port as a VLAN trunk, then VLAN tags will be carried into the Flex-10 Virtual Connect switches and then onto the vSwitches in the ESX/ESXi host (with the limitations described in this post). Search this site for other posts I’ve written on working with VLANs in a VMware environment for more information. Good luck!

  22. Mitchell’s avatar

    Hi Scott
    Just doing some followup.
    “Matt,

    I do not know if there are similar limitations with VLAN tunneling. That is on my test plan, so I’ll post results here as soon as I have more information.”
    Have you had a chance to test this and post results?

    Great blogs!

  23. oliver’s avatar

    Hi,

    limitation with Virtual Connect is that you can only use,

    1. VLAN tagging
    2. VLAN tunneling

    If you change this setting inside the VC module it counts for all blades and ports connected. Basically you need 2×2 VC Modules to drive both configurations parallel…

  24. slowe’s avatar

    Mitchell, unfortunately I have not been able to do any follow-up on that; my access to HP Virtual Connect Flex-10 equipment is pretty limited. Perhaps another reader can do some investigation here?

    Oliver, thanks for your comment. To my understanding, that is a limitation of VC, and something for which you’ll have to account in your designs.

  25. izhar’s avatar

    how to share hp single blade in number of vlan, because network dudes provides new series of ip , we have 4 switch port which is used for network zone like app, db, web ,and mgmt. network dudes new series ip has been trunk in app network zone. we had mapped free blade app zone but my os is not able to ping,how to create trunk in blade so we communicate the blade with any network zone any can help me or send the detail on my mail

  26. Rob Yeichner’s avatar

    2 x 4 x 10GbE Uplinks (vPC, LACP, all ports active)
    LOM 1a: mapped VLAN 2000 – 2050 for Management Stuff
    LOM 2a: mapped VLAN 2000 – 2050 for Management Stuff
    LOM 1b: trunk port (all VLANs from Uplink)
    LOM 2b: trunk port (all VLANs from Uplink)
    LOM 1c: mapped VLAN 2100, 2101, 2102, 2103
    LOM 2c: mapped VLAN 2100, 2101, 2102, 2103
    LOM 1d: mapped VLAN 2199
    LOM 2d: mapped VLAN 2199

    =-=-=-=

    Geeko71, this is an invalid configuration and should not work. You cannot present the same VLANs across 2 different Flex-NICs on the same LOM. That doesn’t mean the same combination, that means in your setup you cannot pass VLAN 2000 on 1a and then try to pass it again on 1b. 1a, 1b, 1c and 1d are all Flex-NICs on the same LOM #1. Ditto for those duplicated VLANs on Flex-NIC B and C/D.

    Chris B (HP) says the following:

    “There is no advantage to using the same VLANs one each FlexNIC beyond the additional bandwidth”

    He is preaching HP perspective here and it isn’t exactly perfect thinking if you ask me and my community peers. I don’t agree with this because there *is* utility in passing my management traffic on one Flex-NIC to a svSwitch and trunking all VLANs for guests to a dvSwitch. HP looks at it from the perspective of “there is no need to do this because if you loose a LOM, you lose the LOM and there it no benefit from the redundancy.” That would only be true if you were using it for redundancy. I am using it because my VLAN 1500 is for management traffic and where I pass vmkernel traffic for vmotion, ft and also management interface communications. These just so happen to all use 1500 but they are not for redundancy purposes. I spread those correctly across different LOMs.

    What this forces you to do is architect around the hardware limitations. Either share 1 Flex-NIC for all three functions (not a great idea) or redesign your vSphere environment to use different VLANs. Perhaps use internal only networks if you are a VCEM licensed environment.

  27. Rob Yeichner’s avatar

    @Jeremy Pack

    >>>> If you need to make any changes to a server profile like adding a VLAN or adjusting the bandwidth of the Flex NICs you have to reboot the host

    >> I’m not an expert on this but from my own personal experience in July2011 This restriction has gone away. (At least for Hyper-V) As I have seen repeated changes to the VC configuration immediately visible in the OS, with out the need for a reboot.

    Jeremy, to make hardware changes to virtual connect hardware/configuration, the power state of the assigned server profile must be off. If the server is powered on in any state (OS loaded and running, paused at POST screen, etc) your server profiles changes will fail. Here’s a log of me trying this:

    Job Name: Edit server profile [ESVMCL05] in VC Domain [ESBLDT03_VcD]
    Job Description: Edit server profile
    User Name:
    Status Failed
    Start Time: 06-25-12 07:56:03
    End Time: 06-25-12 07:56:40
    Log: Checking target resource.
    Start executing job.
    Started edit server profile.
    Started edit server profile.
    Validating server profile data model.
    Processing Ethernet network connections.
    Processing iSCSI connections.
    Processing FC SAN connections.
    Processing FCoE connections.
    Saving the server profile in the database.
    Checking server profile bay assignment.
    Error during Edit server profile [ESVMCL05] in VC Domain [ESBLDT03_VcD]. Details: This action could not be performed because the server is powered on. Power down the server associated with the Server Bay and retry the operation.

    We are not bleeding edge on our firmware and I haven’t heard of this power state requirement having changed but I suppose it is possible. I know we are updated beyond when you made your post though.

  28. AlexGB’s avatar

    I always think that a better name for this product would have been “Inflexible Connect”.

  29. Eddie’s avatar

    I have VLANs that have issues with vPC, and therefore have to configure non-vPC for these troublesome VLANs. I pipe VLANs that are either vPC or non-vPC to my HP 7000c with Flex-10s… Has anyone done the following? Is it feasable? to have vPC and non-VPC links between 2 Nexus 5020s and HP 7000c with 2 Flex-10s (A and B)?

  30. KingKong’s avatar

    Will OS see FlexNIC interface at all ? Appreciate if somebody could send output of ifconfig from server when FlexNIC is configured.

  31. Dan (HP)’s avatar

    @AlexGB – wow, thanks for the constructive criticism.

    @Eddie – I have customers using Cisco vPC on N5Ks and have not run into any major issues aside from the LACP timer needing to be short (1 sec and default on the Nexus) for the time being. You cannot however form an LACP LAG with 2 connections going to 2 different VC modules. Basically there is no vPC like feature on the VC side yet.
    Past that I am not sure I understand the question.

    @KingKing – Yes, all 8 FlexNICs will show in the OS. ifconfig on RHEL would see eth0 through eth7. Ipconfig on Windows would see Local Area Connection (1) through 8.

    Changes while running:
    You can and have been able to for a while, make changes to the profile while its running. FlexNIC assignments and Speed can be changed on the fly. If you have a G6 blade with the absolute earliest Broadcom firmware (as in Launch + 2 months I think) there is a bug in the firmware that prevents changes from propagating. Update the firmware to anything moderately current and you should be fine. No such issue in G7 or Gen8.
    If you are however Adding or Removing connections from the Ethernet list in the profile, then this will require the profile to be OFF as mentioned. Best practice for me up to this point has been to add 6 or 8 connections (6 if using FCoE on FlexFabric) even if you initially only need 2 or 4. They will show up in the OS anyway, so having them in the profile doesn’t hurt much.

    Performance:
    I saw someone having a performance issue. Hard to troubleshoot an old issue, but a customer I worked with recently was getting 9.3Gbps from a Blade through FlexFabric up to an N5K, over to a 6K FI and then down through the FEX into a Cisco blade just a few months ago. So performance should obviously not be a problem.

    FlexNIC Speed capping:
    As of right now, FlexNIC speeds defined in the profile are for transmit only. (Blade outbound). It didn’t make alot of sense to cap the inbound side if the packet was already successfully delivered to the VC module. Chances are you have a lot more downstream bandwidth (aggregate) than upstream basically.

    Hope some of that helps,
    Dan (HP PreSales Architect)

    PS: If you are still buying Flex-10 modules, you should switch to the newer Flex-10/10D. Faster ASIC, more ports, lower power usage and DCB support. List price is 3% higher than original Flex-10.

  32. Immanuel’s avatar

    Hi,

    I have a implementation to do.
    The customer has a BLc7000 Enclosure with Bays 1-8 populated with identical BL460c Gen8 Servers [They have FlexLOMs].
    Interconnect Bays 1 & 2 have VC-FlexFabric.
    There is only one Cisco 2960-S Catalyst Switch.
    Ports X5,S6 from each VC [total of 4 from bays 1&2] go to the same switch on their uplink ports. Ports X1,X2 from Bays 1 & 2 Go to a single SAN Switch. Customer wants to implement CentOS, as this is a non production (Test) environment.

    I do not understand why the customer has provided just one IP & SAN Switch. Anyways, this is the hardware that I have to implement. I guess because its a Test Enviroment.

    The customer has 16 VLANs.
    Specific VLANs are for Servers in Specific Bays.
    But certain VLANs need to be allowed on all Server Bays.
    These are :
    VLAN_100 for Management & Shared Services (DHCP, DNS, Nagios, NTP, SMTP).
    VLAN_250 for user Access.

    Customer wants a Load Balancing + Fault Tolerance.

    So I created Two Shared Uplinks (which includes all these 16 VLAN IDs) and asked the Cisco admin to do LAG (Link Aggregation Grouping) for the ports that connect to the same VC (X5,X6). Hence there are 2 LAGs. Thereby I see all 4 uplinks as Linked-Active.

    Cisco admin has done trunking for only VLAN 100.

    My issues are with Ethernet and not with the SAN.

    On the Server Profile, I assigned Multiple Networks (Selecting all VLAN).
    Two were created. I could not add more to may to Flex ports 1c,1d,2c,2d.

    The issue is that:
    a. I am not able to do inter-server communication.
    Does it require that for inter-server communication, we need to have the VLAN configured on the Switch?
    b. I was able to do inter-server communication when I created a Single simple vNET and added all 4 uplinks and assigned it to the Server Bays.
    c. Not all Flex ports 1a,2a, 1c,2c, 1d,2d are active. July ports 1a,2a are active.

    What is the best implementation?
    1.Shall I create a mix of vNET Tunnels & Shared Uplinks.
    i.e. 2 Shared Uplinks from Ports x5 on each VC-FlexFabric, each Uplink to have VLAN named as VLAN_-1 & VLAN_-2. There will be a total of 32 networks.
    & 2 vNET Tunnels on ports x6 on each VC-FlexFabric for inter-server communication and also for any other untagged VLAN Traffic?

Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>