On Tuesday, 04/04/2006, Chuckie wrote: > Also, in z/VM 5.1 (or was it 5.2? I forget...) we initialize the backup > OSAs when you activate the VSWITCH and will detect the "unplug" event on > the backups and issue messages. In earlier releases we didn't initialize > or watch the backup OSAs unless the primary failed.
After a all-too-brief absence, Chuckie has returned from wherever it is he hides. <THUMP> OW! He *obviously* has been posting again as the above ruminations contain assertions which have a negative correlation with the nominal operating parameters of said functi--- CUT IT OUT, CHUCKIE!! GIMME THAT KEYBOARD! NOW. Ahem... or to put it another way, it's wrong. :-) The backup OSAs are not monitored. As an alternative, I would suggest using a "private" VSWITCH that has a *primary* OSA on the same chpid as the *backup* OSA on your "public" VSWITCH. That will cause the VSWITCH to monitor the "backup" and issue messages if the cable is pulled or the port is disabled. This technique requires one "private" VSWITCH per backup OSA. Or you could, as David K. suggested, use a TCP/IP stack (with no running apps) connected to those alternate subchannels. Then you could monitor all backup OSAs from a single guest. Use IP addresses that are specifically NOT in the subnet range for the LAN. We will be examinig this issue to see if there's something we can do in a future release to address the issue. [Will someone PLEASE call a Dr? There is an imprint of TAB Q W E R on the back of my head...] Alan Altmark z/VM Development IBM Endicott ---------------------------------------------------------------------- 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
