Linux For You Mate ...

If we have one network interface, eth0. And when you add IP addresses, you actually create virtual network interfaces named eth0:1, eth0:2, ...... eth0:n. How to set it on temporary basis on all OS's : #ifconfig eth0:1 up [IP address] netmask [chosen netmask, if unsure use 255.255.255.0]. You can add commands like this to your startup scripts to have them come up on reboot, but there is cleaner way which is maintioned below; How to set it Permanently basis on RHEL / CentOS : All interface configuration files are located in "/etc/sysconfig/network-scripts/". Each interface is represented by a file corresponding to ifcfg-eth<x> where <x> represents the unique interface number for that card (e.g. the first interface card is represented by ifcfg-eth0). To create an alias for that interface, you need to create a file in the format of ifcfg-eth0:<y> where <y> represents the alias number (e.g. the 2nd ip for the first card would be ifcfg-eth0:1)....

The first step is to rename the server-change /etc/sysconfig/network to match your new server name.That’s easy :) Now to the bonding driver. RHEL6 and OL 6 have deprecated /etc/modprobe.conf in favour of /etc/modprobe.d and its configuration files. It’s still necessary to tell the kernel that it should use the bonding driver for my new device, bond0 so I created a new file /etc/modprobe.d/bonding.conf with just one line in it: alias bond0 bonding That’s it, don’t put any further information about module parameters in the file, this is deprecated. The documentation clearly states “Important: put all bonding module parameters in ifcfg-bondN files”. Now I had to create the configuration files for eth0, eth1 and bond0. They are created as follows: File: ifcfg-eth0 DEVICE=eth0  BOOTPROTO=none  ONBOOT=yes  MASTER=bond0  SLAVE=yes  USERCTL=no/ File: ifcfg-eth1 DEVICE=eth1  BOOTPROTO=none  ONBOOT=yes  MASTER=bond0  SLAVE=yes ...

                     You can try below things to get it done; In RHEL / CentOS : #/sbin/ifconfig ethX promisc   (Temporary solution, You will loose setting if you reboot VM ) To set it permanently Edit file – #cat /etc/sysconfig/network-scripts/ifcfg-eth1 BOOTPROTO=static DEVICE=eth1 TYPE=Ethernet PROMISC=yes USERCTL=no PEERDNS=no HWADDR=xx:xx:xx:C8:67:0E In SLES : Temporary solution is same as above. But for permanent change edit file “ /etc/sysconfig/network/ifcfg-rth-id-xx:xx:xx:xx:xx:xx” Here you can add line “ ifconfig eth0 promisc ” OR if this doesn’t work add “ PROMISC=yes ” And to disable this mode either simply remove added line from the respective files or use command ; #/sbin/ifconfig ethX -promisc   (Temporary solution)

Version Code name Release date Supported until Desktops Servers 4.10 Warty Warthog 20 October 2004 30 April 2006 5.04 Hoary Hedgehog 8 April 2005 31 October 2006 5.10 Breezy Badger 13 October 2005 13 April 2007 6.06 LTS Dapper Drake 1 June 2006 14 July 2009 1 June 2011 6.10 Edgy Eft 26 October 2006 25 April 2008 7.04 Feisty Fawn 19 April 2007 19 October 2008 7.10 Gutsy Gibbon 18 October 2007 18 April 2009 8.04 LTS Hardy Heron 24 April 2008 12 May 2011 April 2013 8.10 Intrepid Ibex 30 October 2008 30 April 2010 9.04 Jaunty Jackalope 23 April 2009 23 October 2010 9.10 Karmic Koala 29 October 2009 30 April 2011 10.04 LTS Lucid Lynx 29 April 2010 April 2013 April 2015 10.10 Maverick Meerkat 10 October 2010 April 2012 11.04 Natty Narwhal 28 April 2011 October 2012 11.10 Oneiric Ocelot 13 October 2011 April 2013 12.04 LTS Precise Pangolin 26 April 2012 [ 129 ] April 2015 April 2017 Colour Meaning Red Release no longer supported Green Release still supported Blue Futu...

Red Hat Enterprise Linux Life Cycle Overview Red Hat provides support and maintenance during the stated time periods for each of the major releases of Red Hat Enterprise Linux (RHEL), the "Life Cycle". The Life Cycle allows customers and partners to effectively plan, deploy and support Red Hat Enterprise Linux. Each major release of RHEL is denoted by a single number, i.e.: RHEL 4, RHEL 5, RHEL 6. The RHEL Life Cycle identifies the various levels of maintenance for each major release of RHEL over a total period of up to ten years from the initial release date, which is often referred to as the general availability (GA) date. The RHEL Life Cycle is designed to reduce the level of change within each major release over time, increasing predictability and decreasing maintenance costs. Red Hat published this Life Cycle in an effort to provide as much transparency as possible and may make exceptions from these policies as conflicts may arise. Software changes to RHEL are delivered...