[SOLVED] help me check right?

H

haiwan

Well-Known Member
Apr 23, 2019
249
1
58
37
root@pve-10-140:~# omping -c 600 -i 1 -q 172.16.10.140 172.16.10.141
172.16.10.141 : waiting for response msg
172.16.10.141 : waiting for response msg
172.16.10.141 : waiting for response msg
172.16.10.141 : waiting for response msg
172.16.10.141 : waiting for response msg
172.16.10.141 : waiting for response msg
172.16.10.141 : joined (S,G) = (*, 232.43.211.234), pinging
172.16.10.141 : given amount of query messages was sent

172.16.10.141 : unicast, xmt/rcv/%loss = 600/600/0%, min/avg/max/std-dev = 0.084/0.178/0.304/0.032
172.16.10.141 : multicast, xmt/rcv/%loss = 600/181/69%, min/avg/max/std-dev = 0.132/0.220/0.642/0.040
 
Hi,

you have network problems because you loos 69% of the multicast traffic.
Maybe stormcontroll is enabled on your switch.
Anyway, an interval on 1 sec is not enough for testing the network use instead of this command.
And you should use all nodes you wanna join in this test.
Code: 
omping -c 10000 -i 0.001 -F -q 172.16.10.140 172.16.10.141
 
ot@pve-10-141:~# omping -c 10000 -i 0.001 -F -q 172.16.10.140 172.16.10.141
172.16.10.140 : waiting for response msg
172.16.10.140 : joined (S,G) = (*, 232.43.211.234), pinging
172.16.10.140 : given amount of query messages was sent

172.16.10.140 : unicast, xmt/rcv/%loss = 10000/10000/0%, min/avg/max/std-dev = 0.049/0.063/0.181/0.009
172.16.10.140 : multicast, xmt/rcv/%loss = 10000/9952/0% (seq>=49 0%), min/avg/max/std-dev = 0.062/0.076/0.199/0.009

root@pve-10-140:~# omping -c 10000 -i 0.001 -F -q 172.16.10.140 172.16.10.141
172.16.10.141 : waiting for response msg
172.16.10.141 : waiting for response msg
172.16.10.141 : waiting for response msg
172.16.10.141 : waiting for response msg
172.16.10.141 : waiting for response msg
172.16.10.141 : waiting for response msg
172.16.10.141 : joined (S,G) = (*, 232.43.211.234), pinging
172.16.10.141 : waiting for response msg
172.16.10.141 : server told us to stop

172.16.10.141 : unicast, xmt/rcv/%loss = 9257/9257/0%, min/avg/max/std-dev = 0.050/0.064/0.889/0.016
172.16.10.141 : multicast, xmt/rcv/%loss = 9257/9257/0%, min/avg/max/std-dev = 0.063/0.078/1.085/0.022
 
we switch is cisco n3k
this trouble let we 4 server no successful create
 
168.100.141 : unicast, xmt/rcv/%loss = 10000/10000/0%, min/avg/max/std-dev = 0.046/0.078/0.204/0.015
192.168.100.141 : multicast, xmt/rcv/%loss = 10000/10000/0%, min/avg/max/std-dev = 0.060/0.094/0.222/0.016
192.168.100.142 : unicast, xmt/rcv/%loss = 9895/9895/0%, min/avg/max/std-dev = 0.047/0.097/0.261/0.023
192.168.100.142 : multicast, xmt/rcv/%loss = 9895/9895/0%, min/avg/max/std-dev = 0.060/0.113/0.290/0.023
root@pve140:~# omping -c 600 -i 1 -q 192.168.100.140 192.168.100.141 192.168.100.142
192.168.100.141 : waiting for response msg
192.168.100.142 : waiting for response msg
192.168.100.141 : waiting for response msg
192.168.100.142 : waiting for response msg
192.168.100.141 : waiting for response msg
192.168.100.142 : waiting for response msg
192.168.100.141 : waiting for response msg
192.168.100.142 : waiting for response msg
192.168.100.141 : waiting for response msg
192.168.100.142 : waiting for response msg
192.168.100.141 : joined (S,G) = (*, 232.43.211.234), pinging
192.168.100.142 : waiting for response msg
192.168.100.142 : joined (S,G) = (*, 232.43.211.234), pinging
192.168.100.141 : given amount of query messages was sent
192.168.100.142 : given amount of query messages was sent

192.168.100.141 : unicast, xmt/rcv/%loss = 600/600/0%, min/avg/max/std-dev = 0.065/0.178/0.298/0.038
192.168.100.141 : multicast, xmt/rcv/%loss = 600/183/69%, min/avg/max/std-dev = 0.080/0.215/0.278/0.037
192.168.100.142 : unicast, xmt/rcv/%loss = 600/600/0%, min/avg/max/std-dev = 0.070/0.195/0.309/0.050
192.168.100.142 : multicast, xmt/rcv/%loss = 600/181/69%, min/avg/max/std-dev = 0.101/0.239/0.302/0.043


