On 10/27/11 11:07 AM, Marcy Cortes wrote: > Offer, I do get the erratic pings too. Not as high as 200, but some 50s. > > It was reported to me a few weeks ago by one of our more sophisticated users > that traceroute occasionally fails over the same vswitch. > Run it like 20 times 1 right after another to recreate or use the -q option > with something like -q 8. > > I checked with another customer and he also saw the same behavior. > > I opened a PMR with VM but they said to open one with Linux. I have not > gotten around to opening one with Novell yet. > > Could some of you others out there try this simple ping test? > > We are also vlan aware and it does happen on both LACP and non-LACP. > We have both aware and unaware VSWITCHes.
Results of two guests connected to the same aware VSWITCH and on the same VLAN: pzawap01:~ # traceroute pzawap03 traceroute to pzawap03 (172.2.2.211), 30 hops max, 40 byte packets 1 pzawap03.svc (172.2.2.211) 0.114 ms 0.134 ms 0.016 ms pzawap01:~ # traceroute pzawap03 traceroute to pzawap03 (172.2.2.211), 30 hops max, 40 byte packets 1 pzawap03.svc (172.2.2.211) 0.055 ms 0.136 ms 0.024 ms pzawap01:~ # traceroute pzawap03 traceroute to pzawap03 (172.2.2.211), 30 hops max, 40 byte packets 1 pzawap03.svc (172.2.2.211) 0.000 ms * * Results of two guests connected to the same unaware VSWITCH: pzsdns01:~ # traceroute 192.1.1.28 traceroute to 192.1.1.28 (192.1.1.28), 30 hops max, 40 byte packets 1 192.1.1.28 (192.1.1.28) 0.199 ms 0.036 ms 0.074 ms pzsdns01:~ # traceroute 192.1.1.28 traceroute to 192.1.1.28 (192.1.1.28), 30 hops max, 40 byte packets 1 192.1.1.28 (192.1.1.28) 0.189 ms 0.492 ms * pzsdns01:~ # traceroute 192.1.1.28 traceroute to 192.1.1.28 (192.1.1.28), 30 hops max, 40 byte packets 1 192.1.1.28 (192.1.1.28) 0.140 ms 0.038 ms 0.087 ms pzsdns01:~ # traceroute 192.1.1.28 traceroute to 192.1.1.28 (192.1.1.28), 30 hops max, 40 byte packets 1 192.1.1.28 (192.1.1.28) 0.244 ms 0.044 ms 0.026 ms pzsdns01:~ # traceroute 192.1.1.28 traceroute to 192.1.1.28 (192.1.1.28), 30 hops max, 40 byte packets 1 * * * 2 * * * 3 * * * 4 * * * 5 * * * 6 * * * 7 192.1.1.28 (192.1.1.28) 0.306 ms 0.196 ms 0.286 ms Results from a guest on an unaware VSWITCH to a guest on a different unaware VSWITCH (same LPAR) pzsdns01:~ # traceroute pzsadm01 traceroute to pzsadm01 (172.1.1.35), 30 hops max, 40 byte packets 1 192.1.1.1 (192.1.1.1) 0.289 ms 0.254 ms 0.230 ms 2 pzsadm01.svc (172.1.1.35) 0.271 ms 0.311 ms 0.324 ms pzsdns01:~ # traceroute pzsadm01 traceroute to pzsadm01 (172.1.1.35), 30 hops max, 40 byte packets 1 192.1.1.1 (192.1.1.1) 0.320 ms 0.276 ms 0.682 ms 2 pzsadm01.svc (172.1.1.35) 0.321 ms 0.263 ms 0.296 ms pzsdns01:~ # traceroute pzsadm01 traceroute to pzsadm01 (172.1.1.35), 30 hops max, 40 byte packets 1 192.1.1.1 (192.1.1.1) 0.322 ms 0.278 ms 0.259 ms 2 * * * 3 * * * 4 * * * 5 * * * 6 pzsadm01.svc (172.1.1.35) 0.755 ms * * Results from a guest on an aware VSWITCH to a guest on an aware VSWITCH on different LPARs (same VLAN) pzawap01:~ # traceroute pzawap04 traceroute to pzawap04 (172.3.3.212), 30 hops max, 40 byte packets 1 pzawap04.svc (172.3.3.212) 0.540 ms 0.298 ms 0.310 ms pzawap01:~ # traceroute pzawap04 traceroute to pzawap04 (172.3.3.212), 30 hops max, 40 byte packets 1 pzawap04.svc (172.3.3.212) 0.463 ms 0.312 ms 0.313 ms pzawap01:~ # traceroute pzawap04 traceroute to pzawap04 (172.3.3.212), 30 hops max, 40 byte packets 1 pzawap04.svc (172.3.3.212) 0.381 ms * * All guests are SLES10-SP3 (kernel 2.6.16.60-0.76.8-default) Leland ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
