Re: Cluster in IBM Bladecenter HS20

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

I am not a big fan of booting from the SAN. Why add the risk of failure when
it's really not needed?

Cheers,

Rod

MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training


"rbin" <rbin@xxxxxxxxxxxxxx> wrote in message
news:A3628D26-ECF8-443D-AB79-E74AC52EE723@xxxxxxxxxxxxxxxx
> Thanks for that working solution. A major drawback seems to be the lack of
> redundancy in that configuration. If the switch that connects the public
> NICs
> fails the whole cluster becomes unavailable. Maybe an expansion for the
> HS20
> does the thing?
>
> A question by the way: Do you use local disks for the boot partition?
>
> "Isaac Story" wrote:
>
>> I don't know if this is official "best practice" but I have just set up
>> my
>> HS20 blades in the following way. Take the secondary NIC's in each server
>> (which are linked to the second Ethernet module in the chassis) and
>> designate
>> them on a private network (give them static addesses on a different
>> subnet
>> then you public network). Then create VLAN's in the secondary switch
>> module
>> to contain the secondary NIC's from each server in the cluster you are
>> creating. Create a VLAN for each cluster. This puts the secondary NIC's
>> on
>> thier own network segment coming as close to private NIC communication as
>> you
>> can get with a blade chassis since you cannot pysically cross connect the
>> NIC's to each other.
>>
>> Again, I don't know that this is official "best practice" since, like you
>> expereinced, I also could not find any recommendations from IBM. So if
>> anyone
>> knows of a better method please let us know.
>>
>>
>> Isaac
>>
>> "rbin" wrote:
>>
>> > Hi,
>> >
>> > we plan to implement a MS Cluster (Windows 2003) consisting of 2 IBM
>> > HS20
>> > blades. My question is: What is the correct LAN configuration? All
>> > blades in
>> > the chassis end in 2 Cisco Switches.Each of the 2 have 4 ports for the
>> > connection to the campus switch. They are configured as an
>> > EtherChannel-Port.
>> >
>> > How to implement the Heartbeat-Connection between the 2 nodes? The
>> > configuration is certified by the Windows Server Catalog. Unfortunately
>> > there
>> > is no information about the network configuration. Also IBM seems to
>> > ignore
>> > the MSCS in the online documentation.
>> >
>> > Any help out there?
>> >
>> > Thanks,
>> > rbin
>> >


.

Relevant Pages

  • Re: Cluster in IBM Bladecenter HS20
    ... > HS20 blades in the following way. ... > then you public network). ... What is the correct LAN configuration? ... >> configuration is certified by the Windows Server Catalog. ...
    (microsoft.public.windows.server.clustering)
  • Re: Windows 2008 bizarre cluster issue
    ... Then we went through all the network ... having run out of troubleshooting items for the server configuration ... First I would try to break any and all teaming, ... Cluster servers are IBM blades ...
    (microsoft.public.windows.server.clustering)
  • Re: Clustering across teamed / trunked adapters
    ... Windows Server 2003 ... Network adapter teaming and server clustering ... Recommended private "Heartbeat" configuration on a cluster server ...
    (microsoft.public.windows.server.clustering)
  • Re: Heartbeat question
    ... Without fully knowing how this Cluster server is configured, ... 286342 Network failure detection and recovery in Windows Server 2003 ... > I followed all MS recommendations for heartbeat config. ...
    (microsoft.public.windows.server.clustering)
  • Re: Question for the Group
    ... If the whole VMS cluster was affected, ... Such incidents were one of the reasons to leave VMS for greener Unix ... the technical staff who designed the configuration, be they local, HP/ ... VAXStations clustered over the network died, ...
    (comp.os.vms)