• Learning Map
  • Unix Quiz Center
  • Unix Professional Network
  • Just-Unix-No-Noise FB Group

unixadminschool.com

  • Home
  • Announcements
    • Feed
    • MISC
  • Beginners zone
    • Beginners Lessons
    • Career Guidance
  • Experts Zone
    • Cloud Computing
    • Configuration Solutions
    • Migrations
    • Network Design
    • Scripting
    • Server Security
    • SUN CLUSTERS
    • SUN LDOMS
    • Tools & Applications
    • Veritas Cluster Services ( VCS ) Learning
  • Intermediate Zone
    • Linux Learning
      • Linux Booting
      • Linux Disk Management
      • Linux LVM
      • Linux Networking
      • Linux Performance
      • Linux Troubleshooting
      • Linux YUM/RPM
      • Performance Analysis
      • Redhat Linux Kernel
      • RHEL 6
        • RHEL LDAP
        • Rhel6 Storage
      • Web Servers
    • Solaris Admin
      • Blog for Unix Admin
        • Storage Administration – SAN
      • Oracle Hardware
      • Reference Docs
      • Solaris 10 Zones & LDOMs
      • Solaris 11
      • Solaris Access Control
      • Solaris Best Practices
      • Solaris Booting
      • Solaris Disk Management
      • Solaris DNS
      • Solaris How-to
      • Solaris Installation
      • Solaris Kernel
      • Solaris Networking
      • Solaris NFS
      • Solaris NIS
      • Solaris Packages & Patching
      • Solaris Performance
      • Solaris Tips
      • Solaris Troubleshooting
      • Solaris User Authentication
      • solaris X86
      • Solaris ZFS and Boot Environment
      • Storage Configurations
      • SUN Hardware
      • Troubleshooting Flow charts
    • Veritas Admin
      • Veritas Netbackup
      • VxVM Learning
      • VxVM Troubleshooting
  • QUIZ Center
  • Vlabs
  • Unix Magazine

Subscribe

Redhat Enterprise Linux – Network Bonding – Quick Reference ( RHEL5 / RHEL6)

 

Bonding is a feature that can be enabled bu the Linux kernel, to allow system administrators to combine two or more network interface to form a single, logical “bonded” interface, for redundancy or increased throughput purpose.

We can configure Linux bonding in 7 different modes. The behavior of the bonded interfaces depends upon the mode.

Below are the available bonding modes

 

 

 

 

  • Balance-rr (mode 0)
  • Active-backup (mode 1)
  • Balance-xor (mode 2)
  • Broadcast (mode 3)
  • 802.3ad (mode 4)
  • Balance-tlb (mode 5)
  • Balance-alb (mode 6) Full Story

Ramdev
8 Comments

Linux Network Troubleshooting

Network connection problems include slow connections, as well as complete loss of connectivity. Factors that may cause slow connectivity include incorrectly configured domain name system (DNS) settings, inefficiently configured routing tables, inferior cabling, overloaded servers, and network congestion. The same set of factors, as well as power or server failures, may result in complete loss of connectivity.

To troubleshoot a network connectivity problem, you should first check for the presence of a physical connection. If the network interface card (NIC) link light on a system is off, it indicates that no physical connection exists. This may result from

the use of incompatible or damaged cables
loose or unplugged cables
loss of power to a network switch or router
Troubleshooting interface problems

Linux tools you can use to troubleshoot network interface problems include

  • ifconfig -  Used to determine the status of NICs.Without arguments, this command returns the status of all active interfaces. If you specify the name of an interface, it returns the status only of that interface. With the -a argument, the command displays the status of all interfaces on a computer, including any that may be inactive. This is the basic syntax for using the ifconfig command: ifconfig [interface] [options]
  • mii-tool – The mii-tool utility enables you to display and manipulate the media-independent interface status. In its simplest form, you can use it to display the status of the interface’s link. This is the basic syntax for using the mii-tool command: mii-tool [options] [interface]
  • ethtool – The ethtool utility is a diagnostic tool that enables you to configure and diagnose problems with NICs. However, not all NICs support its use. This is the basic syntax for using the ethtool command: ethtool [options] interface Full Story

Ramdev
7 Comments
Tagged with: [ linux, linux learning, linux network, linux network error, linux troubleshooting, Redhat linux ]

Network Physical Connectivity Check for Solaris and Linux

Network connectivity checks For the server without OS  ( just Racked hardware and powered up)

 

For X86 Hardware

We have to make LED checks – like when we disconnect the cable at the server side / switch side the Link / Act LEDs should lit up on powered on machines.

For Sparc based Servers:

We can watch individual interfaces to see if they have a connection and can ‘see’ the network. At the OBP prompt on the client, use the “watch-net-all” command to test and see the network devices.

Full Story

Ramdev
11 Comments
Tagged with: [ linux error, linux networking, linux trooublesthooing, solaris error, solaris networking, Solaris Troubleshooting ]

Redhat Linux : Collect System Diagnosis report for the Support Call purpose

Red Hat Enterprise Linux 4.5 and previous

On a default installation the package Sysreport should be already installed. If not you need to install the package “sysreport-.rpm” with the following command

# rpm -ivh sysreport-.rpm

or, if your system is registered at the Red Hat Network “RHN”, simply running

# up2date -i sysreport

This will install the latest version of Sysreport on your system.

To collect the information you need to start troubleshooting just enter the command

# sysreport

and follow the instructions on screen. At the end you get a filename and the location where to find the compressed information collected by this script. Please keep this data for further support.

Please note that Sysreport will need some time to collect all the data, depending on the speed of the system and how many packages are installed.

