No, the POR and IPLs were completed before the remote HMC was
installed....
-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of
Shelia Chalk
Sent: Monday, August 15, 2022 8:37 AM
To: [email protected]
Subject: Re: Remote HMC
[[ SEI WARNING *** This email was sent from an external source. Do not open
attachments or click on links from unknown or suspicious senders. *** ]]
After you made the changes on the HMC did you do a POR then IPL?
Thanks
Shelia Chalk
-----Original Message-----
From: IBM Mainframe Discussion List <[email protected]> On Behalf Of
Radoslaw Skorupka
Sent: Sunday, August 14, 2022 10:00 AM
To: [email protected]
Subject: Re: Remote HMC
Tony,
Assuming you really described all the picture (*) it may be an issue with
network rules based on MAC address - that's the only "network thing" you have
changed with HMC replacement.
(*) it is not honest/dishonest, it is about trust. I trust NO ONE, when
analysing IT problems. No one, including me. Nobody's perfect, it is possible
to miss some detail. :-)
--
Radoslaw Skorupka
Lodz, Poland
W dniu 13.08.2022 o 03:50, Cieri, Anthony pisze:
> Thanks for your reply.
> We do appear to have a "network" issue. It is strange because we copied
> the configs from the old machine are moved the cables from the old HMC to the
> new HMC. One interface work for remote access to the remote HMC. One the
> other interface, I can ping the remote gateway and the local HMC, but I
> cannot ping the SEs at the local site so the manual installation does not
> work.
>
> We certainly could (add do) use the remote access to the local HMC. We
> want to get the remote HMC working for our DR test.
>
> Thanks again.
> Tony
>
>
> -----Original Message-----
> From: IBM Mainframe Discussion List <[email protected]> On
> Behalf Of Radoslaw Skorupka
> Sent: Friday, August 12, 2022 5:53 PM
> To: [email protected]
> Subject: Re: Remote HMC
>
> [[ SEI WARNING *** This email was sent from an external source. Do not
> open attachments or click on links from unknown or suspicious senders.
> *** ]]
>
>
> Well, as far as I understood you have a problem with connectivity.
> 1. Check network connectivity, internal firewalls, rules, etc.
> 2. Use "manual object installation" - remote HMC will NOT discover your CPCs.
> You have to define it manually, it is not hard.
> 3. Domain security. Leave default or check it thoroughly.
>
> BTW: What do you need actually?
> I'm asking, because you wrote about remote HMC, but usually users need remote
> access to (local) HMC. I did use both and I have to admit the functionality
> available with remote HMC *but not with remote access* to the local HMC is
> rather rare. In other words: vast majority of features is available though
> remote access.
>
> Last, but not least: remote access to local HMC is much easier to set up.
>
> HTH
>
> --
> Radoslaw Skorupka
> Lodz, Poland
>
>
>
> W dniu 11.08.2022 o 17:57, Cieri, Anthony pisze:
>> Hi List,
>>
>> I have a new DR machine (BC15) that we have installed in Austin. The
>> machine is running and we tested out a DR scenario when we were there. At
>> that time , we did NOT have our remote HMC installed. A few week later we
>> are now installing our remote HMC and we are having an issue. The HMC do not
>> seem to talk to each other.
>>
>> We have used the same cables and copied the configurations from the
>> previous machines. Our remote HMC (Oaks, PA) cannot ping the SEs in Austin,
>> however the eth1 interface is up and running.
>>
>> Has anyone run into this situation??
>> Can you suggest any potential solutions??
>>
>> Thanks in advance
>> Tony
>>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
[email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
[email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
