|
Why does everything have to be so complicated.
The AIX server ended up being covered by an extended hardware warranty, so
the guy that came and replaced it just swapped blade servers out. Software
support is another area. He gave me some contact information for someone
who specializes in this area, but before I got a third party in here to
work on it figured I would ask to see if it was hopefully just as simple as
telling the DS3500 that the new Host Interface was allowed to connect and
access those logical drives and everything would go back to working.
And it is a production machine. Kind of. Need it to access and move old
medical records.
He did place some little chip back in the chassis and the serial number
changed over to match the old one, but that may not mean anything when it
comes to getting it back going.
Thanks for your help, I at least know now what to expect when I call in
additional support.
Sent from AT&T Yahoo Mail for iPhone
On Friday, July 9, 2021, 12:38 PM, Roberto José Etcheverry Romero <
yggdrasil.raiker@xxxxxxxxx> wrote:
Replacing the sysboard on a PS700 is not a trivial matter, there's a lot of
procedures you have to follow and if you didn't have a backup of your
VIOS/IVM config you have to tinker to repair devices if they get enumerated
differently (just to start).
Whoever replaced the sysboard should have migrated the VPD, disks, and FC
adapter. With that you shouldn't have to remap anything, but you will have
to fix the VIOS because the FSP lives in the sysboard and replacing it
means losing the partition information.
I hope you can at least start that way, but it's not something I'd like to
learn to fix on my production machine.
Best of luck
Roberto
On Fri, 9 Jul 2021 at 11:35, BRUCE VAIL <bjvail@xxxxxxxxxxxxx> wrote:
Yesterday we swapped out a PS700 (840670Y). It's in a BladeCenter S. Thedon't
planar went bad on the old one. New one is powered up, in SMS, but I
want to screw up and lose all my existing data. I'm not familiar enoughmanager
with these setups to just start clicking and typing. In the storage
I can see the old Host Port Identifiers, so is it just a matter of addingbackend
the new Host Port Identifier as an option in storage manager? The
storage is a DS3500 So, my overall question is this, in order to regainin
access to the existing data in the new blade, do I just need to add the
Host Port Identifier to the mappings for the host?
I've tried to provide as much information as I can and ask the question
a way it makes sense. If I need to provide more information please letme
know. Because at this point I don't know what I don't know and don'twant
to muddy the water up by including too much impertinent information.list
Thanks in advance,
BJ
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.