From what I know and can quickly find the notes.ini variable
"TCPIP_TcpIpAddress" doesn't support DNS names so I don't know of any
way to on startup bind the Domino server ports to a DNS entry instead of
an actual IP address. You might have to request a change for them to
update that field.
The rule is one DHCP interface per line description so you'll need
multiple connections to the network, either physical or virtual, to have
multiple IP's and I don't know that it would do the Dynamic DNS updates
for all of the interfaces that are created.
That leads me to your last question, with Mimix involved I would highly
suggest you use static IP's for everything. If I remember right, the
IP's are defined in the cluster setup and changing them without going
through the Mimix process can cause problems.
Personally, I only see this being useful in very small footprints.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, February 21, 2011 12:35 PM
To: Midrange Systems Technical Discussion
Subject: RE: iSeries, DHCP
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
--
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "Patrick Bingham" <PBingham@xxxxxxxxxxx>
To: "Midrange Systems Technical Discussion"
<midrange-l@xxxxxxxxxxxx>
Date: 02/21/2011 01:14 PM
Subject: RE: iSeries, DHCP
Sent by: midrange-l-bounces@xxxxxxxxxxxx
http://ibmsystemsmag.blogs.com/i_can/2010/03/i-can-be-a-dhcp-client.html
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Chris Bipes
Sent: Monday, February 21, 2011 11:39 AM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: iSeries, DHCP
I have never seen a place to set the iSeries to a DHCP client. But you
can add additional IP address, get them started, connect to new IP,
update DNS, connect to new and shut down old.
Now your network guys know nothing about NON windows domain machines.
When a PC or Windows Server that is part of an Active Directory Domain
retrieve a DHCP address, they automatically register in the Active
Directory Domain DNS. Your iSeries will not as of 6.1 that I know of.
These new guys, IMHO, do not know what they are doing. Servers should
be static and not moved around. In the perfect world, your servers will
be behind a firewall with only the necessary services open to the client
DHCP subnet. Your Primary Domain Controller will be with the servers.
Each DHCP subnet would have a secondary Domain Controller providing DNS
and DHCP for the Clients. Each subnet would be defined as Domain Site
with a connector to the Primary DC.
But that is just imho.
--
Chris Bipes
Director of Information Services
CrossCheck, Inc.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Tom Hightower
Sent: Monday, February 21, 2011 8:49 AM
To: midrange-l@xxxxxxxxxxxx
Subject: iSeries, DHCP
Client has a new set of network admin guys (Windows-centric), and
they've been reconfiguring the network, creating new subnets and
what-not, to make it easier to move addresses around as they want/need.
They want to remove the internal static IP addresses assigned to the
iSeries partitions ('dev', 'test', 'live') and configure the box to use
DHCP (not as a DHCP server, as DHCP client).
The iSeries is at 6.1, no current plans to move to 7.1.
Can we configure their iSeries to pull an address using DHCP instead of
static addressing?
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
This message (including any attachments) is intended only for
the use of the individual or entity to which it is addressed and
may contain information that is non-public, proprietary,
privileged, confidential, and exempt from disclosure under
applicable law or may constitute as attorney work product.
If you are not the intended recipient, you are hereby notified
that any use, dissemination, distribution, or copying of this
communication is strictly prohibited. If you have received this
communication in error, notify us immediately by telephone and
(i) destroy this message if a facsimile or (ii) delete this message
immediately if this is an electronic communication.
Thank you.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
This message (including any attachments) is intended only for
the use of the individual or entity to which it is addressed and
may contain information that is non-public, proprietary,
privileged, confidential, and exempt from disclosure under
applicable law or may constitute as attorney work product.
If you are not the intended recipient, you are hereby notified
that any use, dissemination, distribution, or copying of this
communication is strictly prohibited. If you have received this
communication in error, notify us immediately by telephone and
(i) destroy this message if a facsimile or (ii) delete this message
immediately if this is an electronic communication.
Thank you.
midrange.com
