Thank You for the reply. Our sysconfig is in fact down level: c-jsxxxx@pdlnx26m0001dl:~> rpm -qa | grep sysconfig
yast2-sysconfig-2.13.9-0.3 sysconfig-0.50.9-13.60.1 c-jsxxxx@pdlnx26m0001dl:~> cat /etc/SuSE-release SUSE Linux Enterprise Server 10 (s390x) VERSION = 10 PATCHLEVEL = 3 ---------------------------------------------------------------------------------------------------- Can you direct me to the known issue that was fixed in SLES10, I would like to review the problem text for more detail! Thanks Regards. John R. Stout From: Mark Post <[email protected]> To: [email protected] Date: 09/13/2011 02:27 PM Subject: Re: Fw: z/Linux MQ Guest hsi0 Config Problem Sent by: Linux on 390 Port <[email protected]> >>> On 9/13/2011 at 01:30 PM, John R Stout <[email protected]> wrote: > Several weeks ago the COPA account IPL'ed one of our z/VM LPARs(z/VM 5.4) > which hosts > many > z/Linux guests. One of the z/Linux guests(SLES 10 SP3), an MQ Server, > uses a Hipersocket interface to communicate with a z/OS LPAR on the same > CPU. At the > z/Linux boot > up, we had a failure where the virtual address DEDICATEd in the VM > directory to the > physical addresses associated with the HiperSocket IQD channel was not > available, or not > detected, to the z/Linux Network Configuration BOOT sequence. The HSI0 > interface did not > start and returned the following BOOT message: > > Setting up network interfaces: > lo > lo IP address: 127.0.0.1/8 > IP address: 127.0.0.2/8 > Checking for network time protocol daemon (NTPD): ..unused > lo > [1A..done > eth0 > eth0 configuration: qeth-bus-ccw-0.0.0900 > eth0 IP address: 10.26.6.141/25 > Checking for network time protocol daemon (NTPD): ..unused > eth0 > [1A..done > Waiting for mandatory devices: hsi-bus-ccw-0.0.7000 __NSC__ > 18 > 17 > 16 > 15 > 14 > 13 > 12 > 11 > 10 > 9 > 8 > 7 > 6 > 5 > 4 > 3 > 2 > 1 > 0 > hsi-bus-ccw-0.0.7000 No interface found > [1A..failedSetting up service > network . . . . . . . . . . . . . . . ...failed There was a problem that was fixed some time ago in SLES10. The version of the kernel your customer is running should contain it. It also required an update to the sysconfig package. If they have sysconfig-0.50.9-13.62.67.1 or later installed, then this is likely not the same problem. Mark Post ---------------------------------------------------------------------- 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 more information on Linux on System z, visit http://wiki.linuxvm.org/ ---------------------------------------------------------------------- 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 more information on Linux on System z, visit http://wiki.linuxvm.org/
