I know this is probably "elementary", but I'm confused about the cluster
IP address scheme. Is it possible for my Master IP Address to be an
internal address (ie, 192.168.1.100), and all of my resources also
assigned on the 192 subnet? My front-end servers have 2 nics (one
assigned an external ip address to be accessible to end-users. And one
internal ip address (192)). I can't get my cluster to work using 192
addresses. But I can if I use external addresses. I don't want to use
up a bunch of external IP addresses, so I'm trying to figure out how to
make the internal addresss scheme work for me. Can someone please
enlighten me? Thank you!


--
jessbryant
------------------------------------------------------------------------
jessbryant's Profile: http://forums.novell.com/member.php?userid=13263
View this thread: http://forums.novell.com/showthread.php?t=345365

All cluster IP addresses must be in the same subnet. In what way do the
"internal" addresses not work? Have you assigned the heartbeat to that
same subnet?


--
Andrew C Taubman
Novell Support Forums Volunteer SysOp
http://forums.novell.com/
(Sorry, support is not provided via e-mail)

Opinions expressed above are not
necessarily those of Novell Inc.
------------------------------------------------------------------------
ataubman's Profile: http://forums.novell.com/member.php?userid=34
View this thread: http://forums.novell.com/showthread.php?t=345365

Here's how I tried to set it up:

Cluster IP (Master): 129.255.xxx.x

Front-end Server "A": 129.255.xxx.x (nic1), 192.168.1.10 (nic2)
Front-end Server "B": 129.255.xxx.x (nic1), 192.168.1.11 (nic2)
Shared Storage: 129.255.xxx.x (nic1), 192.168.1.12 (nic2)

Cluster Pool "A": 192.168.1.13
Cluster Pool "B": 192.168.1.14


This doesn't work (probably because the Cluster IP is on the 129.255
subnet).

My question is, if I set the Cluster IP address up as: 192.168.1.x
and then set my cluster pool addresses up as specified above, will this
work? And will I be able to access the cluster from the 129.255.
subnet? I tried to manually change the Cluster IP address from
129.255.xxx.x to something on the 192.168 subnet, and then I was unable
to manage it in iManager...everything broke.

These servers are not in production yet, so I was thinking about
trashing the cluster and starting over - with all the cluster ip's on
the 192 subnet. But I wanted an answer on the forum (or an explanation
about the best way to set this up) before I start over.

Thanks!!!


--
jessbryant
------------------------------------------------------------------------
jessbryant's Profile: http://forums.novell.com/member.php?userid=13263
View this thread: http://forums.novell.com/showthread.php?t=345365

jessbryant wrote:
> Here's how I tried to set it up:
>
> Cluster IP (Master): 129.255.xxx.x
>
> Front-end Server "A": 129.255.xxx.x (nic1), 192.168.1.10 (nic2)
> Front-end Server "B": 129.255.xxx.x (nic1), 192.168.1.11 (nic2)
> Shared Storage: 129.255.xxx.x (nic1), 192.168.1.12 (nic2)
>
> Cluster Pool "A": 192.168.1.13
> Cluster Pool "B": 192.168.1.14
>
>
> This doesn't work (probably because the Cluster IP is on the 129.255
> subnet).
>
> My question is, if I set the Cluster IP address up as: 192.168.1.x
> and then set my cluster pool addresses up as specified above, will this
> work? And will I be able to access the cluster from the 129.255.
> subnet? I tried to manually change the Cluster IP address from
> 129.255.xxx.x to something on the 192.168 subnet, and then I was unable
> to manage it in iManager...everything broke.
>
> These servers are not in production yet, so I was thinking about
> trashing the cluster and starting over - with all the cluster ip's on
> the 192 subnet. But I wanted an answer on the forum (or an explanation
> about the best way to set this up) before I start over.
>
> Thanks!!!
>
>
So the servers have two nics one with 129.255.x.x. and the other with
192.168.1.10, and the virtual servers ip address is 192.168.1.xx these
are the ip address the users will need to access the shared resources.
As stated in the documentation the cluster IP and the resources must
share the same network, so as far as I know this will not work.

> This doesn't work (probably because the Cluster IP is on the 129.255
> subnet).Correct. As I said before, all cluster IP addresses must be on the same
subnet.> My question is, if I set the Cluster IP address up as: 192.168.1.x
> and then set my cluster pool addresses up as specified above, will this
> work? Yes. That's how every cluster in the world works now, with the exception
that they usually don't have a second NIC. But that won't stop normal
stuff from working.> And will I be able to access the cluster from the 129.255. subnet?Obviously you'd have to set up normal proper routing between the
networks, either in your network infrastructure or within the NW
servers. Also you'd need to configure SLP.> I tried to manually change the Cluster IP address from 129.255.xxx.x to
> something on the 192.168 subnet, and then I was unable to manage it in
> iManager...everything broke.In what way?


--
Andrew C Taubman
Novell Support Forums Volunteer SysOp
http://forums.novell.com/
(Sorry, support is not provided via e-mail)

Opinions expressed above are not
necessarily those of Novell Inc.
------------------------------------------------------------------------
ataubman's Profile: http://forums.novell.com/member.php?userid=34
View this thread: http://forums.novell.com/showthread.php?t=345365

Aha - and herein lies the problem.
I can't communicate with the 192 subnet from the 129. Nor do I know
how to set this routing up. This is such a learning curve for me...and
a frustrating one at that.

As I mentioned, the reason we want to use 192 addresses for our cluster
resources, is that we have limited addresses on the 129. All of the
servers and clients have 129 addresses (with the exception of this
cluster).

You said that this routing can be set up within the NW Servers.
Where???? So sorry for sounding dumb. But this is completely new to
me!!!

And THANK YOU for responding and shedding some light on this for me!


--
jessbryant
------------------------------------------------------------------------
jessbryant's Profile: http://forums.novell.com/member.php?userid=13263
View this thread: http://forums.novell.com/showthread.php?t=345365

Well...I think we've decided to just use 129 addresses. Setting up a
router won't work in our environment due to security protocols set up in
the institution. Thanks for all your help.


--
jessbryant
------------------------------------------------------------------------
jessbryant's Profile: http://forums.novell.com/member.php?userid=13263
View this thread: http://forums.novell.com/showthread.php?t=345365

In article <jessbryant.3glwqo@no-mx.forums.novell.com>, Jessbryant
wrote:
> You said that this routing can be set up within the NW Servers.
> Where???? So sorry for sounding dumb. But this is completely new to
> me!!!
>
This is easier than you think.

In INETCFG.NLM, Protocols, TCPIP, you will see the second option from
the top is either End Node or Router. Make that Router.

Next, make sure the server has an address bound in both subnets.
INETCFG, Bindings. If you assign two IP addresses to the same NIC, it
will automatically route traffic between them. You just need to be
sure your host sends traffic to the server to get to the other subnet.
(Which it would do if you have the NW server as your host's default
gateway).

Craig Johnson
Novell Support Connection SysOp