Everyone,
We run Linux for system z appservers and DB2 under z/os database servers.
For our networks, the naming convention here is set up where TCPIP hostname = rdisp/mshost = DNSname = primary interface.
Right now our rdisp/mshost parameter in our appservers say George. The TCPIP hostname says George. The DNS entry for George resolves to 10,10,10,10 which happens to be our primary network interface attached to George.
Life is good. When we have secondary interfaces, we add an appropriate suffix to the dns entry and have it resolve to another address. For example, a gigabit fiber interface with large frames would resolve to 10.10.120.10.
Notice no routes. The only route is the default route.
But the time has come to change the network. The network folks are putting in some new hardware. And we want to move some of the traffic that goes to hostname George to a network with a suffix of t1. That is we would like to have the rdisp/mshost paramter say Georgt1, but still have the actual tcpip hostname called George. Is there anything inside of SAP that would prevent us from doing this?
Ron Foster
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.