On Fri, Sep 3, 2010 at 9:12 PM, Marcy Cortes <[email protected]> wrote:
> And while it says State: Down on the ones with a blank Node: , clearly it's > not since the byte counts keep increasing... Back then, when Alan was still among us, he'd ask to draw a picture ;-) Are you sure the counts for the "down" links are still increasing, or is this from before it went down? I know from experience that it is best not to add redundant links that allow systems to communicate via different paths. So if you have 3 systems, I would make just use 2 connections. CP does not like two routes to the same node, and race conditions during link establishment do weird things. So (A) ----- (B) ----- (C) Obviously you would give the role of (B) to the system that is most popular in conversations (eg where the SFS server runs). That avoids overhead of the extra hop for most of the traffic. It appears less robust, but the duplicate links don't prevent a short outage (and loss of conversations) anyway. If you need that, get something done in your programmable operator to activate the other ISLINK when you have an outage. | Rob PS My experience is based on z/VM 5 and earlier. I can't comment on what future z/VM levels will do.
