05-31-2006
network redundancy with software
Here we want to implement the network redundancy on UNIX with the software.
The two network interface cards are configured on the UNIX node,once one card is down or unnormal,the other can take over. Those aplications that used the tcp ,udp,multicast protocol can also been switched at the same time.
The question is :
1. how to monitor the network interface card is falied.(niff daemon might been ok?)
2. How to monitor the network traffic ?(include the switch port)
3. Once find the card failed or network traffic was high, are there any good ideas to switch the application?
If not the above, any other suggestions?
By the way, the above implementation should be finished with the programing instead of hardware.
Thanks
3 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi guys,
I'm not very familiar with UNIX.. still have a lot to learn. I also
interested in Networking... Can anyone tell me what are the tool or software for network administration which we can monitor our network activities such as network traffic analysis,can capture and decode network... (2 Replies)
Discussion started by: Nucleus
2 Replies
2. UNIX for Dummies Questions & Answers
hi
can i know if there is any GUI interface software to help in monitoring the network of the servers i have? something like a web pages or a stock pages when a processes is down, a red colour is flashes. best if it is free ;) (1 Reply)
Discussion started by: legato
1 Replies
3. IP Networking
We are a small legal firm in the UK and looking to upgrade from some open source network management tools we are using.
I'm not finding very many commercially supported network management software solutions that run on Linux or UNIX for that matter.
Does anyone have any recommendations?
... (2 Replies)
Discussion started by: ctrenton
2 Replies
LEARN ABOUT LINUX
network_namespaces
NETWORK_NAMESPACES(7) Linux Programmer's Manual NETWORK_NAMESPACES(7)
NAME
network_namespaces - overview of Linux network namespaces
DESCRIPTION
Network namespaces provide isolation of the system resources associated with networking: network devices, IPv4 and IPv6 protocol stacks, IP
routing tables, firewall rules, the /proc/net directory (which is a symbolic link to /proc/PID/net), the /sys/class/net directory, various
files under /proc/sys/net, port numbers (sockets), and so on. In addition, network namespaces isolate the UNIX domain abstract socket
namespace (see unix(7)).
A physical network device can live in exactly one network namespace. When a network namespace is freed (i.e., when the last process in the
namespace terminates), its physical network devices are moved back to the initial network namespace (not to the parent of the process).
A virtual network (veth(4)) device pair provides a pipe-like abstraction that can be used to create tunnels between network namespaces, and
can be used to create a bridge to a physical network device in another namespace. When a namespace is freed, the veth(4) devices that it
contains are destroyed.
Use of network namespaces requires a kernel that is configured with the CONFIG_NET_NS option.
SEE ALSO
nsenter(1), unshare(1), clone(2), veth(4), proc(5), sysfs(5), namespaces(7), user_namespaces(7), brctl(8), ip(8), ip-address(8), ip-
link(8), ip-netns(8), iptables(8), ovs-vsctl(8)
Linux 2018-02-02 NETWORK_NAMESPACES(7)