× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



10.10.1.195 can ping both 10.10.1.1 and 10.10.6.1.

10.10.6.48 can ping 10.10.6.1 but not 10.10.1.1

Gateways being 10.10.x.1...

10.10.1.195 has had two routes for a long time. *DFTROUTE hops through
10.10.1.1 with no preferred interface. "mimix" route hops through
10.10.252.1 via preferred interface 10.10.252.192. Two nics. (old power
6)

10.10.6.48 *DFTROUTE hops through 10.10.6.1 through preferred interface
10.10.6.48. No other routes. fiber ethernet virtualized through two vios
lpars. New Power 8. Other lpars on this same Power 8, also using

I hope no static ARP entries exist. But I'll leave that up to the network
guy to determine. I really don't know what they are.

I wondered if it might be something that needed to flush out. But it's
been 46 hours or more since the network changes were made.

I have another lpar (10.10.6.129) on that same power 8 with two routes
(10.10.6.1 and 10.10.252.1) being served up by the same vios lpars and
through the same switches. It can ping '10.10.1.1' and '10.10.6.1' with
no problems.

Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.