Re: [opensuse] Up to date bonding documentation ?

On Sun, 2007-09-02 at 11:53 -0500, Rajko M. wrote:
On Friday 31 August 2007 10:37, Christian Zoz wrote:
On Thu, Aug 30, Frank Bonnet wrote:
I've found some docs about "bonding" but it is written that it is an
obsolete page !

What is the "good" doc page URL for opensuse 10.2 ?

man ifcfg-bonding

Hi Christian,

If Frank prefer URL, in Konqueror Location field:
man:ifcfg-bonding
;-)

http://en.opensuse.org/Bonding
http://en.opensuse.org/Bonded_Interfaces_With_Optional_VLAN

BTW, as coauthor of ifcfg-bonding manual, can you see above links.
First probably needs update for newer versions of SUSE.

--
Regards,
Rajko.


All of these references to bonding are "CRAP" , I have a stack of IBM
x305 servers all of which come with two Broadcom nics which under
Netware are very easy to load balance with, I have released a few of
these servers by building vmware replacements for functions like the
"printserver" I was using for Iprint. With the released servers I have
been working with SLES 10 sp1 and OES2 BETA, the documentation for
bonding is as vague as one could possibly find in a enterprise solution.
I had to combine all of these papers and some seat of the pants know how
to get it working. The new Yast Networking module supports bonding , but
there is no documentation that tells you how to set your physical nics
up as "slaves" so you have to read and apply the CLI papers to figure
that out. Then there are issues with options, the documentation
regarding the setting of the "VNic" (bond0) are even worse, only trial
and error got me to use the -rr (round robin) setting correctly. Novell
and the SUSE team need to invest heavily in YaST usability. YaST is a
very useful tool but it too often assumes that it is a shortcut for a
CLI user rather than the primary tool set for a new Linux Admin\User.
The left pain that is supposed to be the guide to setup needs to include
more links to, preferably Novell on-line Docs, but really good community
docs specific to SUSE\YaST usage would be acceptable

p.s this documentation void is also very evident in the advanced
functions of the DHCP and DNS servers.
--
James Tremblay
Director of Technology
Newmarket School District
Newmarket,NH
http://en.opensuse.org/Education
"let's make a difference"

--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

Relevant Pages

  • Re: HELP - Maintenance Plan
    ... I'm also keeping weekly backups that are then overwritten ... Patch management - needs imporvement. ... Hardware inventory - Some documentation ... We have two web servers, ...
    (microsoft.public.win2000.networking)
  • Re: AIX Sendmail - change senders address
    ... were 6 servers whose domains were unknown and could not send emails ... where the system admin spent his time ... researching sendmail documentation for this was something relatively ...
    (comp.unix.aix)
  • Re: AIX Sendmail - change senders address
    ... were 6 servers whose domains were unknown and could not send emails ... where the system admin spent his time ... researching sendmail documentation for this was something relatively ...
    (comp.unix.aix)
  • Re: Need help figuring out whats on a server
    ... when the servers rolled out in 2002, ... You can find out the hardware configuration fairly easily but not what software is installed. ... I'd suggest starting with the documentation you have and trying to verify as much of it as you can. ... Part of my prior experience as a consultant is to know a good part of what's supposed to be on a vanilla install of the OS in front of me. ...
    (comp.sys.sun.admin)