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: [email protected]
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: [email protected]
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:* [email protected]
> *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" <[email protected]>
> 
> 09/26/2008 04:38 PM
> 
> Please respond to
> "The IBM z/VM Operating System" <[email protected]>
> 
>       
> 
> To
> 
>       
> 
> [email protected]
> 
> 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 TCPIP    E003 DEVTYPE OSA         CHPID 00 OSD
> OSA  E004 ATTACHED TO TCPIP    E004 DEVTYPE OSA         CHPID 00 OSD
> OSA  E005 ATTACHED TO TCPIP    E005 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
Please see the following link for the BlueCross BlueShield of Tennessee E-mail 
disclaimer:  http://www.bcbst.com/email_disclaimer.shtm

Reply via email to