Interesting article. But, for our lpars which host numerous IP addresses
(like multiple Domino servers) this might be tricky at best.
I am rather a babe in the woods when it comes to DHCP. Let's start
simple. A system with a single IP address. You get the MAC from the line
description. The MAC in the line description can either be hard coded or
get it from the card that the line is attached on. Then the system has
it's host name in CFGTCP, 12. So it broadcasts it's host name and it's
MAC to a DHCP server. The DHCP server assigns it an address and somehow
your DNS server ties that address to that host name (or is it required
that your DHCP and DNS server be one and the same?).
Now, let's say you have the following Domino servers on that lpar:
NOTES01, GDDATA, etc. And they all bind specific so that when you go to
http://notes01 you get different results than
http://gddata. Often this
is done with a NOTES.INI entry like:
TCPIP_TcpIpAddress=0,10.10.1.130:1352
where notes01 would be 10.10.1.130. How would all this swim in that pool?
Or is the rule: One DHCP IP address per line description? (I think it
is.) Do you make the Domino addresses not DHCP and the OS one dhcp? How
does your DHCP server know which one wants to be the DHCP address?
Another one for you: Two line descriptions: LANLINSYS, LANLINMX.
Normally LANLINSYS is tied to the IP address for GDIHQ and LANLINMX is
tied to the IP address for HQMIMIX. This is so that Mimix can talk to the
machine and assist with the switch process via HQMIMIX when the switch
process may be ending and starting the interface on LANLINSYS. Could both
of those play in the DHCP sandbox? I understand they would have their own
MAC and that's QED. However, you don't have both names in CFGTCP, 12.
Rob Berendt
midrange.com
