I have done MANY of these and never seen IPV6 flood a network. Actually I've never seen IPV4 floods from an i either for that matter.

Does the flood stop while the system is IPLing or does it continue throughout? Frankly the only part of IPV6 that actually is configured by default is the loopback address ::1. There is no IPV6 configured on any Ethernet line unless you did so so this on the surface doesn't make any sense at all.

I'm assuming that the network guys are saying 'from this LPAR' because the MAC address is a match to that of your Ethernet line. You didn't say what sort of Ethernet card the machine has (i.e. 5706 or IVE card for example)

Can we be sure the switch itself isn't at fault here? Tried any other ports on the switch?

- Larry "DrFranken" Bolhuis

On 5/14/2011 5:55 PM, fbocch2595@xxxxxxx wrote:
Hi Folks, overnight we upgraded from V5R4 to V6R1M1 (LIC at V6R1M1) and after an upgrade of about 6 hours (including the object conversion) our network started to be flooded by IPV6 traffic from the newly upgraded lpar and it's causing slowdowns all over the network and affecting users and production. Has anyone else had similar circumstances or issues like this? I did not know or realize that IPV6 would start so we changed the cmd default so STRTCP would not start IPV6 and we also CHGIPLA to Start TCP/IP *NO and we've ipl'd several time and our network folks continue to say the newly upgraded system is flooding the network with traffic.

If anyone has any help or info to share on this type of situation, plz let me know

Management wants to go back to the prior release!

Thanks

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.