RE: Power 8 to Power 9 swap out -- MIDRANGE-L

Rob / Jim,

I'm currently planning a Power7 to Power9 -S914 (6 or 8 core) swap out, non-vios.

2 lpars

I was talking to some folks and some point came up.

1) Was told no need for DASD controllers, the P9 embedded will suffice with no issue.

I didn't confirm the cache specs, but I was thinking of possibly EJ14.

2) SSD - Currently using Enterprise, not sure if I should switch to Mainstream.

Possibly utilizing the P7 Enterprise SSD, place in ASP2 for R&D only.

Still researching.

Size is also up in the air 775gb, 1.9tb, etc.

Any IBM Mainstream devices (previously called read intensive device) identified in

this document have a maximum number of write cycles. IBM Mainstream device

failures will be replaced during standard warranty and maintenance period for

devices that have not reached the maximum number of write cycles. Devices that

reach this limit may fail to operate according to specifications and must be replaced

at the client's expense. Individual service life may vary and can be monitored using

an operating system command.

3) Ethernet - stay at 1gb or possibly utilize the 10gb.

From a network side the 10gb could get expensive.

4) Fiber for LTO7 - upgrade from 8gb to 16gb.

Will require a new fiber switch.

5) I hosting I.

I'm considering having Production own all the DSAD, then have Production host the R&D LPAR with NWS.

My only concern is if both Production and R&D are super busy, will DADS substystem, (controllers and SSD) become a bottleneck.

6) CPU - currently have 3 cores, I was told 2 would be plenty on P9.

I can't go with the 4 core, 64gb mem max.

So 6 or 8 core.

Still researching.

7) Memory - currently at 256, I'm going to double to 512, at a minimum.

8) HA/DR - currently none - I was asked to investigate.

9) Live Partition Mobility - checking on how this may help.
With Live Partition Mobility, users can migrate an AIX or IBM i partition running on
one POWER partition system to another POWER system without disrupting services.
The migration transfers the entire system environment, including processor state,
memory, attached virtual devices, and connected users. It provides continuous
operating system and application availability during planned partition outages for

repair of hardware and firmware faults.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Oberholtzer
Sent: Friday, March 16, 2018 3:08 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Power 8 to Power 9 swap out

The how do you do VIOS without a SAN is really easy. Don't. Get a SAN.

If you want to use VIOS to virtualize Ethernet and Tape, go for it, however it's not really meant for IBM i production I/O loads with internal storage.

VIOS will require a dedicated DASD controller to build. It cannot be run as a client.

With a SAN migration to the new environment is really simple.

Configure SAN/VIOS/Fibre Network to support partitions (medium difficulty) Add new DASD units from SAN to partitions (basic knowledge) Leave one drive non-configured (it will be your new load source) Start removing old DASD units (easy and while system is running and live) Migrate Load source (that requires downtime to copy the load source drive) Done.

That would eliminate all the i hosting i and the I/O performance is significantly better (assuming a properly sized SAN)

This is coming from a guy that swore to never go to external storage only a

few short years ago.

--

Jim Oberholtzer

Agile Technology Architects

-----Original Message-----

From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob Berendt

Sent: Friday, March 16, 2018 1:56 PM

To: midrange-l@xxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxx>

Subject: Power 8 to Power 9 swap out

Think 3 different Power 8's being upgraded to Power 9's.

Somewhat similar configurations.

- Two lpars of VIOS on each redundantly serving up DVD, fiber tape, Ethernet.

- Each VIOS lpar has their own CEC mirrored pair of disk drives.

- Hosting lpar of IBM i on each

- Four guest lpars of IBM i on each

- lpar of AIX on 2 of the 3.

We may move all disk back to the system ASP. Currently each rack has a system ASP and one secondary ASP. No iASPs. No SAN (except VTL tape).

I'm wondering how you do the VIOS. I've already forgotten the Power 6 to Power 8 migration. I don't think we used VIOS on Power 6. That's right, we had separate ethernet and fc for each lpar.

Is there some sort of magic "dump the vios config to script" or some such thing?

Also, the sysplan migration?

We're thinking save, rip, replace, etc. We weren't thinking put the New Power 9 into the rack and just move cables later after getting vios ready.

Maybe stupidity on my part but it would ugly my rack config. Then again, I could always move it again... Hmm... Get the power 9 fired up. Get VIOS configed on it. Power it off. Remove from rack, then replace later...

Rob Berendt

--

IBM Certified System Administrator - IBM i 6.1 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

--

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx> To subscribe, unsubscribe, or change list options,

visit: https://lists.midrange.com/mailman/listinfo/midrange-l

or email: MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxx> Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link:

http://amzn.to/2dEadiD

--

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxx> To subscribe, unsubscribe, or change list options,

visit: https://lists.midrange.com/mailman/listinfo/midrange-l

or email: MIDRANGE-L-request@xxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxx> Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx<mailto:support@xxxxxxxxxxxx> for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD