The guests are on the same LPAR but we do have the Hipersocket connected to a third vse machine in another LPAR and that connection is functioning. The addresses for the failing hipersocket are F509 F50A & F50B.
Ken Libutti CNE, CNI, SCSA, RHCT Asst. Director of Systems Services Broward Community College 225 E. Las Olas Blvd. 31/330 Ft. Lauderdale, Fl 33301 Phone: 954-201-7361 Fax: 954-201-7053 [EMAIL PROTECTED] Please Note: Due to Florida's very broad public records law, most written communications to or from College employees regarding College business are public records, available to the public and media upon request. Therefore, this email communication may be subject to public disclosure. >>> [EMAIL PROTECTED] 3/29/2006 5:36 PM >>> Also you describe hipersockets between two guests. Are these guests on the same LPAR? Is the hipersocket being used by different LPARs? David Kenneth Libutti wrote: >We have a Hipersocket defined between two guests. It has stopped >working on one of the guests. I have deleted the configuration and >recreated it and ran mkinitrd. We have also rebooted the guest. Below >is the config file for the failing interface: > >BOOTPROTO='static' >BROADCAST='10.14.1.255' >IPADDR='10.14.1.4' >MTU='' >NETMASK='255.255.255.0' >NETWORK='10.14.1.0' >REMOTE_IPADDR='' >STARTMODE='onboot' >UNIQUE='baQy.awRbBiMDygF' >_nm_name='hsi-bus-ccw-0.0.f509' > >This is the config file for the working interface: > >BOOTPROTO='static' >BROADCAST='10.14.1.255' >IPADDR='10.14.1.3' >MTU='' >NETMASK='255.255.255.0' >NETWORK='10.14.1.0' >REMOTE_IPADDR='' >STARTMODE='onboot' >UNIQUE='+mkK.awRbBiMDygF' >_nm_name='hsi-bus-ccw-0.0.f506' > >In vm the F5xx devices are all still attached to the guest machines. > >Any help would be appreciated. > >Ken Libutti CNE, CNI, SCSA, RHCT >Asst. Director of Systems Services >Broward Community College >225 E. Las Olas Blvd. 31/330 >Ft. Lauderdale, Fl 33301 >Phone: 954-201-7361 >Fax: 954-201-7053 >[EMAIL PROTECTED] > >Please Note: Due to Florida's very broad public records law, most >written >communications to or from College employees regarding College business >are public records, available to the public and media upon request. >Therefore, this email communication may be subject to public >disclosure. > > >---------------------------------------------------------------------- >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 > > > > > ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
