|
Hey, we keep it right there on the post it note by the hmc. We figure,
hey, it's a card access room and it's only hmc/fsp stuff. Not like we
keep qsecofr or some such thing on a post it note. Data's secure and
we're only opening ourselves to a DOS attack. But if they can get into
the machine room a few yanks on some network and/or power cables is a much
simpler DOS attack.
Rob Berendt
--
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: Jim Oberholtzer <midrangel@xxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 02/09/2012 08:20 AM
Subject: Re: HMC code update from the grave
Sent by: midrange-l-bounces@xxxxxxxxxxxx
One way to ensure you know the HMC password is to go into the ASMI from
the HMC and change it BEFORE you do anything else. That has saved my
backside a time or two since customers rarely know what the CE or
installer set it to in the first place. Then if they think they know,
it's almost always not correct. Customers with legislative
constraints, or that have a full time administration staff usually know
the password and it's correct.
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects
On 2/8/2012 7:34 PM, DrFranken wrote:
Two things to keep in mind:do it. He ended up wiping the HMC and discarding the backup data. He
1) Watch for the relationship between the firmware and HMC. That is,
don't update the HMC too far all at once so that you loose connection to
the FSP.
-and more importantly-
2) Make sure you have the HMC access password. If you completely reload
the HMC then it will 're-introduce itself' to the FSP and the FSP will
require that password. (Yes you can reset the FSP with the magical
switches but then it kinda forgets everything it knows.)
- Larry "DrFranken Bolhuis"
On 2/8/2012 8:02 PM, Chris Bipes wrote:
I had to make the same upgrade a while back. I hired an expert to
reloaded the one server with one partition back from the service processor
with no loss of production data. Your plan sounds valid and about what we
did over a fuzzy and busy year ago.
----
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 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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.