Re: SLES10 Client
Hello again. Well, I tried both the starter system default password and the new password I changed it to to logon on as root for the full-service starter system from my SSH client and neither one works. Also, when I logo as root, it does asks for a password. Is there a different default password for root for the full-service server? Thanks, Alyce From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Scott Rohling Sent: Tuesday, September 30, 2008 3:18 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client Don't be afraid -- you're not going to break anything... And besides - we're here if you do :-) Best of luck - Scott On Tue, Sep 30, 2008 at 4:02 PM, Austin, Alyce (CIV) [EMAIL PROTECTED] wrote: I was afraid I might get locked out -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mike Walter Sent: Tuesday, September 30, 2008 2:54 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client Why not just try the default NOVSTART root password and find out for yourself? If it works (which it should) you have your answer. But if you followed the instructions, you changed your NOVSTART root password immediately. So try that one, if the default fails. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Austin, Alyce (CIV) [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 09/30/2008 04:33 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: SLES10 Client OK...i was able to ssh to my new client. Is the default root password the same as it was for the starter system? Thanks, Alyce -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mike Walter Sent: Tuesday, September 30, 2008 2:20 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client As long as you left it RUNNING in the bottom right hand corner of the screen, having issued at some point since logon, (perhaps in the PROFILE EXEC), you should be good to SSH in right away. Also, see SHARE session Installing a Novell SLES 10 Starter System without a Net(work) at: http://linuxvm.org/Present/SHARE111/S9287mw.pdf some parts may have helped you, and still may. You're right at the end of the session. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Austin, Alyce (CIV) [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 09/30/2008 04:01 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: SLES10 Client OOPs...I already disonnected from Client Do I need to start the process again before SSH'g? Thanks, Alyce -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Tuesday, September 30, 2008 1:33 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client On 9/30/2008 at 4:20 PM, in message [EMAIL PROTECTED], Austin, Alyce (CIV) [EMAIL PROTECTED] wrote: 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? Neither. Leave your TN3270 session as it is, since you'll need it later. From your desktop, SSH to the IP address shown in the message, then issue the yast command. Mark Post The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please
Re: SLES10 Client
On 10/2/2008 at 2:04 PM, in message [EMAIL PROTECTED], Austin, Alyce (CIV) [EMAIL PROTECTED] wrote: Well, I tried both the starter system default password and the new password I changed it to to logon on as root for the full-service starter system from my SSH client and neither one works. I need some clarification here. Are you trying to SSH to a Linux system that you are in the process of installing? If so, there is no default password. During the setup process before you SSH in, you are asked for a temporary root password to be used. That is the password you need to use when you SSH in to enter the yast command. The prompt is right after you select the display type. Select the display type. 1) X11 2) VNC 3) SSH 3 Enter your temporary SSH password Or, if you're entering the network information into the parmfile, it is the SSHPassword= keyword. Mark Post
Re: SLES10 Client
Hello Everyone, I am now able to logon to the root userid on my full-service server SLES10 SP2. I will start yast tomorrow. Thanks for all your support, Alyce -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Thursday, October 02, 2008 1:00 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client On 10/2/2008 at 2:04 PM, in message [EMAIL PROTECTED], Austin, Alyce (CIV) [EMAIL PROTECTED] wrote: Well, I tried both the starter system default password and the new password I changed it to to logon on as root for the full-service starter system from my SSH client and neither one works. I need some clarification here. Are you trying to SSH to a Linux system that you are in the process of installing? If so, there is no default password. During the setup process before you SSH in, you are asked for a temporary root password to be used. That is the password you need to use when you SSH in to enter the yast command. The prompt is right after you select the display type. Select the display type. 1) X11 2) VNC 3) SSH 3 Enter your temporary SSH password Or, if you're entering the network information into the parmfile, it is the SSHPassword= keyword. Mark Post
Re: SLES10 Client
I've added an annotated console log for both the starter system install and a client system install as appendices in the document, assuming that Novell does another release. -- db
Re: SLES10 Client
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: IBMVM@LISTSERV.UARK.EDU 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: IBMVM@LISTSERV.UARK.EDU 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
Re: SLES10 Client
*** 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; Yes.
Re: SLES10 Client
On 9/30/2008 at 4:20 PM, in message [EMAIL PROTECTED], Austin, Alyce (CIV) [EMAIL PROTECTED] wrote: 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? Neither. Leave your TN3270 session as it is, since you'll need it later. From your desktop, SSH to the IP address shown in the message, then issue the yast command. Mark Post
Re: SLES10 Client
OOPs...I already disonnected from Client Do I need to start the process again before SSH'g? Thanks, Alyce -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Tuesday, September 30, 2008 1:33 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client On 9/30/2008 at 4:20 PM, in message [EMAIL PROTECTED], Austin, Alyce (CIV) [EMAIL PROTECTED] wrote: 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? Neither. Leave your TN3270 session as it is, since you'll need it later. From your desktop, SSH to the IP address shown in the message, then issue the yast command. Mark Post
Re: SLES10 Client
As long as you left it RUNNING in the bottom right hand corner of the screen, having issued at some point since logon, (perhaps in the PROFILE EXEC), you should be good to SSH in right away. Also, see SHARE session Installing a Novell SLES 10 Starter System without a Net(work) at: http://linuxvm.org/Present/SHARE111/S9287mw.pdf some parts may have helped you, and still may. You're right at the end of the session. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Austin, Alyce (CIV) [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 09/30/2008 04:01 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: SLES10 Client OOPs...I already disonnected from Client Do I need to start the process again before SSH'g? Thanks, Alyce -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Tuesday, September 30, 2008 1:33 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client On 9/30/2008 at 4:20 PM, in message [EMAIL PROTECTED], Austin, Alyce (CIV) [EMAIL PROTECTED] wrote: 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? Neither. Leave your TN3270 session as it is, since you'll need it later. From your desktop, SSH to the IP address shown in the message, then issue the yast command. Mark Post The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
Re: SLES10 Client
OK...i was able to ssh to my new client. Is the default root password the same as it was for the starter system? Thanks, Alyce -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mike Walter Sent: Tuesday, September 30, 2008 2:20 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client As long as you left it RUNNING in the bottom right hand corner of the screen, having issued at some point since logon, (perhaps in the PROFILE EXEC), you should be good to SSH in right away. Also, see SHARE session Installing a Novell SLES 10 Starter System without a Net(work) at: http://linuxvm.org/Present/SHARE111/S9287mw.pdf some parts may have helped you, and still may. You're right at the end of the session. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Austin, Alyce (CIV) [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 09/30/2008 04:01 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: SLES10 Client OOPs...I already disonnected from Client Do I need to start the process again before SSH'g? Thanks, Alyce -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Tuesday, September 30, 2008 1:33 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client On 9/30/2008 at 4:20 PM, in message [EMAIL PROTECTED], Austin, Alyce (CIV) [EMAIL PROTECTED] wrote: 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? Neither. Leave your TN3270 session as it is, since you'll need it later. From your desktop, SSH to the IP address shown in the message, then issue the yast command. Mark Post The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
Re: SLES10 Client
Why not just try the default NOVSTART root password and find out for yourself? If it works (which it should) you have your answer. But if you followed the instructions, you changed your NOVSTART root password immediately. So try that one, if the default fails. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Austin, Alyce (CIV) [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 09/30/2008 04:33 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: SLES10 Client OK...i was able to ssh to my new client. Is the default root password the same as it was for the starter system? Thanks, Alyce -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mike Walter Sent: Tuesday, September 30, 2008 2:20 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client As long as you left it RUNNING in the bottom right hand corner of the screen, having issued at some point since logon, (perhaps in the PROFILE EXEC), you should be good to SSH in right away. Also, see SHARE session Installing a Novell SLES 10 Starter System without a Net(work) at: http://linuxvm.org/Present/SHARE111/S9287mw.pdf some parts may have helped you, and still may. You're right at the end of the session. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Austin, Alyce (CIV) [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 09/30/2008 04:01 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: SLES10 Client OOPs...I already disonnected from Client Do I need to start the process again before SSH'g? Thanks, Alyce -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Tuesday, September 30, 2008 1:33 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client On 9/30/2008 at 4:20 PM, in message [EMAIL PROTECTED], Austin, Alyce (CIV) [EMAIL PROTECTED] wrote: 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? Neither. Leave your TN3270 session as it is, since you'll need it later. From your desktop, SSH to the IP address shown in the message, then issue the yast command. Mark Post The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
Re: SLES10 Client
I don't believe you'll be asked for a password -- just enter root for the userid and you should go right in... Scott On Tue, Sep 30, 2008 at 3:33 PM, Austin, Alyce (CIV) [EMAIL PROTECTED] wrote: OK...i was able to ssh to my new client. Is the default root password the same as it was for the starter system? Thanks, Alyce -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mike Walter Sent: Tuesday, September 30, 2008 2:20 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client As long as you left it RUNNING in the bottom right hand corner of the screen, having issued at some point since logon, (perhaps in the PROFILE EXEC), you should be good to SSH in right away. Also, see SHARE session Installing a Novell SLES 10 Starter System without a Net(work) at: http://linuxvm.org/Present/SHARE111/S9287mw.pdf some parts may have helped you, and still may. You're right at the end of the session. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Austin, Alyce (CIV) [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 09/30/2008 04:01 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: SLES10 Client OOPs...I already disonnected from Client Do I need to start the process again before SSH'g? Thanks, Alyce -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Tuesday, September 30, 2008 1:33 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client On 9/30/2008 at 4:20 PM, in message [EMAIL PROTECTED], Austin, Alyce (CIV) [EMAIL PROTECTED] wrote: 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? Neither. Leave your TN3270 session as it is, since you'll need it later. From your desktop, SSH to the IP address shown in the message, then issue the yast command. Mark Post The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
Re: SLES10 Client
I was afraid I might get locked out -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mike Walter Sent: Tuesday, September 30, 2008 2:54 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client Why not just try the default NOVSTART root password and find out for yourself? If it works (which it should) you have your answer. But if you followed the instructions, you changed your NOVSTART root password immediately. So try that one, if the default fails. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Austin, Alyce (CIV) [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 09/30/2008 04:33 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: SLES10 Client OK...i was able to ssh to my new client. Is the default root password the same as it was for the starter system? Thanks, Alyce -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mike Walter Sent: Tuesday, September 30, 2008 2:20 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client As long as you left it RUNNING in the bottom right hand corner of the screen, having issued at some point since logon, (perhaps in the PROFILE EXEC), you should be good to SSH in right away. Also, see SHARE session Installing a Novell SLES 10 Starter System without a Net(work) at: http://linuxvm.org/Present/SHARE111/S9287mw.pdf some parts may have helped you, and still may. You're right at the end of the session. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Austin, Alyce (CIV) [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 09/30/2008 04:01 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: SLES10 Client OOPs...I already disonnected from Client Do I need to start the process again before SSH'g? Thanks, Alyce -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Tuesday, September 30, 2008 1:33 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client On 9/30/2008 at 4:20 PM, in message [EMAIL PROTECTED], Austin, Alyce (CIV) [EMAIL PROTECTED] wrote: 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? Neither. Leave your TN3270 session as it is, since you'll need it later. From your desktop, SSH to the IP address shown in the message, then issue the yast command. Mark Post The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
Re: SLES10 Client
Don't be afraid -- you're not going to break anything... And besides - we're here if you do :-) Best of luck - Scott On Tue, Sep 30, 2008 at 4:02 PM, Austin, Alyce (CIV) [EMAIL PROTECTED] wrote: I was afraid I might get locked out -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mike Walter Sent: Tuesday, September 30, 2008 2:54 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client Why not just try the default NOVSTART root password and find out for yourself? If it works (which it should) you have your answer. But if you followed the instructions, you changed your NOVSTART root password immediately. So try that one, if the default fails. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Austin, Alyce (CIV) [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 09/30/2008 04:33 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: SLES10 Client OK...i was able to ssh to my new client. Is the default root password the same as it was for the starter system? Thanks, Alyce -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mike Walter Sent: Tuesday, September 30, 2008 2:20 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client As long as you left it RUNNING in the bottom right hand corner of the screen, having issued at some point since logon, (perhaps in the PROFILE EXEC), you should be good to SSH in right away. Also, see SHARE session Installing a Novell SLES 10 Starter System without a Net(work) at: http://linuxvm.org/Present/SHARE111/S9287mw.pdf some parts may have helped you, and still may. You're right at the end of the session. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Austin, Alyce (CIV) [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 09/30/2008 04:01 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: SLES10 Client OOPs...I already disonnected from Client Do I need to start the process again before SSH'g? Thanks, Alyce -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Tuesday, September 30, 2008 1:33 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client On 9/30/2008 at 4:20 PM, in message [EMAIL PROTECTED], Austin, Alyce (CIV) [EMAIL PROTECTED] wrote: 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? Neither. Leave your TN3270 session as it is, since you'll need it later. From your desktop, SSH to the IP address shown in the message, then issue the yast command. Mark Post The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot
Re: SLES10 Client
Hello again, While implementing the SLES exec for the SLES10 full-service server, it asks for a MAC address. (I thought the MAC address was automatically assigned. Why is it asking for a static address?) We are using OSA GB-EXP. Please see below: Device address for read channel [0.0340] 0.0.0340 Device address for write channel 0.0.0341 Device address for data channel 0.0.0342 Portname to use osasles10 Enable OSI Layer 2 support? 1) Yes 2) No 1 MAC address Please select the type of your network device. 1) OSA-2 or OSA Express 2) Hipersockets 3) Channel To Channel (CTC) 4) ESCON 5) Inter-User Communication Vehicle (IUCV) * * * End of File * * * * -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Rich Smrcina Sent: Friday, September 26, 2008 3:15 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client There's apparently some code in the card image install kernel that looks for a real CD. Don't worry about that. When it asks for the network device addresses you need to key in the virtual device numbers in the format that is presented right before the question is asked. So when the question comes up: Device address for read channel [e003] You respond: 0.0.0340 It will subsequently ask for the write channel and data channel, just reply with the device numbers in ascending sequence in the same format. Austin, Alyce (CIV) wrote: But, why does is say: Searching for info file... *** Could not find the SUSE Linux Enterprise Server 10 Installation CD. Activating manual setup program. Thanks, Alyce *From:* The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] *On Behalf Of *Mike Walter *Sent:* Friday, September 26, 2008 2:55 PM *To:* IBMVM@LISTSERV.UARK.EDU *Subject:* Re: SLES10 Client Alyce, E007 ATTACHED TO CLIENT 0340 Why doesn't it like my E000 and/or e007 response? Because you attached your REAL device E007-E009 as VIRTUAL device addresses 0340-0342. Using consistent virtual addresses on each server is a *GOOD THING*. This permits you to have fewer changes between SLES guests. You just attach different REAL devices to the guests as the same VIRTUAL addresses. Linux only sees the same virtual device addresses, so the Linux configuration is the same for pretty much everything except the IP address and Hostname. That way you take that same Golden Image, copy it to the next virtual guest server, only have to change the IP address and Hostname, and add whatever middleware it needs. The virtual OSA addresses are the same. But you'd be far better off spending a little time researching VIRTUAL SWITCHes and using them instead of real OSA addresses. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. *Austin, Alyce (CIV) [EMAIL PROTECTED]* Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 09/26/2008 04:38 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: SLES10 Client Hello, From my Client userid, I type SLES to bring up the full-service server for SLES10: This is what I get: Why is it looking for the CDs when I have a starter system implemented? sles NO FILES PURGED RDR FILE 0027 SENT FROM CLIENT PUN WAS 0027 RECS 090K CPY 001 A NOHOLD NOKEEP RDR FILE 0028 SENT FROM CLIENT PUN WAS 0028 RECS 0001 CPY 001 A NOHOLD NOKEEP RDR FILE 0029 SENT FROM CLIENT PUN WAS 0029 RECS 107K CPY 001 A NOHOLD NOKEE Searching for info file... *** Could not find the SUSE Linux Enterprise Server 10 Installation CD. Activating manual setup program. Linuxrc v2.0.79 (Kernel 2.6.16.60-0.21-default) Please select the type of your network device. 1) OSA-2 or OSA Express 2) Hipersockets 3) Channel To Channel (CTC) 4) ESCON 5) Inter-User Communication Vehicle (IUCV) 1 Please choose the CCW bus interface. 1) QDIO 2) LCS 1 1) QDIO 2) LCS Please choose the physical medium. 1) Ethernet 2) Token Ring 1 0.0.0340 1731/01 0.0.0341 1731/01 0.0.0342 1731/01 evice address for read channel [e003] e007 *** This is not a valid CCW address. Please select the type of your network device. 1) OSA-2 or OSA Express 2) Hipersockets Why doesn't it like my E000 and/or e007 response? When I do a q osa, this is what I see on my system: q osa OSA E003 ATTACHED TO TCPIPE003 DEVTYPE OSA CHPID 00 OSD OSA E004 ATTACHED TO TCPIPE004 DEVTYPE OSA CHPID 00 OSD OSA E005 ATTACHED TO TCPIPE005
Re: SLES10 Client
Turn off level 2. David Dean Information Systems *bcbstauthorized* -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Austin, Alyce (CIV) Sent: Monday, September 29, 2008 2:07 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client Hello again, While implementing the SLES exec for the SLES10 full-service server, it asks for a MAC address. (I thought the MAC address was automatically assigned. Why is it asking for a static address?) We are using OSA GB-EXP. Please see below: Device address for read channel [0.0340] 0.0.0340 Device address for write channel 0.0.0341 Device address for data channel 0.0.0342 Portname to use osasles10 Enable OSI Layer 2 support? 1) Yes 2) No 1 MAC address Please select the type of your network device. 1) OSA-2 or OSA Express 2) Hipersockets 3) Channel To Channel (CTC) 4) ESCON 5) Inter-User Communication Vehicle (IUCV) * * * End of File * * * * -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Rich Smrcina Sent: Friday, September 26, 2008 3:15 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client There's apparently some code in the card image install kernel that looks for a real CD. Don't worry about that. When it asks for the network device addresses you need to key in the virtual device numbers in the format that is presented right before the question is asked. So when the question comes up: Device address for read channel [e003] You respond: 0.0.0340 It will subsequently ask for the write channel and data channel, just reply with the device numbers in ascending sequence in the same format. Austin, Alyce (CIV) wrote: But, why does is say: Searching for info file... *** Could not find the SUSE Linux Enterprise Server 10 Installation CD. Activating manual setup program. Thanks, Alyce *From:* The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] *On Behalf Of *Mike Walter *Sent:* Friday, September 26, 2008 2:55 PM *To:* IBMVM@LISTSERV.UARK.EDU *Subject:* Re: SLES10 Client Alyce, E007 ATTACHED TO CLIENT 0340 Why doesn't it like my E000 and/or e007 response? Because you attached your REAL device E007-E009 as VIRTUAL device addresses 0340-0342. Using consistent virtual addresses on each server is a *GOOD THING*. This permits you to have fewer changes between SLES guests. You just attach different REAL devices to the guests as the same VIRTUAL addresses. Linux only sees the same virtual device addresses, so the Linux configuration is the same for pretty much everything except the IP address and Hostname. That way you take that same Golden Image, copy it to the next virtual guest server, only have to change the IP address and Hostname, and add whatever middleware it needs. The virtual OSA addresses are the same. But you'd be far better off spending a little time researching VIRTUAL SWITCHes and using them instead of real OSA addresses. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. *Austin, Alyce (CIV) [EMAIL PROTECTED]* Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 09/26/2008 04:38 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: SLES10 Client Hello, From my Client userid, I type SLES to bring up the full-service server for SLES10: This is what I get: Why is it looking for the CDs when I have a starter system implemented? sles NO FILES PURGED RDR FILE 0027 SENT FROM CLIENT PUN WAS 0027 RECS 090K CPY 001 A NOHOLD NOKEEP RDR FILE 0028 SENT FROM CLIENT PUN WAS 0028 RECS 0001 CPY 001 A NOHOLD NOKEEP RDR FILE 0029 SENT FROM CLIENT PUN WAS 0029 RECS 107K CPY 001 A NOHOLD NOKEE Searching for info file... *** Could not find the SUSE Linux Enterprise Server 10 Installation CD. Activating manual setup program. Linuxrc v2.0.79 (Kernel 2.6.16.60-0.21-default) Please select the type of your network device. 1) OSA-2 or OSA Express 2) Hipersockets 3) Channel To Channel (CTC) 4) ESCON 5) Inter-User Communication Vehicle (IUCV) 1 Please choose the CCW bus interface. 1) QDIO 2) LCS 1 1) QDIO 2) LCS Please choose the physical medium. 1) Ethernet 2) Token Ring 1 0.0.0340 1731/01 0.0.0341 1731/01 0.0.0342 1731/01 evice address for read channel [e003] e007 *** This is not a valid CCW address. Please select the type of your network device. 1) OSA-2 or OSA Express 2) Hipersockets
Re: SLES10 Client
While implementing the SLES exec for the SLES10 full-service server, it asks for a MAC address. (I thought the MAC address was automatically assigned. Why is it asking for a static address?) We are using OSA GB-EXP. You should respond no to the layer 2 prompt here. Nothing in the setup process needs layer 2 access. In general, it's asking so that it correctly identifies the interface you want to use. CP generates a random MAC for the last 3 bytes of any virtual interface (the first 3 bytes are set by MACPREFIX in SYSTEM CONFIG), so if you are going to use the layer 2 function, it matches the virtual MAC to identify which interface to use.
Re: SLES10 Client
I initially said no to layer 2 and eventually is ask me again if I want to enable layer 2 Thanks, Alyce Enable OSI Layer 2 support? 1) Yes 2) No 2 Please select the type of your network device. 1) OSA-2 or OSA Express 2) Hipersockets 3) Channel To Channel (CTC) 4) ESCON 5) Inter-User Communication Vehicle (IUCV) 1 Please choose the CCW bus interface. 1) QDIO 2) LCS 1 Please choose the physical medium. 1) Ethernet 2) Token Ring 1 0.0.0340 1731/01 0.0.0341 1731/01 0.0.0342 1731/01 Device address for read channel [0.0.0340] 0.0.0340 Device address for write channel [0.0.0341] 0.0.0341 Device address for data channel [0.0.0342] 0.0.0342 Portname to use [osasles10] osasles10 Enable OSI Layer 2 support? 1) Yes 2) No 2 Please select the type of your network device. 1) OSA-2 or OSA Express 2) Hipersockets 3) Channel To Channel (CTC) 4) ESCON 5) Inter-User Communication Vehicle (IUCV) * * * End of Fi -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Monday, September 29, 2008 11:23 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client While implementing the SLES exec for the SLES10 full-service server, it asks for a MAC address. (I thought the MAC address was automatically assigned. Why is it asking for a static address?) We are using OSA GB-EXP. You should respond no to the layer 2 prompt here. Nothing in the setup process needs layer 2 access. In general, it's asking so that it correctly identifies the interface you want to use. CP generates a random MAC for the last 3 bytes of any virtual interface (the first 3 bytes are set by MACPREFIX in SYSTEM CONFIG), so if you are going to use the layer 2 function, it matches the virtual MAC to identify which interface to use.
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
Re: SLES10 Client
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: IBMVM@LISTSERV.UARK.EDU 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
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: IBMVM@LISTSERV.UARK.EDU 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
Re: SLES10 Client
Hello, From my Client userid, I type SLES to bring up the full-service server for SLES10: This is what I get: Why is it looking for the CDs when I have a starter system implemented? sles NO FILES PURGED RDR FILE 0027 SENT FROM CLIENT PUN WAS 0027 RECS 090K CPY 001 A NOHOLD NOKEEP RDR FILE 0028 SENT FROM CLIENT PUN WAS 0028 RECS 0001 CPY 001 A NOHOLD NOKEEP RDR FILE 0029 SENT FROM CLIENT PUN WAS 0029 RECS 107K CPY 001 A NOHOLD NOKEE Searching for info file... *** Could not find the SUSE Linux Enterprise Server 10 Installation CD. Activating manual setup program. Linuxrc v2.0.79 (Kernel 2.6.16.60-0.21-default) Please select the type of your network device. 1) OSA-2 or OSA Express 2) Hipersockets 3) Channel To Channel (CTC) 4) ESCON 5) Inter-User Communication Vehicle (IUCV) 1 Please choose the CCW bus interface. 1) QDIO 2) LCS 1 1) QDIO 2) LCS Please choose the physical medium. 1) Ethernet 2) Token Ring 1 0.0.0340 1731/01 0.0.0341 1731/01 0.0.0342 1731/01 evice address for read channel [e003] e007 *** This is not a valid CCW address. Please select the type of your network device. 1) OSA-2 or OSA Express 2) Hipersockets Why doesn't it like my E000 and/or e007 response? When I do a q osa, this is what I see on my system: q osa OSA E003 ATTACHED TO TCPIPE003 DEVTYPE OSA CHPID 00 OSD OSA E004 ATTACHED TO TCPIPE004 DEVTYPE OSA CHPID 00 OSD OSA E005 ATTACHED TO TCPIPE005 DEVTYPE OSA CHPID 00 OSD OSA E007 ATTACHED TO CLIENT 0340 DEVTYPE OSA CHPID 00 OSD OSA E008 ATTACHED TO CLIENT 0341 DEVTYPE OSA CHPID 00 OSD OSA E009 ATTACHED TO CLIENT 0342 DEVTYPE OSA CHPID 00 OSD Any help will be appreciated, Thanks, Alyce -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Thursday, September 25, 2008 11:39 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client Do I need a secondary user defined It's not required, but it is a good idea to have somewhere central for all the console logs on your system to go by default, rather than have them scattered all over the spool. If you want to silence the message, change the CONLOG on the CONSOLE statement in the directory entry to any valid userid on your system, or remove it if you want the console logs to end up in CLIENT's rdr. do I need both CPU statements? No. Most guests seem to feel healthier and more responsive if you have more than one logical CPU, but it's not required or desirable in some cases. Do note that there are some applications that don't build properly in a UP system, so we put the extra statement in to try to catch that. As Rich said, it's an example. Tailor it as you see fit. 19F and the disks you plan to use to put the Linux system on are the important bits. The rest is as you like it.
Re: SLES10 Client
Alyce, E007 ATTACHED TO CLIENT 0340 Why doesn't it like my E000 and/or e007 response? Because you attached your REAL device E007-E009 as VIRTUAL device addresses 0340-0342. Using consistent virtual addresses on each server is a *GOOD THING*. This permits you to have fewer changes between SLES guests. You just attach different REAL devices to the guests as the same VIRTUAL addresses. Linux only sees the same virtual device addresses, so the Linux configuration is the same for pretty much everything except the IP address and Hostname. That way you take that same Golden Image, copy it to the next virtual guest server, only have to change the IP address and Hostname, and add whatever middleware it needs. The virtual OSA addresses are the same. But you'd be far better off spending a little time researching VIRTUAL SWITCHes and using them instead of real OSA addresses. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Austin, Alyce (CIV) [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 09/26/2008 04:38 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: SLES10 Client Hello, From my Client userid, I type SLES to bring up the full-service server for SLES10: This is what I get: Why is it looking for the CDs when I have a starter system implemented? sles NO FILES PURGED RDR FILE 0027 SENT FROM CLIENT PUN WAS 0027 RECS 090K CPY 001 A NOHOLD NOKEEP RDR FILE 0028 SENT FROM CLIENT PUN WAS 0028 RECS 0001 CPY 001 A NOHOLD NOKEEP RDR FILE 0029 SENT FROM CLIENT PUN WAS 0029 RECS 107K CPY 001 A NOHOLD NOKEE Searching for info file... *** Could not find the SUSE Linux Enterprise Server 10 Installation CD. Activating manual setup program. Linuxrc v2.0.79 (Kernel 2.6.16.60-0.21-default) Please select the type of your network device. 1) OSA-2 or OSA Express 2) Hipersockets 3) Channel To Channel (CTC) 4) ESCON 5) Inter-User Communication Vehicle (IUCV) 1 Please choose the CCW bus interface. 1) QDIO 2) LCS 1 1) QDIO 2) LCS Please choose the physical medium. 1) Ethernet 2) Token Ring 1 0.0.0340 1731/01 0.0.0341 1731/01 0.0.0342 1731/01 evice address for read channel [e003] e007 *** This is not a valid CCW address. Please select the type of your network device. 1) OSA-2 or OSA Express 2) Hipersockets Why doesn't it like my E000 and/or e007 response? When I do a q osa, this is what I see on my system: q osa OSA E003 ATTACHED TO TCPIPE003 DEVTYPE OSA CHPID 00 OSD OSA E004 ATTACHED TO TCPIPE004 DEVTYPE OSA CHPID 00 OSD OSA E005 ATTACHED TO TCPIPE005 DEVTYPE OSA CHPID 00 OSD OSA E007 ATTACHED TO CLIENT 0340 DEVTYPE OSA CHPID 00 OSD OSA E008 ATTACHED TO CLIENT 0341 DEVTYPE OSA CHPID 00 OSD OSA E009 ATTACHED TO CLIENT 0342 DEVTYPE OSA CHPID 00 OSD Any help will be appreciated, Thanks, Alyce -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Thursday, September 25, 2008 11:39 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client Do I need a secondary user defined It's not required, but it is a good idea to have somewhere central for all the console logs on your system to go by default, rather than have them scattered all over the spool. If you want to silence the message, change the CONLOG on the CONSOLE statement in the directory entry to any valid userid on your system, or remove it if you want the console logs to end up in CLIENT's rdr. do I need both CPU statements? No. Most guests seem to feel healthier and more responsive if you have more than one logical CPU, but it's not required or desirable in some cases. Do note that there are some applications that don't build properly in a UP system, so we put the extra statement in to try to catch that. As Rich said, it's an example. Tailor it as you see fit. 19F and the disks you plan to use to put the Linux system on are the important bits. The rest is as you like it. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E
Re: SLES10 Client
But, why does is say: Searching for info file... *** Could not find the SUSE Linux Enterprise Server 10 Installation CD. Activating manual setup program. Thanks, Alyce From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Mike Walter Sent: Friday, September 26, 2008 2:55 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client Alyce, E007 ATTACHED TO CLIENT 0340 Why doesn't it like my E000 and/or e007 response? Because you attached your REAL device E007-E009 as VIRTUAL device addresses 0340-0342. Using consistent virtual addresses on each server is a *GOOD THING*. This permits you to have fewer changes between SLES guests. You just attach different REAL devices to the guests as the same VIRTUAL addresses. Linux only sees the same virtual device addresses, so the Linux configuration is the same for pretty much everything except the IP address and Hostname. That way you take that same Golden Image, copy it to the next virtual guest server, only have to change the IP address and Hostname, and add whatever middleware it needs. The virtual OSA addresses are the same. But you'd be far better off spending a little time researching VIRTUAL SWITCHes and using them instead of real OSA addresses. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Austin, Alyce (CIV) [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 09/26/2008 04:38 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: SLES10 Client Hello, From my Client userid, I type SLES to bring up the full-service server for SLES10: This is what I get: Why is it looking for the CDs when I have a starter system implemented? sles NO FILES PURGED RDR FILE 0027 SENT FROM CLIENT PUN WAS 0027 RECS 090K CPY 001 A NOHOLD NOKEEP RDR FILE 0028 SENT FROM CLIENT PUN WAS 0028 RECS 0001 CPY 001 A NOHOLD NOKEEP RDR FILE 0029 SENT FROM CLIENT PUN WAS 0029 RECS 107K CPY 001 A NOHOLD NOKEE Searching for info file... *** Could not find the SUSE Linux Enterprise Server 10 Installation CD. Activating manual setup program. Linuxrc v2.0.79 (Kernel 2.6.16.60-0.21-default) Please select the type of your network device. 1) OSA-2 or OSA Express 2) Hipersockets 3) Channel To Channel (CTC) 4) ESCON 5) Inter-User Communication Vehicle (IUCV) 1 Please choose the CCW bus interface. 1) QDIO 2) LCS 1 1) QDIO 2) LCS Please choose the physical medium. 1) Ethernet 2) Token Ring 1 0.0.0340 1731/01 0.0.0341 1731/01 0.0.0342 1731/01 evice address for read channel [e003] e007 *** This is not a valid CCW address. Please select the type of your network device. 1) OSA-2 or OSA Express 2) Hipersockets Why doesn't it like my E000 and/or e007 response? When I do a q osa, this is what I see on my system: q osa OSA E003 ATTACHED TO TCPIPE003 DEVTYPE OSA CHPID 00 OSD OSA E004 ATTACHED TO TCPIPE004 DEVTYPE OSA CHPID 00 OSD OSA E005 ATTACHED TO TCPIPE005 DEVTYPE OSA CHPID 00 OSD OSA E007 ATTACHED TO CLIENT 0340 DEVTYPE OSA CHPID 00 OSD OSA E008 ATTACHED TO CLIENT 0341 DEVTYPE OSA CHPID 00 OSD OSA E009 ATTACHED TO CLIENT 0342 DEVTYPE OSA CHPID 00 OSD Any help will be appreciated, Thanks, Alyce -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Thursday, September 25, 2008 11:39 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client Do I need a secondary user defined It's not required, but it is a good idea to have somewhere central for all the console logs on your system to go by default, rather than have them scattered all over the spool. If you want to silence the message, change the CONLOG on the CONSOLE statement in the directory entry to any valid userid on your system, or remove it if you want the console logs to end up in CLIENT's rdr. do I need both CPU statements? No. Most guests seem to feel healthier and more responsive if you have more than one logical CPU, but it's not required or desirable in some cases. Do note that there are some applications that don't build properly in a UP system, so we put the extra statement in to try to catch that. As Rich said, it's an example. Tailor it as you see fit. 19F and the disks you plan to use to put the Linux system on are the important bits. The rest is as you like it. The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately
Re: SLES10 Client
There's apparently some code in the card image install kernel that looks for a real CD. Don't worry about that. When it asks for the network device addresses you need to key in the virtual device numbers in the format that is presented right before the question is asked. So when the question comes up: Device address for read channel [e003] You respond: 0.0.0340 It will subsequently ask for the write channel and data channel, just reply with the device numbers in ascending sequence in the same format. Austin, Alyce (CIV) wrote: But, why does is say: Searching for info file... *** Could not find the SUSE Linux Enterprise Server 10 Installation CD. Activating manual setup program. Thanks, Alyce *From:* The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] *On Behalf Of *Mike Walter *Sent:* Friday, September 26, 2008 2:55 PM *To:* IBMVM@LISTSERV.UARK.EDU *Subject:* Re: SLES10 Client Alyce, E007 ATTACHED TO CLIENT 0340 Why doesn't it like my E000 and/or e007 response? Because you attached your REAL device E007-E009 as VIRTUAL device addresses 0340-0342. Using consistent virtual addresses on each server is a *GOOD THING*. This permits you to have fewer changes between SLES guests. You just attach different REAL devices to the guests as the same VIRTUAL addresses. Linux only sees the same virtual device addresses, so the Linux configuration is the same for pretty much everything except the IP address and Hostname. That way you take that same Golden Image, copy it to the next virtual guest server, only have to change the IP address and Hostname, and add whatever middleware it needs. The virtual OSA addresses are the same. But you'd be far better off spending a little time researching VIRTUAL SWITCHes and using them instead of real OSA addresses. Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. *Austin, Alyce (CIV) [EMAIL PROTECTED]* Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 09/26/2008 04:38 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: SLES10 Client Hello, From my Client userid, I type SLES to bring up the full-service server for SLES10: This is what I get: Why is it looking for the CDs when I have a starter system implemented? sles NO FILES PURGED RDR FILE 0027 SENT FROM CLIENT PUN WAS 0027 RECS 090K CPY 001 A NOHOLD NOKEEP RDR FILE 0028 SENT FROM CLIENT PUN WAS 0028 RECS 0001 CPY 001 A NOHOLD NOKEEP RDR FILE 0029 SENT FROM CLIENT PUN WAS 0029 RECS 107K CPY 001 A NOHOLD NOKEE Searching for info file... *** Could not find the SUSE Linux Enterprise Server 10 Installation CD. Activating manual setup program. Linuxrc v2.0.79 (Kernel 2.6.16.60-0.21-default) Please select the type of your network device. 1) OSA-2 or OSA Express 2) Hipersockets 3) Channel To Channel (CTC) 4) ESCON 5) Inter-User Communication Vehicle (IUCV) 1 Please choose the CCW bus interface. 1) QDIO 2) LCS 1 1) QDIO 2) LCS Please choose the physical medium. 1) Ethernet 2) Token Ring 1 0.0.0340 1731/01 0.0.0341 1731/01 0.0.0342 1731/01 evice address for read channel [e003] e007 *** This is not a valid CCW address. Please select the type of your network device. 1) OSA-2 or OSA Express 2) Hipersockets Why doesn't it like my E000 and/or e007 response? When I do a q osa, this is what I see on my system: q osa OSA E003 ATTACHED TO TCPIPE003 DEVTYPE OSA CHPID 00 OSD OSA E004 ATTACHED TO TCPIPE004 DEVTYPE OSA CHPID 00 OSD OSA E005 ATTACHED TO TCPIPE005 DEVTYPE OSA CHPID 00 OSD OSA E007 ATTACHED TO CLIENT 0340 DEVTYPE OSA CHPID 00 OSD OSA E008 ATTACHED TO CLIENT 0341 DEVTYPE OSA CHPID 00 OSD OSA E009 ATTACHED TO CLIENT 0342 DEVTYPE OSA CHPID 00 OSD Any help will be appreciated, Thanks, Alyce -- 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
Re: SLES10 Client
So, the starter systems does need to be up to implement the new server? Thanks, Alyce -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Wednesday, September 24, 2008 3:10 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client OK, then Rich is correct. You're telling it the address of the install server (where it's going to get the files to install the new server). The new server will eventually need a unique address of it's own, though.
Re: SLES10 Client
Only for initial installation and adding more packages. For normal operation of your colony, it does not need to be up. Austin, Alyce (CIV) wrote: So, the starter systems does need to be up to implement the new server? Thanks, Alyce -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Wednesday, September 24, 2008 3:10 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client OK, then Rich is correct. You're telling it the address of the install server (where it's going to get the files to install the new server). The new server will eventually need a unique address of it's own, though. -- 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
Re: SLES10 Client
Hi again, When I log on to client, I get the following message: LOGON CLIENT HCPLGN196I Secondary user not in CP directory I use the client sampdir downloaded from Novell: USER CLIENT x 512M 512M G IPL CMS PARM AUTOCR MACHINE XA 2 CPU 0 ??? CPU 1 ??? CONSOLE 0009 3215 T CONLOG??? SPOOL 000C 2540 READER * SPOOL 000D 2540 PUNCH A SPOOL 000E 1403 A ... Do I need a secondary user defined and do I need both CPU statements? Thanks, Alyce -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Rich Smrcina Sent: Thursday, September 25, 2008 9:37 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client Only for initial installation and adding more packages. For normal operation of your colony, it does not need to be up. Austin, Alyce (CIV) wrote: So, the starter systems does need to be up to implement the new server? Thanks, Alyce -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Wednesday, September 24, 2008 3:10 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client OK, then Rich is correct. You're telling it the address of the install server (where it's going to get the files to install the new server). The new server will eventually need a unique address of it's own, though. -- 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
Re: SLES10 Client
Remember this is a sample directory entry, it can be tailored to look like pretty much anything you like. The secondary user can or can not be used if you like. The secondary user provides another point of control for the virtual machine to receive messages and issue commands. The additional CPU is also optional, and if it is not *absolutely* required for the workload I would suggest removing it and changing the numeric value in the MACHINE statement to 1. Austin, Alyce (CIV) wrote: Hi again, When I log on to client, I get the following message: LOGON CLIENT HCPLGN196I Secondary user not in CP directory I use the client sampdir downloaded from Novell: USER CLIENT x 512M 512M G IPL CMS PARM AUTOCR MACHINE XA 2 CPU 0 ??? CPU 1 ??? CONSOLE 0009 3215 T CONLOG??? SPOOL 000C 2540 READER * SPOOL 000D 2540 PUNCH A SPOOL 000E 1403 A ... Do I need a secondary user defined and do I need both CPU statements? Thanks, Alyce -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Rich Smrcina Sent: Thursday, September 25, 2008 9:37 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client Only for initial installation and adding more packages. For normal operation of your colony, it does not need to be up. Austin, Alyce (CIV) wrote: So, the starter systems does need to be up to implement the new server? Thanks, Alyce -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Wednesday, September 24, 2008 3:10 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client OK, then Rich is correct. You're telling it the address of the install server (where it's going to get the files to install the new server). The new server will eventually need a unique address of it's own, though. -- 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
Re: SLES10 Client
Do I need a secondary user defined It's not required, but it is a good idea to have somewhere central for all the console logs on your system to go by default, rather than have them scattered all over the spool. If you want to silence the message, change the CONLOG on the CONSOLE statement in the directory entry to any valid userid on your system, or remove it if you want the console logs to end up in CLIENT's rdr. do I need both CPU statements? No. Most guests seem to feel healthier and more responsive if you have more than one logical CPU, but it's not required or desirable in some cases. Do note that there are some applications that don't build properly in a UP system, so we put the extra statement in to try to catch that. As Rich said, it's an example. Tailor it as you see fit. 19F and the disks you plan to use to put the Linux system on are the important bits. The rest is as you like it.
SLES10 Client
HELLO, I HAVE SUCCESSFULLY IMPLEMENTED THE STARTER SYSTEM FOR SLES10. I'M PREPARING TO IMPLEMENT THE FULL-SERVICE SERVER/CLIENT). ON PAGE 31 OF THE STARTER SYSTEM, IT SAYS TO USE THE SAME NETWORK ADDRESS OF THE STARTER SYSTEM FOR THE CLIENT SYSTEM. I ASSUME THIS MEANS THAT I NEED TO TAKE DOWN THE NOVSTART SYSTEM AND USE ITS IP ADDR THAT IS DEFINED IN THE NETWORK PARMS FILE FOR MY CLIENT SYSTEM. IS THIS CORRECT? OR, CAN I USE A DIFFERENT IP FOR THE CLIENT SYSTEM? THANK YOU FOR YOUR SUPPORT, ALYCE
Re: SLES10 Client
It's asking for the installation source IP address. The starter system is being used to host the installation. Your 'client' system will retrieve the packages from the starter system over your Vswitch (or network). So ultimately, they will have different IP Addresses. Alyce Austin wrote: HELLO, I HAVE SUCCESSFULLY IMPLEMENTED THE STARTER SYSTEM FOR SLES10. I'M PREPARING TO IMPLEMENT THE FULL-SERVICE SERVER/CLIENT). ON PAGE 31 OF THE STARTER SYSTEM, IT SAYS TO USE THE SAME NETWORK ADDRESS OF THE STARTER SYSTEM FOR THE CLIENT SYSTEM. I ASSUME THIS MEANS THAT I NEED TO TAKE DOWN THE NOVSTART SYSTEM AND USE ITS IP ADDR THAT IS DEFINED IN THE NETWORK PARMS FILE FOR MY CLIENT SYSTEM. IS THIS CORRECT? OR, CAN I USE A DIFFERENT IP FOR THE CLIENT SYSTEM? THANK YOU FOR YOUR SUPPORT, ALYCE -- 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
Re: SLES10 Client
Does NOVSTART have to be up to IPL the client? Thanks, Alyce -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Rich Smrcina Sent: Wednesday, September 24, 2008 1:48 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client It's asking for the installation source IP address. The starter system is being used to host the installation. Your 'client' system will retrieve the packages from the starter system over your Vswitch (or network). So ultimately, they will have different IP Addresses. Alyce Austin wrote: HELLO, I HAVE SUCCESSFULLY IMPLEMENTED THE STARTER SYSTEM FOR SLES10. I'M PREPARING TO IMPLEMENT THE FULL-SERVICE SERVER/CLIENT). ON PAGE 31 OF THE STARTER SYSTEM, IT SAYS TO USE THE SAME NETWORK ADDRESS OF THE STARTER SYSTEM FOR THE CLIENT SYSTEM. I ASSUME THIS MEANS THAT I NEED TO TAKE DOWN THE NOVSTART SYSTEM AND USE ITS IP ADDR THAT IS DEFINED IN THE NETWORK PARMS FILE FOR MY CLIENT SYSTEM. IS THIS CORRECT? OR, CAN I USE A DIFFERENT IP FOR THE CLIENT SYSTEM? THANK YOU FOR YOUR SUPPORT, ALYCE -- 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
Re: SLES10 Client
No, you should use an different IP address from the same subnet, or from a subnet that is reachable from the starter system. You need the starter system to be up when you try to build the new system. What page in the docs are you referring to? If I goofed, I'd like to make sure I fix the docs. -- db
Re: SLES10 Client
No, the SLES exec punches the install deck to the new client rdr and IPLs from that. NOVSTART does have to be up to deliver the files to the client during installation. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Austin, Alyce (CIV) Sent: Wednesday, September 24, 2008 5:17 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client Does NOVSTART have to be up to IPL the client?
Re: SLES10 Client
It is on page 31, starting with Specify the network address of the starter system server... -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of David Boyes Sent: Wednesday, September 24, 2008 2:35 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SLES10 Client No, you should use an different IP address from the same subnet, or from a subnet that is reachable from the starter system. You need the starter system to be up when you try to build the new system. What page in the docs are you referring to? If I goofed, I'd like to make sure I fix the docs. -- db
Re: SLES10 Client
OK, then Rich is correct. You're telling it the address of the install server (where it's going to get the files to install the new server). The new server will eventually need a unique address of it's own, though.