192.168.100.140 : unicast, xmt/rcv/%loss = 10000/10000/0%, min/avg/max/std-dev = 0.048/0.078/0.224/0.017
192.168.100.140 : multicast, xmt/rcv/%loss = 10000/9988/0% (seq>=13 0%), min/avg/max/std-dev = 0.060/0.091/0.235/0.017
192.168.100.142 : unicast, xmt/rcv/%loss = 10000/10000/0%, min/avg/max/std-dev = 0.051/0.095/0.275/0.023
192.168.100.142 : multicast, xmt/rcv/%loss = 10000/10000/0%, min/avg/max/std-dev = 0.062/0.111/0.287/0.023
root@pve141:~# omping -c 600 -i 1 -q 192.168.100.140 192.168.100.141 192.168.100.142
192.168.100.140 : waiting for response msg
192.168.100.142 : waiting for response msg
192.168.100.140 : joined (S,G) = (*, 232.43.211.234), pinging
192.168.100.142 : waiting for response msg
192.168.100.142 : waiting for response msg
192.168.100.142 : waiting for response msg
192.168.100.142 : joined (S,G) = (*, 232.43.211.234), pinging
192.168.100.140 : given amount of query messages was sent
192.168.100.142 : given amount of query messages was sent

192.168.100.140 : unicast, xmt/rcv/%loss = 600/600/0%, min/avg/max/std-dev = 0.072/0.183/0.286/0.032
192.168.100.140 : multicast, xmt/rcv/%loss = 600/184/69%, min/avg/max/std-dev = 0.145/0.213/0.308/0.033
192.168.100.142 : unicast, xmt/rcv/%loss = 600/600/0%, min/avg/max/std-dev = 0.070/0.178/0.327/0.043
192.168.100.142 : multicast, xmt/rcv/%loss = 600/181/69%, min/avg/max/std-dev = 0.109/0.217/0.336/0.041




192.168.100.140 : unicast, xmt/rcv/%loss = 10000/10000/0%, min/avg/max/std-dev = 0.048/0.081/0.248/0.018
192.168.100.140 : multicast, xmt/rcv/%loss = 10000/9981/0% (seq>=20 0%), min/avg/max/std-dev = 0.063/0.093/0.277/0.017
192.168.100.141 : unicast, xmt/rcv/%loss = 9813/9813/0%, min/avg/max/std-dev = 0.051/0.087/0.247/0.019
192.168.100.141 : multicast, xmt/rcv/%loss = 9813/9794/0% (seq>=20 0%), min/avg/max/std-dev = 0.064/0.100/0.258/0.018
root@pve142:~# omping -c 600 -i 1 -q 192.168.100.140 192.168.100.141 192.168.100.142
192.168.100.140 : waiting for response msg
192.168.100.141 : waiting for response msg
192.168.100.140 : joined (S,G) = (*, 232.43.211.234), pinging
192.168.100.141 : joined (S,G) = (*, 232.43.211.234), pinging
192.168.100.140 : given amount of query messages was sent
192.168.100.141 : given amount of query messages was sent

192.168.100.140 : unicast, xmt/rcv/%loss = 600/600/0%, min/avg/max/std-dev = 0.075/0.184/0.289/0.039
192.168.100.140 : multicast, xmt/rcv/%loss = 600/181/69%, min/avg/max/std-dev = 0.105/0.210/0.292/0.036
192.168.100.141 : unicast, xmt/rcv/%loss = 600/600/0%, min/avg/max/std-dev = 0.063/0.161/0.330/0.043
192.168.100.141 : multicast, xmt/rcv/%loss = 600/181/69%, min/avg/max/std-dev = 0.086/0.187/0.253/0.033
 
[QUOTE =“wolfgang，帖子：247727，成员：30221”]嗨，

您遇到网络问题，因为您丢失了69％的多播流量。
也许你的交换机启用了stormcontroll。
无论如何，1秒的间隔不足以测试网络使用而不是此命令。
并且您应该使用您想要参加此测试的所有节点。
[码]
omping -c 10000 -i 0.001 -F -q 172.16.10.140 172.16.10.141
[/代码] [/ QUOTE]
pase help me check support
 
Again it looks like you switch has storm control enabled.
Check your Cisco documentation.
 
wolfgang said:
Again it looks like you switch has storm control enabled.
Check your Cisco documentation.
Click to expand...
we and my switch make sure have closed

interface Ethernet1/29
description SERVER-4
lacp port-priority 32768
lacp rate normal
priority-flow-control mode auto
lldp transmit
lldp receive
no switchport block unicast
no switchport block multicast
no hardware multicast hw-hash
no hardware vethernet mac filtering per-vlan
cdp enable
switchport
switchport mode access
no switchport monitor
no switchport dot1q ethertype
no switchport priority extend
spanning-tree port-priority 128
spanning-tree cost auto
spanning-tree link-type auto
spanning-tree port type normal
no spanning-tree bpduguard
no spanning-tree bpdufilter
speed 10000
duplex full
flowcontrol receive off
flowcontrol send off
no negotiate auto
link debounce time 100
no beacon
mtu 1500
delay 1
snmp trap link-status
logging event port link-status default
logging event port trunk-status default
bandwidth 10000000
no bandwidth inherit
mdix auto
storm-control broadcast level 100.00
storm-control multicast level 100.00
storm-control unicast level 100.00
no shutdown lan
load-interval counter 1 30
load-interval counter 2 300
no load-interval counter 3
medium broadcast
no shutdown
 
The only thing I can tell is that the network is the problem.
Maybe your IMGP querier and IMGP Snooping is not working correctly.
 
Hi,

I'm glad to hear it is working.
I mark this thread as solved.
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom