Hyper-V teaming cannot failover

I have created two NIC teaming, one for a 147 subnet and one for a 192 subnet,
And used these two teaming in a Hyper-V virtual switch
But when I disable one of the NIC in the 147 team, some VM will loss connection,
It seems to me that the VM originally using the disabled NIC cannot failover to the remaining active NIC.
Anyone have any idea about what might be wrong? Thank you very much.

Hi Kevin,
It shouldn't happen , Please try another combination of your physical NICs , such as team members "slot7port1"and "slot7port4" for "external-147" teaming.
Also please try to configure a standby NIC then check if it can failover .
Any further information please feel free to let us know .
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.

Similar Messages

  • Change Hyper-V 2012 R2 failover cluster management subnet

    Hi,
    We have an existing Hyper-V 2012 R2 Failover cluster.  Virtual machines are live on this cluster.  The networking team has decided to reorganise the network subnets.  As a consequence we need to change the management IPs of our Hyper-V failover
    clusters.
    What are the possibilities?
    Evect 1 node from the cluster, set correct management IP on the evicted cluster. Create a single-node cluster.  Mask a new LUN to the single-host cluster.  Execute a shared nothing live migration of the VMs which are hosted on old cluster.
    Kr,

    Hi Kr,
    You can refer the following similar scenario article:
    Changing Hyper-V Cluster Virtual IP Address (VIP) After Layer 3 Changes
    http://blogs.technet.com/b/chrad/archive/2011/09/16/changing-hyper-v-cluster-virtual-ip-address-vip-after-layer-3-changes.aspx
    Change IP address Hyper-V Cluster
    http://bartvanvugt.blogspot.com/2012/01/change-ip-address-hyper-v-cluster.html
    More related third party article:
    Change IP address Hyper-V Cluster
    http://bartvanvugt.blogspot.com/2012/01/change-ip-address-hyper-v-cluster.html
    I’m glad to be of help to you!
    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.

  • Hyper-v Replica: Planned Failover from Cluster to another Cluster Failed

    Hi Guys,
    i have one issue and i cannot find a way to troubleshooting
    i Have one Primary Site running 8 nodes Hyper-v with Failover Cluster and Hyper-v Replica Broker confguration
    i have one Replica Site  running 8 nodes Hyper-v with Failover Cluster and Hyper-v Replica Broker
    Replica Broker Configuration:
    https://onedrive.live.com/redir?resid=45C59B28F67FC71C%212271
    both side are pinging and name resolution is ok
    all ports are open
    The Virtual Machine Replication is ok
    The Planned Failover cannot complete and show me this simple error
    "failed" 
    i have no message on event Viewer
    Error:
    https://onedrive.live.com/redir?resid=45C59B28F67FC71C%212270
    Planned Failover from Cluster (Primary site) to another Cluster (Replica site) with Replica
    Start Hyper-V Manager pr failover cluster console on the primary server and choose a virtual machine to fail over.
    1. Turn off the virtual machine that you want to fail over.
    2. Right-click the virtual machine, point to Replication, and then point to
    Planned Failover.
    3. Click Fail Over to actually transfer operations to the virtual machine on the Replica server.

    Hi Samuel,
    In the original post :
    Tests: 1 -
    Planned Failover from Cluster to StandAlone Hyper-v is ok
    Test: 2
    Planned Failover from Standalone hyper-v to Cluster is ok
    Test:3
    Planned Failover from Cluster (Primary site) to another Cluster (Replica site) with Replica
    There is no  standalone hyper-v to standalone hyper-v between two sites .
    After the last test , if they still can not do planned failover , maybe you can focus on network configuration .
    Best Regads
    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.

  • 2 Hyper-V Servers with Failover Cluster and a single File Server and .VHDs stored on a SMB 3 Share

    I have 2 X M600 Dell Blades (100 GB local storage and 2 NICs)  and a Single R720 File Server (2.5 TB local SAS storage and 6 NICs).  I´m planning a Lab/developer enrironment using 2 Hyper-V Servers with Failover Cluster and a single File Server putting
    all  .VHDs stored on a SMB 3 Share on the File Server.
    The ideia is to have a HA solution, live migration, etc, storing the .VHDs onm a SMB 3 share
    \\fileserver\shareforVHDs
    It is possible? How Cluster will understand the
    \\fileserver\shareforVHDs as a cluster disk and offer HA on it?
    Or i´ll have to "re-think" and forget about VHDs on SMb 3 Share and deploy using iSCSI?
    Storage Spaces makes difference in this case?
    All based on wind2012 R2 STD English version

    I have 2 X M600 Dell Blades (100 GB local storage and 2 NICs)  and a Single R720 File Server (2.5 TB local SAS storage and 6 NICs).  I´m planning a Lab/developer enrironment using 2 Hyper-V Servers with Failover Cluster and a single File Server putting
    all  .VHDs stored on a SMB 3 Share on the File Server.
    The ideia is to have a HA solution, live migration, etc, storing the .VHDs onm a SMB 3 share
    \\fileserver\shareforVHDs
    It is possible? How Cluster will understand the
    \\fileserver\shareforVHDs as a cluster disk and offer HA on it?
    Or i´ll have to "re-think" and forget about VHDs on SMb 3 Share and deploy using iSCSI?
    Storage Spaces makes difference in this case?
    All based on wind2012 R2 STD English version
    You can do what you want to do just fine. Hyper-V / Windows Server 2012 R2 can use SMB 3.0 share instead of a block storage (iSCSI/FC/etc). See:
    Deploy Hyper-V over SMB
    http://technet.microsoft.com/en-us/library/jj134187.aspx
    There would be no shared disk and no CSV just SMB 3.0 folder both hypervisor hosts would have access to. Much simplier to use. See:
    Hyper-V recommends SMB or CSV ?
    http://social.technet.microsoft.com/Forums/en-US/d6e06d59-bef3-42ba-82f1-5043713b5552/hyperv-recommends-smb-or-csv-
    You'll have however a limited solution as your single physical server being a file server would be a single point of failure.
    You can use Storage Spaces just fine but you cannot use Clustered Storage Spaces as in this case you'll have to take away your SAS spindles from your R720 box and mount them into SAS JBOD (make sure it's certified). So you get rid of an active components
    (CPU, RAM) and keep more robust all-passive SAS JBOD as your physical shared storage. Better then a single Windows-running server but for a true fault tolerance you'll have to have 3 SAS JBODs. Not exactly cheap :) See:
    Deploy Clustered Storage Spaces
    http://technet.microsoft.com/en-us/library/jj822937.aspx
    Storage Spaces,
    JBODs, and Failover Clustering – A Recipe for Cost-Effective, Highly Available Storage
    http://blogs.technet.com/b/storageserver/archive/2013/10/19/storage-spaces-jbods-and-failover-clustering-a-recipe-for-cost-effective-highly-available-storage.aspx
    Using
    Storage Spaces for Storage Subsystem Performance
    http://msdn.microsoft.com/en-us/library/windows/hardware/dn567634.aspx#enclosure
    Storage
    Spaces FAQ
    https://social.technet.microsoft.com/wiki/contents/articles/11382.storage-spaces-frequently-asked-questions-faq.aspx
    Alternative way would be using Virtual SAN similar to VMware VSAN in this case you can get rid of a physical shared storage @ all and use cheap high capacity SATA spindles (and SATA SSDs!) instead of an expensive SAS.
    Hope this helped :)
    StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

  • Server 2012 R2 Team - cannot be teamed as it has a Hyper-V role enabled on it

    Hi
    I removed a team Server 2012 R2 Server with Hyper-V Roles installed. When I go to recreate the team I don't get any adapters listed even though they are there and have picked up ip addresses. I tried to create it using powershell and get the following
    PS C:\Users\trcadmin> new-netlbfoteam -name "Virtual Production Team" -TeamMembers "Production Virtual Network A", "Production Virtual Network B" -TeamingMode SwitchIndependent
    new-netlbfoteam : Member 'Production Virtual Network A' cannot be teamed as it has a Hyper-V role enabled on it
    At line:1 char:1
    + new-netlbfoteam -name "Virtual Production Team" -TeamMembers "Production Virtual ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidArgument: (MSFT_NetLbfoTeam:root/StandardCimv2/MSFT_NetLbfoTeam) [New-NetLbfoTeam
       ], CimException
        + FullyQualifiedErrorId : MiClientApiError_InvalidParameter,New-NetLbfoTeam

    Hi ,
    "Member 'Production Virtual Network A' cannot be teamed as it has a Hyper-V role enabled on it"
    According to this error message , please try to check if the other process occupied the NIC in host .
    Also you can try to remove the NIC from device manager and reload it  , then please create teaming again .
    If it is not the answer please unmark it to continue
    Hope this helps
    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.

  • Cannot apply Hyper v Replica ip failover. [RESOLVED]

    Hello,
    I'm using Hyper with replica server. I have two hosts in Windows Server 2012 with hyper v installed and last integration installed both sides on each VM.
    I have set up the failover ip on each side, and when I try to failoer a machine evryhting work good execpt the ip failover... I have this error : 
    « xxxx» n’a pas pu appliquer les paramètres IP à l’adaptateur « {6f71b925-f7d3-4f7a-b987-ca787eca5643} » : Erreur non spécifiée (0x80004005). (ID d’ordinateur virtuel 3B423647-943C-444C-9E2A-E8C24973B643)
    English : « xxxx»cannot apply ip settings to the adaptor« {6f71b925-f7d3-4f7a-b987-ca787eca5643} » : non specified error (0x80004005). (ID d’ordinateur virtuel 3B423647-943C-444C-9E2A-E8C24973B643)...
    +
    System
    Provider
    [ Name]
    Microsoft-Windows-Hyper-V-Integration-KvpExchange
    [ Guid]
    {82D60869-5ADA-4D49-B76A-309B09666584}
    EventID
    4132
    Version
    0
    Level
    2
    Task
    0
    Opcode
    0
    Keywords
    0x8000000000000000
    TimeCreated
    [ SystemTime]
    2013-12-14T15:02:24.884325200Z
    EventRecordID
    359
    Correlation
    Execution
    [ ProcessID]
    4192
    [ ThreadID]
    1368
    Channel
    Microsoft-Windows-Hyper-V-Integration-Admin
    Computer
    xxxx
    Security
    [ UserID]
    S-1-5-83-1-994195015-1145869372-3269995166-1136030537
    UserData
    VmlEventLog
    VmName
    xxxServer
    VmId
    3B423647-943C-444C-9E2A-E8C24973B643
    String
    {6f71b925-f7d3-4f7a-b987-ca787eca5643}
    ErrorCodeString
    %%2147500037
    ErrorCode
    0x80004005
    Is someone can help me, I'm stucked for one week now and cannot find any solutions... Thank you very much...

    Hi,
    I am glad that this issue is solved. Thank you very much for your sharing.
    This solution you provided will help lots of people who have similar issues.
    Please feel free to ask us if there are any issues in the future.
    Best Regards,
    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.

  • Windows Pro 8.1 Hyper-V enabled - cannot connect to Virtual Machines

    I'm running Windows Pro 8.1. Virtualization is enabled in BIOS. Account is in Admin, Hyper-V, RDP groups. I open Hyper-V manager. Create a new Virtual Switch (internal) and name it. Then create a new virtual machine - name it, place it in a folder under
    C:, Specify Generation (tried both 1 and 2), startup memory 512mb not dynamic, Lan- select the virtual switch created earlier, create an vhdx hard disk, and install the O.S. from an ISO on C. Creates the new VM under Virtual Machines.
    I select the new VM, click connect, then start. A window opens with the new VM on server and says it's connecting to it and it's status is Running. In the Hyper-V manager  in the New Virtual Machine pane (bottom pane) it shows a image that
    appears to have a login screen. The VM window that displays the "Connection to" eventually throws an error : Virtual machine connection: Cannot connect to the virtual machine, Try to connect again. contact your admin, Try again etc. selecting connect
    eventually errors out with check integration services etc. I've read the logs, there are no errors. When I try to shut down or turn off the vm it doesn't respond. I've configured this before on different boxes. It's the work environment for the MCSA 70-462
    training kit Preparation. any direction would be greatly appreciated.

    That is correct.  This has been well documented.
    The WMI namespace changed.  2008 and 2008 R2 now of the v1 virtualization namespace.  2012 knows of both v1 and v2.  And 2012 R2 only knows the v2 virtualization namespace.
    That said, there is more to this.
    2008 management console only knows 2008 features.  So if you connect it to a 2012 server to manage the 2012 server, you cannot manage any of the features released with 2008 R2 nor 2012.
    So, take this second point, mix it with the first point and I recommend that your management server / client release matches the release of the Server you are managing.
    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.
    Disclaimer: Attempting change is of your own free will.

  • Hyper-V Guest Cannot Find Host Domain Controller 2012 R2

    Poweredge T320 server as a Domain Controller,  file server and an EXCHANGE 2010 server. There are no other servers at the site. 
    DHCP is from the firewall.   The DC and the file server will be on the host. 
    The 2010 EXCHANGE server will be on the guest.  The Hyper-V 
    2012 R2 server cannot see the Domain Controller on the host 2012 R2 server. 
    The Active Directory is requesting to be promoted to a Domain Controller.  
    I have a logical or physical error in the installation. 
    It is asking to promote the  Hyper-V guest 2012 R2 to a Domain Controller. 
    I believe I should have only one  Domain Controller in this application.  
    After the Hyper-V guest can see the host domain controller I will install EXCHANGE 2010.
    This is a test environment, offsite.
    NIC1 – Host IP:192.168.1.130, 255.255.255.0, Gateway:192.168.1.1, DNS:127.0.0.1
    NIC2- Only Hyper-V switch checked
    Virtual Switch: 192.168.1.140, 255.255.255.0, Gateway: Blank, DNS: Was 127.0.0.1 didn’t work so I pointed it to the host, 192.168.1.130, but that didn’t work either.
    Host adapter: IP:192.168.1.150, 255.255.255.0, 192.168.1.1, DNS Pointing to HOST:162.168.1.130
    Active Directory and DNS installed on the guest.
    Removed IPv6 from both NICs without any change.
    IPAM is not installed on the host or the guest.
    Several articles in Internet search didn’t help.
    Thanks for your help.

    Hi Steve,
    I suggest referring to the following links:
    REMOTEFX, WINDOWS SERVER & HYPER-V SERVER
    http://blogs.technet.com/b/puneetvig/archive/2011/04/21/remotefx-windows-server-amp-hyper-v-server.aspx
    RemoteFX (with Hyper-V) is a serious business tool. For games.
    http://blogs.technet.com/b/tristank/archive/2012/02/17/remotefx-with-hyper-v-is-a-serious-business-tool-for-games.aspx
    Best Regards,
    Vincent Wu
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Cannot failover cluster

    Hi all,
    In my environment I have 2 exchange 2013 servers : ex01 & ex02 in 1 DAG01. Recently my ex02 server has problem, some exchange service crash ... I'm still finding reason, maybe because lack of memory ... BTW I have a "Mailbox Database 01":
    Get-MailboxDatabaseCopyStatus "Mailbox Database 01"
    Name Status ContentIndexState
    Mailbox Database 01\EX01 Mounted Healthy
    Mailbox Database 01\EX02 Healthy Healthy
    When ex02 has problem, something happen with "Mailbox Database 01" copy on both ex01 & ex02, it cannot be mounted on boths. The status of them keep switching : Mounted , Mounting , Initializing , Disconnected... like this:
    Get-MailboxDatabaseCopyStatus "Mailbox Database 01"
    Name Status ContentIndexState
    Mailbox Database 01\EX01 Mounting Failed
    Mailbox Database 01\EX02 Initializing Failed
    Get-MailboxDatabaseCopyStatus "Mailbox Database 01"
    Name Status ContentIndexState
    Mailbox Database 01\EX01 Initializing Failed
    Mailbox Database 01\EX02 Mounting Failed
    Get-MailboxDatabaseCopyStatus "Mailbox Database 01"
    Name Status ContentIndexState
    Mailbox Database 01\EX01 Disconected Failed
    Mailbox Database 01\EX02 Mounting Failed
    Until I suspend "Mailbox Database 01" copy on ex02, "Mailbox Database 01" will mount on ex01 successfully, then "Mailbox Database 01" edb file on ex02 has "dirty shutdown" state, and I have to reseed "Mailbox
    Database 01" from ex01 to ex02 manually.
    Get-ClusterGroup -Cluster EX01
    Name OwnerNode State
    ClusterGroup ex01 Online
    Available Storage ex02 Offline
    Get-DatabaseAvailabilityGroup -Status -Identity DAG01 | fl name,primaryActiveManager
    Name : DAG01
    PrimaryActiveManager : EX01
    Please let me know if you need any information.
    Thanks for your help.
    Jack.

    Hi John,
    Last time, after re-seed the database status changed to healthy on EX02. I have to note that my DAG can failover before, ex: "Mailbox database 01" can be "mounted" on EX01 , "healthy" on EX02 or vice versa and when one server
    is down (I unplug network cable for example), the mailbox database copy on the other server is mounted automatically, when down server back to online , the mailbox database copy on it is resynchronized from the other automatically. Like I said it has just
    happened recently.
    Recently, even when "Mailbox Database 01" is mounted on EX01 , "healthy" on EX02
    Get-MailboxDatabaseCopyStatus "Mailbox Database 01"
    Name Status ContentIndexState
    Mailbox Database 01\EX01 Mounted Healthy
    Mailbox Database 01\EX02 Healthy Healthy
    When EX02 has problem, "Mailbox Database 01" copy cannot be mounted on boths, its status keep switching...
    During problem I have noticed that there are events appear only on EX02, relating to some exchange programs/services are crashed , ex lastime:
    Faulting application name: MSExchangeHMWorker.exe, version: 15.0.712.0, time stamp: 0x5199cd1a
    Faulting module name: RPCRT4.dll, version: 6.1.7601.21855, time stamp: 0x4eb4c921
    Exception code: 0xc0020043
    Fault offset: 0x000000000008aa13
    Faulting process id: 0x5cfc
    Faulting application start time: 0x01d0067aa7da6ac7
    Faulting application path: C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeHMWorker.exe
    Faulting module path: C:\Windows\system32\RPCRT4.dll
    Report Id: 432d5040-cdfe-11e4-9bb7-3440b58d323f
    Faulting application name: svchost.exe_RpcEptMapper, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1
    Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e
    Exception code: 0xc0000374
    Fault offset: 0x00000000000c40f2
    Faulting process id: 0x2c0
    Faulting application start time: 0x01ce90e16804a9e2
    Faulting application path: C:\Windows\system32\svchost.exe
    Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
    [RpcHttp] An internal server error occurred. The unhandled exception was: System.TypeInitializationException: The type initializer for 'Microsoft.Exchange.Data.Directory.Globals' threw an exception. ---> System.Runtime.InteropServices.COMException: Call was canceled by the message filter. (Exception from HRESULT: 0x80010002 (RPC_E_CALL_CANCELED))
    at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
    at System.Management.ManagementScope.InitializeGuts(Object o)
    at System.Management.ManagementScope.Initialize()
    at System.Management.ManagementObjectSearcher.Initialize()
    at System.Management.ManagementObjectSearcher.Get()
    at Microsoft.Exchange.Data.Directory.Globals.DetectIfMachineIsVirtualMachine()
    at Microsoft.Exchange.Data.Directory.Globals..cctor()
    Watson report about to be sent for process id: 19380, with parameters: E12IIS, c-RTL-AMD64, 15.00.0712.024, w3wp#MSExchangeRpcProxyAppPool, M.E.Data.Directory, M.E.D.D.Globals.DetectIfMachineIsVirtualMachine, System.TypeInitializationException, 55de, 15.00.0712.016.
    ErrorReportingEnabled: False
    [RpcHttp] An internal server error occurred. The unhandled exception was: System.TypeInitializationException: The type initializer for 'Microsoft.Exchange.Data.Directory.Globals' threw an exception. ---> System.Runtime.InteropServices.COMException: Call was canceled by the message filter. (Exception from HRESULT: 0x80010002 (RPC_E_CALL_CANCELED))
    at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
    at System.Management.ManagementScope.InitializeGuts(Object o)
    at System.Management.ManagementScope.Initialize()
    at System.Management.ManagementObjectSearcher.Initialize()
    at System.Management.ManagementObjectSearcher.Get()
    at Microsoft.Exchange.Data.Directory.Globals.DetectIfMachineIsVirtualMachine()
    at Microsoft.Exchange.Data.Directory.Globals..cctor()
    and this time, I found one event appear only on EX02 before problem happened :
    Log Name: Application
    Source: MSExchange Transport Migration
    Date: 3/28/2015 10:34:01 AM
    Event ID: 2005
    Task Category: General
    Level: Error
    Keywords: Classic
    User: N/A
    Computer: EX02.mydomain.com
    Description:
    An unexpected failure has occurred. The problem was ignored but may indicate other problems in the system. Diagnostic information:
    at Microsoft.Exchange.Data.Storage.MapiPropertyBag.SaveChanges(Boolean force) at Microsoft.Exchange.Data.Storage.StoreObjectPropertyBag.SaveChanges(Boolean force) at Microsoft.Exchange.Data.Storage.AcrPropertyBag.SaveChanges(Boolean force) at Microsoft.Exchange.Data.Storage.CoreItem.InternalSave(SaveMode saveMode, CallbackContext callbackContext) at Microsoft.Exchange.Data.Storage.Item.SaveInternal(SaveMode saveMode, Boolean commit) at Microsoft.Exchange.Data.Storage.Item.Save(SaveMode saveMode) at Microsoft.Exchange.Migration.MigrationJob.UpdatePoisonCount(IMigrationDataProvider provider, Int32 count) at Microsoft.Exchange.MailboxReplicationService.CommonUtils.ProcessKnownExceptions(Action actionDelegate, FailureDelegate failureDelegate)|Error clearing posion count for job: local move 3:14a96ad4-4506-4ab8-9be7-c0308a72e555:ExchangeLocalMove:Staged:4:[email protected]:Completed:11/26/2013 7:59:11 PM::|Microsoft.Exchange.Data.Storage.ConnectionFailedTransientException|Cannot save changes made to an item to store.|InnerException:MapiExceptionNetworkError:16.55847:3E000000, 18.59943:BE060000BD07000000000000, 0.62184:00000000, 255.16280:BE0600006E2F610000000000, 255.8600:A81D0000, 255.12696:802C8F080869D001000FC882, 255.10648:02000000, 255.14744:BE060000, 255.9624:F2030000, 255.13720:00000000, 255.11672:01000000, 255.12952:00000000010700C000000000, 3.23260:BE060000, 0.43249:000FC882, 4.39153:15010480, 4.32881:15010480, 0.50035:07000000, 4.64625:15010480, 20.52176:000FC88211001010FE000000, 20.50032:000FC8827E17401076040000, 0.50128:00000000, 0.50288:00000000, 4.23354:15010480, 0.25913:76040000, 255.21817:15010480, 0.17361:76040000, 4.19665:15010480, 0.37632:76040000, 4.37888:15010480|Microsoft.Mapi.MapiExceptionNetworkError: MapiExceptionNetworkError: Unable to save changes. (hr=0x80040115, ec=0) Diagnostic context: Lid: 55847 EMSMDBPOOL.EcPoolSessionDoRpc called [length=62] Lid: 59943 EMSMDBPOOL.EcPoolSessionDoRpc exception [rpc_status=0x6BE][latency=1981] Lid: 62184 Lid: 16280 dwParam: 0x0 Msg: EEInfo: ComputerName: n/a Lid: 8600 dwParam: 0x0 Msg: EEInfo: ProcessID: 7592 Lid: 12696 dwParam: 0x0 Msg: EEInfo: Generation Time: 3/28/0415 3:34:01 AM Lid: 10648 dwParam: 0x0 Msg: EEInfo: Generating component: 2 Lid: 14744 dwParam: 0x0 Msg: EEInfo: Status: 1726 Lid: 9624 dwParam: 0x0 Msg: EEInfo: Detection location: 1010 Lid: 13720 dwParam: 0x0 Msg: EEInfo: Flags: 0 Lid: 11672 dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 1 Lid: 12952 dwParam: 0x0 Msg: EEInfo: prm[0]: Long val: 3221227265 Lid: 23260 Win32Error: 0x6BE Lid: 43249 Lid: 39153 StoreEc: 0x80040115 Lid: 32881 StoreEc: 0x80040115 Lid: 50035 Lid: 64625 StoreEc: 0x80040115 Lid: 52176 ClientVersion: 15.0.712.17 Lid: 50032 ServerVersion: 15.0.712.6014 Lid: 50128 Lid: 50288 Lid: 23354 StoreEc: 0x80040115 Lid: 25913 Lid: 21817 ROP Failure: 0x80040115 Lid: 17361 Lid: 19665 StoreEc: 0x80040115 Lid: 37632 Lid: 37888 StoreEc: 0x80040115 at Microsoft.Mapi.MapiExceptionHelper.InternalThrowIfErrorOrWarning(String message, Int32 hresult, Boolean allowWarnings, Int32 ec, DiagnosticContext diagCtx, Exception innerException) at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, IExInterface iUnknown, Exception innerException) at Microsoft.Mapi.MapiProp.SaveChanges(SaveChangesFlags flags) at Microsoft.Exchange.Data.Storage.MapiPropertyBag.SaveChanges(Boolean force)|: ,,
    %2
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="MSExchange Transport Migration" />
    <EventID Qualifiers="49152">2005</EventID>
    <Level>2</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-03-28T03:34:01.000000000Z" />
    <EventRecordID>10409597</EventRecordID>
    <Channel>Application</Channel>
    <Computer>IDCEXC002.itl.com</Computer>
    <Security />
    </System>
    <EventData>
    <Data> at Microsoft.Exchange.Data.Storage.MapiPropertyBag.SaveChanges(Boolean force) at Microsoft.Exchange.Data.Storage.StoreObjectPropertyBag.SaveChanges(Boolean force) at Microsoft.Exchange.Data.Storage.AcrPropertyBag.SaveChanges(Boolean force) at Microsoft.Exchange.Data.Storage.CoreItem.InternalSave(SaveMode saveMode, CallbackContext callbackContext) at Microsoft.Exchange.Data.Storage.Item.SaveInternal(SaveMode saveMode, Boolean commit) at Microsoft.Exchange.Data.Storage.Item.Save(SaveMode saveMode) at Microsoft.Exchange.Migration.MigrationJob.UpdatePoisonCount(IMigrationDataProvider provider, Int32 count) at Microsoft.Exchange.MailboxReplicationService.CommonUtils.ProcessKnownExceptions(Action actionDelegate, FailureDelegate failureDelegate)|Error clearing posion count for job: local move 3:14a96ad4-4506-4ab8-9be7-c0308a72e555:ExchangeLocalMove:Staged:4:[email protected]:Completed:11/26/2013 7:59:11 PM::|Microsoft.Exchange.Data.Storage.ConnectionFailedTransientException|Cannot save changes made to an item to store.|InnerException:MapiExceptionNetworkError:16.55847:3E000000, 18.59943:BE060000BD07000000000000, 0.62184:00000000, 255.16280:BE0600006E2F610000000000, 255.8600:A81D0000, 255.12696:802C8F080869D001000FC882, 255.10648:02000000, 255.14744:BE060000, 255.9624:F2030000, 255.13720:00000000, 255.11672:01000000, 255.12952:00000000010700C000000000, 3.23260:BE060000, 0.43249:000FC882, 4.39153:15010480, 4.32881:15010480, 0.50035:07000000, 4.64625:15010480, 20.52176:000FC88211001010FE000000, 20.50032:000FC8827E17401076040000, 0.50128:00000000, 0.50288:00000000, 4.23354:15010480, 0.25913:76040000, 255.21817:15010480, 0.17361:76040000, 4.19665:15010480, 0.37632:76040000, 4.37888:15010480|Microsoft.Mapi.MapiExceptionNetworkError: MapiExceptionNetworkError: Unable to save changes. (hr=0x80040115, ec=0) Diagnostic context: Lid: 55847 EMSMDBPOOL.EcPoolSessionDoRpc called [length=62] Lid: 59943 EMSMDBPOOL.EcPoolSessionDoRpc exception [rpc_status=0x6BE][latency=1981] Lid: 62184 Lid: 16280 dwParam: 0x0 Msg: EEInfo: ComputerName: n/a Lid: 8600 dwParam: 0x0 Msg: EEInfo: ProcessID: 7592 Lid: 12696 dwParam: 0x0 Msg: EEInfo: Generation Time: 3/28/0415 3:34:01 AM Lid: 10648 dwParam: 0x0 Msg: EEInfo: Generating component: 2 Lid: 14744 dwParam: 0x0 Msg: EEInfo: Status: 1726 Lid: 9624 dwParam: 0x0 Msg: EEInfo: Detection location: 1010 Lid: 13720 dwParam: 0x0 Msg: EEInfo: Flags: 0 Lid: 11672 dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 1 Lid: 12952 dwParam: 0x0 Msg: EEInfo: prm[0]: Long val: 3221227265 Lid: 23260 Win32Error: 0x6BE Lid: 43249 Lid: 39153 StoreEc: 0x80040115 Lid: 32881 StoreEc: 0x80040115 Lid: 50035 Lid: 64625 StoreEc: 0x80040115 Lid: 52176 ClientVersion: 15.0.712.17 Lid: 50032 ServerVersion: 15.0.712.6014 Lid: 50128 Lid: 50288 Lid: 23354 StoreEc: 0x80040115 Lid: 25913 Lid: 21817 ROP Failure: 0x80040115 Lid: 17361 Lid: 19665 StoreEc: 0x80040115 Lid: 37632 Lid: 37888 StoreEc: 0x80040115 at Microsoft.Mapi.MapiExceptionHelper.InternalThrowIfErrorOrWarning(String message, Int32 hresult, Boolean allowWarnings, Int32 ec, DiagnosticContext diagCtx, Exception innerException) at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, IExInterface iUnknown, Exception innerException) at Microsoft.Mapi.MapiProp.SaveChanges(SaveChangesFlags flags) at Microsoft.Exchange.Data.Storage.MapiPropertyBag.SaveChanges(Boolean force)|: ,,</Data>
    </EventData>
    </Event>
    I also noticed that "Mailbox Database 01" edb file on EX02 has "dirty shutdown" state (yes, last time too)
    eseutil /mh “path to Mailbox Database 01 edb file on EX02″ and result :
    State: Dirty Shutdown
    Log Required: 4656967-4657077 (0x470f47-0x470fb5)
    Log Committed: 0-4657078 (0x0-0x470fb6)
    I'm going to reseed "Mailbox Database 01" copy on EX02 tonight, should I repair it with eseutil /r to get it into clean shutdown state before ?
    How can I check if my DAG configuration is fine ? Is result from Get-Clustergroup before ok ?

  • 3 Node hyper-V 2012 R2 Failover Clustering with Storage spaces on one of the Hyper-V hosts

    Hi,
    We have 3x Dell R720s with 5x 600GB 3.5 15K SAS and 128 GB RAM each. Was wondering if I could setup a Fail-over Hyper-V 2012 R2 Clustering with these 3 with the shared storage for the CSV being provided by one of the Hyper-V hosts with storage spaces installed
    (Is storage spaces supported on Hyper-V?) Or I can use a 2-Node Failover clustering and the third one as a standalone Hyper-V or Server 2012 R2 with Hyper-V and storage spaces.  
    Each Server comes with QP 1G and a DP10G nics so that I can dedicate the 10G nics for iSCSI
    Dont have a SAN or a 10G switch so it would be a crossover cable connection between the servers.
    Most of the VMs would be Non-HA. Exchange 2010, Sharepoint 2010 and SQL Server 2008 R2 would be the only VMS running as HA-VMs. CSV for the Hyper-V Failover cluster would be provided by the storage spaces.

    I thought I was tying to do just that with 8x600 GB RAID-10 using the H/W RAID controller (on the 3rd Server) and creating CSVs out of that space so as to provide better storage performance for the HA-VMs.
    1. Storage Server : 8x 600GB RAID-10 (For CSVs to house all HA-VMs running on the other 2 Servers) It may also run some local VMs that have very little disk I/O
    2. Hyper-V-1 : Will act has primary HYPER-V hopst for 2x Exchange and Database Server HA-VMs (the VMDXs would be stored on the Storage Servers CSVs on top of the 8x600GB RAID-10). May also run some non-HA VMs using the local 2x600 GB in RAID-1 
    3. Hyper-V-2 : Will act as a Hyper-V host when the above HA-VMs fail-over to this one (when HYPER-V-1 is down for any reason). May also run some non-HA VMs using the local 2x600 GB in RAID-1 
    The single point of failure for the HA-VMs (non HA-VMs are non-HA so its OK if they are down for some time) is the Storage Server. The Exchange servers here are DAG peers to the Exchange Servers at the head office so in case the storage server mainboard
    goes down (disk failure is mitigated using RAID, other components such as RAM, mainboard may still go but their % failure is relatively low) the local exchange servers would be down but exchange clients will still be able to do their email related tasks using
    the HO Exchange servers.
    Also they are under 4hr mission critical support including entire server replacement within the 4 hour period. 
    If you're OK with your shared storage being a single point of failure then sure you can proceed the way you've listed. However you'll still route all VM-related I/O over Ethernet which is obviously slower then running VMs from DAS (with or without virtual SAN
    LUN-to-LUN replication layer) as DAS has higher bandwidth and smaller latency. Also with your scenario you exclude one host from your hypervisor cluster so running VMs on a pair of hosts instead of three would give you much worse performance and resilience:
    with 1 from 3 physical hosts lost cluster would be still operable and with 1 from 2 lost all VMs booted on a single node could give you inadequate performance. So make sure your hosts would be insanely underprovisioned as every single node should be able to
    handle ALL workload in case of disaster. Good luck and happy clustering :)
    StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

  • Our team cannot see shared and sync'd files in our Creative Cloud account.  How can we fix this?

    The team members are logged in, have loaded a test file in the Creative Cloud Files directory, uploaded them to the Cloud and made the files public, but we cannot see them in the web browser under "Creative Cloud Files".
    The files seem to be there because we can send an email with a link to the files and can see them through the linke, just not in the browser.
    What might we be doing wrong?

    Folder sharing is not available yet. It is being worked on.
    So currently a file is owned by one Adobe ID. That Adobe ID can create a public sharing link to that file. Anyone can access this link whether or not they are signed in with an Adobe ID.

  • Hyper NIC teaming HP ProLiant BL685c G7

    we are in process of creating HYPER-V 2012 r2 with 2 server initially.
    HP ProLiant BL685c G7 (2 server )
    Below are the NIC details, and we have IBM SAN storage,
    Can someone provide or links some details, where I can create a NIC bonding
    Can I bond all the 4 NIC and from there Can i create a VNIC, 1 for management, I for Vmotion, I for cluster and 1 for VM
    Is that Correct my assumption is ?

    Sam,
    As you have given guidance, Just few more query when I am configuring, Below is the script I have run to complete the task.
    Questions are on Red color
    New-NetLbfoTeam -Name TEAMNIC -TeamMembers NIC1,NIC2,NIC3,NIC4 -LoadBalancingAlgorithm HyperVPort -TeamingMode SwitchIndependent
    New-VMSwitch -Name VSWITCH -NetAdapterName TEAMNIC -AllowManagementOS $False -MinimumBandwidthMode Weight
    Set-VMSwitch VSWITCH -DefaultFlowMinimumBandwidthWeight 20
    Add-VMNetworkAdapter -ManagementOS -Name "Management" -SwitchName "VSWITCH"
    Add-VMNetworkAdapter -ManagementOS -Name "LiveMigration" -SwitchName "VSWITCH"
    Add-VMNetworkAdapter -ManagementOS -Name "VirtualMachine" -SwitchName "VSWITCH"
    Add-VMNetworkAdapter -ManagementOS -Name "CLuster" -SwitchName "VSWITCH"
    Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "Management" -Access -VlanId 251
    Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "VirtualMachine" -Access -VlanId 61
     Question1 . I am unable to add or set multiple Vlan on One VNIC--Please let me know
    Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "LiveMigration" -Access -VlanId 62
    Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "CLuster" -Access -VlanId ???
             Question2 . Do I need to assign Vlan and IP adress for the Cluster NIC and Livemigration
             Question3 . For example If  want to give IP on Cluster VNIC like treditional SQL  heartbeat NIC IP without Gateway, do I need to enable the Vlan on switch trunk, As of now only        
    Vlan 251,61,62 allowed at this moment
    Set-VMNetworkAdapter -ManagementOS -Name "Management" -MinimumBandwidthWeight 10
    Set-VMNetworkAdapter -ManagementOS -Name "VirtualMachine" -MinimumBandwidthWeight 50
    Set-VMNetworkAdapter -ManagementOS -Name "LiveMigration" -MinimumBandwidthWeight 30
    Set-VMNetworkAdapter -ManagementOS -Name "CLuster" -MinimumBandwidthWeight 30

  • Cannot migrate VM in VMM but can in Failover Cluster Manager network adapters network optimization warning

    I have a 4 node Server 2012 R2 Hyper-V Cluster and manage it with VMM 2012 R2.  I just upgraded the cluster from 2012 RTM to 2012 R2 last week which meant pulling 2 nodes out of the existing cluster, creating the new R2 cluster, running the copy
    cluster roles wizard since the VHDs are stored on CSVs, and then added the other 2 nodes after installing R2 on them, back into the cluster.  After upgrading the cluster I am unable to migrate some VMs from one node to another.  When trying to do
    a live migration, I get the following notifications under the Rating Explanation tab:
    Warning: There currently are not network adapters with network optimization available on host Node7. 
    Error: Configuration issues related to the virtual machine VM1 prevent deployment and must be resolved before deployment can continue. 
    I get this error for 3 out of the 4 nodes in the cluster.  I do not get this error for Node10 and I can live migrate to that node in VMM.  It has a green check for Network optimization.  The others do not.  These errors only affect
    VMM. In the Failover Cluster Manager, I can live migrate any VM to any node in the cluster without any issues.  In the old 2012 RTM cluster I used to get the warning but I could still migrate the VMs anywhere I wanted to.  I've checked the network
    adapter settings in VMM on VM1 and they are the same as VM2 which can migrate to any host in VMM.  I then checked the network adapter settings of the VMs from the Failover Cluster Manager and VM1 under Hardware Acceleration has "Enable virtual machine
    queue" and Enable IPsec task offloading" checked.  I unchecked those 2 boxes refreshed the VMs, refreshed the cluster, rebooted the VM and refreshed again but I still could not live migrate VM1.  Why is this an issue now but it wasn't before
    running on the new cluster?  How do I resolve the issue?  VMM is useless if I can't migrate all my VMs with it.

    I checked the settings on the physical nics on each node and here is what I found:
    Node7: Virtual machine queue is not listed (Cannot live migrate problem VM's to this node in VMM)
    Node8: Virtual machine queue is not listed (Cannot live migrate problem VM's to this node in VMM)
    Node9: Virtual machine queue is listed and enabled (Cannot live migrate problem VM's to this node in VMM)Node10: Virtual machine queue is listed and enabled (Live Migration works on all VMs in VMM)
    From Hyper-V or the Failover Cluster manager I can see in the network adapter settings of the VMs under Hardware Acceleration that these two settings are checked "Enable virtual machine queue" and Enable IPsec task offloading".  I unchecked those
    2 boxes, refreshed the VMs, refreshed the cluster, rebooted the VM and refreshed again but I still cannot live migrate the problem VMs.
    It seems to me that if I could adjust those VM settings from VMM that it might fix the problem.  Why isn't that an option to do so in VMM? 
    Do I have to rebuild the VMM server with a new DB and then before adding the Hyper-V cluster uncheck those two settings on the VM's from Hyper-V manager?  That would be a lot of unnecessary work but I don't know what else to do at this point.

  • Failover Cluster Hyper-V Storage Choice

    I am trying to deploy a 2 nodes Hyper-V Failover cluster in a closed environment.  My current setup is 2 servers as hypervisors and 1 server as AD DC + Storage server.  All 3 are running Windows Server 2012 R2.
    Since everything is running on Ethernet, my choice of storage is between iSCSI and SMB3.0 ?
    I am more inclined to use SMB3.0 and I did find some instructions online about setting up a Hyper-V cluster connecting to a SMB3.0 File server cluster.  However, I only have budget for 1 storage Server.  Is it a good idea to choice SMB over iSCSI
    in this scenario?  ( where there is only 1 storage for the Hyper-V Cluster ). 
    What do I need to pay attention to in this setup?  Except some unavoidable single points of failures. 
    In the SMB3.0 File server cluster scenario that I mentioned above, they had to use SAS drives for the file server cluster (CSV).  I am guessing in my scenario, SATA drives should be fine, right?

    "I suspect that Starwind solution achieves FT by running shadow copies of VMs on the partner Hypervisor"
    No, it does not run shadow VMs on the partner hypervisor.  Starwind is a product in a family known as 'software defined storage'.  There are a number of solutions on the market.  They all provide a similar service in that they allow for the
    use of local storage, also known as Direct Attached Storage (DAS), instead of external, shared storage for clustering.  Each of these products provides some method to mirror or 'RAID' the storage among the nodes in the software defined storage. 
    So, yes, there is some overhead to ensure data redundancy, but none of this class of product will 'shadow' VMs on another node.  Products like Starwind, Datacore, and others are nice entry points to HA without the expense of purchasing an external storage
    shelf/array of some sort because DAS is used instead.
    1) "Software Defined Storage" is a VERY wide term. Many companies use it for solutions that DO require actual hardware to run on. Say Nexenta claims they do SDS and they need a separate physical servers running Solaris and their (Nexenta) storage app. Microsoft
    we all love so much because they give us infrastructure we use to make our living also has Clustered Storage Spaces MSFT tells is a "Software Defined Storage" but they need physical SAS JBODs, SAS controllers and fabric to operate. These are hybrid software-hardware
    solutions. More pure ones don't need any hardware but they still share actual server hardware with hypervisor (HP VSA, VMware Virtual SAN, oh, BTW, it does require flash to operate so it's again not pure software thing). 
    2) Yes there are number of solutions but devil is in details. Technically all virtualization world is sliding away from ancient way of VM-running storage virtualization stacks to ones being part of a hypervisor (VMware Virtual Storage Appliance replaced
    with VMware Virtual SAN is an excellent example). So talking about Hyper-V there are not so many companies who have implemented VM-less solutions. Except the ones you've named it's also SteelEye and that's all probably (Double-Take cannot replicate running
    VMs effectively so cannot be counted). Running storage virtualization stack as part of a Hyper-V has many benefits compared to VM-running stuff:
    - Performance. Obviously kernel-space running DMA engines (StarWind) and polling driver model (DataCore) are faster in terms of latency and IOPS compared to VM-running I/O all routed over VMBus and emulated storage and network hardware.
    - Simplicity. With native apps it's click and install. With VMs it's UNIX management burden (BTW, who will update forked-out Solaris VSA is running on top of? Sun? Out of business. Oracle? You did not get your ZFS VSA from Oracle. Who?) and always "hen and
    chicken" issue. Cluster starts, it needs access to shared storage to spawn a VMs but VMs are inside a VM VSA that need to be spawned. So first you start storage VMs, then make them sync (few terabytes, maybe couple of hours to check access bitmaps for volumes)
    and only after that you can start your other production VMs. Very nice!
    - Scenario limitations. You want to implement a SCV for Scale-Out File Servers? You canont use HP VSA or StorMagic because SoFS and Hyper-V roles cannot mix on the same hardware. To surf SMB 3.0 tide you need native apps or physical hardware behind. 
    That's why current virtualization leader VMware had clearly pointed where these types of things need to run - side-by-side with hypervisor kernel.
    3) DAS is not only cheaper but also faster then SAN and NAS (obviously). So sure there's no "one size fits all" but unless somebody needs a a) very high LUN density (Oracle or huge SQL database or maybe SAP) and b) very strict SLAs (friendly telecom company
    we provide Tier2 infrastructure for runs cell phone stats on EMC, $1M for a few terabytes. Reason? EMC people have FOUR units like that marked as a "spare" and have requirement to replace failed one in less then 15 minutes) there's no point to deploy hardware
    SAN / NAS for shared storage. SAN / NAS is an sustained innovation and Virtual SAN is disruptive. Disruptive comes to replace sustained for 80-90% of business cases to allow sustained live in a niche deployments. Clayton Christiansen\s "Innovator's Dilemma".
    Classic. More here:
    Disruptive Innovation
    http://en.wikipedia.org/wiki/Disruptive_innovation
    So I would not consider Software Defined Storage as a poor-mans HA or usable to Test & Development only. Thing is ready for prime time long time ago. Talk to hardware SAN VARs if you have connections: How many stand-alone units did they sell to SMBs
    & ROBO deployments last year?
    StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

  • Packets sent out the wrong Interface on Hyper-V 2012 Failover Cluster

    Here is some background information:
    2 Dell PowerEdge servers running Windows Server 2012 w/ Hyper-V in a Failover Cluster environment.  Each has:
    1 NIC for Live Migration 192.168.80.x/24 (connected to a private switch)
    1 NIC for Cluster Communication 192.168.90.x/24 (connected to a private switch)
    1 NIC for iscsi 192.168.100.x/24 (connected to a private switch)
    1 NIC for host management with a routable public IP (*connected to corp network) w/ gateway on this interface
    1 NIC for Virtual Machine traffic (*connected to corp network)
    All NICs are up, we can ping the IPs between servers on the private network and on the public facing networks.  All functions of hyper-v are working and the failover cluster reports all interfaces are up and we receive no errors.  Live migration
    works fine.  In the live migration settings i have restricted the use of the 2 NICs (live migration or cluster comm).
    My problem is that our networking/security group sees on occasion (about every 10 minutes with a few other packets thrown in at different times) syn packets that are destined for the 192.168.80.3 interface goes out of the public interface and is dropped
    at our border router.  These should be heading out of the 192.168.80.x or 192.168.90.x interfaces without ever hitting our corporate network. Anyone have an idea of why this might be happening?  Traffic is on TCP 445.
    Appreciate the help.
    Nate

    Hi,
    Please check live migration and Cluster Communication network settings in cluster:
    In the Failover Cluster Manager snap-in, if the cluster that you want to configure is not displayed, in the console tree, right-click Failover Cluster Manager, click Manage a Cluster, and then select or specify the cluster that you want.
    If the console tree is collapsed, expand the tree under the cluster that you want to configure.
    Expand Networks.
    Right-click the network that you want to modify settings for, and then click Properties.
    There are two options:
    Allow cluster network communication on this network-- Allow clients to connect through this network
    Do not allow cluster network communication on this network
    If the network is used only for cluster node communication, clear “Allow clients to connect through this network” option.
    Check that and give us feedback for further troubleshooting, for more information please refer to following MS articles:
    Modify Network Settings for a Failover Cluster
    http://technet.microsoft.com/en-us/library/cc725775.aspx
    Lawrence
    TechNet Community Support

Maybe you are looking for