Douglas,
Have you tried to setup the networks.gateway to be the keyword
"<xcatmaster>"?
[root@c910f02c01p02 ~]# tabdump -d networks | grep gateway
gateway: The network gateway. It can be set to an ip address or the
keyword <xcatmaster>, the keyword <xcatmaster> indicates the cluster-facing
ip address configured on this management node or service node. Leaving this
field blank means that there is no gateway for this network.
[root@c910f02c01p02 ~]#
-------------------------------------------------------------------------
Li,Guang Cheng (李光成)
IBM China System Technology Laboratory
Tel: 86-10-82453499
Tie-Line: 9053499
Email: ligua...@cn.ibm.com
Address: Building 28, ZhongGuanCun Software Park,
No.8, Dong Bei Wang West Road, Haidian District Beijing 100193,
PRC
北京市海淀区东北旺西路8号中关村软件园28号楼
邮编: 100193
From: Douglas Myers <dgmy...@us.ibm.com>
To: "xCAT Users Mailing list" <xcat-user@lists.sourceforge.net>
Date: 2015/05/20 08:23
Subject: [xcat-user] rnetboot issue in 2.9.1
SLES 11.3 x86_64 MS node ppc64 SNs
We've upgraded a cluster from 2.7.8 to 2.9.1 and have run into a problem.
When running rnetboot on a lpar it is writing out gateway IP to OF prompt.
This causes issue when we want a client to use a different SN, the OF of
the lpar attempts to bootp to gw (a known issue in the past). Using 2.7.8
either xCAT wasn't exhibiting the same behavior, two SNs in same network
could be used, we did not have errant bootp packets. So, with this upgrade
we have the following situation:
Two SNs on same network, one on .1 and one on .2 the network table has .1
as gw:
lpar that is assigned to .1 SN will bootp and get response fine from .1 and
install normally
lpar that is assigned ot .2 SN will attempt bootp to .1 (even though that
is only the gw assignation on OF prompt, server IP is .2 and OF reflects
that) and eventually fails.
If we flip gw in network table to .2 the reverse of those two outcomes
happens
If we remove gw from the OF command, installs happen to either SN as
directed with no issues (e.g. .1 SN clients bootp and install from .1
SN, .2 clients bootp and install from .2 SN. However removing gw from
network table results is rnetboot failing on no gw and lpar never reaching
bootp attempt. Note that we do not need a gw at all, it is a admin
network, no routing allowed.
_________________________________
Douglas Myers,
IBM Special Events - Smart Cloud BMS Lead
_________________________________
"It's not an opportunity if it doesn't scare you a little bit"
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user
