How would that work for diskless nodes that use xCAT's DHCP for
booting? Would the xNBA image have some sort of special smarts where
it just assigns the IP for the node when it sees that node is
supposed to have a static address instead of relying on DHCP to do
it?
Having trouble figuring out how the node would get it's right IP if
DHCP isn't giving it to it :-)
On 2/25/2014 8:09 AM, Jarrod B Johnson
wrote:
How odd, in 2.3 we already
were using omshell to do this stuff (it was one of the changes
from 1.x to 2.0). Perhaps I can look at the complexity of
stuff pushed in...
That said, as a perhaps more
further flung hypothetical future, what would people say to a
scheme where dhcp does have to exist and serve some leases to
facilitate PXE, but doesn't necessarily have to serve the
'right' addresses as the deployment ignores DHCP and goes to
static if node is configured with a static address, instead of
today where we push the static information into DHCP. It's a
concept I'm exploring at the moment. The biggest downside I
can think of is that you'd probably want to allocate a bigger
dynamic range, but that could be outside of the 'production'
subnet entirely (or use IPv6, which I also hope to assure can
work given adequate firmware support). In such a world, dhcp
could be either managed by xCAT or externally curated without
care about PXE directives or just slapped down with little
thought and a generous dynamic range. I was primarily
thinking about cases where xCAT curated dhcp is inconvenient,
but these cases could be sped up as well.
 Russell Jones
---02/25/2014 12:13:15 AM---Hi all, We are noticing that with
a service node that is responsible for around
From: Russell Jones
<[email protected]>
To: [email protected]
Date: 02/25/2014 12:13 AM
Subject: [xcat-user] Restarting xcatd
insanely slow with DHCP lease generation
Hi all,
We are noticing that with a service node that is responsible
for around
5000 nodes, restarting xcatd takes over an hour and a half due
to how
long it takes to generate the dhcp.leases file. This appears
to be tied
to how slow omapi is. In xCAT 2.3, it only took about 20
minutes to
restart xcatd / regenerate the leases file.
Is there a way of going back to the old method of handling
DHCP leases,
or a way of significantly speeding this up?
------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco
certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow
Analyzer
Customize your own dashboards, set traffic alerts and generate
reports.
Network behavioral analysis & security monitoring.
All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user
------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user
|
------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user
