Re: vHMC web/network access WAS: vHMC desktop size

[Gerald Magnuson <gmagqcy.midrange@xxxxxxxxx>]

AAAA,  found it,   I had consoles excluded in my ACSCONFIG.PROPERTIES file

On Fri, Jan 7, 2022 at 9:07 AM Gerald Magnuson <gmagqcy.midrange@xxxxxxxxx>
wrote:

> > > > Now go back to the iACS main stuff.  Right under Welcome make sure
> your system name is there.  Under Console select 5250 console.  There's
> your system console session.
> I don't see the "Under Console select 5250 console".
>
> On Fri, Jan 7, 2022 at 6:43 AM Rob Berendt <rob@xxxxxxxxx> wrote:
>
> > Pete,
> > I went to our VMcenter.  From there I launched a remote console session
> > to our vHMC.
> > Console Management, Console settings, Change Network Settings, LAN
> > Adapters tab.  I have four entries
> > Eth0 ... 0.0.0.0
> > Eth1 ... 192.xxx.xxx.1
> > Eth2 ... 192.xxx.xxx.24
> > Eth3 ... 10.10.6.97
> > We do not use the 192 settings.  Those are probably there from initial
> > setup.  Our Power systems are in the 10. network.
> > Check your Name Services tab and see that you have DNS setup.  We have
> > both boxes checked and four DNS entries.  We also have two suffix search
> > orders entered.  We may be transitioning domains.
> > Now click on Test Network connectivity.  Enter in your PC name, with the
> > domain name (if you do not have that domain in the search list).  In my
> > case I had to enter GDL83.dekko-1.  Did I mention we are transitioning
> > domains?
> >
> > Now on your PC try this:
> > Nslookup 10.10.6.97
> > This should return your hmc name.  If it doesn't slap yourself silly
> > (since you're the network guy) until you go fix your DNS and enter your HMC
> > in there.
> > Now you should be able to get to https://hmcussi.corp.dekko.com
> >
> > Now open iACS.  Not an emulator session!  But the full enchilada with the
> > General, Database, Console and Management sections.  Under Management,
> > System Configurations.  Find your system in there and click Edit.  Under
> > the console tab select HMC, then enter in your host name / ip address for
> > your hmc.  I use names and not IP addresses.  Our network guy has studied
> > under Catbert and loves to play games with us by renumbering stuff on a
> > periodic basis.  If you click the Verify Connection tab you will see that
> > it uses ports 2300 and 2301.
> > Now go back to the iACS main stuff.  Right under Welcome make sure your
> > system name is there.  Under Console select 5250 console.  There's your
> > system console session.  "Hardware Management Interface 1" is your ASM or
> > Advanced Systems Management.  There are those who feel that it's ok to have
> > your payroll data, engineering drawings, missile launch codes, etc on your
> > corporate network but heaven forbid you should put your ASM or HMC
> > interfaces to your power systems on your corporate network.  I fail to
> > understand that.
> >
> > Normally the only time I use Vcenter to get to the vHMC is for upgrades
> > and to start the shared system console sessions.
> >
> > 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
> > Pete Helgren
> > Sent: Thursday, January 6, 2022 6:05 PM
> > To: midrange-l@xxxxxxxxxxxxxxxxxx
> > Subject: Re: vHMC web/network access WAS: vHMC desktop size
> >
> > CAUTION: This email originated from outside of the organization. Do not
> > click links or open attachments unless you recognize the sender and know
> > the content is safe.
> >
> >
> > Patrik,
> >
> > *I* am the "network guys" you refer to.  I didn't realize that the HMC
> > was delivering the web interface on port 2300.  Also, this is a straight
> > up, VMWare workstation installed on Windows 10. Based on what I see in
> > the network settings for the VMWare Guest (vHMC) it's on a
> > 192.168.47.1/24 network.  The attributes of the vHMC network connection
> > show that the IP is 192.168.47.129.  It has a default gateway of
> > 192.168.47.2
> >
> > The Network Connection setting show it's on a Custom: Specific virtual
> > network (VMnet8 (NAT))  Frankly, I can't remember why some of these
> > options were chosen or whether I should change them.
> >
> > Perhaps someone who has a vHMV running on VMWare workstation on Windows
> > 10 could take a look at their network settings and see how they compare
> > (if they can access the vHMC web interface from the host PC).
> >
> > Pete Helgren
> > www.petesworkshop.com
> >
> > On 1/5/2022 5:42 PM, Patrik Schindler wrote:
> >
> > > Hello Pete,
> > >
> > > Am 05.01.2022 um 23:03 schrieb Pete Helgren <pete@xxxxxxxxxx>:
> > >
> > > > Hmmm...what IP would that be?
> > > Check with your network guys.
> > >
> > > > VMWare has it's own virtual network that the vHMC is on. Closest I can
> > find on the vHMC is looking at Console Settings and then viewing the
> > network topology.  It has an address of 192.168.47.129.  Local IP on laptop
> > hosting the VMWare Workstation is 192.168.1.114  and I don't see a route to
> > the vHMC IP running in VMWare...
> > > If you're lucky, it will be handled by the default gateway entries. Try
> > to ping from the workstation to the HMC. If that works: Congrats. If you
> > can't connect via Browser or on port 2300 => Firewall in between.
> > > > Perhaps the config needs a tweak.....?
> > > Most likely no. Without knowledge of the local network topology
> > involved at large, almost everything is like trying to shoot into the dark.
> > > :wq! PoC
> > --
> > 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