how bout unique host names or FQDN that points to the HiperSocket address? something like:
zos1.hiper.blah.foo.bar.biz -> 172.16.1.1 zos1.blah.foo.bar.biz -> real OSPF virtual IP that the rest of the world sees Hipersockets would be an island network with their DNS services provided by your current DNS infrastructure, but isolated into their own zone. Then you don't have to hardcode IP addresses on your TSM clients which makes it a little more flexibile than simply sticking the z/OS hipersocket IP address in for the tsm server address. Or you can add the Hipersocket interfaces to the existing OSPF config so that it becomes a valid path, and make sure the hsi device has a lower cost than any eth. This has the effect of using the hipersocket for all internal CEC traffic through, not just the TSM traffic. -- Jay Brenneman ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
