Networking

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. LBFO Team: Prevent duplicate multicast traffic on virtual nic

    When using a switch independent team, multicast traffic is received by all physical nics in the team (switch does not know the ports are in a team). When attaching a virtual switch to the team, it appears as if virtual nics receive the multicast traffic multiple times (once from each physical team member). Is it not possible to send it to the virtual nic only once (eg. only from the physical nic the virtual nic's VMQ is associated with)?

    2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Teaming & load balancing  ·  Flag idea as inappropriate…  ·  Admin →
  2. Bring load balancing to windows server!

    Many modern HTTP applications are deployed in enterprises with 3rd party load balancers running in layer 7 mode. I have yet to find a solution which runs on windows. NLB is often difficult to deploy because of incompatibilities with switches/hypervisors (some improvement with IGMP multicast), and does not operate in layer 7.

    IIS AAR can do layer 7 but does not do high availability without combining with NLB

    35 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Teaming & load balancing  ·  Flag idea as inappropriate…  ·  Admin →
  3. Give more control for NIC teaming

    In Active/Passive NIC teaming configuration, there could be more control for failback, that when active NIC fails and failover happens, the team did not failback to previously (default) active NIC for specified amount of time.

    12 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Teaming & load balancing  ·  Flag idea as inappropriate…  ·  Admin →
  4. Override teming mode for management OS virtual NICs

    It would be greate, if we can tell for this particular vNIC to send/receive traffic trough one NIC and not to perform loadbalancing or failover. If you've got only 2 NIC adapters, you can't properly install hyper-V host with iSCSI (for iSCSI Multipath I/O is better option, than teaming), SMB v3 also would benefit (we than could keep traffic not crossing switches or stacking (IRF/MLAG) connection). Another option could be partition HW NIC using SR IOV technology, and bring VF to management OS.

    5 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Teaming & load balancing  ·  Flag idea as inappropriate…  ·  Admin →
  5. Keep Network Teams intact after upgrade

    After in-place upgrading Srv2016 Build 10154 to build 10158 the network teams needed to be reconfigured. All teams disappeared, hopefully this will be fixed in the following updates. Rebuilding the teams isn't fun..

    5 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Teaming & load balancing  ·  Flag idea as inappropriate…  ·  Admin →
  6. Provide support for changing LACP timer value to long/slow for NIC teams

    If you use native support for NIC teaming, LACP teams use a short/fast timer. This is an issue if you the team is connected to a Cisco Nexus and want to use In-Service Software Upgrades because ISSU requires slow/long timers.

    4 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Teaming & load balancing  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base