Bob
Yes, realized that afterwards. Saw NWSD and started to cringe. Those IXS cards were great while they lasted, particularly windows domain synchronization.
thanks
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> On Behalf Of Rob Berendt
Sent: Wednesday, December 19, 2018 11:08 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: NWSD and NWSSTG recommendations
Tom,
I think you jumped in the middle of something.
He is talking about using NWSD to run IBM i hosted by IBM i.
It's been around for a decade (at least since 6.1).
It works quite well for IBM i hosting IBM i. We also use it for a massive partition of AIX hosted by IBM i.
When you use the hosting method for hosting IBM i, AIX and Linux you do not require any special card or connection like you did for hosting Windows.
NWSD is not just for hosting Windows.
ps: I used to have 9 IXS cards in one server.
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
From: "Tom Hambel" <thambel@xxxxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Date: 12/19/2018 10:55 AM
Subject: RE: NWSD and NWSSTG recommendations
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
What type of NWSD? Do you realize as of V7R3, windows isn't supported on
these by IBM?
We used these extensively since the days of the FSIOP and it was great
back then.
But the Iscsi solutions via diskless Xseries servers was horrible with a
capital H.
We have since migrated to 2 standalone physical Dell servers running core
Hyper-V only (no gui, less overhead), with all windows servers virtualized
and replicated between them.
It is pure heaven compare with Iscsi and NWSD. Servers boot in literally
seconds, have redundant replicas, etc.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> On Behalf Of Kevin
Bucknum
Sent: Wednesday, December 19, 2018 10:47 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: NWSD and NWSSTG recommendations
No vios this time. When we built the old system 9 years ago the thought
was to bring some linux workload on board. That is all hosted on AWS now,
so just two IBM i partitions. Production and development. Only two people
use development, so it is small. New system as it stands now is 18 283
drives in the CEC. 2 hot spares and Raid 5. So 4245 gigs of drive (up from
1702 before). I want to just carve out about 500 gigs for development
(current 283) and run it IBM i hosting IBM i.
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim
Oberholtzer
Sent: Wednesday, December 19, 2018 9:32 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: NWSD and NWSSTG recommendations
Kevin:
Are you keeping VIOS and using ViSCSI support or going completely to IBM i
hosting IBM i?
IBM i cannot host anything if it is virtualized as well.
IF VIOS then the rules are very different than IBM i as a hosting
environment. Frankly VIOS is awful at iSCSI virtualization so if that's
all that VIOS is doing I would far prefer an IBM i host. (IBM i can host
IBM i , Linux, and AIX)
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> On Behalf Of Kevin
Bucknum
Sent: Wednesday, December 19, 2018 9:08 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: NWSD and NWSSTG recommendations
Is there a guide somewhere on setting this up? And maybe a best practices?
We are working on getting our next box now. Our dev partition which is 2
mirrored 283 gig drives hosted on vios (and slow as hell!) is going to
become about 500 gigs in an i on i situation. I'd like to optimize that
disk speed, as that is the only really bad thing about that partition now.
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim
Oberholtzer
Sent: Wednesday, December 19, 2018 8:53 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: NWSD and NWSSTG recommendations
200GB drives in the quantity you are proposing should work well.
The limits on the number of NWSSTG units a NWSD instance would support was
16 and was raised later, I'm not sure what the limit is now, but I've
always found performance is best when we put no more than 12-13 drives per
NWSD instance. It also gives you the ability to add drives later and
spread them out vs. putting all the new drives in one place.
Watch memory in the machine pool and *BASE, carefully. That's where quite
a bit of this virtualization is done, you'll be surprised at how much
memory it takes. Don't short it.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> On Behalf Of Steinmetz,
Paul
Sent: Wednesday, December 19, 2018 8:38 AM
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxx>
Subject: NWSD and NWSSTG recommendations
New P9, 9009-42A, V7R3.
I will be virtualizing about 20 TB of SSD to client R&D LPAR.
The entire R&D LPAR will virtualized.
My plan was 10 NWSD each consisting of 5 200gb NWSSTG.
This would give me 50 arms, each about 200gb each, one would be the load
source.
Some rules and guidelines from previous posts.
More arms the better.
For performance - at least 6 NWSSTG per system, max 16 (32?) NWSSTG per
NWSD Consistently sized and at least 70GB ??
Goal is for optimal performance on both the host and the client LPARs.
1) Does anyone have any history on the optimal number of NWSD?
2) Can too many NWSD cause a performance issue.
Also, I will be repeating this process for 2 additional sandbox LPARS,
each about 5 TB.
When complete, host LPAR will have about 20 NWSD.
Any thoughts from the group?
Thank You
_____
Paul Steinmetz
IBM i Systems Administrator
Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071
610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home
psteinmetz@xxxxxxxxxx
http://www.pencor.com/
--
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:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: 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 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@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: 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 for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link:
https://amazon.midrange.com
[
https://www.medtronsoftware.com/img/MedtronMinilogo.bmp] Kevin Bucknum
Senior Programmer Analyst
MEDDATA / MEDTRON
120 Innwood Drive
Covington LA 70433
Local: 985-893-2550
Toll Free: 877-893-2550
https://www.medtronsoftware.com
CONFIDENTIALITY NOTICE
This document and any accompanying this email transmission contain
confidential information, belonging to the sender that is legally
privileged. This information is intended only for the use of the
individual or entity named above. The authorized recipient of this
information is prohibited from disclosing this information to any other
party and is required to destroy the information after its stated need has
been fulfilled. If you are not the intended recipient, or the employee of
agent responsible to deliver it to the intended recipient, you are hereby
notified that any disclosure, copying, distribution or action taken in
reliance on the contents of these documents is STRICTLY PROHIBITED. If
you have received this email in error, please notify the sender
immediately to arrange for return or destruction of these documents.
--
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:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: 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 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@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: 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 for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link:
https://amazon.midrange.com
[
https://www.medtronsoftware.com/img/MedtronMinilogo.bmp] Kevin Bucknum
Senior Programmer Analyst
MEDDATA / MEDTRON
120 Innwood Drive
Covington LA 70433
Local: 985-893-2550
Toll Free: 877-893-2550
https://www.medtronsoftware.com
CONFIDENTIALITY NOTICE
This document and any accompanying this email transmission contain
confidential information, belonging to the sender that is legally
privileged. This information is intended only for the use of the
individual or entity named above. The authorized recipient of this
information is prohibited from disclosing this information to any other
party and is required to destroy the information after its stated need has
been fulfilled. If you are not the intended recipient, or the employee of
agent responsible to deliver it to the intended recipient, you are hereby
notified that any disclosure, copying, distribution or action taken in
reliance on the contents of these documents is STRICTLY PROHIBITED. If
you have received this email in error, please notify the sender
immediately to arrange for return or destruction of these documents.
--
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:
https://lists.midrange.com/mailman/listinfo/midrange-l
or email: 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 for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link:
https://amazon.midrange.com
midrange.com
