high ping and ip forwarding unstable

SUSE Linux Enterprise Server SLES Networking
1

Hi!

Problem with high ping 1ms to 500ms at no traffic to the server (even if I just have one network cabel connected)
also problem to ping from a client on 10.0.3.X to 10.0.1.2 (or any other machine on 10.0.1.x network) , but it can ping a to 10.0.32.x network from the same client and so on…
can ping all the servers NICs ip.
The network side in the feels unstable…
unable to install edirectory on it, and when that didn’t i tried to get a dhcp proxy to work on the machine… but NO…

Are there any known issues with this NIC:s or server… or OS
or anything I have missed ?

I just want the server as a router with a DHCP/DNS server on…

I have this new server: (good on paper but…)
Dell PowerEdge R520
-2INTEL XEON E5-2420
-4DELL 4GB DDR3-1333 RDIMM LV 2RX8 ECC
-2DELL 300GB 15K 6G SAS HOT-PLUG 3.5" HDD
-2DELL GIGABIT ET QUAD PORT NIC PCIE INTEL 82576
-1DELL GIGABIT ET DUAL PORT NIC PCIE INTEL 82576
-2 st Gigabit onboard Broadcom BCM5720
-1DELL PERC H710P/1GB

should be latest firmwares

Installed the OES11sp1WithSLES11sp2 with no extra.

configured all NIC:s and enabled IP forwading

sahs2:~ # netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 10.0.1.20 0.0.0.0 UG 0 0 0 em1
10.0.1.0 0.0.0.0 255.255.255.0 U 0 0 0 em1
10.0.2.0 0.0.0.0 255.255.255.0 U 0 0 0 p2p1
10.0.3.0 0.0.0.0 255.255.255.0 U 0 0 0 em2
10.0.4.0 0.0.0.0 255.255.255.0 U 0 0 0 p2p3
10.0.5.0 0.0.0.0 255.255.255.0 U 0 0 0 p2p4
10.0.7.0 0.0.0.0 255.255.255.0 U 0 0 0 p3p2
10.0.10.0 0.0.0.0 255.255.255.0 U 0 0 0 p3p3
10.0.20.0 0.0.0.0 255.255.255.0 U 0 0 0 p3p4
10.0.32.0 0.0.0.0 255.255.255.0 U 0 0 0 p2p2
10.0.40.0 0.0.0.0 255.255.255.0 U 0 0 0 p3p1
10.0.50.0 0.0.0.0 255.255.255.0 U 0 0 0 p4p2
10.0.100.0 0.0.0.0 255.255.255.0 U 0 0 0 p4p1
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo

and

sahs2:~ # ifconfig
em1 Link encap:Ethernet HWaddr 90:B1:1C:16:52:A4
inet addr:10.0.1.34 Bcast:10.0.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:28573 errors:0 dropped:107 overruns:0 frame:0
TX packets:100850 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4808084 (4.5 Mb) TX bytes:57961866 (55.2 Mb)
Interrupt:16

em2 Link encap:Ethernet HWaddr 90:B1:1C:16:52:A5
inet addr:10.0.3.2 Bcast:10.0.3.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4874 errors:0 dropped:1 overruns:0 frame:0
TX packets:344 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1093272 (1.0 Mb) TX bytes:56842 (55.5 Kb)
Interrupt:17

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:108876 errors:0 dropped:0 overruns:0 frame:0
TX packets:108876 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:83338170 (79.4 Mb) TX bytes:83338170 (79.4 Mb)

p2p1 Link encap:Ethernet HWaddr 90:E2:BA:28:3A:08
inet addr:10.0.2.2 Bcast:10.0.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:19 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:878 (878.0 b)

p2p2 Link encap:Ethernet HWaddr 90:E2:BA:28:3A:09
inet addr:10.0.32.2 Bcast:10.0.32.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:677810 errors:0 dropped:2 overruns:0 frame:0
TX packets:1690 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:42647547 (40.6 Mb) TX bytes:182940 (178.6 Kb)

p2p3 Link encap:Ethernet HWaddr 90:E2:BA:28:3A:0C
inet addr:10.0.4.2 Bcast:10.0.4.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2283 errors:0 dropped:0 overruns:0 frame:0
TX packets:394 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1069134 (1.0 Mb) TX bytes:48558 (47.4 Kb)

p2p4 Link encap:Ethernet HWaddr 90:E2:BA:28:3A:0D
inet addr:10.0.5.2 Bcast:10.0.5.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1928 errors:0 dropped:0 overruns:0 frame:0
TX packets:164 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1011151 (987.4 Kb) TX bytes:7636 (7.4 Kb)

p3p1 Link encap:Ethernet HWaddr 90:E2:BA:28:39:C0
inet addr:10.0.40.2 Bcast:10.0.40.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:215 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:9130 (8.9 Kb)

p3p2 Link encap:Ethernet HWaddr 90:E2:BA:28:39:C1
inet addr:10.0.7.2 Bcast:10.0.7.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1854 errors:0 dropped:0 overruns:0 frame:0
TX packets:126 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1013606 (989.8 Kb) TX bytes:5372 (5.2 Kb)

p3p3 Link encap:Ethernet HWaddr 90:E2:BA:28:39:C4
inet addr:10.0.10.2 Bcast:10.0.10.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1919 errors:0 dropped:0 overruns:0 frame:0
TX packets:1667 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:317612 (310.1 Kb) TX bytes:172174 (168.1 Kb)

p3p4 Link encap:Ethernet HWaddr 90:E2:BA:28:39:C5
inet addr:10.0.20.2 Bcast:10.0.20.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1310 errors:0 dropped:0 overruns:0 frame:0
TX packets:467 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:151700 (148.1 Kb) TX bytes:34318 (33.5 Kb)

p4p1 Link encap:Ethernet HWaddr 90:E2:BA:28:56:24
inet addr:10.0.100.2 Bcast:10.0.100.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:186 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:7812 (7.6 Kb)

p4p2 Link encap:Ethernet HWaddr 90:E2:BA:28:56:25
inet addr:10.0.50.2 Bcast:10.0.50.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:180 errors:0 dropped:0 overruns:0 frame:0
TX packets:570 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:19242 (18.7 Kb) TX bytes:23940 (23.3 Kb)

cat /etc/resolv.conf

/etc/resolv.conf file autogenerated by netconfig!

Before you change this file manually, consider to define the

static DNS configuration using the following variables in the

/etc/sysconfig/network/config file:

NETCONFIG_DNS_STATIC_SEARCHLIST

NETCONFIG_DNS_STATIC_SERVERS

NETCONFIG_DNS_FORWARDER

or disable DNS configuration updates via netconfig by setting:

NETCONFIG_DNS_POLICY=’’

See also the netconfig(8) manual page and other documentation.

Note: Manual change of this file disables netconfig too, but

may get lost when this file contains comments or empty lines

only, the netconfig settings are same with settings in this

file and in case of a “netconfig update -f” call.

Please remove (at least) this line when you modify the file!

search sahd.aland.fi
nameserver 10.0.1.2

2

I’m not sure I completely understand the problems in their entirety. It
sounds like you are experiencing inconsistent connections and maybe high
latency in ICMP (the ping) packets.

Could you show us the ping command output and maybe describe where the
other side is physically/logically for each set? Also, have you tried
capturing traffic to see if anything is showing up but no getting back for
some reason?

Code:

sudo /usr/sbin/tcpdump -n -s 0 -v

Each time something pings you should see it like this:

Code:

15:00:58.802450 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto
ICMP (1), length 84)
192.168.1.3 > 192.168.1.202: ICMP echo request, id 10584, seq 1, length 64

15:00:58.802774 IP (tos 0x0, ttl 64, id 8556, offset 0, flags [none],
proto ICMP (1), length 84)
192.168.1.202 > 192.168.1.3: ICMP echo reply, id 10584, seq 1, length 64

Having tcpdump run on the other side as well to be sure that the reply
from this box makes it back may be worthwhile.

Out of curiosity are you using OES vs. just SLES for some reason? There
are good reasons to do so, but otherwise using SLES alone may be simpler.
Which OES components, if any, did you install? What does
“OES11sp1WithSLES11sp2 with no extra” mean?

Good luck.

3

[QUOTE=ab;14140]I’m not sure I completely understand the problems in their entirety. It
sounds like you are experiencing inconsistent connections and maybe high
latency in ICMP (the ping) packets.

Could you show us the ping command output and maybe describe where the
other side is physically/logically for each set? Also, have you tried
capturing traffic to see if anything is showing up but no getting back for
some reason?

Code:

sudo /usr/sbin/tcpdump -n -s 0 -v

Each time something pings you should see it like this:

Code:

15:00:58.802450 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto
ICMP (1), length 84)
192.168.1.3 > 192.168.1.202: ICMP echo request, id 10584, seq 1, length 64

15:00:58.802774 IP (tos 0x0, ttl 64, id 8556, offset 0, flags [none],
proto ICMP (1), length 84)
192.168.1.202 > 192.168.1.3: ICMP echo reply, id 10584, seq 1, length 64

Having tcpdump run on the other side as well to be sure that the reply
from this box makes it back may be worthwhile.

Out of curiosity are you using OES vs. just SLES for some reason? There
are good reasons to do so, but otherwise using SLES alone may be simpler.
Which OES components, if any, did you install? What does
“OES11sp1WithSLES11sp2 with no extra” mean?

Good luck.[/QUOTE]

Thanks for the reply , the communication error I had was a typo in a routing tabell.

The dhcp proxy is now working (I have the old DHCP server in use until I can install Novell-DHCP server on this server)

The high latency in ICMP when I ping the server is still there…
and I can’t still install eDir. (but that can be a CA problem)

I using OES because I want to have the Replica masters on this server (if it’s stable).

and I want the Novell-dhcp server.

With no “extra” I meant default settings.

Br
Matias

4

As I understand it the remaining issue is high latency when pinging this
box from another box. Try a couple of things. First, run a LAN trace
both on this box as well as the client machine from which you are pinging
this box. The following command should do it assuming tcpdump is installed:

Code:

sudo /usr/sbin/tcpdump -n -s 0 -i any -w /tmp/server0.cap icmp #on server

sudo /usr/sbin/tcpdump -n -s 0 -i any -w /tmp/client0.cap icmp #on client

Let ping run for a bit… a minute or two perhaps, and then use Ctrl+C to
stop the command; post the /tmp/*.cap files from each box somewhere after
tarring them up together. These should not be too big.

Also, try something else like copying a file from one box to another using
scp (Secure CoPy, or copying via SSH) just to see how long it takes to do
something big. On the client side generate a decent-sized file:

Code:

dd if=/dev/zero of=/tmp/1gib bs=1048576 count=0 seek=1024
scp /tmp/1gib root@server:/tmp

Post the output showing the transmission speed. On a gigabit network you
might get up around 100 MiB/second; theoretical max is 120 but usually
errors on the way prevent that. If you are running at gigabit with
nothing else interfering you should definitely get higher than 50.

Finally, post the output from the ‘ip addr’ command on the server.

Good luck.

5

hm…

How can I attach files to a post in this forum?

Br
Matias

6

Choose ‘Go Advanced’ when replying to this post, then there is a button
for attachments. Use compression to get relevant files in there, please.

Good luck.