- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: KZPSC-XB
Operating System - Tru64 Unix
1748018
Members
3512
Online
108757
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-31-2004 01:25 PM
тАО08-31-2004 01:25 PM
KZPSC-XB
I have a ds20 with FW 6.8 and need to reinstall T64 V5.1A
For what I have been reading this RAID card is no longer supported after V5.0A, so my question is ?
How come this system has a KZPSC-XB card under T64 5.1A . I am not the orginal SA for the system and I am trying to find out all of the parts intallation history.
From the loging banner:
Compaq Tru64 UNIX V5.1A (Rev. 1885); Thu Feb 20 15:16:28 PST 2003
****************************************************************************
On Tue Feb 18 15:03:13 PST 2003 your system was successfully updated from:
Compaq Computer Corporation Tru64 UNIX V5.1 (Rev. 732)
****************************************************************************
On Tue Feb 18 11:14:42 PST 2003 your system was successfully updated from:
Compaq Computer Corporation Tru64 UNIX V4.0G (Rev. 1530)
Tru64 UNIX V4.0G (Rev. 1530)
****************************************************************************
On Tue Feb 18 09:30:07 PST 2003 your system was successfully updated from:
Digital UNIX V4.0E [Rev. 1091]; Tue Jul 20 11:36:23 PDT 1999
==============================================
$ uname -a
OSF1 delta V5.1 1885 alpha
kern.log
==============================================
Aug 27 22:03:09 xx01 vmunix: Alpha boot: available memory from 0x63130000 to 0x8fffa000
Aug 27 22:03:09 xx01 vmunix: Compaq Tru64 UNIX V5.1A (Rev. 1885); Thu Feb 20 15:16:28 PST 2003
Aug 27 22:03:09 xx01 vmunix: physical memory = 2304.00 megabytes.
Aug 27 22:03:09 xx01 vmunix: available memory = 718.78 megabytes.
Aug 27 22:03:09 xx01 vmunix: using 2840 buffers containing 22.18 megabytes of memory
Aug 27 22:03:10 xx01 vmunix: Master cpu at slot 0
Aug 27 22:03:10 xx01 vmunix: Starting secondary cpu 1
Aug 27 22:03:10 xx01 vmunix: Firmware revision: 6.8-9
Aug 27 22:03:10 xx01 vmunix: PALcode: UNIX version 1.92-74
Aug 27 22:03:10 xx01 vmunix: AlphaServer DS20 500 MHz
Aug 27 22:03:10 xx01 vmunix: pci1 (primary bus:1) at nexus
Aug 27 22:03:10 xx01 vmunix: Loading SIOP: script c0000000, reg 1011000, data c000a000
Aug 27 22:03:10 xx01 vmunix: scsi0 at psiop0 slot 0 rad 0
Aug 27 22:03:10 xx01 vmunix: isp0 at pci1 slot 8
Aug 27 22:03:10 xx01 vmunix: isp0: QLOGIC ISP1040B/V2
Aug 27 22:03:10 xx01 vmunix: isp0: Firmware revision 5.57 (loaded by console)
Aug 27 22:03:10 xx01 vmunix: isp0: Fast RAM timing enabled.
Aug 27 22:03:10 xx01 vmunix: scsi1 at isp0 slot 0 rad 0
Aug 27 22:03:10 xx01 vmunix: pci0 (primary bus:0) at nexus
Aug 27 22:03:10 xx01 vmunix: isa0 at pci0
Aug 27 22:03:10 xx01 vmunix: gpc0 at isa0
Aug 27 22:03:10 xx01 vmunix: gpc1 not probed
Aug 27 22:03:10 xx01 vmunix: ace0 at isa0
Aug 27 22:03:10 xx01 vmunix: ace1 at isa0
Aug 27 22:03:10 xx01 vmunix: lp0 at isa0
Aug 27 22:03:10 xx01 vmunix: fdi0 at isa0
Aug 27 22:03:10 xx01 vmunix: fd0 at fdi0 unit 0
Aug 27 22:03:10 xx01 vmunix: ata0 at pci0 slot 105 (slot 5, function 1)
Aug 27 22:03:10 xx01 vmunix: ata0: CYPRESS 82C693
Aug 27 22:03:10 xx01 vmunix: scsi2 at ata0 slot 0 rad 0
Aug 27 22:03:10 xx01 vmunix: ata1 at pci0 slot 205 (slot 5, function 2)
Aug 27 22:03:10 xx01 vmunix: ata1: CYPRESS 82C693
Aug 27 22:03:10 xx01 vmunix: scsi3 at ata1 slot 0 rad 0
Aug 27 22:03:10 xx01 vmunix: usb0 at pci0 slot 305 (slot 5, function 3)
Aug 27 22:03:10 xx01 vmunix: tga0 at pci0 slot 7
Aug 27 22:03:10 xx01 vmunix: tga0: depth 8, map size 2MB, 1024x768
Aug 27 22:03:10 xx01 vmunix: pci3 (primary bus:0 subordinate bus:2) at pci0 slot 8
Aug 27 22:03:10 xx01 vmunix: Initializing xcr0. Please wait....
Aug 27 22:03:11 xx01 vmunix: xcr0 at pci0 slot 9
Aug 27 22:03:11 xx01 vmunix: RAID-ctlr-0-unit-0 at xcr0 unit 0 (unit status = ONLINE, raid lev
el = 1)
Aug 27 22:03:11 xx01 vmunix: RAID-ctlr-0-unit-1 at xcr0 unit 1 (unit status = ONLINE, raid lev
el = 5)
Aug 27 22:03:11 xx01 vmunix: RAID-ctlr-0-unit-2 at xcr0 unit 2 (unit status = ONLINE, raid lev
el = 5)
Aug 27 22:03:11 xx01 vmunix: RAID-ctlr-0-unit-3 at xcr0 unit 3 (unit status = ONLINE, raid lev
el = 1)
Aug 27 22:03:11 xx01 vmunix: RAID-ctlr-0-unit-4 at xcr0 unit 4 (unit status = ONLINE, raid lev
el = 1)
So is this a supported board ?
TIA
Ed Silva
esilva@silvex.com
For what I have been reading this RAID card is no longer supported after V5.0A, so my question is ?
How come this system has a KZPSC-XB card under T64 5.1A . I am not the orginal SA for the system and I am trying to find out all of the parts intallation history.
From the loging banner:
Compaq Tru64 UNIX V5.1A (Rev. 1885); Thu Feb 20 15:16:28 PST 2003
****************************************************************************
On Tue Feb 18 15:03:13 PST 2003 your system was successfully updated from:
Compaq Computer Corporation Tru64 UNIX V5.1 (Rev. 732)
****************************************************************************
On Tue Feb 18 11:14:42 PST 2003 your system was successfully updated from:
Compaq Computer Corporation Tru64 UNIX V4.0G (Rev. 1530)
Tru64 UNIX V4.0G (Rev. 1530)
****************************************************************************
On Tue Feb 18 09:30:07 PST 2003 your system was successfully updated from:
Digital UNIX V4.0E [Rev. 1091]; Tue Jul 20 11:36:23 PDT 1999
==============================================
$ uname -a
OSF1 delta V5.1 1885 alpha
kern.log
==============================================
Aug 27 22:03:09 xx01 vmunix: Alpha boot: available memory from 0x63130000 to 0x8fffa000
Aug 27 22:03:09 xx01 vmunix: Compaq Tru64 UNIX V5.1A (Rev. 1885); Thu Feb 20 15:16:28 PST 2003
Aug 27 22:03:09 xx01 vmunix: physical memory = 2304.00 megabytes.
Aug 27 22:03:09 xx01 vmunix: available memory = 718.78 megabytes.
Aug 27 22:03:09 xx01 vmunix: using 2840 buffers containing 22.18 megabytes of memory
Aug 27 22:03:10 xx01 vmunix: Master cpu at slot 0
Aug 27 22:03:10 xx01 vmunix: Starting secondary cpu 1
Aug 27 22:03:10 xx01 vmunix: Firmware revision: 6.8-9
Aug 27 22:03:10 xx01 vmunix: PALcode: UNIX version 1.92-74
Aug 27 22:03:10 xx01 vmunix: AlphaServer DS20 500 MHz
Aug 27 22:03:10 xx01 vmunix: pci1 (primary bus:1) at nexus
Aug 27 22:03:10 xx01 vmunix: Loading SIOP: script c0000000, reg 1011000, data c000a000
Aug 27 22:03:10 xx01 vmunix: scsi0 at psiop0 slot 0 rad 0
Aug 27 22:03:10 xx01 vmunix: isp0 at pci1 slot 8
Aug 27 22:03:10 xx01 vmunix: isp0: QLOGIC ISP1040B/V2
Aug 27 22:03:10 xx01 vmunix: isp0: Firmware revision 5.57 (loaded by console)
Aug 27 22:03:10 xx01 vmunix: isp0: Fast RAM timing enabled.
Aug 27 22:03:10 xx01 vmunix: scsi1 at isp0 slot 0 rad 0
Aug 27 22:03:10 xx01 vmunix: pci0 (primary bus:0) at nexus
Aug 27 22:03:10 xx01 vmunix: isa0 at pci0
Aug 27 22:03:10 xx01 vmunix: gpc0 at isa0
Aug 27 22:03:10 xx01 vmunix: gpc1 not probed
Aug 27 22:03:10 xx01 vmunix: ace0 at isa0
Aug 27 22:03:10 xx01 vmunix: ace1 at isa0
Aug 27 22:03:10 xx01 vmunix: lp0 at isa0
Aug 27 22:03:10 xx01 vmunix: fdi0 at isa0
Aug 27 22:03:10 xx01 vmunix: fd0 at fdi0 unit 0
Aug 27 22:03:10 xx01 vmunix: ata0 at pci0 slot 105 (slot 5, function 1)
Aug 27 22:03:10 xx01 vmunix: ata0: CYPRESS 82C693
Aug 27 22:03:10 xx01 vmunix: scsi2 at ata0 slot 0 rad 0
Aug 27 22:03:10 xx01 vmunix: ata1 at pci0 slot 205 (slot 5, function 2)
Aug 27 22:03:10 xx01 vmunix: ata1: CYPRESS 82C693
Aug 27 22:03:10 xx01 vmunix: scsi3 at ata1 slot 0 rad 0
Aug 27 22:03:10 xx01 vmunix: usb0 at pci0 slot 305 (slot 5, function 3)
Aug 27 22:03:10 xx01 vmunix: tga0 at pci0 slot 7
Aug 27 22:03:10 xx01 vmunix: tga0: depth 8, map size 2MB, 1024x768
Aug 27 22:03:10 xx01 vmunix: pci3 (primary bus:0 subordinate bus:2) at pci0 slot 8
Aug 27 22:03:10 xx01 vmunix: Initializing xcr0. Please wait....
Aug 27 22:03:11 xx01 vmunix: xcr0 at pci0 slot 9
Aug 27 22:03:11 xx01 vmunix: RAID-ctlr-0-unit-0 at xcr0 unit 0 (unit status = ONLINE, raid lev
el = 1)
Aug 27 22:03:11 xx01 vmunix: RAID-ctlr-0-unit-1 at xcr0 unit 1 (unit status = ONLINE, raid lev
el = 5)
Aug 27 22:03:11 xx01 vmunix: RAID-ctlr-0-unit-2 at xcr0 unit 2 (unit status = ONLINE, raid lev
el = 5)
Aug 27 22:03:11 xx01 vmunix: RAID-ctlr-0-unit-3 at xcr0 unit 3 (unit status = ONLINE, raid lev
el = 1)
Aug 27 22:03:11 xx01 vmunix: RAID-ctlr-0-unit-4 at xcr0 unit 4 (unit status = ONLINE, raid lev
el = 1)
So is this a supported board ?
TIA
Ed Silva
esilva@silvex.com
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-31-2004 09:04 PM
тАО08-31-2004 09:04 PM
Re: KZPSC-XB
why not simply look at the HP website, checking the adapter and hardware requirements? It will describe what is supported and how....
so select machine ds20, have a look into supported options, search your adapter and simple read if it is supported and what are the requirements...
http://h18002.www1.hp.com/alphaserver/options/asds20/asds20_15_options_sorted.html#OptListHead
Btw. the given identifier is not listed within the support option list of the machine, so it is unsupported! Replace adapter by a supported one.
so select machine ds20, have a look into supported options, search your adapter and simple read if it is supported and what are the requirements...
http://h18002.www1.hp.com/alphaserver/options/asds20/asds20_15_options_sorted.html#OptListHead
Btw. the given identifier is not listed within the support option list of the machine, so it is unsupported! Replace adapter by a supported one.
Help() { FirstReadManual(urgently); Go_to_it;; }
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-04-2004 12:49 PM
тАО09-04-2004 12:49 PM
Re: KZPSC-XB
Ralf,
Not to be a smartass, but my basic question(s) are:
Why does an unsupported card works, when the release notes state that it is no longer supported ?
What is the definition of 'no supported/unsupported' ?
-- Use it at your own risk ?
-- It works , but if you have a problem don't call us ?
Now, if it is unsupported, why include drivers OR if you upgraded why migrate legacy drivers of unsuported hardware?
TIA!!
-Ed
esilva@silvex.com
Not to be a smartass, but my basic question(s) are:
Why does an unsupported card works, when the release notes state that it is no longer supported ?
What is the definition of 'no supported/unsupported' ?
-- Use it at your own risk ?
-- It works , but if you have a problem don't call us ?
Now, if it is unsupported, why include drivers OR if you upgraded why migrate legacy drivers of unsuported hardware?
TIA!!
-Ed
esilva@silvex.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-05-2004 07:58 PM
тАО09-05-2004 07:58 PM
Re: KZPSC-XB
A highend system is not a plug and play system like a PC where playing around (=frickling) is an option. If using it be sure you meet the vendor requirements. Our engineering team and most software companies (oracle, informix etc.) tests their products for compatiblity including firmware, patches etc. If a problem occures during testing the product fail the supported state.
If it is not supported you are on your own, means no engineering support, no help at all until you change it back to a supported configuration. This is an issue if you are using the machine for production. If you play around it is ok but don't ask in case of trouble.
Plugin cards into a machine without checking compatiblity is fairly risky due to restrictions. We offers enough documentation to prevent such issues so why not using them to get an supported configuration?
Btw. not all cards are supported in every machine due to technical differences (chipsets, sideeffects). In your case the card is not listed for the used machine so please replace it by another one.
If it is not supported you are on your own, means no engineering support, no help at all until you change it back to a supported configuration. This is an issue if you are using the machine for production. If you play around it is ok but don't ask in case of trouble.
Plugin cards into a machine without checking compatiblity is fairly risky due to restrictions. We offers enough documentation to prevent such issues so why not using them to get an supported configuration?
Btw. not all cards are supported in every machine due to technical differences (chipsets, sideeffects). In your case the card is not listed for the used machine so please replace it by another one.
Help() { FirstReadManual(urgently); Go_to_it;; }
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP