wildness

To content | To menu | To search

Tag - cluster

Entries feed - Comments feed

Sunday, May 2 2010

Solaris SUN Cluster: Live update

By wildcat on Sunday, May 2 2010, 11:34 - Solaris

As I've recently tried the patching of a sun cluster with Zones/ZFS/global filesystem and everything running, I've noticed that not so much people have tried this, so I might share the experience here ;)

So read the complete article to see how it behaves ;)

Continue reading...

2 comments no trackback

Thursday, April 29 2010

Solaris Sun cluster core patch 126106-40 issue

By wildcat on Thursday, April 29 2010, 09:12 - Solaris

I've recently had to apply the 126106-40 core patch for SUN Cluster and had some issues with it.. Seeing on the Internet, some issues with this patchs are documented by Juergen Scheich's blog and describing a howto fix some of them. Actually, the error I had was a bit different from the "loaddid" cycling dependencies that was found on his blog. I had a similar issues with the sysidtool:net service which gave me the almost same error as the loaddid did. No pun intented ;-)

Applying the same procedure as found on Juergen's blog fixed also that issue! So you can just:

  1. Boot in non clustered mode
  2. Remove the loaddid service from SMF: svccfg delete loaddid
  3. Import it again from the patch's XML file: svccfg import /path/to/patch/loaddid.xml
  4. Refresh the service: svcadm refresh loaddid
  5. init 6

This has not been faced on all the node of the cluster I was patching, but I thought it was worth a note here ;-)

no comment no trackback

Tuesday, November 18 2008

Cisco: HSRP to improve redundancy

By wildcat on Tuesday, November 18 2008, 10:00 - Networking

In a previous post, I have talk about how to put in place a heartbeat failover cluster for services. Now I'd like to improve my network redundancy by putting two routers in failover, I've achieved this simply by using HSRP protocol on both node.

Here is the IOS configuration of the two nodes:

node1 - primary

interface Vlan10
 description inet
 ip address 42.42.42.251 255.255.255.0
 no ip redirects
 standby 3 ip 42.42.42.254
 standby 3 priority 105
 standby 3 preempt
 standby 3 authentication md5 key-string 7 **
 standby 3 track FastEthernet0
 standby 3 track FastEthernet3

node2 - secondary

interface Vlan10
 description inet
 ip address 42.42.42.252 255.255.255.0
 no ip redirects
 standby 3 ip 42.42.42.254
 standby 3 preempt
 standby 3 authentication md5 key-string 7 **
 standby 3 track FastEthernet0
 standby 3 track FastEthernet3

You can see some difference:

  • priority: the default is 100, putting a higher priority makes the router being the default primary
  • track: This is the condition when failover needs to be down, in this case, when either fastethernet0 or 3 falls down, the failover will be done.

Hope it helps.

no comment no trackback

Tuesday, October 28 2008

Debian LAMP Failover cluster: Implementation

By wildcat on Tuesday, October 28 2008, 10:29 - GNU/Linux

Today, I had to build a solution to implement a redundant LAMP failover cluster.. I will report here how I achieved that and which software I used.

Requirements:

  • 2 Nodes (hardware identical, if possible);
  • 2 Network card per node;
  • 2 Hard drive per node;

Softwares used:

  • Debian GNU/Linux (any other linux distribution could fit);
  • Software RAID-1 (md);
  • Heartbeat-2;
  • DRBD-8;
  • Apache-2;
  • PHP5;
  • MySQL;
  • BIND9

This permit to have following functionnalities:

  • Prevent Harddisk failure (RAID-1);
  • Prevent network failure (Bonding, for my part, two interfaces connected on redundant network switches)
  • Prevent node failure (DRBD+Heartbeat : files are replicated to second node and services are balanced when a node falls)

Assumptions:

  • node1 is at 42.42.42.20;
  • node2 is at 42.42.42.21;
  • clusturized ip is at 42.42.42.22;
  • gateway is 42.42.42.254

Read more to see how exactly the implentation has goes on...

Continue reading...

7 comments no trackback