RMAN to connect to all nodes within the cluster to parallelize backups

Hi,
I wish to configure my RMAN catalog to backup my Production RAC backups. I wish to parallelize my backups to backup database files of different nodes.
Can anyone help me how can it be done?
Regards,
Srini

Hi,
May be you are right. I see my RAC cluster databases grow very fast and some nodes are not really performing well resources wise. So, i may need to parallalize the backups across the nodes.
However, i have another idea of finding the best node and take backup on it. checking with my system admins at this point.
Is there any way RMAN can know if the node went down so that it needs to backup the database on a different node instead of the first node it attempted?
May be this is a different question.
Regards,
srini

Similar Messages

  • RAC Instalation Problem (shared accross all the nodes in the cluster)

    All experts
    I am trying for installing Oracle 10.2.0 RAC on Redhat 4.7
    reff : http://www.oracle-base.com/articles/10g/OracleDB10gR2RACInstallationOnLinux
    All steps successfully completed on all nodes (rac1,rac2) every thing is okey for each node
    on single node rac instalation successfull.
    when i try to install on two nodes
    on specify Oracle Cluster Registry (OCR) location showing error
    the location /nfsmounta/crs.configuration is not shared accross all the nodes in the cluster. Specify a shared raw partation or cluster file system file that is visible by the same name on all nodes of the cluster.
    I create shared disks on all nodes as:
    1 First we need to set up some NFS shares. Create shared disks on NAS or a third server if you have one available. Otherwise create the following directories on the RAC1 node.
    mkdir /nfssharea
    mkdir /nfsshareb
    2. Add the following lines to the /etc/exports file. (edit /etc/exports)
    /nfssharea *(rw,sync,no_wdelay,insecure_locks,no_root_squash)
    /nfsshareb *(rw,sync,no_wdelay,insecure_locks,no_root_squash)
    3. Run the following command to export the NFS shares.
    chkconfig nfs on
    service nfs restart
    4. On both RAC1 and RAC2 create some mount points to mount the NFS shares to.
    mkdir /nfsmounta
    mkdir /nfsmountb
    5. Add the following lines to the "/etc/fstab" file. The mount options are suggestions from Kevin Closson.
    nas:/nfssharea /nfsmounta nfs rw,bg,hard,nointr,tcp,vers=3,timeo=300,rsize=32768,wsize=32768,actimeo=0 0 0
    nas:/nfsshareb /nfsmountb nfs rw,bg,hard,nointr,tcp,vers=3,timeo=300,rsize=32768,wsize=32768,actimeo=0 0 0
    6. Mount the NFS shares on both servers.
    mount /mount1
    mount /mount2
    7. Create the shared CRS Configuration and Voting Disk files.
    touch /nfsmounta/crs.configuration
    touch /nfsmountb/voting.disk
    Please guide me what is wrong

    I think you did not really mount it on the second server. what is the output of 'ls /nfsmounta'.
    step 6 should be 'mount /nfsmounta', not 'mount 1'. I also don't know if simply creating a zero-size file is sufficient for ocr (i have always used raw devices, not nfs for this)

  • How to find out the IP@s of all nodes in a cluster?

    Is there any way to retrieve the IP addresses of all nodes in a cluster?
    The problem is the following. We intend to write an administration program
    that administers all nodes of a cluster using rmi (e.g. tell all singletons
    in the cluster to reload configuration values etc.). My understanding is
    that rmi only talks to a single node in a cluster. It would be a convenient
    feature if the administration program could figure out all nodes in a
    cluster by itself and then administers each node sequentially. So far we're
    planning to pass all IP addresses to the administration program e.g. as
    command line arguments but what if a node gets left out due to human error?
    Thanks for your help.
    Bernie

    There is no public interface to inquire about the IP addresses of the servers in a cluster. If you use WLS 6.0, there is an administrative console that uses JMX to manage the cluster. Perhaps that would be of use to you?
    Bernhard Lenz wrote:
    Is there any way to retrieve the IP addresses of all nodes in a cluster?
    The problem is the following. We intend to write an administration program
    that administers all nodes of a cluster using rmi (e.g. tell all singletons
    in the cluster to reload configuration values etc.). My understanding is
    that rmi only talks to a single node in a cluster. It would be a convenient
    feature if the administration program could figure out all nodes in a
    cluster by itself and then administers each node sequentially. So far we're
    planning to pass all IP addresses to the administration program e.g. as
    command line arguments but what if a node gets left out due to human error?
    Thanks for your help.
    Bernie

  • Retrieve data from other context node within the same context

    Hi Experts,
    I want to redefine method BUILD_TABLE for a table context node and I need to access data from another context node within the same context. I have looked through the methods of class CL_BSP_WD_CONTEXT_NODE_TV but could not find a mean of retrieving the other context nodes.
    Any ideas?
    Thanks a lot. Your help is appreciated.
    Cheers,
    Jens

    Hi Jens,
    Check this [wiki|http://wiki.sdn.sap.com/wiki/pages/viewpage.action?pageId=201066680] it should be helpful.
    Regards,
    Shobhit

  • Four straight lines have appeared on my screen, top to bottom.  Any idea where the came from, and can they be removed?  These all come within the past few days.

    Four straight lines have appeared on my screen, top to bottom.  Any idea where the came from, and can they be removed?  These all come within the past few days.

    It's most likely the Display going out on a few lines, but can be Graphic card related, which model & display?

  • Add node to the cluster

    Dear Experts,
    Please help me, I am new in RAC and I have a question please;
    We have 6 nodes cluster of 11.2.0.2.3 version and my manager wants me to add a new node to the cluster.
    Could you please send me the steps 1, 2 , 3 ...
    we have not shared oracle homes (oracle user), not shared grid homes (grid user) and they are all patched with patch set update 3 (11.2.0.2.3) all under Enterprise Redhat Linux 5.5.
    Please also tell me with which system user (oracle, root or grid) I have to run each command...
    Could you help me?
    S

    I have the following errors, could you help me please? (Oracle and grid homes are not shared)
    -bash-3.2$ ./addNode.sh "CLUSTER_NEW_NODES={db07}" "CLUSTER_NEW_VIRTUAL_HOSTNAMES={db07-vip}"
    Performing pre-checks for node addition
    Checking node reachability...
    Node reachability check passed from node "db01"
    Checking user equivalence...
    User equivalence check passed for user "grid"
    Checking node connectivity...
    Checking hosts config file...
    Verification of the hosts config file successful
    Check: Node connectivity for interface "bond1"
    Node connectivity passed for interface "bond1"
    Node connectivity check passed
    Checking CRS integrity...
    CRS integrity check passed
    Checking shared resources...
    Checking CRS home location...
    ERROR:
    PRVF-4864 : Path location check failed for: "/opt/11.2.0/grid"
    Shared resources check for node addition failed
    Check failed on nodes:
            db07
    Checking node connectivity...
    Checking hosts config file...
    Verification of the hosts config file successful
    Check: Node connectivity for interface "bond0"
    Node connectivity passed for interface "bond0"
    Check: Node connectivity for interface "bond1"
    Node connectivity passed for interface "bond1"
    Node connectivity check passed
    Total memory check passed
    Available memory check passed
    Swap space check failed
    Check failed on nodes:
            db01,db07
    Free disk space check failed for "db01:/tmp"
    Check failed on nodes:
            db01
    Free disk space check failed for "db07:/tmp"
    Check failed on nodes:
            db07
    Check for multiple users with UID value 501 passed
    User existence check passed for "grid"
    Run level check passed
    Hard limits check passed for "maximum open file descriptors"
    Soft limits check passed for "maximum open file descriptors"
    Hard limits check passed for "maximum user processes"
    Soft limits check passed for "maximum user processes"
    System architecture check passed
    Kernel version check passed
    Kernel parameter check passed for "semmsl"
    Kernel parameter check passed for "semmns"
    Kernel parameter check passed for "semopm"
    Kernel parameter check passed for "semmni"
    Kernel parameter check passed for "shmmax"
    Kernel parameter check passed for "shmmni"
    Kernel parameter check passed for "shmall"
    Kernel parameter check passed for "file-max"
    Kernel parameter check passed for "ip_local_port_range"
    Kernel parameter check passed for "rmem_default"
    Kernel parameter check passed for "rmem_max"
    Kernel parameter check passed for "wmem_default"
    Kernel parameter check passed for "wmem_max"
    Kernel parameter check passed for "aio-max-nr"
    Package existence check passed for "make-3.81( x86_64)"
    Package existence check passed for "binutils-2.17.50.0.6( x86_64)"
    Package existence check passed for "gcc-4.1.2 (x86_64)( x86_64)"
    Package existence check passed for "libaio-0.3.106 (x86_64)( x86_64)"
    Package existence check passed for "glibc-2.5-24 (x86_64)( x86_64)"
    Package existence check passed for "compat-libstdc++-33-3.2.3 (x86_64)( x86_64)"
    Package existence check passed for "elfutils-libelf-0.125 (x86_64)( x86_64)"
    Package existence check passed for "elfutils-libelf-devel-0.125( x86_64)"
    Package existence check passed for "glibc-common-2.5( x86_64)"
    Package existence check passed for "glibc-devel-2.5 (x86_64)( x86_64)"
    Package existence check passed for "glibc-headers-2.5( x86_64)"
    Package existence check passed for "gcc-c++-4.1.2 (x86_64)( x86_64)"
    Package existence check passed for "libaio-devel-0.3.106 (x86_64)( x86_64)"
    Package existence check passed for "libgcc-4.1.2 (x86_64)( x86_64)"
    Package existence check passed for "libstdc++-4.1.2 (x86_64)( x86_64)"
    Package existence check passed for "libstdc++-devel-4.1.2 (x86_64)( x86_64)"
    Package existence check passed for "sysstat-7.0.2( x86_64)"
    Package existence check passed for "ksh-20060214( x86_64)"
    Check for multiple users with UID value 0 passed
    Current group ID check passed
    Checking OCR integrity...
    OCR integrity check passed
    Checking Oracle Cluster Voting Disk configuration...
    Oracle Cluster Voting Disk configuration check passed
    Time zone consistency check passed
    Starting Clock synchronization checks using Network Time Protocol(NTP)...
    NTP Configuration file check started...
    NTP Configuration file check passed
    Checking daemon liveness...
    Liveness check passed for "ntpd"
    Check for NTP daemon or service alive passed on all nodes
    NTP daemon slewing option check passed
    NTP daemon's boot time configuration check for slewing option passed
    NTP common Time Server Check started...
    Check of common NTP Time Server passed
    Clock time offset check from NTP Time Server started...
    PRVF-5413 : Node "db01" has a time offset of -165613.0 that is beyond permissible limit of 1000.0 from NTP Time Server "192.168.248.253"
    PRVF-5413 : Node "db07" has a time offset of -161593.0 that is beyond permissible limit of 1000.0 from NTP Time Server "192.168.248.253"
    PRVF-5424 : Clock time offset check failed
    Clock synchronization check using Network Time Protocol(NTP) failed
    User "grid" is not part of "root" group. Check passed
    Checking consistency of file "/etc/resolv.conf" across nodes
    File "/etc/resolv.conf" does not have both domain and search entries defined
    domain entry in file "/etc/resolv.conf" is consistent across nodes
    search entry in file "/etc/resolv.conf" is consistent across nodes
    All nodes have one search entry defined in file "/etc/resolv.conf"
    The DNS response time for an unreachable node is within acceptable limit on all nodes
    File "/etc/resolv.conf" is consistent across nodes
    Checking VIP configuration.
    Checking VIP Subnet configuration.
    Check for VIP Subnet configuration passed.
    Checking VIP reachability
    Check for VIP reachability passed.
    Pre-check for node addition was unsuccessful on all the nodes.
    -bash-3.2$

  • Can I use one transport adapter on the nodes of the cluster?

    Hi
    I am new to sun cluster, in the cluster documentation they mentioned that each node should have 2 network cards one for public connections and one for private connection. what if I do not want the nodes to have public connections except for one node. In other words, I want to use one network card on each node except for the first node in the cluster, users can access the rest of the nodes through the fist node . Is that possible? If yes, what should be the name of the second transport adapter while installing the cluster software on the nodes.
    Thank You for the help

    Dear
    We are using cluster for HA on failover condition, If you have only one network adapter so how you work in failover, and you can't assign one adaptor to two node as same, you have min 2 network adapter for 2 node cluster..
    :)GooDLucK
    Mohammed Tanvir

  • How is index data managed within the cluster?

    Hello
    We are in the process of evaluating Coherence.
    With regard to indexes, am I correct in thinking that the data for the index is stored in an (internally managed) cache on the same node as the attendant indexed values? I'm not interested in getting at the index data, but rather just understanding how the index data itself is treated/stored within the cluster.
    So in a 2 node cluster where an index is applied to a distributed cache that only has 2 entries, will there be an index cache on each node that has 1 {Binary,key} entry where the key points to the value that is stored on that same node? That is, I trust that the index data is spread out across the cluster in the case of a partitioned topology?
    Regards
    Peter

    user11279467 wrote:
    Hello
    We are in the process of evaluating Coherence.
    With regard to indexes, am I correct in thinking that the data for the index is stored in an (internally managed) cache on the same node as the attendant indexed values? I'm not interested in getting at the index data, but rather just understanding how the index data itself is treated/stored within the cluster.
    So in a 2 node cluster where an index is applied to a distributed cache that only has 2 entries, will there be an index cache on each node that has 1 {Binary,key} entry where the key points to the value that is stored on that same node? That is, I trust that the index data is spread out across the cluster in the case of a partitioned topology?
    Regards
    PeterHi Peter,
    up to 3.4.x indexes were supported only on partitioned topology, and yes, indexes on each node contain only data corresponding to entries which have their primary copy on that node (referred to as local entries from now on).
    The indexes are not stored in a cache but they are managed as part of the information Coherence maintains about the backing map (the map which contains local entries).
    The indexes are made of 2 parts:
    - forward index: this is a mapping from the cache key in an internal representation (backing map keys from now on) to the value extracted with the extractor used to create the index from the entry belonging to the cache key (extracted value from now on)
    - reverse index (aka. reverse map): this is a mapping from the extracted value to a set of backing map keys of entries from which the reverse index key was extracted with the extractor used to create the index
    The index can be sorted which means that the reverse index will be a SortedMap (so sorting order is the ordering of extracted values)
    Let's see an example. Assuming you have the following cache content within a particular storage-enabled node :
    A --> Object (getX=5 ,...)
    B --> Object (getA=3 ,...)
    C --> Object (getA=3 ,...)
    D --> Object (getA=4 ,...)
    The forward index in that node will contain:
    Binary(A) --> 5
    Binary(B) --> 3
    Binary(C) --> 3
    Binary(D) --> 4
    The reverse index will contain:
    3 --> { Binary(B), Binary(C) }
    4 --> { Binary(D) }
    5 --> { Binary(A) }
    Where Binary(...) means the internal (binary) representation of the ... object.
    If the index is not ordered, then the order of iteration on entries in the reverse index are not deterministic.
    If the index is ordered, then the iteration of entries in the reverse index will be as shown above. Also, you can cast the reverse index to SortedMap so you have the very useful headMap and tailMap and firstKey and lastKey methods.
    Hope this helps.
    Best regards,
    Robert

  • Cant't start node on the cluster

    when I start my node in the cluster I have this error, what I should do to solve this?
    <Oct 30, 2011 11:06:00 PM BRST> <Error> <ALSB Statistics Manager> <BEA-473003> <Aggregation Server Not Available. Failed to get remote aggregator
    java.rmi.UnknownHostException: Could not discover URL for server 'Node1'
    at weblogic.protocol.URLManager.findURL(URLManager.java:145)
    at com.bea.alsb.platform.weblogic.topology.WlsRemoteServerImpl.getInitialContext(WlsRemoteServerImpl.java:94)
    at com.bea.alsb.platform.weblogic.topology.WlsRemoteServerImpl.lookupJNDI(WlsRemoteServerImpl.java:54)
    at com.bea.wli.monitoring.statistics.ALSBStatisticsManager.getRemoteAggregator(ALSBStatisticsManager.java:291)
    at com.bea.wli.monitoring.statistics.ALSBStatisticsManager.access$000(ALSBStatisticsManager.java:38)
    at com.bea.wli.monitoring.statistics.ALSBStatisticsManager$RemoteAggregatorProxy.send(ALSBStatisticsManager.java:55)
    at com.bea.wli.monitoring.statistics.collection.Collector.sendRawSnaphotToAggregator(Collector.java:284)
    at com.bea.wli.monitoring.statistics.collection.Collector.doCheckpoint(Collector.java:245)
    at com.bea.wli.monitoring.statistics.collection.Collector$CheckpointThread.doWork(Collector.java:69)
    at com.bea.wli.monitoring.utils.Schedulable.timerExpired(Schedulable.java:68)
    at com.bea.wli.timer.ClusterTimerImpl$InternalTimerListener.timerExpired(ClusterTimerImpl.java:255)
    at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
    at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    >

    I solved this on two steps:
    1 - I run ifconfig and check if my network card has MULTICAST flag
    2 - I add this route run this command:
    route add -host 239.192.0.10 dev eth0
    afeter this my nodes has started with sucess

  • RetrieveJXM metrics from within the cluster?

    I would like to know if it is possible to retrieve the metrics the JMX adapter exposes from within the cluster e.g. by running a thread on the invocation service that would query the underlying data structures to get the metrics out.

    You could still snapshot the stats if you wanted to but you would have to do it using queries into the local JMS server running in the JVM rather than using Coherence API calls.
    Or, depending on what you want to do with the stats, you could look at the JMX reporter that will log stats to a file every so often or you could look at one of the third-party monitoring tolls that will do this.
    JK

  • JTree - How to Expand all Nodes in the Tree

    I have a tree that has one primary node, two sub-nodes, and multiple sub-sub-nodes under those. I want to expand (show) all these nodes in the tree when the tree first loads. I tried expandRow() but that only seems to expand one row at a time by entering a single integer for the row. Is there any way to expand all rows/nodes when loading the tree?

    see
    http://forum.java.sun.com/thread.jsp?forum=57&thread=148793

  • In a content editable page right clicking within a div highlights all content within the div

    Open the following page in firefox. In a separate tab open another page, highlight some content and copy it. Move back to the original tab and try pasting the content. Whenever you right click in the area which is within the div tags the whole content between them gets highlighted.
    &lt;html&gt;
    &lt;head&gt;&lt;title&gt;edit area&lt;/title&gt;&lt;/head&gt;
    &lt;body contenteditable="true"&gt;
    &lt;div style="font-family: 'Times New Roman'; font-size: 16px;"&gt;These are a few of my&lt;br&gt;favourite&lt;br&gt;things :&lt;br&gt;&lt;br&gt;&lt;/div&gt;
    &lt;/body&gt;
    &lt;/html&gt;

    Go to File > New page from template. 
    Select your Template.dwt file from the list and hit Create.
    Save your child page.
    Nancy O.

  • Different distributed caches within the cluster

    Hi,
    i've three machines n1 , n2 and n3 respectively that host tangosol. 2 of them act as the primary distributed cache and the third one acts as the secondary cache. i also have weblogic running on n1 and based on some requests pumps data on to the distributed cache on n1 and n2. i've a listener configured on n1 and n2 and on the entry deleted event i would like to populate tangosol distributed service running on n3. all the 3 nodes are within the same cluster.
    i would like to ensure that the data directly coming from weblogic should only be distributed across n1 and n2 and NOT n3. for e.g. i do not start an instance of tangosol on node n3. and an object gets pruned from either n1 or n2. so ideally i should get a storage not configured exception which does not happen.
    The point is the moment is say CacheFactory.getCache("Dist:n3") in the cache listener, tangosol does populate the secondary cache by creating an instance of Dist:n3 on either n1 or n2 depending from where the object has been pruned.
    from my understanding i dont think we can have a config file on n1 and n2 that does not have a scheme for n3. i tried doing that and got an illegalstate exception.
    my next step was to define the Dist:n3 scheme on n1 and n2 with local storage false and have a similar config file on n3 with local-storage for Dist:n3 as true and local storage for the primary cache as false.
    can i configure local-storage specific to a cache rather than to a node.
    i also have an EJB deployed on weblogic that also entertains a getData request. i.e. this ejb will also check the primary cache and the secondary cache for data. i would have the statement
    NamedCahe n3 = CacheFactory.getCache("n3") in the bean as well.

    Hi Jigar,
    i've three machines n1 , n2 and n3 respectively that
    host tangosol. 2 of them act as the primary
    distributed cache and the third one acts as the
    secondary cache.First, I am curious as to the requirements that drive this configuration setup.
    i would like to ensure that the data directly coming
    from weblogic should only be distributed across n1
    and n2 and NOT n3. for e.g. i do not start an
    instance of tangosol on node n3. and an object gets
    pruned from either n1 or n2. so ideally i should get
    a storage not configured exception which does not
    happen.
    The point is the moment is say
    CacheFactory.getCache("Dist:n3") in the cache
    listener, tangosol does populate the secondary cache
    by creating an instance of Dist:n3 on either n1 or n2
    depending from where the object has been pruned.
    from my understanding i dont think we can have a
    config file on n1 and n2 that does not have a scheme
    for n3. i tried doing that and got an illegalstate
    exception.
    my next step was to define the Dist:n3 scheme on n1
    and n2 with local storage false and have a similar
    config file on n3 with local-storage for Dist:n3 as
    true and local storage for the primary cache as
    false.
    can i configure local-storage specific to a cache
    rather than to a node.
    i also have an EJB deployed on weblogic that also
    entertains a getData request. i.e. this ejb will also
    check the primary cache and the secondary cache for
    data. i would have the statement
    NamedCahe n3 = CacheFactory.getCache("n3") in the
    bean as well.In this scenario, I would recommend having the "primary" and "secondary" caches on different cache services (i.e. distributed-scheme/service-name). Then you can configure local storage on a service by service basis (i.e. distributed-scheme/local-storage).
    Later,
    Rob Misek
    Tangosol, Inc.

  • [SOLVED] Can't add a node to the cluster with error (Exchange 2010 SP3 DAG Windows Server 2012)

    Hi there!
    I have a problem which makes me very angry already :)
    I have two servers Exchange 2010 SP3 with MB role started on Windows Server 2012. I decided to create a DAG.
    I have created the prestaged AD object for the cluster called msc-co-exc-01c, assigned necessary permissions and disabled it. Allowed through the Windows Firewall traffic between nodes and prepared the File Share Witness server.
    Then I have tried to add nodes. The first node has been added successfully, but the second node doesn't want to be added :). Now I can add only one node to the DAG. I tried to add different servers first, but only the first one was added.
    LOGS on the second nodes: 
    Application Log
    "Failed to initialize cluster with error 0x80004005." (MSExchangeIS)
    Failover Clustering Diagnostic Log
    "[VER] Could not read version data from database for node msc-co-exc-04v (id 1)."
    CMDLET Error:
    Summary: 1 item(s). 0 succeeded, 1 failed.
    Elapsed time: 00:06:21
    MSC-CO-EXC-02V
    Failed
    Error:
    A database availability group administrative operation failed. Error: The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode()
    (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed. [Server: msc-co-exc-04v.int.krls.ru]
    An Active Manager operation failed. Error An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode() (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed..
    This operation returned because the timeout period expired
    Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.174.1&t=exchgf1&e=ms.exch.err.ExC9C315
    Warning:
    Network name 'msc-co-exc-01c' is not online. Please check that the IP address configuration for the database availability group is correct.
    Warning:
    The operation wasn't successful because an error was encountered. You may find more details in log file "C:\ExchangeSetupLogs\DagTasks\dagtask_2014-11-17_13-54-56.543_add-databaseavailabiltygroupserver.log".
    Exchange Management Shell command attempted:
    Add-DatabaseAvailabilityGroupServer -MailboxServer 'MSC-CO-EXC-02V' -Identity 'msc-co-exc-01c'
    Elapsed Time: 00:06:21
    UPD:
    when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
    I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
    on both nodes.
    It's confused me, because there is normal connectivity between these DAG members through the main interface.
    Please, help me if you can.

    Hi, Jared! Thank you for the reply.
    Of course I did it already :) I have new info:
    when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
    I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
    on both nodes.
    It's confused me, because there is normal connectivity between these DAG members through the main interface.

  • Timeout when adding a node to the cluster

    I'm creating a cluster between 2 Windows Server 2012 servers in different datacenters.
    Servers are on 2 different networks N1 (10.0.17.1 ) and N2 (10.1.17.2).  
    The servers are virtualized on VMWare ESX Sphere5.5. 
    When we create the cluster on the node N1, node N2 ends with error timeout. 
    When we create the cluster on the node N2, node N1 ends with error timeout.
    * No Antivirus
    * No firewalls
    * Ping from N1 to N2 OK.
    * Ping from N2 to N1 OK.
    * Windows are updated.
    Thank you
    Logs:
    000006dc.000012d4::2014/04/29-12:18:10.431 WARN  [RCM] Failed to load restype 'MSMQTriggers': error 21.
    000006dc.000012d4::2014/04/29-12:18:10.431 ERR   [RCM] [GIM] ResType Máquina virtual has no resources, not collecting local utilization info
    000006dc.000012d4::2014/04/29-12:18:10.431 INFO  [RCM] [GIM] Scheduling Local Node Crawler to run in 300000 millisec.
    00000ad0.00000dac::2014/04/29-12:18:12.671 INFO  [RES] Network Name <Nombre del clúster>: Dns: HealthCheck: SQLCLUSTER
    00000ad0.00000dac::2014/04/29-12:18:12.671 INFO  [RES] Network Name <Nombre del clúster>: Dns: End of Slow Operation, state: Initialized/Reading, prevWorkState: Reading
    00000ad0.0000054c::2014/04/29-12:18:12.677 INFO  [RES] Network Name <Nombre del clúster>: Dns: PingName internal returned 0
    00000ad0.0000054c::2014/04/29-12:18:12.677 INFO  [RES] Network Name <Nombre del clúster>: Dns: Endpoint is up
    00000ad0.0000054c::2014/04/29-12:18:12.677 INFO  [RES] Network Name <Nombre del clúster>: Dns: Slow Operation, FinishWithReply: 0
    00000ad0.0000054c::2014/04/29-12:18:12.677 INFO  [RES] Network Name <Nombre del clúster>: Dns: InternalReplyHandler: 0
    00000ad0.0000054c::2014/04/29-12:18:12.677 INFO  [RES] Network Name <Nombre del clúster>: Dns: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00000dac::2014/04/29-12:18:12.726 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.0000054c::2014/04/29-12:18:12.726 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.0000054c::2014/04/29-12:18:12.726 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.0000054c::2014/04/29-12:18:12.726 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.0000054c::2014/04/29-12:18:17.726 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00000dac::2014/04/29-12:18:17.726 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00000dac::2014/04/29-12:18:17.726 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00000dac::2014/04/29-12:18:17.726 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00000dac::2014/04/29-12:18:22.727 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.0000054c::2014/04/29-12:18:22.727 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.0000054c::2014/04/29-12:18:22.727 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.0000054c::2014/04/29-12:18:22.727 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.0000054c::2014/04/29-12:18:27.728 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00000dac::2014/04/29-12:18:27.728 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00000dac::2014/04/29-12:18:27.728 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00000dac::2014/04/29-12:18:27.728 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00000dac::2014/04/29-12:18:32.728 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.0000054c::2014/04/29-12:18:32.728 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.0000054c::2014/04/29-12:18:32.728 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.0000054c::2014/04/29-12:18:32.728 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.0000054c::2014/04/29-12:18:37.729 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00000dac::2014/04/29-12:18:37.729 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00000dac::2014/04/29-12:18:37.729 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00000dac::2014/04/29-12:18:37.729 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00000dac::2014/04/29-12:18:42.729 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.0000054c::2014/04/29-12:18:42.729 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.0000054c::2014/04/29-12:18:42.729 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.0000054c::2014/04/29-12:18:42.729 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.0000054c::2014/04/29-12:18:47.730 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00000dac::2014/04/29-12:18:47.730 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00000dac::2014/04/29-12:18:47.730 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00000dac::2014/04/29-12:18:47.730 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00000dac::2014/04/29-12:18:52.731 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.0000054c::2014/04/29-12:18:52.731 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.0000054c::2014/04/29-12:18:52.731 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.0000054c::2014/04/29-12:18:52.731 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.0000054c::2014/04/29-12:18:57.731 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00000dac::2014/04/29-12:18:57.731 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00000dac::2014/04/29-12:18:57.731 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00000dac::2014/04/29-12:18:57.731 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00000dac::2014/04/29-12:19:02.732 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.0000054c::2014/04/29-12:19:02.732 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.0000054c::2014/04/29-12:19:02.732 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.0000054c::2014/04/29-12:19:02.732 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.0000054c::2014/04/29-12:19:07.733 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00000dac::2014/04/29-12:19:07.733 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00000dac::2014/04/29-12:19:07.733 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00000dac::2014/04/29-12:19:07.733 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.0000054c::2014/04/29-12:19:12.670 INFO  [RES] Network Name <Nombre del clúster>: Dns: HealthCheck: SQLCLUSTER
    00000ad0.0000054c::2014/04/29-12:19:12.670 INFO  [RES] Network Name <Nombre del clúster>: Dns: End of Slow Operation, state: Initialized/Reading, prevWorkState: Reading
    00000ad0.0000054c::2014/04/29-12:19:12.673 INFO  [RES] Network Name <Nombre del clúster>: Dns: PingName internal returned 0
    00000ad0.0000054c::2014/04/29-12:19:12.673 INFO  [RES] Network Name <Nombre del clúster>: Dns: Endpoint is up
    00000ad0.0000054c::2014/04/29-12:19:12.673 INFO  [RES] Network Name <Nombre del clúster>: Dns: Slow Operation, FinishWithReply: 0
    00000ad0.0000054c::2014/04/29-12:19:12.673 INFO  [RES] Network Name <Nombre del clúster>: Dns: InternalReplyHandler: 0
    00000ad0.0000054c::2014/04/29-12:19:12.673 INFO  [RES] Network Name <Nombre del clúster>: Dns: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00000dac::2014/04/29-12:19:12.726 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.0000054c::2014/04/29-12:19:12.726 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.0000054c::2014/04/29-12:19:12.726 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.0000054c::2014/04/29-12:19:12.726 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00001720::2014/04/29-12:19:17.727 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00000dac::2014/04/29-12:19:17.727 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00000dac::2014/04/29-12:19:17.727 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00000dac::2014/04/29-12:19:17.727 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00000dac::2014/04/29-12:19:22.728 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00001720::2014/04/29-12:19:22.728 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00001720::2014/04/29-12:19:22.728 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00001720::2014/04/29-12:19:22.728 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00001720::2014/04/29-12:19:27.728 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00000dac::2014/04/29-12:19:27.728 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00000dac::2014/04/29-12:19:27.728 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00000dac::2014/04/29-12:19:27.728 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00000dac::2014/04/29-12:19:32.729 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00001720::2014/04/29-12:19:32.729 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00001720::2014/04/29-12:19:32.729 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00001720::2014/04/29-12:19:32.729 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00001720::2014/04/29-12:19:37.729 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00000dac::2014/04/29-12:19:37.729 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00000dac::2014/04/29-12:19:37.729 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00000dac::2014/04/29-12:19:37.729 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00000dac::2014/04/29-12:19:42.730 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00001720::2014/04/29-12:19:42.730 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00001720::2014/04/29-12:19:42.730 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00001720::2014/04/29-12:19:42.730 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00001720::2014/04/29-12:19:47.731 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00000dac::2014/04/29-12:19:47.731 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00000dac::2014/04/29-12:19:47.731 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00000dac::2014/04/29-12:19:47.731 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00000dac::2014/04/29-12:19:52.731 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00001720::2014/04/29-12:19:52.731 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00001720::2014/04/29-12:19:52.731 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00001720::2014/04/29-12:19:52.731 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00001720::2014/04/29-12:19:57.732 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00000dac::2014/04/29-12:19:57.732 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00000dac::2014/04/29-12:19:57.732 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00000dac::2014/04/29-12:19:57.732 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00000dac::2014/04/29-12:20:02.733 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00001720::2014/04/29-12:20:02.733 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00001720::2014/04/29-12:20:02.733 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00001720::2014/04/29-12:20:02.733 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00001720::2014/04/29-12:20:07.733 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00000dac::2014/04/29-12:20:07.733 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00000dac::2014/04/29-12:20:07.733 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00000dac::2014/04/29-12:20:07.733 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00000dac::2014/04/29-12:20:12.670 INFO  [RES] Network Name <Nombre del clúster>: Dns: HealthCheck: SQLCLUSTER
    00000ad0.00000dac::2014/04/29-12:20:12.670 INFO  [RES] Network Name <Nombre del clúster>: Dns: End of Slow Operation, state: Initialized/Reading, prevWorkState: Reading
    00000ad0.00000dac::2014/04/29-12:20:12.673 INFO  [RES] Network Name <Nombre del clúster>: Dns: PingName internal returned 0
    00000ad0.00000dac::2014/04/29-12:20:12.673 INFO  [RES] Network Name <Nombre del clúster>: Dns: Endpoint is up
    00000ad0.00000dac::2014/04/29-12:20:12.673 INFO  [RES] Network Name <Nombre del clúster>: Dns: Slow Operation, FinishWithReply: 0
    00000ad0.00000dac::2014/04/29-12:20:12.673 INFO  [RES] Network Name <Nombre del clúster>: Dns: InternalReplyHandler: 0
    00000ad0.00000dac::2014/04/29-12:20:12.673 INFO  [RES] Network Name <Nombre del clúster>: Dns: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.0000054c::2014/04/29-12:20:12.727 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00000dac::2014/04/29-12:20:12.727 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00000dac::2014/04/29-12:20:12.727 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00000dac::2014/04/29-12:20:12.727 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    000006dc.00000044::2014/04/29-12:20:15.779 INFO  [CLI] Get last update time from db
    000006dc.00000044::2014/04/29-12:20:15.779 INFO  [CLI] forming node has not updated last update time yet
    000006dc.00000044::2014/04/29-12:20:15.780 INFO  [CLI] UpdatePasswordPolicy len 8 secs maxage 2592000 secs
    000006dc.00000044::2014/04/29-12:20:15.780 INFO  [CLI] UpdatePasswordPolicy curreAge 180 secs
    000006dc.00000044::2014/04/29-12:20:15.781 INFO  [CLI] UpdatePasswordPolicy - maxAge 30 days passAge 0 days
    000006dc.00000044::2014/04/29-12:20:15.781 INFO  [CLI] Password MaxAge 30 DisablePasswordChange 0
    000006dc.00000044::2014/04/29-12:20:15.781 INFO  [CLI] Password  MaxAge 30 after checking with clusterdb
    000006dc.00000044::2014/04/29-12:20:15.781 INFO  [CLI] Update CAM now
    000006dc.00000044::2014/04/29-12:20:15.781 INFO  [CLI] DeCryptPassword successful
    000006dc.00000044::2014/04/29-12:20:15.781 INFO  [CLI] Update user passwd
    000006dc.00000044::2014/04/29-12:20:15.800 INFO  [CLI] User passwd updated
    0000021c.00000710::2014/04/29-12:20:15.800 INFO  [CAM] CamApCallPackage
    0000021c.00000710::2014/04/29-12:20:15.801 INFO  [CAM] CallInfo: Proc 1756 Thread 68 Count 0 Att 512
    0000021c.00000710::2014/04/29-12:20:15.801 INFO  [CAM] ClientInfo: Logon 999 Proc 1756 Thread 68 TCB 1 Impersonating 1 Restrict 0 Flags 0
    0000021c.00000710::2014/04/29-12:20:15.801 INFO  [CAM] SetCNOCred 1756 14 10 74 0
    0000021c.00000710::2014/04/29-12:20:15.801 INFO  [CAM] Setting User CLIUSR, Dom SQL2 (Proc 1756)
    0000021c.00000710::2014/04/29-12:20:15.801 INFO  [CAM] IsCredentialsReplacementNeeded - Passwords match
    000006dc.00000044::2014/04/29-12:20:15.801 INFO  [CLI] LsaCallAuthenticationPackage: 0, 0 size: 0, buffer: HDL( 0 )
    000006dc.00000044::2014/04/29-12:20:15.801 INFO  [CLI] Credentials Notified
    000006dc.00000044::2014/04/29-12:20:15.801 INFO  [CLI] IsLocalIdentityExpired age 0 maxage 30
    000006dc.00000044::2014/04/29-12:20:15.801 INFO  [CLI] IsLocalIdentityExpired, password not expired
    00000ad0.00000dac::2014/04/29-12:20:17.728 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.0000054c::2014/04/29-12:20:17.728 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.0000054c::2014/04/29-12:20:17.728 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.0000054c::2014/04/29-12:20:17.728 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.0000054c::2014/04/29-12:20:22.728 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00000dac::2014/04/29-12:20:22.728 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00000dac::2014/04/29-12:20:22.728 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00000dac::2014/04/29-12:20:22.728 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00000dac::2014/04/29-12:20:27.729 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.0000054c::2014/04/29-12:20:27.729 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.0000054c::2014/04/29-12:20:27.729 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.0000054c::2014/04/29-12:20:27.729 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.0000054c::2014/04/29-12:20:32.730 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00000dac::2014/04/29-12:20:32.730 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00000dac::2014/04/29-12:20:32.730 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00000dac::2014/04/29-12:20:32.730 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00000dac::2014/04/29-12:20:37.730 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.0000054c::2014/04/29-12:20:37.730 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.0000054c::2014/04/29-12:20:37.730 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.0000054c::2014/04/29-12:20:37.730 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    000006dc.00000044::2014/04/29-12:20:42.274 INFO  [NM] Received request from client address SQL2.
    000006dc.00001640::2014/04/29-12:20:42.274 INFO  [NM] Received request from client address SQL2.
    00000ad0.0000054c::2014/04/29-12:20:42.731 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00000dac::2014/04/29-12:20:42.731 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00000dac::2014/04/29-12:20:42.731 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00000dac::2014/04/29-12:20:42.731 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    000006dc.00001650::2014/04/29-12:20:45.293 INFO  [NM] Received request from client address SQL2.
    00000ad0.0000054c::2014/04/29-12:20:47.731 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00000dac::2014/04/29-12:20:47.731 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00000dac::2014/04/29-12:20:47.731 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00000dac::2014/04/29-12:20:47.731 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00000dac::2014/04/29-12:20:52.732 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.0000054c::2014/04/29-12:20:52.732 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.0000054c::2014/04/29-12:20:52.732 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.0000054c::2014/04/29-12:20:52.732 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.0000054c::2014/04/29-12:20:57.733 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00000dac::2014/04/29-12:20:57.733 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00000dac::2014/04/29-12:20:57.733 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00000dac::2014/04/29-12:20:57.733 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00000dac::2014/04/29-12:21:02.733 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.0000054c::2014/04/29-12:21:02.733 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.0000054c::2014/04/29-12:21:02.733 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.0000054c::2014/04/29-12:21:02.733 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.0000054c::2014/04/29-12:21:07.734 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00000dac::2014/04/29-12:21:07.734 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00000dac::2014/04/29-12:21:07.734 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00000dac::2014/04/29-12:21:07.734 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.0000054c::2014/04/29-12:21:12.671 INFO  [RES] Network Name <Nombre del clúster>: Dns: HealthCheck: SQLCLUSTER
    00000ad0.0000054c::2014/04/29-12:21:12.671 INFO  [RES] Network Name <Nombre del clúster>: Dns: End of Slow Operation, state: Initialized/Reading, prevWorkState: Reading
    00000ad0.0000054c::2014/04/29-12:21:12.673 INFO  [RES] Network Name <Nombre del clúster>: Dns: PingName internal returned 0
    00000ad0.0000054c::2014/04/29-12:21:12.673 INFO  [RES] Network Name <Nombre del clúster>: Dns: Endpoint is up
    00000ad0.0000054c::2014/04/29-12:21:12.673 INFO  [RES] Network Name <Nombre del clúster>: Dns: Slow Operation, FinishWithReply: 0
    00000ad0.0000054c::2014/04/29-12:21:12.673 INFO  [RES] Network Name <Nombre del clúster>: Dns: InternalReplyHandler: 0
    00000ad0.0000054c::2014/04/29-12:21:12.673 INFO  [RES] Network Name <Nombre del clúster>: Dns: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00001720::2014/04/29-12:21:12.727 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.0000054c::2014/04/29-12:21:12.727 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.0000054c::2014/04/29-12:21:12.727 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.0000054c::2014/04/29-12:21:12.727 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.0000054c::2014/04/29-12:21:17.727 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00001720::2014/04/29-12:21:17.727 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00001720::2014/04/29-12:21:17.727 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00001720::2014/04/29-12:21:17.727 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00001720::2014/04/29-12:21:22.728 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.0000054c::2014/04/29-12:21:22.728 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.0000054c::2014/04/29-12:21:22.728 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.0000054c::2014/04/29-12:21:22.728 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.0000054c::2014/04/29-12:21:27.728 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00001720::2014/04/29-12:21:27.728 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00001720::2014/04/29-12:21:27.728 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00001720::2014/04/29-12:21:27.728 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00001720::2014/04/29-12:21:32.729 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.0000054c::2014/04/29-12:21:32.729 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.0000054c::2014/04/29-12:21:32.729 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.0000054c::2014/04/29-12:21:32.729 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.0000054c::2014/04/29-12:21:37.730 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00001720::2014/04/29-12:21:37.730 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00001720::2014/04/29-12:21:37.730 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00001720::2014/04/29-12:21:37.730 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00001720::2014/04/29-12:21:42.730 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.0000054c::2014/04/29-12:21:42.730 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.0000054c::2014/04/29-12:21:42.730 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.0000054c::2014/04/29-12:21:42.730 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.0000054c::2014/04/29-12:21:47.731 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00001720::2014/04/29-12:21:47.731 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00001720::2014/04/29-12:21:47.731 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00001720::2014/04/29-12:21:47.731 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00001720::2014/04/29-12:21:52.732 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.0000054c::2014/04/29-12:21:52.732 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.0000054c::2014/04/29-12:21:52.732 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.0000054c::2014/04/29-12:21:52.732 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.0000054c::2014/04/29-12:21:57.732 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00001720::2014/04/29-12:21:57.732 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00001720::2014/04/29-12:21:57.732 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00001720::2014/04/29-12:21:57.732 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00001720::2014/04/29-12:22:02.733 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.0000054c::2014/04/29-12:22:02.733 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.0000054c::2014/04/29-12:22:02.733 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.0000054c::2014/04/29-12:22:02.733 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.0000054c::2014/04/29-12:22:07.734 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00001720::2014/04/29-12:22:07.734 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00001720::2014/04/29-12:22:07.734 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00001720::2014/04/29-12:22:07.734 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00001720::2014/04/29-12:22:12.670 INFO  [RES] Network Name <Nombre del clúster>: Dns: HealthCheck: SQLCLUSTER
    00000ad0.00001720::2014/04/29-12:22:12.670 INFO  [RES] Network Name <Nombre del clúster>: Dns: End of Slow Operation, state: Initialized/Reading, prevWorkState: Reading
    00000ad0.00001720::2014/04/29-12:22:12.673 INFO  [RES] Network Name <Nombre del clúster>: Dns: PingName internal returned 0
    00000ad0.00001720::2014/04/29-12:22:12.673 INFO  [RES] Network Name <Nombre del clúster>: Dns: Endpoint is up
    00000ad0.00001720::2014/04/29-12:22:12.673 INFO  [RES] Network Name <Nombre del clúster>: Dns: Slow Operation, FinishWithReply: 0
    00000ad0.00001720::2014/04/29-12:22:12.673 INFO  [RES] Network Name <Nombre del clúster>: Dns: InternalReplyHandler: 0
    00000ad0.00001720::2014/04/29-12:22:12.673 INFO  [RES] Network Name <Nombre del clúster>: Dns: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00000dac::2014/04/29-12:22:12.727 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00001720::2014/04/29-12:22:12.727 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00001720::2014/04/29-12:22:12.727 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00001720::2014/04/29-12:22:12.727 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00001720::2014/04/29-12:22:17.728 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00000dac::2014/04/29-12:22:17.728 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00000dac::2014/04/29-12:22:17.728 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00000dac::2014/04/29-12:22:17.728 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00000dac::2014/04/29-12:22:22.728 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00001720::2014/04/29-12:22:22.728 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00001720::2014/04/29-12:22:22.728 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00001720::2014/04/29-12:22:22.728 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00001720::2014/04/29-12:22:27.729 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00000dac::2014/04/29-12:22:27.729 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00000dac::2014/04/29-12:22:27.729 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00000dac::2014/04/29-12:22:27.729 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    000006dc.00000044::2014/04/29-12:22:30.860 INFO  [NM] Received request from client address fe80::7822:e960:da9b:175f.
    00000ad0.00000dac::2014/04/29-12:22:32.730 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00001720::2014/04/29-12:22:32.730 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00001720::2014/04/29-12:22:32.730 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00001720::2014/04/29-12:22:32.730 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00001720::2014/04/29-12:22:37.730 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00000dac::2014/04/29-12:22:37.730 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00000dac::2014/04/29-12:22:37.730 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00000dac::2014/04/29-12:22:37.730 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00000dac::2014/04/29-12:22:42.731 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00001720::2014/04/29-12:22:42.731 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00001720::2014/04/29-12:22:42.731 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00001720::2014/04/29-12:22:42.731 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00001720::2014/04/29-12:22:47.732 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00000dac::2014/04/29-12:22:47.732 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00000dac::2014/04/29-12:22:47.732 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00000dac::2014/04/29-12:22:47.732 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00000dac::2014/04/29-12:22:52.732 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00001720::2014/04/29-12:22:52.732 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00001720::2014/04/29-12:22:52.732 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00001720::2014/04/29-12:22:52.732 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00001720::2014/04/29-12:22:57.733 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00000dac::2014/04/29-12:22:57.733 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00000dac::2014/04/29-12:22:57.733 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00000dac::2014/04/29-12:22:57.733 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00000dac::2014/04/29-12:23:02.734 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00001720::2014/04/29-12:23:02.734 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00001720::2014/04/29-12:23:02.734 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00001720::2014/04/29-12:23:02.734 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00001720::2014/04/29-12:23:07.734 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00000dac::2014/04/29-12:23:07.734 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00000dac::2014/04/29-12:23:07.734 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00000dac::2014/04/29-12:23:07.734 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad8.00001580::2014/04/29-12:23:10.436 ERR   [RHS] s_RhsRpcCreateResType: ERROR_NOT_READY(21)' because of 'Startup routine for ResType MSMQ returned 21.'
    000006dc.00001488::2014/04/29-12:23:10.436 INFO  [RCM] result of first load attempt for type MSMQ: 21
    000006dc.00001488::2014/04/29-12:23:10.436 WARN  [RCM] Failed to load restype 'MSMQ': error 21.
    00000ad8.00001580::2014/04/29-12:23:10.438 ERR   [RHS] s_RhsRpcCreateResType: ERROR_NOT_READY(21)' because of 'Startup routine for ResType MSMQTriggers returned 21.'
    000006dc.00001488::2014/04/29-12:23:10.438 INFO  [RCM] result of first load attempt for type MSMQTriggers: 21
    000006dc.00001488::2014/04/29-12:23:10.438 WARN  [RCM] Failed to load restype 'MSMQTriggers': error 21.
    000006dc.00001488::2014/04/29-12:23:10.438 ERR   [RCM] [GIM] ResType Máquina virtual has no resources, not collecting local utilization info
    000006dc.00001488::2014/04/29-12:23:10.439 INFO  [RCM] [GIM] Scheduling Local Node Crawler to run in 300000 millisec.
    00000ad0.00000dac::2014/04/29-12:23:12.670 INFO  [RES] Network Name <Nombre del clúster>: Dns: HealthCheck: SQLCLUSTER
    00000ad0.00000dac::2014/04/29-12:23:12.670 INFO  [RES] Network Name <Nombre del clúster>: Dns: End of Slow Operation, state: Initialized/Reading, prevWorkState: Reading
    00000ad0.00000dac::2014/04/29-12:23:12.673 INFO  [RES] Network Name <Nombre del clúster>: Dns: PingName internal returned 0
    00000ad0.00000dac::2014/04/29-12:23:12.673 INFO  [RES] Network Name <Nombre del clúster>: Dns: Endpoint is up
    00000ad0.00000dac::2014/04/29-12:23:12.673 INFO  [RES] Network Name <Nombre del clúster>: Dns: Slow Operation, FinishWithReply: 0
    00000ad0.00000dac::2014/04/29-12:23:12.673 INFO  [RES] Network Name <Nombre del clúster>: Dns: InternalReplyHandler: 0
    00000ad0.00000dac::2014/04/29-12:23:12.673 INFO  [RES] Network Name <Nombre del clúster>: Dns: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.0000054c::2014/04/29-12:23:12.727 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00000dac::2014/04/29-12:23:12.727 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00000dac::2014/04/29-12:23:12.727 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00000dac::2014/04/29-12:23:12.727 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    000006dc.00001488::2014/04/29-12:23:15.802 INFO  [CLI] Get last update time from db
    000006dc.00001488::2014/04/29-12:23:15.802 INFO  [CLI] forming node has not updated last update time yet
    000006dc.00001488::2014/04/29-12:23:15.803 INFO  [CLI] UpdatePasswordPolicy len 8 secs maxage 2592000 secs
    000006dc.00001488::2014/04/29-12:23:15.804 INFO  [CLI] UpdatePasswordPolicy curreAge 180 secs
    000006dc.00001488::2014/04/29-12:23:15.804 INFO  [CLI] UpdatePasswordPolicy - maxAge 30 days passAge 0 days
    000006dc.00001488::2014/04/29-12:23:15.804 INFO  [CLI] Password MaxAge 30 DisablePasswordChange 0
    000006dc.00001488::2014/04/29-12:23:15.804 INFO  [CLI] Password  MaxAge 30 after checking with clusterdb
    000006dc.00001488::2014/04/29-12:23:15.804 INFO  [CLI] Update CAM now
    000006dc.00001488::2014/04/29-12:23:15.804 INFO  [CLI] DeCryptPassword successful
    000006dc.00001488::2014/04/29-12:23:15.804 INFO  [CLI] Update user passwd
    000006dc.00001488::2014/04/29-12:23:15.823 INFO  [CLI] User passwd updated
    0000021c.00000f88::2014/04/29-12:23:15.823 INFO  [CAM] CamApCallPackage
    0000021c.00000f88::2014/04/29-12:23:15.823 INFO  [CAM] CallInfo: Proc 1756 Thread 5256 Count 0 Att 512
    0000021c.00000f88::2014/04/29-12:23:15.823 INFO  [CAM] ClientInfo: Logon 999 Proc 1756 Thread 5256 TCB 1 Impersonating 1 Restrict 0 Flags 0
    0000021c.00000f88::2014/04/29-12:23:15.823 INFO  [CAM] SetCNOCred 1756 14 10 74 0
    0000021c.00000f88::2014/04/29-12:23:15.823 INFO  [CAM] Setting User CLIUSR, Dom SQL2 (Proc 1756)
    0000021c.00000f88::2014/04/29-12:23:15.823 INFO  [CAM] IsCredentialsReplacementNeeded - Passwords match
    000006dc.00001488::2014/04/29-12:23:15.823 INFO  [CLI] LsaCallAuthenticationPackage: 0, 0 size: 0, buffer: HDL( 0 )
    000006dc.00001488::2014/04/29-12:23:15.823 INFO  [CLI] Credentials Notified
    000006dc.00001488::2014/04/29-12:23:15.823 INFO  [CLI] IsLocalIdentityExpired age 0 maxage 30
    000006dc.00001488::2014/04/29-12:23:15.823 INFO  [CLI] IsLocalIdentityExpired, password not expired
    00000ad0.00000dac::2014/04/29-12:23:17.727 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.0000054c::2014/04/29-12:23:17.727 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.0000054c::2014/04/29-12:23:17.727 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.0000054c::2014/04/29-12:23:17.727 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.0000054c::2014/04/29-12:23:22.728 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00000dac::2014/04/29-12:23:22.728 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00000dac::2014/04/29-12:23:22.728 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00000dac::2014/04/29-12:23:22.728 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00000dac::2014/04/29-12:23:27.729 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.0000054c::2014/04/29-12:23:27.729 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.0000054c::2014/04/29-12:23:27.729 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.0000054c::2014/04/29-12:23:27.729 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.0000054c::2014/04/29-12:23:32.729 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00000dac::2014/04/29-12:23:32.729 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00000dac::2014/04/29-12:23:32.729 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00000dac::2014/04/29-12:23:32.729 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00000dac::2014/04/29-12:23:37.730 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.0000054c::2014/04/29-12:23:37.730 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.0000054c::2014/04/29-12:23:37.730 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.0000054c::2014/04/29-12:23:37.730 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.0000054c::2014/04/29-12:23:42.731 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00000dac::2014/04/29-12:23:42.731 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00000dac::2014/04/29-12:23:42.731 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00000dac::2014/04/29-12:23:42.731 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00000dac::2014/04/29-12:23:47.731 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.0000054c::2014/04/29-12:23:47.731 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.0000054c::2014/04/29-12:23:47.731 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.0000054c::2014/04/29-12:23:47.731 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.0000054c::2014/04/29-12:23:52.732 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00000dac::2014/04/29-12:23:52.732 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00000dac::2014/04/29-12:23:52.732 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00000dac::2014/04/29-12:23:52.732 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    000006dc.00000044::2014/04/29-12:23:56.018 INFO  [NM] Received request from client address ::1.
    00000ad0.00000dac::2014/04/29-12:23:57.733 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.0000054c::2014/04/29-12:23:57.733 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.0000054c::2014/04/29-12:23:57.733 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.0000054c::2014/04/29-12:23:57.733 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.0000054c::2014/04/29-12:24:02.733 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00000dac::2014/04/29-12:24:02.733 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00000dac::2014/04/29-12:24:02.733 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00000dac::2014/04/29-12:24:02.733 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00000dac::2014/04/29-12:24:07.734 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.0000054c::2014/04/29-12:24:07.734 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.0000054c::2014/04/29-12:24:07.734 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.0000054c::2014/04/29-12:24:07.734 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.00000dac::2014/04/29-12:24:12.670 INFO  [RES] Network Name <Nombre del clúster>: Dns: HealthCheck: SQLCLUSTER
    00000ad0.00000dac::2014/04/29-12:24:12.670 INFO  [RES] Network Name <Nombre del clúster>: Dns: End of Slow Operation, state: Initialized/Reading, prevWorkState: Reading
    00000ad0.00000dac::2014/04/29-12:24:12.672 INFO  [RES] Network Name <Nombre del clúster>: Dns: PingName internal returned 0
    00000ad0.00000dac::2014/04/29-12:24:12.672 INFO  [RES] Network Name <Nombre del clúster>: Dns: Endpoint is up
    00000ad0.00000dac::2014/04/29-12:24:12.672 INFO  [RES] Network Name <Nombre del clúster>: Dns: Slow Operation, FinishWithReply: 0
    00000ad0.00000dac::2014/04/29-12:24:12.672 INFO  [RES] Network Name <Nombre del clúster>: Dns: InternalReplyHandler: 0
    00000ad0.00000dac::2014/04/29-12:24:12.672 INFO  [RES] Network Name <Nombre del clúster>: Dns: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle
    00000ad0.0000054c::2014/04/29-12:24:12.727 INFO  [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:d2a9bedb-7818-428d-a200-f642b017ae0c:Netbios
    00000ad0.00000dac::2014/04/29-12:24:12.727 INFO  [RES] Network Name <Nombre del clúster>: Netbios: Slow Operation, FinishWithReply: 0
    00000ad0.00000dac::2014/04/29-12:24:12.727 INFO  [RES] Network Name:  [NN] got sync reply: 0
    00000ad0.00000dac::2014/04/29-12:24:12.727 INFO  [RES] Network Name <Nombre del clúster>: Netbios: End of Slow Operation, state: Initialized/Idle, prevWorkState: Idle

    Hi,
    Thanks for your post, but unfortunately this is a English forum, The English will more appropriate for all the forum members. Please try to use the English ,Thanks for your
    understanding and cooperation.
    As far as I know The VMware ESXI® product not certificated by Windows, so you can ‘t get the official support. Personal point is you need first confirm your CSV is work fine,
    then disable all cluster node firewall and AV soft then try again.
    More information:
    Requirements and Recommendations for a Multi-Site Failover Cluster
    http://technet.microsoft.com/en-us/library/dd197575(v=ws.10).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.

Maybe you are looking for