I have server that has a 10g card in it. I need to configure that server so that for a particular IP address (172.16.2.62) traffic goes over two 10g Ports. Here are the rules I have created for that purpose. If I do not setup a rule all traffic will go to Eth0 by default.
Rules for 172.16.2.62 [17:13:01] shock:~ # ip rule show |grep 172.16.2.62
60: from all to 172.16.2.62 lookup eth4
61: from all to 172.16.2.62 lookup eth3
However it seems that only the rule for Eth4 is being implemented [17:13:45] shock:~ # ip route get 172.16.2.62
172.16.2.62 via 172.16.1.1 dev eth4 src 172.16.2.177
cache mtu 1500 advmss 1460 hoplimit 64
As you can see ping will not go out Eth3 to 172.16.2.62
[17:18:02] shock:~ # ping -I eth3 172.16.2.62
PING 172.16.2.62 (172.16.2.62) from 172.16.2.175 eth3: 56(84) bytes of data. ^C --- 172.16.2.62 ping statistics --- 8 packets transmitted, 0 received, 100% packet loss, time 7707ms
[17:18:54] shock:~ # ping -I eth4 172.16.2.62
PING 172.16.2.62 (172.16.2.62) from 172.16.2.177 eth4: 56(84) bytes of data. 64 bytes from 172.16.2.62: icmp_seq=1 ttl=64 time=3.96 ms
Yet Eth3 works for other IPs not setup in the Rules (Notice I am pinging 172.16.1.1 and not 172.16.2.62)
[17:21:02] shock:~ # ping -I eth3 172.16.1.1
PING 172.16.1.1 (172.16.1.1) from 172.16.2.175 eth3: 56(84) bytes of data. 64 bytes from 172.16.1.1: icmp_seq=1 ttl=255 time=0.438 ms
Lastly here is the routing Table.
[17:24:27] shock:~ # netstat -rn Kernel IP routing table
Our Dev teams are like yours. They’re continually cranking out code for new features/bugs fixes, testing, deploying, testing some more, responding to production monitoring events and more. It’s complex. So, we thought you’d like to see what’s working for us.
This article is in response to a question (http://www.experts-exchange.com/Networking/Network_Management/Network_Analysis/Q_28230497.html) here at Experts Exchange. The Original Poster (OP) requires a utility that will accept a list of IP addresses …
David Varnum recently wrote up his impressions of PRTG, based on a presentation by my colleague Christian at Tech Field Day at VMworld in Barcelona.
Thanks David, for your detailed and honest evaluation!
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail. The methods are covered in more detail in o…
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg).
If you're looking for how to monitor bandwidth using netflow or packet s…