In cases you experience that Sysreport seems to hang and will not return after a while, you may pass the parameter “-norpm” to the command. This will skip the checking of the RPM database which may be broken. Full Story

Ramdev
15 Comments

Linux Troubleshooting – Root Password Reset

The General problem that we see in an enterprise environment, where there is no centralized automated password management tool is  …. missing root passwords for the servers.

Missing root passwords are also common when the servers initially managed by one team and later handed over to other team, but not all the changes to root passwords are not handed over to new teams. Full Story

Ramdev
Comment

RHEL 5 Linux : configure Kdump on Red Hat Enterprise Linux 5

Installing required packages

RHEL 5 has the Kdump packages installed by default. If for any reason they are not installed, you need to install the packages “kexec-tools-.rpm” and “system-config-kdump-.rpm” with the following commands:

 

# rpm -ivh kexec-tools-.rpm system-config-kdump-.rpm

or, if your system is registered at the Red Hat Network, by running

# yum install kexec-tools system-config-kdump

Configuration of Kdump

First you need to enable Kdump. There is a configuration dialog available which can be started under a graphical environment by using:

# system-config-kdump

Please check the option box “Enable kdump” at the top of the Dialog.

Next, you have to define the memory to reserve for Kdump In the dialog you see the memory information for your system and the usable memory for Kdump. On most systems a value of “128MB” Kdump memory should be enough.

Finally, you need to define a location where to store the dump file. You have the choice between “file”, “nfs”, “ssh”, “raw”, “ext2″, and “ext3″. This setup is straight forward, please configure the kdump as it fit’s best into your environment. The simplest configuration for the location is “file:///var/crash“.

You need to take care that you have enough disk space on the configured location, at least the physically memory of the system which is expected to dumped.

After you have configured kdump, you need to reboot the system to activate the settings.

More information about the configuration can be found in the file “/usr/share/doc/kexec-tools-*/kexec-kdump-howto.txt“

Full Story

Ramdev
Comment
Tagged with: [ boot, error, Kdump, kernel dump, kernel panic, linux, rhel5 ]
Pages1 2

  • About Author : My name is Ramkumar Ramadevu ( Ramdev ). I have started writing about enterprise unix system administration since 2009 just for my own knowledge reference, and then later I have made this site available for everyone, for better purpose. ... read more

  • Advertise Here Your Video Ad Here
  • Recent Comments

    • Ramdev commented :: Rahul, welcome to unixadminschool.Thanks for the message....
    • Rahul commented :: Awesome Ram, i came to know about this Blog 2 days and go through a...
    • Ramdev commented :: Hi Prajwala, I am glad that you like it :)...
    • Ramdev commented :: Pavan, the below command mentioned in this doc to show how much pemlen...
    • Ramdev commented :: pleae try      --             share -F nfs -o rw=oracle:root /filesyst...
    • Ramdev commented :: Hi Jack, the cfgadm you have to do it anyway to  make sure the disk i...
    • Maniswara Pavan commented :: Nice Post .........
    • Maniswara Pavan commented :: Hi Ram, I have a doubt here .. Lets think we have disk and its pr...
    • jack commented :: Do we need to initialize and configure the replaced disk in this proce...
    • Laxxi commented :: Hi Ram, Please guide me how can I provide Read write access to a Fs...
  • Latest Posts

    • Virtual Lab : Get Your hands dirty with grep & RegEx
    • Quiz – Redhat Linux Intermediate Skills
    • Solaris Quiz – Managing Filesystems and Disk Devices
    • Test Your Understanding about Linux Fundamentals
    • Solaris Quiz – System Startup and Shutdown
    • Solaris Quiz – Software Management
    • RHEL 6 – ISCSI Administration Series – ISCSI Lun resize
    • RHEL 6 – ISCSI Administration Series – Configuring ISCSI Server and Client
    • SAN Storage Migration – Solaris with VxVM
    • RHEL 6.3 – LDAP Series – Part 4 : Troubleshooting
    • RHEL 6.3 – LDAP Series – Part 3 : LDAP Configuration With Encrypted Communication using TLS/SSL
    • RHEL 6.3 – LDAP Series – Part 2 : Configuration of Certification Authority for LDAP encryption.
    • RHEL 6.3 – LDAP Series – Part 1 : Implementation of LDAP Authentication
    • [ Updated with Analysis ] – Finding the Linux Performance Bottleneck !!!
    • VxVM Troubleshooting – Increasing the Size of Veritas Disk Private Region
    • Virtualization for Unix Administrators
    • VCS Learning – I/O Fencing In action [ Video ]
    • VCS Learning : Learn about Cluster Hearbeats
    • Happy New Year 2013, Thank You. >
    • Storage Operations – VxVM vs RHEL LVM2
    • Veritas Netbackup : Unable to detect Robot from master server after Veritas Netbackup upgrade to 7.1.0.4.
    • A tool that changes the way of system administration – PUPPET ( from puppetlabs)
    • Redhat Enterprise Linux : Yum Quick Reference
    • Redhat Enterprise Linux – Network Bonding – Quick Reference ( RHEL5 / RHEL6)
    • Redhat Enterprise Linux Networking Troubleshooting – Quick Reference
    • RedHat Linux Grub Loader – FAQ and Quick Reference
    • Redhat Linux LVM – FAQ & Quick Reference
    • RedHat Linux Kernel – FAQ and Quick Reference
    • Solaris host level SAN migration from Clariion to VMAX – Hands on Lab
    • Linux Samba Server integration with Windows Active Directory – Part 2
  • Site Members

    • Log in
Copyright © 2009 unixadminschool.com. All rights reserved.