Showing posts with label suse. Show all posts
Showing posts with label suse. Show all posts

Jul 18, 2011

bonding in suse linux


Bonding in SUSE Enterprise Linux

Release:
SUSE Enterprise Linux 10

Problem:
Configure the bond0 interface with the interface eth0 and eth1

Solution:
1)     Create a bond0 interface file in the /etc/sysconfig/network directory.

            # vi /etc/sysconfig/network/ifcfg-bond0
           
            BONDING_MASTER='yes'
            BONDING_MODULE_OPTS='mode=1 miimon=100 use_carrier=0'
            BOOTPROTO='static'
            IPADDR='192.168.10.19'
            NETMASK='255.255.255.0'
            STARTMODE='onboot'
            USERCONTROL='no'
            BONDING_SLAVE0='bus-pci-0000:03:00.0'
            BONDING_SLAVE1='bus-pci-0000:03:00.1'

Note: “BONDING_SLAVE” value is available in the ethernet configuration file as a parameter “_nm_name” and also “mode=1” indicates active-backup policy  ( mode=0 indicates Round-robin policy).

2)     configure both the ethernet interface eth0 and eth1 like below

            # vi /etc/sysconfig/network/ifcfg-eth-id-xx:xx:xx:xx:xx:xx

            BOOTPROTO='none'
            STARTMODE='off'
            USERCONTROL='no'
                                        
3)     Restart the network service

            # service network restart

4)     To check the status of the bond0 interface use the below command

            # cat /proc/net/bonding/bond0






Jul 7, 2011

Manually Load Driver in initrd on SUSE

Manually Load Driver in initrd on SUSE Server


Release:

SUSE Linux Enterprise Server 10 SP2

Problem:

Need to manually add the hba card (fibre card) driver in initrd image

Solution:

1)      Load the required driver temporarily using the modprobe command

            # modprobe -v qla2xxx

2)      Check weather the driver module is loaded or not by using lsmod
           
                # lsmod | grep qla

3)      Add the new driver module entry in the kernel file

                # vi /etc/sysconfig/kernel

            INITRD_MODULES="ata_piix mptsas processor thermal fan jbd ext3 edd qla2xxx"

4)      Now recreate the initrd image using the below command.

                # mkinitrd -k /boot/vmlinux-2.6.16.60-0.21-smp.gz -i /boot/initrd-2.6.16.60-0.21-smp

5)      Reboot the server and check weather the driver is loaded or not.
           
                # init 6

       # lsmod | grep qla



Jan 5, 2011

Enable XDMCP in Linux


Enable XDMCP in Linux

Release:
RedHat Enterprise Linux 5
SUSE Linux 10

Problem:
Need to enable the xdmcp protocol in the Linux server for getting remote using XBrowser.

Solution:

In RHEL Server:

1)      Install the gdm package
# yum install gdm

2)      Enable the xdmcp protocol by adding the below entries in the custom.conf file.
# vi /etc/gdm/custom.conf
[security]
AllowRemoteRoot=true
DisallowTCP=false

[xdmcp]
Enable=true

Note: Here “AllowRemoteRoot=true” used to allow root access.

3)      Restart the gdm service
# gdm-restart

4)      Check weather xdmcp port is opened or not, using netstat command
# netstat –an | grep 177
udp        0      0 0.0.0.0:177         0.0.0.0:*  

In SUSE Server:

5)      Install the required 2 packages
# yum install gdm xorg-x11

6)      Set the default display manager by editing the displaymanager file
# vi /etc/sysconfig/displaymanager
DISPLAYMANAGER="gdm"
DISPLAYMANAGER_REMOTE_ACCESS="yes"

7)      Enable the xdmcp protocol by editing the gdm.conf file

# vi /etc/opt/gnome/gdm/gdm.conf
[security]
AllowRoot=true
AllowRemoteRoot=true

[xdmcp]
Enable=true

8)      To make xdmcp listening on xdm by edit the xdm-config file
# vi /etc/X11/xdm/xdm-config
!DisplayManager.requestPort:    0

Note: Comment out this line for xdmcp listen on xdm

9)      Restart the service and check with netstat
# rcxdm restart
# netstat –an | grep 177
udp        0      0 0.0.0.0:177             0.0.0.0:*

10)   Verify from the Windows client using Xbrowser as root.