- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: GS160 failures
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
тАО03-04-2004 09:27 PM
тАО03-04-2004 09:27 PM
GS160 failures
I have a GS160 with 2 QBB each running a VMS node. There is dual everything.
My question is : what can go wrong with 1 qbb that brings the other down too. E.g. can an electrical problem in qbb1 cause failure in qbb2 ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-04-2004 10:56 PM
тАО03-04-2004 10:56 PM
Re: GS160 failures
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-05-2004 01:36 PM
тАО03-05-2004 01:36 PM
Re: GS160 failures
Having to replace a failed PCI card in the old 320 required that I power cycle the entire 320 box before that QBB would come back online. This is one of the reasons that we do not use the GS160/320 for production systems.
Do you have shared memory between the QBB's? Or are you Hard Partitioned with no shared memory?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-07-2004 06:17 PM
тАО03-07-2004 06:17 PM
Re: GS160 failures
Once we had to bring it down because a tapedrive had to be switches with its local scsi.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-07-2004 07:30 PM
тАО03-07-2004 07:30 PM
Re: GS160 failures
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-07-2004 10:35 PM
тАО03-07-2004 10:35 PM
Re: GS160 failures
As Mike has already said Power can be an issue. Unlike the Marvel GS1280 the GS160/320's only have single power rails for all QBB's/FireBox's - which I think was a major design oversight. Losing a PDU will bring the all partitions down. And our GS320 IS running our production system, which is why we have a GS320 DR system as well!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-08-2004 06:15 AM
тАО03-08-2004 06:15 AM
Re: GS160 failures
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-08-2004 08:28 AM
тАО03-08-2004 08:28 AM
Re: GS160 failures
Uncanny that you should ask the question today, just last week we upgraded our GS160 and added another partition. ( Thursday)
On friday the system crashed, adn we had no Idea what the problem was, we logged a acall with HP and the Engineer came out here, he did some checking.
The error message that we got was there is an error with CPU0 in QBB 0, and it takes the entire system down.
After about 2 hours of fiddling around. The answer we got was the firm ware levels in both QBBS do not match, so he did an Upgrade so that all firmware levels and microcodes were at the same level.
Second he mentioned that the missing cable ( The cable that goes from the PCI bus to the Display on the front panel, might be the problem, he then swapped the two PCI shelve status i.e master to slave.
After all this he was still not sure that the problem is fixed, we have the system up and running, it is a test box so we're not to fussed, but we plan to add a partition on the production soon.
Thanks hope this helps.
Orrin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-08-2004 06:19 PM
тАО03-08-2004 06:19 PM
Re: GS160 failures
When hard partitioned, the 160 gives me the equivalent of one rack of ES45's. The 160 takes up 3.5 floor tiles, where the rack of 45's is one floor tile.
Our 320 that is hard partitioned into 8 qbb's that is the equivalent of 2 racks of ES40's, but it uses 5 floor tiles. (4xCPU w 8GB ram)
Like Keith pointed out, if you are servicing the box to upgrade firmware, you take it all down. This is what makes it a bad "Production" box for me. Also, the maintenance and licensing on the GS was 10X the licenses for equivalent ES4x boxes. Another reason not to use it.
So far, replacing CPU's and Memory in the 160/320 has not taken down the rest of the system.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-08-2004 06:54 PM
тАО03-08-2004 06:54 PM
Re: GS160 failures
But it was the management that decided to buy this one ... with only 1 dual cpu per qbb. It is ready for expansion ... while the platform is in phase out.