HP3000-L Archives

December 1995, Week 5

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Leonard S. Berkowitz" <[log in to unmask]>
Reply To:
Leonard S. Berkowitz
Date:
Fri, 29 Dec 1995 13:46:00 PST
Content-Type:
text/plain
Parts/Attachments:
text/plain (91 lines)
Maybe I'm missing something here.  But couldn't you hook the drives up with
unique scsi addresses, run IOMAP from the ISL> prompt and then get the
correct model numbers and the correct path information?  Of course this will
not give you the serial numbers.
 
Speaking of which, It would be a very nice enhancement for HP if when you
ran IOMAP that you could somehow get serial numbers from all directly
connected peripherals.  This would make our jobs and the CE jobs easier.
 
Also, we had an experience with our 987/150.  The system came with an
internal 1GB drive (Ldev 1).  Some months after our initial installation, it
was discovered by HP that the internal drive was configured incorrectly
(wrong ID) at the factory.  If these guys can't get it right, who can?
 
Stephen Vose
Technical Support Manager
Warren, Gorham & Lamont
[log in to unmask]
 ----------
>From: owner-hp3000-l%UTCVM.UTC.EDU
>To: Multiple recipients of list HP3000-L
>Subject: DAT drive mysteries
>Date: Friday, December 29, 1995 8:57AM
>
>---------------------- Information from the mail header
>-----------------------
>Sender:       HP-3000 Systems Discussion <[log in to unmask]>
>Poster:       "Rudderow, Evan" <[log in to unmask]>
>Subject:      DAT drive mysteries
>---------------------------------------------------------------------------
 ----
>-
>
>Neil Harvey <[log in to unmask]> wrote:
>
>>Jeff Woods cleared up a few DDS mysteries. But I have the following wierd
>>problem.
>>
>>Our 959/400 shipped with an internal DDS drive. The label on the drive
>>says DCLZ. The Sysgen says HPC1504B.
>>
>>We also took across 4 x old style DDS drives (C1503B's).
>>
>>Last week we took out the C1503B's and replaced them with C3556U's
>>
>>The HP3000 Sysgen IO says they are C1533A's
>>
>>The Box they shipped in says they are C3556U's.
>>
>>The leaflet inside says they are C3556N's
>
><snip>
>
>>I'm puzzled. Any help appreciated.
>
>Drink heavily?  Watch the Ren & Stimpy marathon?  Sacrifice small animals?
> Seriously though, Neil's predicament raises another marketing/support
issue
>in addition to the recent HP Sales F(o,a)rce Ramblings thread: that of
>product IDs.
>
>Let's see, when I ordered my first round of 2GB SCSI disc drives I ordered
a
>mix of these product IDs: C3023R, C3024R, C3025R and C3028U.  Of course,
>when I configure them on the system, they are all C3010M1s; they're C3010M1
>in Predictive Support as well.  However, I can't enter any meaningful
serial
>numbers for Predictive because, after all, depending what's in it, how it
>was purchased, and how it was upgraded; a Series 6000 peripheral enclosure
>can have anywhere from one to about a million serial numbers on the back of
>it.  Of course, back on my hardware support contract they are C3023R, etc.
>
>And the same thing happened when I got my second round of 2GB SCSI discs,
>except that time the orderable part IDs were C3041R and C3044U (both option
>002 -- can't forget those *options*!) while the, shall we say,
>"configurable" IDs was C2490AM.
>
>This is really a mess.  Does anybody out there know why it's like this?
>
>Perhaps we shouldn't wonder why it takes so long to get a quote out of HP
 --
>perhaps they're not quite sure what they're selling... ;-)
>
>BTW, Neil, what does SYSDIAG | SYSMAP | IOMAP | GENERAL think your DDS
>drives are?  For that matter, what does SYSDIAG | SCSIDDS think they are?
>
>Good Luck, Neil.
>
> -- Evan
>

ATOM RSS1 RSS2