MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » October 2012

Re: The i and DHCP



fixed

In my experience DHCP has not been an issue. Firewalls, duplicate client
IP addresses due to network misconfiguration, running out of DEVDs, etc.
but not DHCP.

What is the resolution for the devices when they can't connect? That
should give you an idea as to how/why the problem is happening.

In the mean time, on the i I would suggest making sure QAUTOCFG and
QAUTOVRT are set appropriately. On the client side, consider configuring
the emulator to generate unique session names (QPADEVnnnn) unless your
environment requires static names.

As to the help desk's attitude about the i, their manager should be
stressing the platform's relative importance to the help desk staff. The
staff needs to care because the company uses it. The debate about legacy
v. modern is immaterial. (And FWIW Windows came out in 1984; OS/400 in
1988. Using the definition of legacy = older, Windows is more legacy.)


On Thu, Oct 4, 2012 at 9:03 AM, John McKee <jmmckee@xxxxxxxxxxxxxx> wrote:

Improper phrasing on my part. I didn't mean a DHCP connection to the
i. I meant a connection from a workstation configured for DHCP
connecting to the i.

The pc people are a tad naive about DHCP. They weren't bothering to
tell me when they switched an IP address . User got "lucky" and had a
functional 5250 session. Then, the lease expired, sometimes days
later. Their other bit of whimsy has been to use the same device name
in the configuration file for multiple workstations. Works randomly.
Loads of laughs tracking down the error.

The corporate help desk views the i as "legacy". They don't care.

John McKee

On Thu, Oct 4, 2012 at 8:54 AM, Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:
There's no such thing as a "DHCP connection to the i"...

connections are done via IP address, it doesn't matter how they were
assigned, the i neither knows nor cares.

If you DHCP envioment is reassigning IP addresses while they are in
use, you have a problem. AFAIK there's nothing in the TCP/IP standard
that would allow for endpoints chnaging IPs in the middle of a
connection...good thing talk about a security issue!

Are users trying to hibernate or sleep their PC for long periods of
time with a 5250 session open? That's not going to work.

I suggest you work with getting procedures changed such that the help
desks first task is to determine if they can reach the system.
Meanwhile, simply re-assign the ticket back to them with a "no it's
not" :)

Charles

On Thu, Oct 4, 2012 at 9:42 AM, John McKee <jmmckee@xxxxxxxxxxxxxx>
wrote:
I haven't checked the countdown clock this morning. Probably 28 days
left. So, this isn't critical.

Corporate mandated switching from static addressing to DHCP. We get
random calls where a 5250 session cannot sign on or just quits
working. The corporate help desk has decided that if they receive two
such calls, then the i just HAS to be down - despite the fact that we
have several hundred attached and functioning workstations.

Anyway, here is my question: If a DHCP connection is established with
the i, and then the lease on the workstation IP address expires, and a
different IP address is subsequently assigned to the workstation
(sorry for the wordiness). is there any way that the i can determine
that address for that session has changed and do something about it?

I know the device description has the IP in it when a connection is
established. But, what happens when that address changes?


BTW, when corporate office sends out a bogus "system down" task, they
are done - task has been assigned. We get the heat for taking "too
long" to resolve the issue.

John McKee
--
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 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.









Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact