Re: OSA Express 7S 1000 base T as console
On Feb 2, 2021, at 12:32 PM, Gilson Cesar de Oliveira 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
Re: OSA Express 7S 1000 base T as console
W dniu 02.02.2021 o 19:32, Gilson Cesar de Oliveira pisze: Dear colleagues: I'd like to know if is it possible to use OSA Express 1000 Base T with the two ports (0 and 1) for console but in different sub-networks ? 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. No. Actually the second port usability in OSA-ICC is rather limited. In the past it was just disabled. Nowadays you can have both ports active, but not as you want - the addressing is not independent. In that case you would need two OSA cards. BTW: Two OSA cards means more session definitions and redundancy. -- Radoslaw Skorupka (looking for new job) Lodz, Poland -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
