×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I get that the host lpar will be up and I should count on that.
However, I thought that by using the virtual ethernet kind of stuff then
it would be a totally private network and I could have even the lpars who
are in our DMZ in on this. They're not all currently in the same subnet.
If our host, RACK2HST, is currently 10.10.6.181, and our guest, GDISYS2,
everyday IP address is 10.10.6.129 then I should abandon a separate vlan
and the whole 10.10.206.x range and use a number like 10.10.6.130 (if
available) on GDISYS2? And end up changing
Internet address . . . . . . 10.10.206.129
Gateway router address . . . 10.10.206.1
Subnet mask . . . . . . . . . 255.255.255.0
to
Internet address . . . . . . 10.10.6.130
Gateway router address . . . 10.10.6.1
Subnet mask . . . . . . . . . 255.255.254.0
*Note: we use subnet 255.255.254.0 for our regular lan traffic.
What happens when we want to do our dmz lpar? It's everyday IP address is
something like 208.xx.yy.zz, and runs in a different vlan. Do I give a
service tools IP address in the 10.10.6 range and vlan?
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
