RE: LPAR validation Tool (LVT) newbie questions

Bryan,

Ok, I think I'm squared away now.

I'd been though all those books but I thought I was seeing some
conflicting information about the 5702/5712.

Specifically, I though I saw that the 5712 was listed as a CIF for the
810 and the 5088, 5094.  Plus reading on the list here that the
5702/5712 were the same, but my BP said I couldn't put the 5712 in my
810.

Going back, I see that the 5712 is not listed as a CIF for the 810 and I
understand now that even though the 5712 would go into a 5088 or 5094
attached to an i5 system, it won't go into a 5088 or 5094 attached to my
810.

One last question, my 810 doesn't have any PCI-X slots.  I've been told
that the 5702 will perform in a regular 32bit PCI slot the same as it
would in a 64bit PCI-X slot.  I thought that seemed weird, but I guess a
32bit PCI slot @ 66MHz has a bandwidth of about 266MB/s (254.4).  So I
guess it makes sense that the slots in the 810 can support it.  However,
wouldn't I get better performance if I move the 5702 away from my DASD
controller (currently in C01)?  Initial thought is to replace the 2749
in C04 with the 5702. Should I rearrange the base 810 or put the 5702
into my 5088 instead.


Thanks for your help.


Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
  

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx 
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Bryan Dietz
> Sent: Friday, December 16, 2005 2:59 PM
> To: Midrange Systems Technical Discussion
> Subject: RE: LPAR validation Tool (LVT) newbie questions
> 
> I think most of the confusion has to do with IBM's ordering 
> mess.  As a BP
> I run into this all the time.
> 
> I would would be nice to say I want a twinax card and you 
> then get to buy a
> 4746.  Of course if it is a base feature then it is a 9746. 
> Then you get
> you new system  and the card shows up in the rack config as a 2746.
> 3 different ways to say twinax.  Makes you want to get out of 
> the hardware
> side altogether.
> 
> Now the 5702/5712 is a bit different.  I believe they are the 
> same card,
> but you cannot order a 5712 for an 8xx box.  You have to 
> order a 5702.   If
> you have a 5xx you cannot order it as a 5702 it has to be a 
> 5712.  Then
> when you get the card the sticker on it says 5702....what gives.....
> 
> 
> confusion reigns supreme.  That is why you need to consult 
> the following
> books......
> 
> system builder:
> http://www.redbooks.ibm.com/Redbooks.nsf/RedbookAbstracts/sg24
> 2155.html?OpenDocument
> 
> and the
> 
> system handbook:
> http://www.redbooks.ibm.com/Redbooks.nsf/RedbookAbstracts/ga19
> 5486.html?OpenDocument
> 
> these are the two books that tell you what and where cards will fit.
> 
> and finially the card placement rules book:
> http://www.redbooks.ibm.com/Redbooks.nsf/RedbookAbstracts/redp
> 4011.html?Open
> 
> 
> Happy reading........
> 
> _____________________________
> Bryan Dietz
> Aktion Associates
> 
> 
> 
> midrange-l-bounces@xxxxxxxxxxxx wrote on 12/16/2005 12:43:17 PM:
> 
> > Brian,
> >
> > I though that the 5702/5712 were the same.  But I'm hearing 
> different
> > from my BP.
> >
> > According to him, the 5702 will go into the base cabinet of 
> my 810, even
> > though the 810 is not PCI-X, and the LVT seems to agree.  
> However, the
> > 5712 won't.
> >
> > Thus, I thought I'd play with it some myself.
> >
> > Again, I understand the some cards may be the same.  But it would be
> > really nice to be able to match the LVT to what is printed 
> on my rack
> > listing.
> >
> > Is there anyway to have the LVT use the old numbers?
> >
> > Charles Wilt
> > --
> 
> -- 
> 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.
> 
>