On Sunday, 12/28/2008 at 02:18 EST, "Ian S. Worthington" <[email protected]> wrote: > Thanks to the help received here I'm making, (I think), good progress with > getting z/tpf under z/vm talking to the outside world. > > I've got the virtual nics and the guest lan defined, and according to the > traces the tcpip stack appears to correctly route incoming pings to the lan, > though there's no stack there yet to respond to them. > > I'm now enabling OSAE support on z/tpf and one of the mandatory parameters is > the osa port name: > > "PORT-osaport > specifies the name of the port on the OSA-Express card, where osaport is a > 3- to 8-character alphanumeric port name. The name of the port must be the > same for all hosts that have connections to the same OSA-Express card. Each > network port defined on a multiport OSA-Express adapter must have a unique > port name." > > I don't appear to be able to specify this on the DEFINE NIC or DEFINE LAN > commands. > > Anyone know where I specify this, or if it just defaults to some standard > name?
A virtual NIC = virtual OSA (or HiperSocket) port. In the same way a guest/host sets the port name in a real OSA, so the guest sets it on a virtual OSA. It is not set on DEFINE LAN or DEFINE NIC. If you want to see the value, CP QUERY NIC. (Just as you would use OSA/SF to see the value on a real OSA.) So, the only place the port name will appear is on ZOSAE DEFINE OSA and on CP QUERY NIC [DETAILS]. Remember that the guest is not sharing the virtual NIC, so it doesn't matter what name the guest uses. I see that PORT is optional on ZOSAE DEFINE OSA. Try leaving it off. Several years ago the OSAs were updated to no longer require a PORT name from the host. If the host doesn't set it, it doesn't have to match any previously set value. If the host DOES set it, then it must match. (The first host to activate the OSA port gets to set the port name.) z/OS still requires you to set the port name. z/VM and Linux do not. Alan Altmark z/VM Development IBM Endicott
