Sponsored Content
Top Forums UNIX for Beginners Questions & Answers Why inactive slave bonding received network package in redhat? Post 303037770 by gull04 on Tuesday 13th of August 2019 07:51:15 AM
Old 08-13-2019
Hi,

It's likely to be because of the link failures on eth0, where it will fail over to eth4.

Regards

Gull04
 

10 More Discussions You Might Find Interesting

1. HP-UX

Connecting To An External Network Using A logical (PACKAGE) IP Address

Hie everyone, I am currently facing a problem whereby I can not connect to an external network from a package ip address on a HP-UX cluster. Below is the illustration: Primary Server IP Address : n.n.n.202 Secondary Server IP Address : n.n.n.212 Package IP Address : n.n.n.211 ... (1 Reply)
Discussion started by: cchilenga
1 Replies

2. SCO

master and slave in lan network

hello , i setup a lan network , but i don't know how configure master and slave in the lan network please help me:confused: (2 Replies)
Discussion started by: hossein
2 Replies

3. Red Hat

how can i get open office package for Redhat Linux 5.0

Dear Team, Any body who have idea to down load the open office package for Redhat linux 5.0. Please send me the URL. so that i can easily down load from net. (2 Replies)
Discussion started by: sahu.tapan
2 Replies

4. Red Hat

Registro Redhat Network

Buenas, Tengo 3 sistemas registrados en redhat network; hace un mes modificamos las ip's de los mismos pero en redhat network igue poniendo las antiguas. Como puedo modificarlas? tengo q registrar los sistemas de nuevo? Otra cosilla, he intentado actualizar packages y erratas: en actualizar ahora... (4 Replies)
Discussion started by: fuentepinel
4 Replies

5. Red Hat

Shutdown server when network inactive

I was referring script to shutdown server from local interface ubuntuforums.org/archive/index.php/t-2017336.html. This is scheduled in CRON. It will run every 20 minutes and check for inactivity. It compares the RX and TX packets from 20 minutes ago to detect if they significantly increased. If... (0 Replies)
Discussion started by: sanjaymp
0 Replies

6. UNIX for Dummies Questions & Answers

Redhat - network question

Hi, I am on Redhat 5. on the /etc/sysconfig/network file I don't see GATEWAY as one line. I also checked /etc/sysconfig/network-scripts/ifcfg-eth0. I don't see GATEWAY. But on the server. But when I do netstat -rn. I see many address. Is there some other settings ? ... (2 Replies)
Discussion started by: samnyc
2 Replies

7. IP Networking

Is bond0 ready and a bonding interface? - 4G Bonding Router Problems (RPI)

HI all, First post on the forum, and my first proper project on the Paspberry Pi, so sorry if this is in the wrong place. I am trying to turn my Pi in to a 3G/4G Bonding router. I have been researching and trying this for a week or so now. The basic plan is to have up to 6 ZTE MF823 USB... (0 Replies)
Discussion started by: elliottlc
0 Replies

8. Red Hat

Network Bonding Issue

I have one production system where my customized application runs.The applications require seamless network connectivity with different machines connected in LAN and WAN. As these applications are very critical, it is very much required to have a seamless network activity.The applications are... (4 Replies)
Discussion started by: Anjan Ganguly
4 Replies

9. Red Hat

Network bonding

Dear All , Very recently we have configured Network bonding in our Linux Server Redhat Linux 5.x. After configuring , we restarted the network services , the link was down after that , we could not login in to the Server. So after that , we logged in to console and tried to... (2 Replies)
Discussion started by: jegaraman
2 Replies

10. UNIX for Advanced & Expert Users

Redhat check when package was updated

Is there a way to check when a package was updated on your redhat system? (2 Replies)
Discussion started by: cokedude
2 Replies
di_link_next_by_node(3DEVINFO)			       Device Information Library Functions			    di_link_next_by_node(3DEVINFO)

NAME
di_link_next_by_node, di_link_next_by_lnode - libdevinfo link traversal functions SYNOPSIS
cc [ flag... ] file... -ldevinfo [ library... ] #include <libdevinfo.h> di_link_t di_link_next_by_node(di_lnode_t node, di_link_t link, uint_t endpoint); di_link_t di_link_next_by_lnode(di_node_t lnode, di_link_t link, uint_t endpoint); PARAMETERS
link The handle to the current the link or DI_LINK_NIL. endpoint Specify which endpoint of the link the node or lnode should correspond to, either DI_LINK_TGT or DI_LINK_SRC. node The device node with which the link is associated. lnode The lnode with which the link is associated. DESCRIPTION
The di_link_next_by_node() function returns a handle to the next link that has the same endpoint node as link. If link is DI_LINK_NIL, a handle is returned to the first link whose endpoint specified by endpoint matches the node specified by node. The di_link_next_by_lnode() function returns a handle to the next link that has the same endpoint lnode as link. If link is DI_LINK_NIL, a handle is returned to the first link whose endpoint specified by endpoint matches the lnode specified by lnode. RETURN VALUES
Upon successful completion, a handle to the next link is returned. Otherwise, DI_LINK_NIL is returned and errno is set to indicate the error. ERRORS
The di_link_next_by_node() and di_link_next_by_lnode() functions will fail if: EINVAL An argument is invalid. ENXIO The end of the link list has been reached. The di_link_next_by_node() function will fail if: ENOTSUP Device usage information is not available in snapshot. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ |MT-Level |Safe | +-----------------------------+-----------------------------+ SEE ALSO
di_init(3DEVINFO), libdevinfo(3LIB), attributes(5) SunOS 5.10 12 Jul 2004 di_link_next_by_node(3DEVINFO)
All times are GMT -4. The time now is 09:40 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy