Disk Witness Failover with simulated network failure

Hello everyone,
I am running two windows server 2012 R2 machines clustered with a disk witness. The disk witness is a LUN created on our SAN, presented to both machines. SAN is connected through two fiber channels per server both servers are networked on split
out network connections teamed together. Now on a hard server fault or simulated power failure (i.e. pulling the power cords from a server) Disk witness will fail over to second node and Cluster survives. But, when simulating a Network card
failure (disconnecting the cat5) from the Node hosting the Disk witness, I see the cluster attempt to offload hosting to UP node. But, the Disk witness will not come online. I think that the issue is because the server is technically
still running and the disk Witness has not really failed on the primary host, so it never releases ownership. I am new to clustering and could use a little guidance here. Is there anyway to make the disk witness
Thank you

Hi,
Please try to modify network settings for a failover cluster
1. 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.
2. If the console tree is collapsed, expand the tree under the cluster that you want to configure.
3. Expand Networks.
4. Right-click the network that you want to modify settings for, and then click Properties.
5. If needed, change the name of the network.
6. Select one of the following options:
-Allow cluster network communication on this network
If you select this option and you want the network to be used by the nodes only (not clients), clear Allow clients to connect through this network. Otherwise, make sure it
is selected.
-Do not allow cluster network communication on this network
Select this option if you are using a network only for iSCSI (communication with storage) or only for backup. (These are among the most common reasons for
selecting this option.)
Quote from:
Modify Network Settings for a Failover Cluster
http://technet.microsoft.com/en-us/library/cc725775.aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

Migration Asssitant w/Disk Image - Fails with a network error?

I'm currently trying to restore an iMac G4 with a disk image that was made before its hard drive was replaced. I've mounted the drive and it successfully copies over the user folders, but when it comes to copying the Library and Applications folders it fails after a long pause with the error indicating "There might be a problem with your network". As a disk image mounted on the desktop, I don't see this being a terribly helpful error, so I checked the console, but I don't see any errors being thrown there. Is there something that I can adjust so that it doesn't "lose contact" with the disk image?

Sorry, I guess I made some poor word choices there. I'm not technically restoring the iMac from an image in the ASR sense. The iMac is already set up with a brand new hard drive and OS install (the old drive was failing and was recovered using Disk Warrior and then imaged before it totally failed). All I'm trying to accomplish now is migrate the user data, apps, and library stuff over to the new drive from the image of the old drive.
The image now lives on the desktop of the new drive. There's no MBP involved (that's my computer and doesn't factor in to this issue). There's no network involved either (hence my confusion with the error message). This is all taking place on just the iMac, nothing more.
So I mount the image on the desktop. I fire up Migration Assistant, do the admin login, select "From a Time Machine backup or other disk", select the volume mounted from the image, in this case I turn off migration of the user folders as that has already completed successfully, Then turn on all the rest (Apps, Files & Folders, Library, Network Settings, etc.) Once it hit transfer it will sit and wait for a long period of time, then produces the error "There might be a problem with your network", but as there is no network involved here, that error only suggests to me that it's having trouble reading from the image.
However, referring to the console, there are apparently no errors reading the image (I've verified the image twice and even rebuilt it as a writable image in case it wanted to write the migration cash to the source volume), in fact I can see it cataloging all of the files that it wants to transfer. If I try to manually drag and drop any of the stuff in the Applications folder on the image of the old drive, it copies without a hitch.
For some reason, it just appears to lose the ablility to communicate with the image even though there are no apparent problems with it.
Any suggestions?

How To(?): build Simulated Networks (iPad) [Cisco Devices, etc.]

Good afternoon!
Thank you for clicking on this thread. Here's a quick synopsis:
-I work in IT
-I have an iPad
-I want to be able to build / play with simulated networks (like I would in 'GNS3') on said iPad
-I need it to be accessible and usable while not connected to a real-world network
I have been searching for quite a while, and have come up with nothing. Any and all assistance will be greatly appreciated!
Thanks in advance!
-James

If there is a MIB for it, most SNMP Capable Management servers can poll them.
This can be such as FHRP states, Routing Peers, ASA Failover status, Seriel numbers for inventory purposes.
The potential is almost endless, it just depends what you should monitor to ensure you are in the know when your network hiccups.
Here is a link to the IOS MIB Viewre
http://tools.cisco.com/ITDIT/MIBS/MainServlet
CCNP, CCIP, CCDP, CCNA: Security/Wireless
Blog: http://ccie-or-null.net/

Oracle 10g CRS autorecovery from network failures - Solaris with IPMP

Hi all,
Just wondering if anyone has experience with a setup similar to mine. Let me first apologise for the lengthy introduction that follows >.<
A quick run-down of my implementation: Sun SPARC Solaris 10, Oracle CRS, ASM and RAC database patched to version 10.2.0.4 respectively, no third-party cluster software used for a 2-node cluster. Additionally, the SAN storage is attached directly with fiber cable to both servers, and the CRS files (OCR, voting disks) are always visible to the servers, there is no switch/hub between the server and the storage. There is IPMP configured for both the public and interconnect network devices. When performing the usual failover tests for IPMP, both the OS logs and the CRS logs show a failure detected, and a failover to the surviving network interface (on both the public and the private network devices).
For the private interconnect, when both of the network devices are disabled (by manually disconnecting the network cables), this results in the 2nd node rebooting, and the CRS process starting, but unable to synchronize with the 1st node (which is running fine the whole time). Further, when I look at the CRS logs, it is able to correctly identify all the OCR files and voting disks. When the network connectivity is restored, both the OS and CRS logs reflect this connection has been repaired. However, the CRS logs at this point still state that node 1 (which is running fine) is down, and the 2nd node attempts to join the cluster as the master node. When I manually run the 'crsctl stop crs' and 'crsctl start crs' commands, this results in a message stating that the node is going to be rebooted to ensure cluster integrity, and the 2nd node reboots, starts the CRS daemons again at startup, and joins the cluster normally.
For the public network, when the 2nd node is manually disconnected, the VIP is seen to not failover, and any attempts to connect to this node via the VIP result in a timeout. When connectivity is restored, as expected the OS and CRS logs acknowledge the recovery, and the VIP for node 2 automatically fails over, but the listener goes down as well. Using the 'srvctl start listener' command brings it up again, and everything is fine. During this whole process, the database instance runs fine on both nodes.
From the case studies above, I can see that the network failures are detected by the Oracle Clusterware, and a simple command run once this failure is repaired restores full functionality to the RAC database. However, is there anyway to automate this recovery, for the 2 cases stated above, so that there is no need for manual intervention by the DBAs? I was able to test case 2 (public network) with the Oracle document 805969.1 (VIP does not relocate back to the original node after public network problem is resolved), is there a similar workaround for the interconnect?
Any and all pointers would be appreciated, and again, sorry for the lengthy post.
Edited by: NS Selvam on 16-Dec-2009 20:36
changed some minor typos

hi
i ve given the shell script.i just need to run that i usually get the op like
[root@rac-1 Desktop]# sh iscsi-corntab.sh
Logging in to [iface: default, target: iqn.2010-02-23.de.sayantan-chakraborty:storage.disk1.amiens.sys1.xyz, portal: 192.168.181.10,3260]
Login to [iface: default, target: iqn.2010-02-23.de.sayantan-chakraborty:storage.disk1.amiens.sys1.xyz, portal: 192.168.181.10,3260]: successfulthe script contains :
iscsiadm -m node -T iqn.2010-02-23.de.sayantan-chakraborty:storage.disk1.amiens.sys1.xyz -p 192.168.181.10 -l
iscsiadm -m node -T iqn.2010-02-23.de.sayantan-chakraborty:storage.disk1.amiens.sys1.xyz -p 192.168.181.10 --op update -n node.startup -v automatic
(cd /dev/disk/by-path; ls -l *sayantan-chakraborty* | awk '{FS=" "; print $9 " " $10 " " $11}')
[root@rac-1 Desktop]# (cd /dev/disk/by-path; ls -l *sayantan-chakraborty* | awk '{FS=" "; print $9 " " $10 " " $11}')
ip-192.168.181.10:3260-iscsi-iqn.2010-02-23.de.sayantan-chakraborty:storage.disk1.amiens.sys1.xyz-lun-1 -> ../../sdc
[root@rac-1 Desktop]# can you post the oput of ls /dev/iscsi ??you may get like this:
[root@rac-1 Desktop]# ls /dev/iscsi
xyz
[root@rac-1 Desktop]#

I am experiencing network failures with my Airport Extremes: the main router is a 2nd Gen, the extension a 5th Gen. The 5th Gen keeps on losing connection with the main router. Any ideas why?

I am experiencing network failures with my Airport Extremes: the main router is a 2nd Gen, the extension a 5th Gen.
The 5th Gen keeps on losing connection with the main router and thus with the internet.
Any ideas why?

Is the second Extreme configured to "extend" the network created by the first? If so its position must be such that it has a strong wireless connection to the first Extreme. If it is at the limits of the first one's wireless range its connection will be tenuous. Place them closer together and determine if that makes a difference.

Upload has failed. Network failure

Hello.
Since i work with indesign cc, i have a trouble wit folio builder panel: Everytime the upload fails at first attempt, it appears this message:"Upload has failed. Network failure." Ever works when i retried, but not at first attempts. This is unworkable with large publications, with a lot of articles. I´ve wrote that this is a trouble with the acrobat.com service outage, i need a solution.
Thanks. Best regards.

Was successfully re-linking indesign files to my dps producer dashboard. Files had been converted to CC (from CS6)-- and was switching from v26 to v 28. Everything was working just FINE, until about 6pm yesterday-- I had re-linked almost 3/4ths of my files, then I began getting the NETWORK FAILURE notice.
This morning, I tried creating a new folio-- managed to upload ONE new file into the new folio, then got the same 'network failure' message on the next one I tried to upload.
These files are from a successful app-- already in the app store, but it sure doesn't work right now! IOS 7 ... #!#*?
It is not about where your files are-- or how much memory -- Something else is going on.
I know you guys will figure it out...and will be standing by, anxious to fix my app!
THANKS.
nancy p

JMS Failover with Distributed Destinations in 7.0

          How does JMS failover with distributed destinations in WL 7.0?
          In an environment using file stores for persistent messages, can a working server
          automatically pick up unprocessed and persisted messages from a failed server?
          If so, what's the best way to set this up?
          Or, is this completely manual? In other words, we have to bring up a new server
          pointing to the location of the file store from the failed server?


          It appears that two JMSServers cannot share the same file store and, I'm assuming,
          two file stores cannot be using the same directory for persistence.
          So the HA you're talking about is something like Veritas automatically restarting
          a server (or starting a new one) to process the messages in the persistent queue
          that were unprocessed at the time of failure with the file store residing on some
          sort of HA disk array.
          The key point is that a message once it arrives at a server must be processed
          by that server or, in the case of failure of that server, must be processed by
          a server similarly configured to the one that failed so that it picks up the unprocessed
          messages. The message can't be processed by another server in the cluster.
          Or, is there some trick that could be employed to copy from the file store of
          the failed server and repost the messages to the still operating servers?
          "Zach" <[email protected]> wrote:
          >Unless you have some sort of HA framework/hardware, this is a manual
          >operation. You either point to the existing persistent storage (shared
          >storage or JDBC connection pool), or you move the physical data.
          >
          >_sjz.
          >
          >"Jim Cross" <[email protected]> wrote in message
          >news:[email protected]...
          >>
          >>
          >> How does JMS failover with distributed destinations in WL 7.0?
          >>
          >> In an environment using file stores for persistent messages, can a
          >working
          >server
          >> automatically pick up unprocessed and persisted messages from a failed
          >server?
          >> If so, what's the best way to set this up?
          >>
          >> Or, is this completely manual? In other words, we have to bring up
          >a new
          >server
          >> pointing to the location of the file store from the failed server?
          >
          >

Cluster node reboots after network failure

hi all,
The suncluster 3.1 8/05 with 2 nodes (E2900) was working fine without any errors in the sccheck.
yesterday one node rebooted saying a network failure,errors in the massage file are
Jan 17 08:00:36 PRD in.mpathd[221]: [ID 594170 daemon.error] NIC failure detected on ce0 of group sc_ipmp0
Jan 17 08:00:36 PRD Cluster.PNM: [ID 890413 daemon.notice] sc_ipmp0: state transition from OK to DOWN.
Jan 17 08:00:47 PRD Cluster.RGM.rgmd: [ID 784560 daemon.notice] resource PROD status on node PRD change to R_FM_DEGRADED
Jan 17 08:00:47 PRD Cluster.RGM.rgmd: [ID 922363 daemon.notice] resource PROD status msg on node PRD change to <IPMP Failure.>
Jan 17 08:00:50 PRD Cluster.RGM.rgmd: [ID 529407 daemon.notice] resource group CFS state on node PRD change to RG_PENDING_OFFLINE
Jan 17 08:00:50 PRD Cluster.RGM.rgmd: [ID 443746 daemon.notice] resource PROD state on node PRD change to R_MON_STOPPING
Jan 17 08:00:50 PRD Cluster.RGM.rgmd: [ID 707948 daemon.notice] launching method <hafoip_monitor_stop> for resource <PROD>, resource group <CFS>, timeout <300> seconds
Jan 17 08:00:50 PRD Cluster.RGM.rgmd: [ID 736390 daemon.notice] method <hafoip_monitor_stop> completed successfully for resource <PROD>, resource group <CFS>, time used: 0% of timeout <300 seconds>
Jan 17 08:00:50 PRD Cluster.RGM.rgmd: [ID 443746 daemon.notice] resource PROD state on node PRD change to R_ONLINE_UNMON
Jan 17 08:00:50 PRD Cluster.RGM.rgmd: [ID 443746 daemon.notice] resource PROD state on node PRD change to R_STOPPING
Jan 17 08:00:50 PRD Cluster.RGM.rgmd: [ID 707948 daemon.notice] launching method <hafoip_stop> for resource <PROD>, resource group <CFS>, timeout <300> seconds
Jan 17 08:00:50 PRD Cluster.RGM.rgmd: [ID 784560 daemon.notice] resource PROD status on node PRD change to R_FM_UNKNOWN
Jan 17 08:00:50 PRD Cluster.RGM.rgmd: [ID 922363 daemon.notice] resource PROD status msg on node PRD change to <Stopping>
Jan 17 08:00:51 PRD ip: [ID 678092 kern.notice] TCP_IOC_ABORT_CONN: local = 172.016.005.025:0, remote = 000.000.000.000:0, start = -2, end = 6
Jan 17 08:00:51 PRD ip: [ID 302654 kern.notice] TCP_IOC_ABORT_CONN: aborted 53 connections
what can be the reason for reabooting?
is there any way to avoid this, with only a failover?
rgds
Message was edited by:
suj

What is in that resource group? The cause is probably something with Failover_mode=HARD set. Check the manual reference section for this. The option would be to set the Failover_mode=SOFT.
Tim
---

I loaded in Lion - but my time capsule will not back up. I get an message: couldn't complete backup due to a network prolem. Also it says "make sure your computer and back up disk are on the same network, and that the backup disk is turned on.

I installed Lion on my Mac Pro laptop. Regarding Time Capsul - I get a messaage as follows: couldn't complete backup due to a network problem. Make sure your computer and back up disk are on the same network and that the backup disk is turned on. Then try again to back up. I have time capsul turned on. bill

I have exactly same problem with my MBP and MBA, after upgrading to Lion. I've tried to fix this issue while cheking key chain issues and network setup, even formating hdd and time capsule firmware upgrade (ver. 7.6.1.). Nothing can help. It is very annoying.

Modbus ip shared variable network failure

I am using lab view 8.6 DSC module to communicate to a watlow system which contains five watlow 96 controllers and an EM gateway. I have created shared variables for the process temperatures and setpoints for each of the five controllers using watlow modbus register Numbers with a 400001 offset. I have also created shared variables for Updating,CommFail,UpdateNow,and UpdateRate which where predefined. I have error when starting the VI if the SV has been dragged and dropped into the block diagram. The message is Error -1967353902 (The Modbus I/O server failed to receive any response from the Modbus slave device.) occurred at SV in vi. If I bind a variable in the VI to this same SV the error does not occur but the variable cycles between Good, Network Failure, No known value, and device failure as stated in the variable manager watched variables. The Updating, CommFail and UpdateRate all have a consistent Good in the quality column of the variable manager. UpdateNow has X in value, type, timestamp, and quality columns. CommFail and Updating does cycle between true and false randomly. I have tried a third party software called SpecView 32 demo to see if the commincation with the modbus system is not working and I can create five watlow controlers on my screen and direct them to the ip address along with a unit address and the system works without faults. This leads me to believe the commincation bewteen the SV Engine and the IP address is not correct. HELP Please.
Robert Jensen
UND EERC

If your application can deal with it I would recommend staying clear of the 'Networked Published' option.
When I started my Modbus development on cRIO....I left it enabled, and with ~100 shared variables on a 9074, the CPU was railing, and I saw a buffering behavior on the shared variables (which was not desirable in my application).
In my application I am using the old modbus library (as apposed to the new API) for cRIO to slave comms, the cRIO being the master.
I am also using the IOserver making the cRIO a slave to an external SCADA - and it passes essentially the same data arrays as I use on the modbus library for my local HMI [Not an NI product].....Which is two full Modbus frame writes (@ 120 words each, and about 60 words more for ~300 words outbound from the cRIO).
The IOserver slave was a recent addition and did not add much to the CPU load - although only 16 bytes is high speed, the balance of the total word package is at either 1 second or 3 seconds.
So, in my experince, the 'Networked Published' option adds significant CPU loading (on entery level cRIOs) YMMV.
I am huge fan of the shared variable engine (some at NI were pusing the CVT, and TCE etc...). However most of my shared variables are not the Networked Published variety (excepting local module channels) those have remained networked published for DSM (Distributed System Manager) use.

Anyone else had issues with phone network being unavailable on iPhone 4 since updating to iOS 5.0.1? My iPhone 4 is continually searching for a network and does not find my provider. I swapped SIMs with another iPhone 4 on ios 4 to confirm device problem.

Has anyone else had issues with phone network being unavailable on iPhone 4 since updating to iOS 5.0.1? My iPhone 4 is continually searching for a network and does not find AT&T, my provider. I swapped SIM cards with another iPhone 4 running ios 4 and established this is a device problem, not a SIM card problem.

Does the device get any signal?
Sounds like the device may have had a hardware failure. If it is out of warranty, the only option is the Out of Warranty replacement.
AppleCare is only an option if it is still under the original warranty.

Migrate Roles failes when migrating VMs with legacy network adapters (2008R2 - 2012)

I'm working on a upgrade of Hyper-V 2008R2 cluster to Hyper-V 2012 cluster. I am using the "migrate roles" feature of failover clustering to migrate the CSV's and VM's. The wizard ask to which switch the VMs need to be connected on the target cluster.
All VMs with network adapters can be started in the new cluster without any issues. If you look at the XML file of the migrated VMs with normal network adapters, a new XML has been generated in the proper 2012 format. However, all VM's with a legacy
network adapter fail to start. Also there is no migrated XML file in the VM directory. It is impossible to check or adjust the settings of the migrated VMs with legacy network adapters using the failover clustering console.
I have reproduced the issue in my lab several times, and it seems like a bug.
There are several workarounds, but I am looking for a real solution.

Hi,
We recommend that you use the legacy network adapter only to perform a network-based installation or when the guest operating system does not support the network adapter.
If the virtual machine continues to use the legacy network adapter it will not be able to leverage many of the features available in the Hyper-V virtual switch. You may want
to replace the legacy network adapter after the operating system is installed.
The related KB:
Building Your Cloud Infrastructure: Converged Data Center without Dedicated Storage Nodes
http://technet.microsoft.com/en-us/library/hh831829.aspx
Configure Networking
http://technet.microsoft.com/en-us/library/cc770380.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.

How to solve this problem? '' can not activate cellular data network failure'' authenticating PDP from already thank you

how to solve this problem? '' can not activate cellular data network failure'' authenticating PDP from already thank you

What does this have to do with using an iPhone in an enterprise environment?
What carrier are you using and where did you get the phone?

JMS adapter webspehere mq, network failure - stop

Hello,
After a network failure the JMS sender adapter (JMS --> XI) goes red, and doesn't automatically recover after a network failure. It is necessary to manually stop and start the adapter. This is bad design from SAP. You would like it to behave like the ftp adapter which automatically continues to poll for files after a network outage.
What can be done to overcome this bad design?
I'm on XI SP 18.
My Idea is to use the new AAM described in
SAP Note 766332
1. com.sap.aii.af.service.administration.cpa: Channel-related interfaces and APIs
2. com.sap.aii.af.service.administration.monitoring: Monitoring interfaces and APIs
3. com.sap.aii.af.service.administration.i18n: Localization interfaces and APIs
I would like to write a standard j2se application to connect using jndi to list the status of the channels, and then stop and start depending on status.
Which jar files should be included?
Example code?

Hello,
I have now built a workaround solution based on the AAM API.
It is implemented as a J2EE stateless session bean and a J2EE client. The client reads config with information about which channels to restart and calls the bean which checks status on the channels and restarts the ones with errors or in a stopped state. We schedult the program to run every 5 minutes and check the status.
Check the channelstatus.jsp for hints on how to use the api.
It's a pity SAP hasn't got this functionality builtin, it's clearly a design error.
/Otto
Edited by: Otto Frost on Dec 18, 2007 4:32 PM

BadRequest: Virtual machines with secondary network interfaces and virtual machines with no secondary network

I'm trying to create an "ExtraLarge" VM with multiple NICs. The New-AzureVM returns the following error:
BadRequest: Virtual machines with secondary network interfaces and virtual machines with no secondary network
interfaces are not supported in the same deployment, also a virtual machine having no secondary network interfaces
cannot be updated to have secondary network interfaces and vice-versa.
But I have no other VMs. Or at least I did and then deleted them and all their disks. The service has no deployments (either staging or production).
Why is New-AzureVM complaining about a mismatch of VMs with and without secondary network interfaces when no other VMs exist?
I have tried many things to fix this, including the deletion of ALL of my resources. I have deleted and created the service many times, both with an affinity group and without. I have a screen print of the -debug output if your interested.
Thanks for the outstanding help.

Hi Ron,
IMPORTANT NOTE: Please do not post the CONFIDENTIAL DETAILS ever on the public forums, this is HIGH RISK action.
Please send an email with your contact details to my email
[email protected] so that I guide you on steps which help you come out of the current scenario. Thank you for understanding.
I suggest you to create a new VNET and new VM with cloud services. Create Multiple NIC VM. Let us know the results.
Ref:
http://azure.microsoft.com/blog/2014/10/30/multiple-vm-nics-and-network-virtual-appliances-in-azure/
http://blogs.technet.com/b/canitpro/archive/2014/11/04/step-by-step-create-a-vm-with-multiple-nics-in-azure.aspx
If you are unable to create a VM with multiple NIC, please open a support case as it requires more confidential information which is out of scope of FORUM support offerings.
Regards,
Girish

Disk Witness Failover with simulated network failure

Similar Messages

Maybe you are looking for