Re: IXA resource failures -- MIDRANGE-L

Ok, thanks.   
 
 
-----Original Message-----
From: John.Jones@xxxxxxxxxx
To: midrange-l@xxxxxxxxxxxx
Sent: Thu, 14 Dec 2006 11:05 AM
Subject: RE: IXA resource failures


IxS = Integrated xSeries Server = "PC on a card" that resides entirely
within the iSeries frame.
IxA = Integrated xSeries Adapter = card for an outboard xSeries server.

Details at http://www-03.ibm.com/systems/i/bladecenter/product_info.html


John A. Jones, CISSP
Americas Information Security Officer
Jones Lang LaSalle, Inc.
V: +1-630-455-2787 F: +1-312-601-1782
john.jones@xxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of fbocch2595@xxxxxxx
Sent: Thursday, December 14, 2006 9:58 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: IXA resource failures

What's IXA vs. IXS?  
 
 
-----Original Message-----
From: Pete@xxxxxxxxxx
To: midrange-l@xxxxxxxxxxxx
Sent: Wed, 13 Dec 2006 10:48 PM
Subject: IXA resource failures


A couple of weeks ago, I posted a question to the list about IXA,
cabling and a failure for the resource to be recognized by the System i.
I have sorted out some of the issues but I still haven't gotten this
resolved.  The resource is now recognized but is fails to become
operational.

Charles Wilt replied with:
--------------------------------------------------
It's been awhile since I did an IxA, I don't recall the jumper info you
described.

But IIRC, the HSL loops are directional, both the cables and the ports
themselves have to be connected in the right direction.  The cables have
tags with arrows on them.  The port directionality can be found in the
manual.

Also, the SPCN cabling is a little strange, I remember spending a lot of
time looking at the diagrams till I figured out how it was supposed to
be.

If all else fails, call IBM.

---------------------------------------------------

First, the HSL cabling:  The cables are unidirectional, fortunately I
can't connect them in the wrong "direction" since each end has a unique
connector that only plugs in one way.  However, I could have them in the
wrong *order* (I am guessing).  I have them as follows: Cable 1 goes
from the xSeries Port 0 to the HSL port on the System i called "T1".  
Cable 2 from the xSeries Port 1 to the HSL port on the System i called
"T2". Is that correct?

Second, the SPCN cabling.  There is a J15 port on the xSeries.  I cabled
this to the SPCN 0 port on the System i.  Is this correct?

Actually, ALL of the cables go to a card in the xServer (the 1519-001
IXA).

The diagrams with the instructions are pretty minimal.  It usually just
says "Make sure the cables are connected correctly and are tight".  Not
much help.

WRKHWDRSC *CMN originally showed the 2689 as "Not Operational" with
resource CC01.  After IPL it shows "Not Detected".  SST shows the
following in the Product Activity Log:

Class . . . . . . . . . . :   Informational
System Ref Code . . . . . :   B6005120    
System LIC detected a program exception   

Class . . . . . . . . . . :   Informational
System Ref Code . . . . . :   B6005275    
URC Information not available             

When I look at HSL resources, drilling down a bit I see:

Opt Description              Type-Model Resource Name Status    
    Multi-adapter Bridge      2689-      PCI04D       Unknown   
    HSL I/O Bridge            2689-      BC02         Operational
    Bus Expansion Adapter     2689-      BCC08        Unknown   
    Communications IOP        2689-001   CC01         Unknown   


Finally, Charles suggested "Call IBM".  Did that (they have a 24/7
support contract).  They guy at level 1 hardware support said that he
didn't know much about the iSeries and xSeries working together.  He
said he would call the local service representative.  He did that, and
the rep called me and said that he hadn't actually worked on an IXA
before so he wasn't sure where to start.  He did say that we should get
the customer to cut a P.O. so he could fly down here and take a look at
it.  He said that support wasn't for MES, Customer installed
troubleshooting.

Sigh.

Any help on diagnostic steps to take would be helpful.

Thanks,

Pete Helgren


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.
________________________________________________________________________
Check out the new AOL.  Most comprehensive set of free safety and
security tools, free access to millions of high-quality videos from
across the web, free AOL Mail and more.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.


This email is for the use of the intended recipient(s) only.  If you have 
received this email in error, please notify the sender immediately and then 
delete it.  If you are not the intended recipient, you must not keep, use, 
disclose, copy or distribute this email without the author's prior permission.  
We have taken precautions to minimize the risk of transmitting software 
viruses, 
but we advise you to carry out your own virus checks on any attachment to this 
message.  We cannot accept liability for any loss or damage caused by software 
viruses.  The information contained in this communication may be confidential 
and may be subject to the attorney-client privilege. If you are the intended 
recipient and you do not wish to receive similar electronic messages from us in 
future then please respond to the sender to this effect.