Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Search results for query: *

  1. mudgeman

    Node powered off - No failover

    All, the problem we were having was directly related to IBM equipment running Microsoft Cluster. Our other clusters were failing over fine. This is IBM specific and the firmware upgrade to 8.x fixes the problem. They have noted this in their lab in raleigh.
  2. mudgeman

    MSCS Cluster Failover

    The nodes can ping each other on the public and private networks. The nodes on the private are setup as 10.1.1.1 and .2 with a subnet of 255.0.0.0. The subnet on the public is 255.255.255.0
  3. mudgeman

    MSCS Cluster Failover

    Hve a simple MSCS cluster on 2 W2K boxes and when I initiate a failover, the 2nd node does not take ownership. It fails back to the 1st node. Why???
  4. mudgeman

    Node powered off - No failover

    We finally figured out what was going on with our setup. We had the 300Gs cabled to a FastT 500 storage array from IBM. After 2 weeks of pain and suffering, we finally got them to say yes to a firmware upgrade on the storage Fastt 500. Upgraded the firmware and the cluster was functioning and...
  5. mudgeman

    Node powered off - No failover

    This sounds exactly like the problem we are having. Running cluster on a 300G NAS device with dual channel qlogic fibres. When we pull both fibre connections, cluster dies.
  6. mudgeman

    Failover on a dual channel fibre card

    Running MCSC on an IBM NAS 300G boxes with RDAC installed. We pull the primary fibre and RDAC fails over to the secondary path. When the 2nd path is pulled, the cluster fails. Same scenario if we do a hard power down on the box.

Part and Inventory Search

Back
Top