True it's easier then but now you'll have a mixed environment that 90% of
the technicians will have no or little clue about how to manage it. Most of
your standard trouble shooting techniques were designed for IPV4 and don't
translate well to IPV6.
Mixed environment, no thanks.
--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
rob@xxxxxxxxx
Sent: Monday, March 30, 2015 7:00 AM
To: Midrange Systems Technical Discussion
Subject: RE: IPv6 Inside the DC (WAS Re: IPv6 disable - yes or no , and
which method)
Actually Jim, I agree with you. But, if you were starting up a whole new
company, branch, etc. With the latest state of the art networking equipment
and all data processing gear using the latest versions of their respective
operating systems, why not start out with IPv6 for internal use?
After all, it's not like going from the English system to Metric. :-)
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 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: "Jim Oberholtzer" <midrangel@xxxxxxxxxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 03/30/2015 07:47 AM
Subject: RE: IPv6 Inside the DC (WAS Re: IPv6 disable - yes or no
, and which method)
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
I still fall on the side of IPV4 inside the enterprise and if your
internet
provider insists IPV6 on the outside.
The conversion to IPV6 on the private network, unless it's really huge and
complex, is just not worth the effort.
--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
rob@xxxxxxxxx
Sent: Monday, March 30, 2015 6:30 AM
To: Midrange Systems Technical Discussion
Subject: Re: IPv6 Inside the DC (WAS Re: IPv6 disable - yes or no , and
which method)
Larry,
That's Raul, not Paul.
Maybe he brings a more international experience to the mix. Perhaps
people
elsewhere do things we wouldn't.
Like put their IBM i directly on the internet trusting in intrusion
detection and whatnot.
Maybe newer smaller companies figure the world is going to IPv6 so they
just
start out with everything internal that way also. New fit versus
retrofit.
If you were a company the size of Microsoft, and had to account for every
desktop, laptop, server, PDA, smartphone, security camera, etc maybe they
get concerned about IPv4 even for internal use.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 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: DrFranken <midrange@xxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 03/29/2015 01:47 PM
Subject: IPv6 Inside the DC (WAS Re: IPv6 disable - yes or no ,
and which method)
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
Paul,
What is the gain inside the DC for moving to IPV6?
I get that globally IPV6 is beyond needed, no argument. For an
organization to go through the effort (planning, equipment changes,
documentation, training, TESTING etc) just to be able to say 'We run
IPV6' isn't enough.
- Larry "DrFranken" Bolhuis
www.frankeni.com
www.iDevCloud.com
www.iInTheCloud.com
On 3/27/2015 5:21 PM, Raul A Jager W wrote:
I sugest you to change your plans, and begin the switch to IPv6 ASAP.
Not doing so will "reinforce" the image of the AS/400 and sucesors as
obsolete.
On 03/27/2015 10:42 AM, Steinmetz, Paul wrote:
midrange.com
