RHEL7 how to configure NIC Teaming as Active Backup (Failover)

', enableHover: false, enableTracking: true, buttons: { twitter: {via: 'aravikumar48'}}, click: function(api, options){ api.simulateClick(); api.openPopup('twitter'); } }); $('#facebook').sharrre({ share: { facebook: true }, template: '
', enableHover: false, enableTracking: true, buttons:{layout: 'box_count'}, click: function(api, options){ api.simulateClick(); api.openPopup('facebook'); } }); $('#pinterest').sharrre({ share: { pinterest: true }, template: '
', enableHover: false, enableTracking: true, buttons: { pinterest: { description: 'RHEL7 how to configure NIC Teaming as Active Backup (Failover)',media: 'https://arkit.co.in/wp-content/uploads/2016/03/NicTeaming-Linux.png' } }, click: function(api, options){ api.simulateClick(); api.openPopup('pinterest'); } }); $('#linkedin').sharrre({ share: { linkedin: true }, template: '
', enableHover: false, enableTracking: true, buttons: { linkedin: { description: 'RHEL7 how to configure NIC Teaming as Active Backup (Failover)',media: 'https://arkit.co.in/wp-content/uploads/2016/03/NicTeaming-Linux.png' } }, click: function(api, options){ api.simulateClick(); api.openPopup('linkedin'); } }); // Scrollable sharrre bar, contributed by Erik Frye. Awesome! var $_shareContainer = $(".sharrre-container"), $_header = $('#header'), $_postEntry = $('.entry'), $window = $(window), startSharePosition = $_shareContainer.offset(),//object contentBottom = $_postEntry.offset().top + $_postEntry.outerHeight(), topOfTemplate = $_header.offset().top, topSpacing = _setTopSpacing(); //triggered on scroll shareScroll = function(){ var scrollTop = $window.scrollTop() + topOfTemplate, stopLocation = contentBottom - ($_shareContainer.outerHeight() + topSpacing); $_shareContainer.css({position : 'fixed'}); if( scrollTop > stopLocation ){ $_shareContainer.css( { position:'relative' } ); $_shareContainer.offset( { top: contentBottom - $_shareContainer.outerHeight(), left: startSharePosition.left, } ); } else if (scrollTop >= $_postEntry.offset().top - topSpacing){ $_shareContainer.css( { position:'fixed',top: '100px' } ); $_shareContainer.offset( { //top: scrollTop + topSpacing, left: startSharePosition.left, } ); } else if (scrollTop 1024 ) { topSpacing = distanceFromTop + $('.nav-wrap').outerHeight(); } else { topSpacing = distanceFromTop; } return topSpacing; } //setup event listeners $window.on('scroll', _.throttle( function() { if ( $window.width() > 719 ) { shareScroll(); } else { $_shareContainer.css({ top:'', left:'', position:'' }) } }, 50 ) ); $window.on('resize', _.debounce( function() { if ( $window.width() > 719 ) { shareMove(); } else { $_shareContainer.css({ top:'', left:'', position:'' }) } }, 50 ) ); });

ARK

My Name is ARK. Expert in grasping any new technology, Interested in Sharing the knowledge. Learn more & Earn MoreView all Posts

2 Responses

  1. Hello. I noticed a serious problem that needs your attention: How to configure automatic recovery of a failed port in RHEL7.0 teaming ? I successfully configured teaming by following the above procedure, in a RHEL 7.0 server. The failover from port1 to port2 (from main to backup) was also successful by just applying the commands mentioned in your procedure, but when I tried to failover again from port2 to port1 (from backup to main), it was not possible. I found port1 still in a failed state and I had to recover it up manually. This is a big problem because if the backup also fails, the network will remain in a failed state and never recovers. So is there a solution to this problem: a command to (try to) immediately recover (stimulate) a failed port after a failover, so that it becomes soon ready to switch back to main (active) again if/when necessary. This means the config must always try keeping both ports UP so that failover never fails. Thanks.

  2. Julie says:

    BIG thank you for these perfect tutorial !!!

Leave a Reply

Your email address will not be published. Required fields are marked *

Exit mobile version