Adapter as a stamby fo LACP Team

Is is possible to make a team of a LACP team and a regular adapter, so that we had 3 Gbps on the LACP and a standby on another switch with 1 Gbps?
by lets say creating another team as an independent switch add the LACP and the adapter as a standby
I was able to do this with a vSwtich, with Hyper-V Role installed, but then I get MAC errors

Hi,
You can’t create the teaming like that, NIC Teaming requires the presence of a single Ethernet network adapter, which can be used for separation of traffic using VLANs. All
modes that provide fault protection through failover require at least two Ethernet network adapters.
The related KB：
NIC Teaming Overview
http://technet.microsoft.com/en-us/library/hh831648.aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

  • Cannot Add Logic Switch To host When Teaming two 10Gbe ports on the same CNA or on different CNAs

    We are trying to set up a new Hyper-V environment for a customer with VMM2012 SP1.  We have the hosts configured, imported, and clustered.  The Uplink Port-Profile is set to the proper LACP teaming method for our switching.  The Logical switch
    is created in uplink mode Team and includes the proper Uplink Port Profile.
    When we go to create a logical switch on the Hosts using the two interfaces to be teamed, we get Warning (25259), Error while applying physical adapter network settings to the teamed adapter.  Error code details 2147942484.
    I reasearched and found articles about setting up NICs in a correct order in the team from least capable to most capable, but in this case we are trying to team two ports on the same adapter... We have tried with Intel X520-2's and Brocade CNA1020's.  The
    odd thing is, if we try to do it on the onboard 1Gbe Broadcom cards, it works fine.
    This happens on both clustered and non-clustered hosts as well.  All VMM components are the latest versions with the latest updates.
    Thanks!

    We are trying to set up a new Hyper-V environment for a customer with VMM2012 SP1.  We have the hosts configured, imported, and clustered.  The Uplink Port-Profile is set to the proper LACP teaming method for our switching.  The Logical switch
    is created in uplink mode Team and includes the proper Uplink Port Profile.
    When we go to create a logical switch on the Hosts using the two interfaces to be teamed, we get Warning (25259), Error while applying physical adapter network settings to the teamed adapter.  Error code details 2147942484.
    I reasearched and found articles about setting up NICs in a correct order in the team from least capable to most capable, but in this case we are trying to team two ports on the same adapter... We have tried with Intel X520-2's and Brocade CNA1020's.  The
    odd thing is, if we try to do it on the onboard 1Gbe Broadcom cards, it works fine.
    This happens on both clustered and non-clustered hosts as well.  All VMM components are the latest versions with the latest updates.
    Thanks!

  • Apps Adapter API is called before Db Adapter inserting data

    Hi All,
    I am using a bpel process which calls db adapter to insert/update data in staging table, after this activity i am calling a Apps Adapter PLSQL API where it takes the data from staging table and performs some functionality. But the problem here is Apps adapter PlSQL API is getting called before isnerting data in staging table.
    Below are the steps in BPEL Process,
    1. receive activity
    2. data transformation
    3. invokes db adapter through merge operation to insert/update in staging tables
    4. invoke Apps Adapter PLSQL API
    Error is thrown at Apps Adapter invoke activity, saying null values. presently we used a wait activity before invoking apps adapter.
    Do the invoke of Apps Adapeter doesnt happen after Db Adapter inserting data?
    Thanks,
    Ra

    Hi Team,
    Even I faced the same problem.
    I am checking, do we have any configuration setting to avaoid these kind of problem.
    Even my process has point 2 & 3 in a single sequence and point 4 in another sequence.
    Any help to resolve this problem is greatly appreciated.
    Thanks for your help in adavance.
    Cheers
    Chandru

  • Can we make server fingerprint field optional instead on mandatory in SFTP adapter

    Dear All,
    We are integrating SAP HCM with Success-factor only for Employee profile as client is only using the "SF PMS" module.
    ABAP program(installed through SH addOn provided by SAP) is generating the Employee profile ".csv" file.
    I am developing a bypass scenario to transfer that ''.csv" file to SuccessFactors SFTP server. However, SuccessFactors SFTP server team is not ready to provide me their "server fingerprint", and they are claiming this info is not required to develop interface in PI. The Authentication mode in SFTP communication channel is "Password" based instead of "Private key".
    Experts please help me understand is there any possibility to make this field optional? if not what else I can try here?
    Thanks,
    Farhan

    Hi Farthan,
    Server Fingerprint is the mandatery field to fonfigure the SFTP adapter. kindly check with your admin team to login thorough CoreFTP, it will be genarte and display the Server fingerpring.
    please go through the below log.
    http://scn.sap.com/community/pi-and-soa-middleware/blog/2012/04/11/sap-sftp-sender-adapter-a-quick-walkthrough
    Regards
    Srinivas

  • Windows 2012 Teaming configuration

    Dear All,
    i want to configure teaming in windows 2012. i have 4 lan card and i am confuse in switch dependent and switch independant.
    which option gives me best performance? this server having failover cluster node.
    teaming will create any problem with cluster?
    please help
    Sunil
    SUNIL PATEL SYSTEM ADMINISTRATOR

    Hi,
    It depend on your configurations and requirements.
    In Switched Independ Mode, all the network adapters are connected to different switches provide alternate routes through the network. This configuration doesn't require switch to participate in the teaming. Since the switch is independent mode the switch doesnot
    know which adapter is part of the NIC Team. This again classified into two mdes:
    Active / Active Mode
    Active / Passive Mode
    In Switched Dependant Mode, it requires the switch to participate in the teaming. And also required all the NIC card to be connected to the same physical switch. This can be configured in Two modes:
    Generic / Static Mode
    Dynamic Teaming
    Network card teaming is now supported in Windows Server 2012 with cluster. However, when iSCSI is used with dedicated NICs, then using any teaming solution is not recommended and MPIO/DSM should be used. But when iSCSI is used with shared NICs, those
    shared NICs can be teamed and will be supported as long as it’s being used with Windows Server 2012 NIC Teaming solution.
    Is NIC Teaming in Windows Server 2012 supported for iSCSI, or not supported
    for iSCSI?
    Best regards,
    Susie
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

  • Configuring NIC teaming

    Hello, everyone. I'm hoping this thread is in the right place.
    I've been doing some research trying to understand logical switches/port profiles/etc. in VMM and have been having a hard time. Most of the articles I've found either don't go into enough detail or seem to lack proper examples. My goal is to enable NIC teaming
    on my cluster hosts.
    Currently, each cluster node has 1 standard switch per physical NIC. One of these NICs is trunked, and the others are not. Everything is working fine, but I'm looking to improve the infrastructure behind these hosts.
    I evicted one node from the cluster to experiment with. I enabled LACP on the switch side (Cisco) and enabled NIC teaming on the server (2012 R2). The server is online and functioning, but this is where my knowledge ends. I can't create a logical switch
    and add it to this host as the job fails stating that the switch can't be added since the host is already teamed. I'm a little confused about the proper process of getting a logical switch created and added to my host. Do I need to remove LACP and disable
    NIC teaming on the host and then re-enable it? Am I going down the wrong path by using LACP? 
    Any tips and advice would be greatly appreciated. I'd also be happy to provide any additional details I may have left out.

    We use LACP teaming for four NICs, two teams, one Production vSwitch and one for management.
    We create the management team on the HyperV host first, add it into VMM then push out a team FROM VMM for the switch. The trick is to create a port profile (using algorithm Hyper-V Port and Teaming Mode LACP.) bind this port profile to your logical network(s).
    then create your virtual switch and select uplink mode TEAM. and add in your uplink port profile.
    Once you have done this you can then right click the host (in VMs and Services) Properties and navigate to virtual switches. Add a new Virtual Switch (New logical switch) then you will be able to add multiple adapters to the switch.
    Hit apply and it *should* team for you.
    If you need further clarification I can send screen prints and exact steps on tuesday when i'm back in the office.

  • From Where can i download  Jar Files for creation of adapter Module.

    From Where can i download these Jar Files.
    aii_af_mp.jar à the interface Module
    aii_af_ms_api.jar  à Dealing with payload and attachment
    aii_af_trace.jar à Writing Trace
    aii_af_svc.jar à Adapter Services
    aii_af_cpa.jar à Reading Channel Entries
    aii_af_ms_spi.jar
    aii_af_cci.jar 
    for creation of adapter Module.

    As k you basisn team,they will provided it.
    usually these jars files available in server, in usr.repositoy folder,if you have server level access then you can copy it else contact your basis team.
    or you can download it from service market place.
    Regards,
    Raj

  • LACP ports used as standalone ports

    we setup a switch for the server team to have LACP team ports for their Teamed nics in the servers.
    on a few servers, the server team did not setup teaming on their nics and connected the nics to the switch teamed ports.  the switch connected each nic in standalone mode.  We did not notice this until some time later.
    Would this have caused any network issues,  or would the switch treated the ports as standalone and work as usual?
    Group  Port-channel  Protocol    Ports
    ------+-------------+-----------+-----------------------------------------------
    2      Po2(SD)         LACP      Gi0/9(I)    Gi0/10(I)
    3      Po3(SU)         LACP      Gi0/29(P)   Gi0/30(P)
    4      Po4(SD)          -
    5      Po5(SU)         LACP      Gi0/27(P)   Gi0/28(P)
    6      Po6(SD)         LACP      Gi0/43(I)   Gi0/44(I)
    7      Po7(SU)         LACP      Gi0/45(P)   Gi0/46(P)
    8      Po8(SD)         LACP      Gi0/47(I)   Gi0/48(I)
    9      Po9(SD)         LACP      Gi0/31(I)   Gi0/32(I)
    10     Po10(SD)        LACP      Gi0/35(I)   Gi0/36(I)
    11     Po11(SU)        LACP      Gi0/37(P)   Gi0/38(P)
    12     Po12(SD)        LACP      Gi0/39(I)   Gi0/40(I)
    13     Po13(SD)        LACP      Gi0/33(I)   Gi0/34(I)
    14     Po14(SD)        LACP      Gi0/3(I)    Gi0/4(D)

    The server should run in active/standby mode for the NICs and the switch would just run in standalone mode. No issues should have been caused by this.

  • SG500 LACP trunk mismatch native vlan on individual ports

    Hi All,
    I have just configured up a sg500 with a lacp trunk to an upstream switch.
    I am getting native vlan mismatch on the individual ports of the lacp team.
    24-Jan-2013 12:54:48 %CDP-W-NATIVE_VLAN_MISMATCH: Native VLAN mismatch detected on interface gi1/1/24.
    24-Jan-2013 12:57:35 %CDP-W-NATIVE_VLAN_MISMATCH: Native VLAN mismatch detected on interface gi1/1/48.
    The following is showing the correct native vlan
    BH-WS-AC-2#show int switchport port 1
    Port : Po1
    Port Mode: Trunk
    Gvrp Status: disabled
    Ingress Filtering: true
    Acceptable Frame Type: admitAll
    Ingress UnTagged VLAN ( NATIVE ): 2000
    Port is member in:
    Vlan               Name               Egress rule Port Membership Type
    1200               1200                 Tagged           Static       
    1210            Management              Tagged           Static       
    1212               1212                 Tagged           Static       
    2000           Native Vlan             Untagged          Static      
    But the following shows that the individual ports think they are the default vlan 1.
    BH-WS-AC-2#show int switchport gi1/1/48
    Port : gi1/1/48
    Port Mode: Trunk
    Gvrp Status: disabled
    Ingress Filtering: true
    Acceptable Frame Type: admitAll
    Ingress UnTagged VLAN ( NATIVE ): 1
    Port is member in:
    Vlan               Name               Egress rule Port Membership Type
    The following shows the LACP as up:
    BH-WS-AC-2#show int Port-Channel 1
    Load balancing: src-dst-mac-ip.
    Gathering information...
    Channel  Ports
    Po1      Active: gi1/1/24,gi1/1/48
    Is this normal behaviour? as i cannot set the native vlan directly on the gi interface due to it being in the trunk.
    Simon

    Hi Simon, native vlan mismatch is a cosmetic error from CDP. It won't affect services provided the vlans are a member of the ports in question.
    You can set the native vlan while it is within the lag. On the SX500 it would be
    config t
    int po1
    switchport trunk native vlan xxxx
    The port channel is the same as any other individual port so it's not a problem. 802.1q specifies the native vlan is the untagged member, if you want to get rid of the error, make sure the untagged vlans match up on both sides.
    -Tom
    Please mark answered for helpful posts

  • Hyper-V 2012 R2 & NLB (Network Load Balancing) with Unicast on VMs

    Hi,
    We set up a 2012 R2 Hyper-V Cluster. On this Cluster we would like to run 2 VM's which are using NLB (Network load Balancing) in Unicast mode.
    We have created a External Virtual Switch wich is connected trough a 3x10GB LACP Team to a Cisco Nexux Switch.
    We have tried to set the NLB up in the way we did with 2008 R2 but we were not be able to get this working. Is there any Change in 2012 R2 we did not think about?
    Each time we form the Cluster one Node becomes unavailable.
    Timo

    Check the virtual network adapter properties - you must enable MAC address spoofing.  We had the same issues.
    Note that this will absolutely pollute your host machine's system log with tons of spam and make it pretty much worthless.  I'm trying to find a way around this as we speak, actually.

  • Teredo Tuneling

    How can I fix teredo tuneling interface? (error 10)
    I tried many fixes that were irrelevant.

    hhdupre7
    There are a few things that can cause this.  Here are some links to read
    http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/microsoft-teredo-tunneling-adaptercode-10/fe2a30a7-bb4e-49db-9e74-6800c5191604
    http://www.tomshardware.com/answers/id-1897213/error-code-teredo-tunneling-adapter-win.html
    Wanikiya and Dyami--Team Zigzag

  • Failback after "Protected Network" failover in Hyper-V

    Hi everyone
    I have a two node hyper-v cluster on Windows Server 2012 R2. I use "Protected Network" feature combined with LACP teaming at the Hyper-V level. Protected Network works fine, it meens when network connection of
    a particular VM is broken, the Live Migration begins and VM starts working on a second node.
    The problem is with a failback action. In the VM properties I have set the preferred owner and I allowed failback immediately. After loosing a network connection Protected Network feature migrates the VM to a second node (not preferred).
    But after the connection is reliable again on the first node, the failback does not happen. When I for example restart a Cluster Service on the first node, then all VMs are migrated to a preferred nodes. Failback also works fine after restarting
    one of the nodes. It does not work only after Protected Network failover.
    Do you think failback is possible with Protected Network feature?

    Hi Konrad,
    First , my apology for the delay .
    I built the cluster for this test and I configured a HA VM to allow failback immediately and preferred owner but it only applied to node failover .
    (I unplugged the cable to trigger failover for that VM but it didn't failback after I plugged the cable back )
    Best Regards
    Elton Ji
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Xsd:string

    Hi
    1) in defining data types in PI : does xsd : string incorporates all the data types ( string ,digits ,dates ,special characters)
    2) the length specified in Data Types : is it validated in PI ? suppose our data type length is 10 and the xml sent across from legacy is 8 characters: does PI raise an exception by default?
    Thnx

    hi ,
    my requirement is : soap to proxy : sync scenario
    sender adapter :soap
    i pass the legacy team a wsdl file.
    i have a sender data type defined ,which is like an xsd :if the sender side does not send me a record which satisfies my data type I want to send an error message back to sender : your record does not match schema or whatever kind of standard message. PI should not process if sender side sends me a record which does not satisfy my data type : eg : if address field is defined as 40 chars in PI and sender side sends 50 char address field : so it does not match my schema defined in the Data type.
    Thnx

  • Firmware upgrade Stand-Alone C-Blade network issues

    Hello,
    I recently upgraded my Stand-Alone C22 M3 blade from version 1.5.5 to version 2.0(3d)
    The VIC 1225  got firmware version 4.0(1b) (old version 2.2(1b))
    After the upgrade using the Host Upgrade Utility I removed all old drivers and installed the newest versions.
    so far so good, but almost immediately i noticed very poor basic nateworking.
    DNS lookups fails
    pings got lost
    tracerts can be instant or take forever to complete
    We use this blade as a commvault backup server and both VIC 1225 Nics are in a LACP team (Status is Active)
    on the host switch Nexus 5548UP there is a FC interface bind to the network interface so we have our backup libaries available on the host
    Only if i keep pinging the servers i want to backup the network connection stays stable, otherwise backups will fail.
    after downgrading the firmware of the vic back to 2.2(1b) everything went to normal again.
    is there any explanation for this? known bug?
    Thanks,
    Ivo 

    You also have a etherchannel configured on your nexus 5K, isn't it right?
    Take a look at the logging messages and try to find a MAC_FLAPPING message related to the servers MAC addresses.
    Also check out this bug: https://tools.cisco.com/bugsearch/bug/CSCuf65032.
    It was corrected on the version 2.22(1b) (your old one), but it may be back on the 4.0(1b).
    Try to apply the workaround suggested and see if it works.
    Cheers,
    Kauy Gabriel.

  • NIC Config Design options

    Hi,
    I am getting ready to create my first Server 2012R2 Hyper-v failover cluster.  I have 2 servers with 6 NICs each and a HP ISCSI SAN.  My question is what is the best way to configure the 6 NICs on each machine to support this?  There are some
    choices that seem required:
    2 NICs from each server to connect to the ISCSI SAN
    Other than that I need the regular stuff.  I have seen some posts where the author recommends using one nic for heartbeat and admin, others that say no to this, etc.  If you were configuring this from scratch, what is the best way?
    Thanks

    If you were configuring this from scratch, what is the best way?
    The operative word there is you. There is no universally correct way.
    I would have two physical NICs set aside for iSCSI in MPIO configuration.
    I would put the other four in a converged configuration and run all host, cluster, and VM networks on it. Because this organization does not overcommit resources, we have an intentionally low VM-to-host ratio and we have intelligent, redundant
    switches, so I would configure the ports in a LACP team in Dynamic or Address Hash balancing mode, depending on what the expected needs were. Those are the best choices for
    me.
    You might have a high VM-to-host ratio with basic switches, in which case you might prefer a switch independent team in Dynamic or Hyper-V Port mode.
    You might not want your management traffic sharing lines with your VM networks, so you might make two teams instead of one.
    The answer really depends on what you want and what your systems need. About the only thing I can say is you're right to not team iSCSI NICs and that you should think hard before isolating any role on a single physical NIC when you have so many at your disposal.
    I would definitely
    read this to get an idea of what your options are. After that, test out some configurations and see.
    IMO, people do a lot of unnecessary hand-wringing over these questions. Unless you're in an environment where every packet matters, just about any configuration you come up with will be just fine in day-to-day uses.
    Eric Siron Altaro Hyper-V Blog
    I am an independent blog contributor, not an Altaro employee. I am solely responsible for the content of my posts.
    "Every relationship you have is in worse shape than you think."

Maybe you are looking for