AW: OSA and bridge_role=primary on boot

2017-11-30 Thread Benjamin Jakob Zimmermann
All the Fish)Von: Peter JansenGesendet: Mittwoch, 29. November 2017 21:18An: x...@ubuntu.comCc: debian-s390@lists.debian.orgBetreff: Re: Re: OSA and bridge_role=primary on boot 

Re: OSA and bridge_role=primary on boot

2017-04-26 Thread Philipp Kern
On 04/26/2017 02:05 PM, Dimitri John Ledkov wrote: > Yeah, in Ubuntu we kind of cheat. The installer is using sysconfig > stuff, but at the end of the install uses chzdev to take a dump of the > running configuration and store that on disk. This way all installed > systems only use chzdev/lszdev.

Re: OSA and bridge_role=primary on boot

2017-04-26 Thread Viktor Mihajlovski
On 26.04.2017 08:15, Benjamin Jakob Zimmermann wrote: > Ok, > thank you for pointing me into the right direction. > > The working solution is the following entry in /etc/network/interfaces: > [...] > allow-ovs br0 > iface br0 inet manual > > allow-ovs [ccwdev0-encif] > iface [ccwdev0-encif] >

Re: OSA and bridge_role=primary on boot

2017-04-25 Thread Viktor Mihajlovski
On 25.04.2017 13:44, Benjamin Jakob Zimmermann wrote: > Hello, > I am using debian stretch and I am trying to have openvswitch to work right > after rebooting the machine. > > So far, I manually configure the card with znetconf and then start > openvswitch and then manually bring up the

OSA and bridge_role=primary on boot

2017-04-25 Thread Benjamin Jakob Zimmermann
Hello, I am using debian stretch and I am trying to have openvswitch to work right after rebooting the machine. So far, I manually configure the card with znetconf and then start openvswitch and then manually bring up the interfaces. To visualize my approach, I list the commands (bridge and port