Gilson,
You need to look at GROUP to isolate LPARs, not ip ranges.
For example, I have one Z with 10 LPARS.
Every LPAR uses CUU addresses in the range 080-09F.
Every LPAR uses the same IP address for the consoles.
Every LPAR has either one or two unique GROUPS.
For example:
GROUP NAMES:
LPAR1CON (LPAR's primary console)
LPAR1 (normal VTAM terminal)
LPAR2CON (LPAR's primary console)
LPAR2 (normal VTAM terminal)
LPAR3CON (LPAR's primary console)
LPAR3 (normal VTAM terminal)
When you connect using a TN3270 terminal emulator, set the LUNAME to be
the same as the GROUP name.
As to your original question: You can have two IP addresses, but if they
are on different sub-nets, only the one that is on the same subnet as
the GATEWAY can be accessed from other sub-nets. So, if you had:
Port 1 IP = 192.168.1.10
Port 2 IP = 192.168.2.10
Gateway = 192.168.1.1
Then, you can only access port 2 if your pc was on 192.168.2.x/24. No
other sub-nets will be able to access it. But, any pc trying to reach
192.168.1.10 will be able to use the port even if on another sub-net.
(Assuming there is a valid route available.)
Tony Thigpen
Gilson Cesar de Oliveira wrote on 2/2/21 5:58 PM:
Dear Curtis:
My concern is related to isolate consoles for different lpars. All
the console clients that will connect to 192.168.10.100 should not connect
to 10.152.200.100 and vice-versa.
Are you saying that I can define the ports in different subnets but
the default gateway should be the same ??
I have the configuration in HCD and there is a panel where I can
configure the ports 0 and 1.
Am I wrong at this point ??
Regards,
Gilson
-----Mensagem original-----
De: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> Em nome de Pew,
Curtis G
Enviada em: terça-feira, 2 de fevereiro de 2021 17:06
Para: IBM-MAIN@LISTSERV.UA.EDU
Assunto: Re: OSA Express 7S 1000 base T as console
On Feb 2, 2021, at 12:32 PM, Gilson Cesar de Oliveira <gil...@gmail.com>
wrote:
For instance I have an OSA where in port 0 I will define it for
network 192.168.10.100/16
And for port 1 I will define it for network 10.152.200.100/16.
I've heard something that we can use it but in the same network.
You can do that, but only one of the ports will be accessible from other
subnets. The OSA-ICC definition only supports a single gateway. So, for
example, if you define the gateway with an address in the 192.168.10.100/16
subnet, any client that can route through that gateway, as well as other
hosts in that subnet, will be able to access the console through port 0, but
only hosts with addresses in the 10.152.200.100/16 subnet will be able to
access the console through port 1.
I hope my explanation makes sense.
--
Pew, Curtis G
curtis....@austin.utexas.edu
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email
to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
