Vlan+bonding+SLES9

[Miguel A Rubio]

I am configuring a SLES9 with bonding and VLAN on top of bonding.

It works , but I don´t know the place to configure the default GW in this scenario.

When using only bonding the routing table its ok.

When I configure 1 VLAN the default GW its not there. I have to enter it manually

[Steven E. Protter]

Shalom miguel.

GATEWAY=192.168.0.254

change the ip address to something real.

Put it either in the /etc/sysconfig/network file or the bond0 configuration file, wherever SLES9 keeps it.

SEP

[Vipulinux]

Hi
You can specify gateway in the NIC conf file itself.
Else do an route add.

To make the route add command permanent either create a startup script or simply append the command to
/etc/rc.local

Cheers
Vipul

[Miguel A Rubio]

The normal place to have the default GW es el fichero:

/etc/sysconfig/network/routes

and it works with bonding only.

When I start bonding with ip 0.0.0.0 in order to configure new VLAN , then the default GW dissapears.

[Craig Jackson_3]

I've been experimenting with this lately.

The HP VLAN stuff really gets in the way of the SuSE VLAN stuff. The driver is already in the SuSE kernel. The SuSE net startup scripts mostly do the right thing. However, the SuSE vlan package puts vconfig in /usr/sbin, not /sbin where the HP stuff puts it. (/sbin is actually more correct, but that's a SuSE bug that I don't care about. I'm not NFS-mounting /usr.)

Here's a How-To to get this to work right:

1. Put the default route in /etc/sysconfig/network/routes as usual.

2. Configure the bonding driver as normal in /etc/sysconfig/network/ifcfg-bond0. Configure it with STARTMODE='onboot'.

3. Put a symlink at /usr/sbin/vconfig to /sbin/vconfig.

4. Turn off the HP VLAN startup with "insserv -r vlan". This is the only thing that reads /etc/vlan.conf, so that can be empty as well.

5. Configure the vlans the SuSE way. This involves installing files with names like /etc/sysconfig/network/ifcfg-vlanNNN. These are like a regular static configuration, except that they've got the extra configuration line ETHERDEVICE='xxxx'. In this case, you use ETHERDEVICE='bond0'.

The vlan number comes from the number in the ifcfg-vlanNNN file name.

As an alternative to (3) and (4), you could remove the HP vlan driver completely and install the SuSE vlan package. However, I've found that this also requires re-installing the kernel, because uninstalling the HP VLAN driver removes the 8021q kernel module. (The problem is that the HP-supplied one is idential to the SuSE-supplied one, so it thinks it's removing the one that it installed.) I ended up re-installing the entire kernel rpm, even though I only needed the one 8021q.ko file. (There may be a way around this, but I haven't learned it.)

If you go down the path of removing the HP VLAN driver, you may also find yourself performing surgery on the PSPs so that it doesn't install in the first place, and making a custom baseline in Version Control Repository Manager so SIM doesn't tell you that you are missing a software update.

If somebody from HP driver development, QA, or support is following this forum, please enter a bug report against the PSP for SLES9. The HP bonding driver really should be removed. It's as unnecessary in SLES9 as it is in RHEL4. (The comments already mention that it's unnecessary in RHEL4.)

[Miguel A Rubio]

I have done the easy way.

One file with route commands executed on runlevels 3 4 and 5

Thanks