×
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.
Hi
We have a production LPAR with two NICs on a P8. Our Development LPAR runs
on another P9 server. Both run off SANs which are in a Metro Mirror
relationship.
We want to implement a sort of reverse DR capability so that if we lose our
P9 and there is an urgent need to perform some development, we can spin up
the Dev LPAR On the P8
From a data point of view that is not an issue since the LUN the
development LPAR runs on is replicated in real-time to the P8. The issue is
network access.
The production server has two NICs in it and they are both dedicated to
production. We have no more spare slots to install another NIC. So it was
suggested we could use ethernet bridging as per this link
https://www.ibm.com/support/pages/ethernet-bridging-between-ibm-i-host-and-ibm-i-guest
That looks like a really good idea on the surface since we have two ports
on each NIC patched into the primary and secondary ports on the switches
and use ViP for resilience. So we could use a third port on one of the NICs
and use its line definition to create a virtual NIC on the development
LPAR. Given that the likelihood of our needing this LPAR is pretty low, it
seemed like a good solution.
Our network guy initially poured cold water on this idea since he said we
don't support layer 2 bridging. But that is on the external network side,
This seems to be an entirely IBMi internal solution that the external need
not know anything about except the port on the NIC we want to use is
patched into the switch and enabled.
Does this seem correct or have I missed some subtlety here?
Thanks
midrange.com
