| Author |
Message |
rbin
Guest
|
Posted:
Thu Oct 20, 2005 12:50 pm Post subject:
Cluster in IBM Bladecenter HS20 |
|
|
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 |
|
| Back to top |
|
 |
Isaac Story
Guest
|
Posted:
Fri Oct 21, 2005 12:50 am Post subject:
RE: Cluster in IBM Bladecenter HS20 |
|
|
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:
| Quote: | 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
|
|
|
| Back to top |
|
 |
Ryan Sokolowski [MVP]
Guest
|
Posted:
Fri Oct 21, 2005 12:50 am Post subject:
Re: Cluster in IBM Bladecenter HS20 |
|
|
You should also ensure that the hardware used is included in the HCT/HCL -
otherwise your solution might not be supported by Microsoft.
--
Ryan Sokolowski
MVP - Windows Server - Clustering
MCSE, CCNA, CCDA, BCFP
"A troubleshooter's best tool is the Event Viewer and understanding the
events and messages contained therein."
This posting is provided "AS IS" with no warranties, and confers no rights.
"Isaac Story" <IsaacStory@discussions.microsoft.com> wrote in message
news:20E4FC21-1058-4D06-9BEE-D256B28C9FFF@microsoft.com...
| Quote: | 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
|
|
|
| Back to top |
|
 |
Jason Tan (MSFT
Guest
|
Posted:
Fri Oct 21, 2005 8:51 am Post subject:
RE: Cluster in IBM Bladecenter HS20 |
|
|
Hi rbin,
Thanks for posting!
You may refer to the following article to configure the network for the
server clusters.
Server Clusters: Network Configuration Best Practices for Windows 2000 and
Windows Server 2003
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/
clustering/clstntbp.mspx
Windows Server 2003 Server Clusters (MSCS)
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/
mscs.mspx
Hope the information helps.
Thanks & Regards,
Jason Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Thread-Topic: Cluster in IBM Bladecenter HS20
| thread-index: AcXVWj5gpwnYwZktQNup4vKaHIK7Dw==
| X-WBNR-Posting-Host: 194.76.232.148
| From: "=?Utf-8?B?cmJpbg==?=" <rbin@news.postalias>
| Subject: Cluster in IBM Bladecenter HS20
| Date: Thu, 20 Oct 2005 02:40:02 -0700
| Lines: 17
| Message-ID: <C8943F21-552F-4F69-8D3F-578393A97DE9@microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.windows.server.clustering
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.clustering:8932
| X-Tomcat-NG: microsoft.public.windows.server.clustering
|
| 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
|
| |
|
| Back to top |
|
 |
rbin
Guest
|
Posted:
Fri Oct 21, 2005 8:51 am Post subject:
RE: Cluster in IBM Bladecenter HS20 |
|
|
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:
| Quote: | 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
|
|
|
| Back to top |
|
 |
Rodney R. Fournier [MVP]
Guest
|
Posted:
Fri Oct 21, 2005 12:50 pm Post subject:
Re: Cluster in IBM Bladecenter HS20 |
|
|
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@news.postalias> wrote in message
news:A3628D26-ECF8-443D-AB79-E74AC52EE723@microsoft.com...
| Quote: | 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
|
|
|
| Back to top |
|
 |
Isaac Story
Guest
|
Posted:
Fri Oct 21, 2005 4:50 pm Post subject:
RE: Cluster in IBM Bladecenter HS20 |
|
|
Yeah, actually I realized that after I thought about it. The only solution
that I can see then is to carry (tag) vlans between the two switch modules.
So you can put one public NIC in switch module one and one public NIC in
switch module two. Then you can uplink between the two switch modules
carrying only the tagged VLAN traffic of the private NIC's in each switch
module. This again is simply an idea. I have not put it into practice, nor is
this a documented solution, so I do not know yet if it's practical. Just
brainstorming.
Isaac Story
"rbin" wrote:
| Quote: | 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
|
|
|
| Back to top |
|
 |
|
|
|
|