Re: IPv6 vs IPv4 Was: HMC RMC IPv4?

On 4/25/19 4:04 PM, Rob Berendt wrote:

I hear that many internal networks will remain IPv4 for years to come as there is little chance of busting the numbers in an internal network.

If it works, do not fix it.  But, it looks like the new HMC uses only
IPv6, or at least it uses IPv6 as first choice.

However,

1-If you were starting a new business setup from scratch with modern equipment would you set up the internal side with IPv4 or just do it all with IPv6?
2-Are there other compelling reasons to go to IPv6 internally? Nothing on the horizon like some future equipment not supporting IPv4? New security stuff requiring IPv6? Anything in that genre?

In the USA there are a lot of institutions with a large number of IPv4
addresses assigned, but for the ones using NAT IPv6 simplifies the network.

New telephone networks 5G is IPv6 only.  It can reach IPv4 sites through
translation (making the IPv4 slower),

Most of the frequently used services are in dual stack, so if you use
IPv6 only more than 60% of your traffic will not be translated to IPv4.

https://www.lightreading.com/ethernet-ip/ip-protocols-software/what-happens-if-youre-ipv4-only/d/d-id/706698

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Raul Jager
Sent: Thursday, April 25, 2019 3:40 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Re: HMC RMC IPv4?

In a PC I set up for console in a V7.3 machine had both, IPv4 and IPv6. The system choose IPv6, even after I suggested an IPv4 address as I read in the manual.

It is very likely that your best option is to enable IPv6,  and start using it as "Dual Stack" to start moving to IPv6.  Remember, there are still lot of IPv4 uses (more than 70%), but IPv4 is a "dead protocol", it will not be enhanced any more, and its user base is shrinking.

On 4/25/19 1:48 PM, Kevin Monceaux wrote:

On Thu, Apr 25, 2019 at 10:14:11AM -0500, Kevin Monceaux wrote:

From netstat on the HMC it looks like it's only listening for IPv6
RMC
connections:

$ netstat -tuln | grep 657
tcp6 0 0 :::657 :::* LISTEN
udp6 0 0 :::657 :::*

Since we don't use IPv6, I tried disabling IPv6 on our HMC with:

$ chhmc -c network -s disable --ipv6

After a reboot lshmc -n shows no IPv6 addresses configured, but
netstat still shows RMC only listening for IPv6 connections.

-- Este e-mail fue enviado desde el Mail Server del diario ABC Color --
-- Verificado por Anti-Virus Corporativo Symantec --
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com

-- Este e-mail fue enviado desde el Mail Server del diario ABC Color --
-- Verificado por Anti-Virus Corporativo Symantec --