Bug 325291

Summary: Description of OSI Layer2 support for System z needed in the release notes
Product: Red Hat Enterprise Linux 4 Reporter: IBM Bug Proxy <bugproxy>
Component: redhat-releaseAssignee: Don Domingo <ddomingo>
Status: CLOSED CURRENTRELEASE QA Contact: Content Services Development <ecs-dev-list>
Severity: high Docs Contact:
Priority: low    
Version: 4.6CC: tao
Target Milestone: ---   
Target Release: ---   
Hardware: s390x   
OS: All   
Whiteboard:
Fixed In Version: 4.6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-02-01 03:33:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 248673    

Description IBM Bug Proxy 2007-10-09 18:01:03 UTC
=Comment: #0=================================================
William J. Goodrich <billgo.com> - 2007-10-09 11:28 EDT
Problem description:
The following text was added to the RHEL5.1 release notes to describe the
changes in Anaconda to provide support for installation over OSI Later2 devices. 

"Anaconda layer 2 Mode Enhancement

           Anaconda now supports connections to a VSWITCH, GuestLAN, or OSA
           in layer 2 mode. The installer now prompts for the mode in the
           initial stage of the installation. The value provided for the mode
           also affects the resulting network interface startup script after
           installation.

           For layer 2 installations, the value OPTIONS="layer2=1" is written
           to ifcfg-eth0; for layer 3, the value ARP=no is written.

           Note that when installing on a System z guest, you can make the
           mode persistent. To do so, add either LAYER2=0 or LAYER2=1 to the
           CMS configration file. Use LAYER2=0 when the OSA is in layer 3
           mode, and LAYER2=1 when the OSA is in layer 2 mode.

           When specifying LAYER2=1, you can also specify VSWITCH=1 when
           connecting to a VSWITCH, or VSWITCH=0 when connecting directly to
           the OSA. If a VSWITCH is not in use, specify the MAC address in
           the CMS configuration file using the parameter MACADDR=<MAC
           address>."

This text should also be added to the RHEL4.6 release notes.

Comment 1 Don Domingo 2007-10-10 00:38:57 UTC
added to RHEL4.6 release notes updates.

Comment 2 Don Domingo 2007-10-22 00:11:06 UTC
*** Bug 336211 has been marked as a duplicate of this bug. ***

Comment 3 John Jarvis 2007-11-14 16:56:17 UTC
Verified the requested text is indeed in the RHEL 4.6 release notes under the
Feature Updates heading.

Comment 5 Don Domingo 2008-02-01 03:33:56 UTC
as per Comment#3, closing this bug.