|
New RFE for this:
https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=153152
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 7310 Innovation Blvd, Suite 104
Ft. Wayne, IN 46818
Ship to: 7310 Innovation Blvd, Dock 9C
Ft. Wayne, IN 46818
http://www.dekko.com
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Rob
Berendt
Sent: Friday, November 12, 2021 8:40 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Automatically getting new Update Access Keys
There's supposed to be ways of automatically getting new Update Access
Keys for your Power systems in order to be able to apply firmware updates,
etc.
The problem I basically have is, to my belief, you still have to go to the
ESS site, My Entitled Hardware, Update Access Keys, Actions, Generate new
key.
Why in the sacred name of Elvis can't it just generate the new keys
automatically, like 30 days before expiration? What's the point of setting
up automatic updating on the HMC and/or standalone system, if you still
have to manually generate the new keys?
ESS site:
https://www.ibm.com/servers/eserver/ess/ProtectedServlet.wss
UAK links:
Management of POWER8 and Later Update Access Keys
https://www.ibm.com/support/pages/management-power8-and-later-update-access-keys
Order and Apply new UAK on Stand Alone IBM i or HMC-Managed POWER8 or
POWER9 servers.
https://www.ibm.com/support/pages/node/687987
Manage update access keys with IBM Electronic Service Agent (ESA) on IBM i
https://www.ibm.com/support/pages/node/635899
How To Automatically Update Access Key
https://www.ibm.com/support/pages/node/6238172
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 7310 Innovation Blvd, Suite 104
Ft. Wayne, IN 46818
Ship to: 7310 Innovation Blvd, Dock 9C
Ft. Wayne, IN 46818
http://www.dekko.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.
midrange.com
