Hi Everyone,
Well, I made it to:
*** login using 'ssh -X [EMAIL PROTECTED]' ***
*** run 'yast' to start the installation ***
Am I suppose to disconnect from client and then ssh to it and enter
YAST; or, do I enter YAST from here?
Thanks,
Alyce
-----Original Message-----
From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On
Behalf Of Rich Smrcina
Sent: Monday, September 29, 2008 5:09 PM
To: [email protected]
Subject: Re: SLES10 Client
Yes.
This is your (as in this virtual machine's) IP Address.
--
Rich Smrcina
VM Assist, Inc.
Phone: 414-491-6001
Ans Service: 360-715-2467
rich.smrcina at vmassist.com
http://www.linkedin.com/in/richsmrcina
Catch the WAVV! http://www.wavv.org
WAVV 2009 - Orlando, FL - May 15-19, 2009
Austin, Alyce (CIV) wrote:
> Hello...
>
> I have good news: after leaving out the portname, I was able to get
> further with my install: However, I'm not sure what IPADDR it wants
> below:
>
> Device address for data channel>
> 0.0.0342
>
> Portname to use>
>
>
> Enable OSI Layer 2 support?
>
> 1) Yes
> 2) No
>
> 2
> qeth: Device 0.0.0340/0.0.0341/0.0.0342 is a OSD Express card (level:
> 035f)
> with link type OSD_1000 (portname: )
> qeth: Hardware IP fragmentation not supported on eth0
> qeth: VLAN enabled
> qeth: Multicast enabled
> qeth: IPV6 enabled
> qeth: Broadcast enabled
> qeth: Could not set up broadcast echo filtering on eth0: 0xe00d
> qeth: Using SW checksumming on eth0.
>
> qeth: Outbound TSO not supported on eth0
>
> Automatic configuration via DHCP?
>
> 1) Yes
> 2) No
>
> 2
> Use a HTTP proxy?
>
> 2) No
>
> 2
>
>
> Enter your IP address>
>
> (Should this be a new IPADDR for the client?)
>
>
> Thanks,
> Alyce
>
>
>
>
> -----Original Message-----
> From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED]
On
> Behalf Of Mark Post
> Sent: Monday, September 29, 2008 2:56 PM
> To: [email protected]
> Subject: Re: SLES10 Client
>
>>>> On 9/29/2008 at 2:47 PM, in message
> <[EMAIL PROTECTED]>,
"Austin,
> Alyce
> (CIV)" <[EMAIL PROTECTED]> wrote:
>> I initially said "no" to layer 2 and eventually is ask me again if I
>> want to enable layer 2....
>
> Unfortunately (or perhaps by design), the installer retries the dialog
> if it cannot activate the NIC. So, something is preventing the system
> from activating the NIC. It may very well be that the OSA is in layer
2
> mode, talking to a physical switch in layer 2 mode. If it is, then
you
> will need to specify layer 2 mode to the installer dialog, and come up
> with an appropriate MAC address for the NIC. If you're still
ATTACHing
> real devices to your guest, I suppose the MAC would be whatever the
real
> OSA reports for that value.
>
> If your OSA and switch are not in layer 2 mode, then something else is
> wrong. I saw that you're specifying a port name for the NIC. Unless
> someone else is already sharing that OSA and specifying a port name,
> don't do that. The usual recommendation also, is to use all upper
case
> letters for the port name, because that's all that z/OS can specify.
If
> you're trying to share the card with a z/OS system, and you specify a
> lower case (or mixed case) port name, you'll prevent the z/OS system
> from activating its NIC. In general, most people recommend that you
> never use port names at all. It's not really needed, and can lead to
a
> lot of head scratching.
>
>
> Mark Post
>
