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 <[email protected]> Em nome de Pew,
Curtis G
Enviada em: terça-feira, 2 de fevereiro de 2021 17:06
Para: [email protected]
Assunto: Re: OSA Express 7S 1000 base T as console
On Feb 2, 2021, at 12:32 PM, Gilson Cesar de Oliveira <[email protected]>
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
[email protected]
----------------------------------------------------------------------
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
