Re: EOS for SWMA Storwize V5010

Yes and I addressed the point:
If by some reason you need a new firmware to use a new card, which isn't
really something that happens, then you are still not going to get any
benefit from having SWMA because the machine is NOT capable of going up in
releases and new features are supported in new branches and not point
releases. A point release for a branch as far back as Justin's 8.2.1.x will
only fix and not enhance the code.

The IBM i External Storage Support Matrix only asks for 7.5 SAN code and up
when mentioning code, so it is a moot point since there's nothing from the
SAN side limiting when you can use it (it has a lot more limitations IBM
i-wise) and if new limitations come up they will be for the current or
future code levels like 8.6+ which aren't supported on that machine anyways.


On Sat, 14 Oct 2023 at 13:46, Rob Berendt <robertowenberendt@xxxxxxxxx>
wrote:

Do you realize I was mainly concerned about new cards, etc in the Power
system? Like perhaps a new FC adapter which may require that the SAN be on
a certain firmware level?

On Fri, Oct 13, 2023 at 6:58 PM Roberto José Etcheverry Romero <
yggdrasil.raiker@xxxxxxxxx> wrote:

As somebody who supports this boxes I can tell you that:
Do you ever plan on putting any fixes on the production machine? - Once

you

are at the last servicing level, a point fix is not something that will
halt production, I've seen very few point fixes being released after the
branch stops being developed it's a bit akin to expecting fixes for v5r4
(it is THAT far from the current branch, it gets fixes only because the
machines are still supported)
Do you ever plan on putting on any OS upgrades on the production

machine? -

You don't care, OS support is baked into the OS for IBM i, included in

the

latest versions of Windows Server and free to download SDDDSM for the

older

versions, and the level required on the box is either compatible or you
can't upgrade to that one because it will most likely not require

8.2.1.17

when you got up to 8.2.1.16
Do you ever plan on putting in any new cards on the production machine? -
The prod machine doesn't care about the storage and the storage won't get
new cards this late in life
Do you ever plan on putting any hardware upgrades on the production
machine? - Idem and disks can be added without issue because you are at

the

last possible branch
If hardware gives you a new card to fix the storwise but it's downlevel

and

there are issues will you be able to get the uplevel code? - Flashsystem
controllers either flash themselves from the working pair or you can go
into the /service tab and force it (and it is a good practice to have a
backup of the currently running levels saved somewhere)
If IBM issues a CVE saying that the Storwise is susceptible to some hack

do

you give a rip? - This is the only real worry and it can be solved by air
gapping/ACL'ing the admin interfaces if needed (nobody does this, I know)
but most security issues haven't been about allowing somebody access to
delete data.

Now, as a BP (but not in the US geo, so I've no horse in this race) I

would

recommend what I already did, if you can save a bit by forgoing the SWMA
and use that towards a new box and you understand the risks? do it. Don't
run production without HWMA, but it's not like dropping SWMA on the i

which

is a bigger issue.

Roberto


On Wed, 11 Oct 2023 at 14:17, Rob Berendt <robertowenberendt@xxxxxxxxx>
wrote:

Do you ever plan on putting any fixes on the production machine?
Do you ever plan on putting on any OS upgrades on the production

machine?

Do you ever plan on putting in any new cards on the production machine?
Do you ever plan on putting any hardware upgrades on the production
machine?
If hardware gives you a new card to fix the storwise but it's downlevel

and

there are issues will you be able to get the uplevel code?
If IBM issues a CVE saying that the Storwise is susceptible to some

hack

do

you give a rip?
Have I cast enough FUD?

--
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.

--
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.

--
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.