Re: recovering DST password *RESOLVED* -- MIDRANGE-L

At the end of the day here is what happened:

After trying to resolve this over the phone and remotely we went on site.

This is where you learn specifically what actually happened and can add visuals to the pot.

There had been and AC failure but the system was IPLed so that should have cleared any errors and started the system.

However, the ethernet line was down likely because the cable had been changed to a different switch.

IBM I doesn't like that so the line was "failed". (unlike a PC where the line will recover)

Still, however, we couldn't get the console to come up because we didn't know the DST password and couldn't know system status

Turns out this machine was generic out-of the-box and luckily the DST QSECOFR pw was QSECOFR.

But the password is case sensitive so you have to press the shift key to get upper case (nuance).

I like this part:

Once we got in to console and a signon display the customer put in creds and pressed enter.

Nothing happened.

HaHa. Trick #8: Keyboard was set to IBM 5250 so bottom right ctrl key was the "enter" key.

Immediately pressed the 5250 ENTER and, voila, we were in.

Much relief all around.

We reset passwords, added redundancy, etc. and will do a system evaluation to see where they are and what needs to happen.

No SWMA, no hardware maintenance contract, back level OS and PTFs.

Thanks for everyone's help on this one.

Last note is that it appears that if you don't know a DST password you can't get into a down system.

It appears that a SLIP install of the LIC might work. Anyone actually done that?

Regards,

Jerry

On 3/16/2023 3:53 PM, Jim Oberholtzer wrote:

The situation is not clear, maybe because he can’t elaborate on it.
Bottom line is, it’s not that bad, and it can be overcome, or it’s really bad and a complete recovery is needed, hopefully not.

It sounds like the the partition comm line is not going active for some reason, so they can’t get in with a normal 5250 session. An IPL should clear that, unless they have a card failure, or there is something in the network that prevents communications, we all know network guys never cause issues, (duck/run) so the diagnosis is a bit difficult at this point.
After re-reading your post you did indeed recommend the bypass.

Jim Oberholtzer
Agile Technology Architects

On Mar 16, 2023, at 5:33 PM, Evan Harris<auctionitis@xxxxxxxxx> wrote:

Hi Jim

yeah that's what I thought I said. Just trying to get a fix on exactly what
Jerry's situation is.

On Fri, Mar 17, 2023 at 11:20 AM Jim Oberholtzer <
midrangel@xxxxxxxxxxxxxxxxx> wrote:

That message to reset is referring to the console, not the system, so I
would bypass it.

Jim Oberholtzer
Agile Technology Architects

On Mar 16, 2023, at 4:37 PM, Evan Harris<auctionitis@xxxxxxxxx> wrote:

Hi Jerry

is there an option at the bottom of the screen to bypass SST ? If so take
the command key (F18 ?) to do that.

It might talk about resetting power or whatever but that relates to
resetting the console not the system.

On Fri, Mar 17, 2023 at 9:45 AM James H. H. Lampert via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

On 3/16/23 1:10 PM, Jerry Draper wrote:
System front panel shows normal: 01 B N
so you would think the system is up and operational but not so.
Usual interface is at 10.10.10.202: customer reports no access
Console is at 10.10.10.2: pings-yes; using ACS we get SST signon

prompt

but user doesn't know valid SST profile/password
LAN console
can't get into DST via front panel 21 since user doesn't know valid SST
profile/password
No SRCs on system LCD panel
Tried multiple IPLs.

That might require somebody from IBM to make a house call. And this
sounds like a reason why there should be at least two different users
with DST passwords, *and* a DST account and password in a sealed
envelope in a secure location.

--
JHHL

--
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
athttps://archive.midrange.com/midrange-l.

Please contactsupport@xxxxxxxxxxxxxxxxxxxx for any subscription

related

questions.

--

Regards
Evan Harris
--
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
athttps://archive.midrange.com/midrange-l.

Please contactsupport@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
athttps://archive.midrange.com/midrange-l.

Please contactsupport@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

--

Regards
Evan Harris
--
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
athttps://archive.midrange.com/midrange-l.

Please contactsupport@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.