RE: iSeries in SAN environment -- MIDRANGE-L

× 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.

Subject: RE: iSeries in SAN environment
From: "Walden H. Leverich" <WaldenL@xxxxxxxxxxxxxxx>
Date: Wed, 2 Aug 2006 09:54:50 -0400
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

No, I'm not saying that, but IBM's diagnosis tools are much more 
precise in internal DASD, as opposed to the blob of external DASD.


I could see that that iSeries tools are more precise, but if you're on a
SAN, then you should be looking at the SAN tools and not the individual
server tools, no? The SAN tools should be able to tell you individual
arm utilization, cache hits/misses and load factors.

-Walden

As an Amazon Associate we earn from qualifying purchases.

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.