If you had a LAN console working and started mucking around the Ops Console
values, you are pretty much hosed and will need to reconfigure from the
Panel.
LAN console uses a security feature where each QCONSOLE device is attached
to only one machine and that machine has a certificate that is erased when
changing parameters.
Search for Function 65+21 and Preparing for Lan Console, there is an entire
RedBook on the subject.

Best of luck


On Wed, Nov 27, 2013 at 5:00 PM, Steve Richter <stephenrichter@xxxxxxxxx>wrote:

I am using the operations console that comes with client access.

I am confused about the difference between the HMC ports and the LAN
ports of the system. The option 30 addresses are only for the HMC
ports? And the same with the "network configuration" info displayed in
ASMI?

Anyway, how does ops console work in regard to its IP address? How to
display the address the system is expecting to be used? And how to
change that address?

thanks,


On Wed, Nov 27, 2013 at 2:19 PM, Roberto José Etcheverry Romero
<yggdrasil.raiker@xxxxxxxxx> wrote:
Ops Console, you mean LAN console?
T5 (the usual adapter for said console) should NOT have a line
description
therefore it shouldn't be able to change it's IP address.
If by ETH0 you mean HMC0 then it might change but the ASMI will work with
the new address.
LAN console and ASMI are two separate things that work on two separate
adapters. LAN console settings are NOT DHCP capable, you set them once
and
they stay that way.
You've got 3 kinds of IP addresses:
IBM i's normal TCPIP stack (the kind you make with go TCPADM)
IBM i's LAN Console, which is configured from the DST menu or
sacrificing a
finger or two using the 65+21 functions of the front panel (when not
LPAR'ed)
ASMI/HMC Interface, which is the IP that the function 30 00 and 01 report
you, this one lies in the Flexible Service Processor and it either gives
you access to the ASMI or communicates to an HMC.

Could you clarify which port you are refering to?

Best Regards,

Roberto



On Wed, Nov 27, 2013 at 4:09 PM, Steve Richter <stephenrichter@xxxxxxxxx
wrote:

my ops console was working, connecting to a power 720 8202-e4b.. But
then I connected the ETH0 port of the system to the LAN. Which caused
ETH0 to have its IP address changed to 192.168.1.3 ( because the 720
is set to "type IP address" - dynamic )

Once the IP address of the system changed I changed the IP of the ops
console PC to 192.168.1.45 to be in the same sub net And I am changing
the OPS console IP address to be something in the 192.168.1 range.

In the OPS console config I set the host name and "server IP address".
Is this the host name and address of the 720 that you see in ASMI?
Trying different combinations and nothing is connecting.

Currently the PC is networked direct to the ETH0 port on the 720.

thanks,
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.