Why is displayed radio member traffic information inaccurate

24

When you display information about all load balancing groups, the radio member traffic information is inaccurate. The possible causes are as follows:
1. Radio frequency does not work up to snuff and upstream and downstream services are abnormal.
2. Check whether the AP reports traffic information at a regular interval of 30s: run the display load-balance-group all command in V200R006 and earlier versions, and the display sta-load-balance static-group command in V200R006 and later versions.
3. Traffic information in the packets reported by the AP is inaccurate.
4. The AC does not receive or correctly process the packets reported by the AP.

Other related questions:
What are causes of inaccurate traffic policing or traffic shaping result on an AR
Traffic policing and traffic shaping may be performed on the SRU or interface card depending on the traffic type. When traffic policing or traffic shaping is performed on the interface card, the accuracy depends on the granularity of rate limiting. If different links are used, there is the problem of protocol encapsulation compensation.

The traffic information about radios is incorrect when checking the information about the load balancing group
Perform the following operations to locate the fault: 1. Check whether the radios operate normally, and whether the uplink and downlink services are interrupted. 2. Check whether the AP reports traffic information periodically (at a fixed period of 30s). In versions earlier than V200R006, run the display load-balance-group all command to view the configuration result. In V200R006 and later versions, run the display sta-load-balance static-group command to view the configuration result. 3. Check whether traffic information in the packets reported by the AP is correct. 4. Check whether the AC receives the packets containing traffic information reported by the AP and whether the packets are processed correctly.

Why is a member switch displayed as unknown or down while the member switch is actually Up
S series switches (excluding the S1700) in V200R002 and later versions, and V100R006C05 do not support HGMP. When a member switch in a cluster is Up but displayed as unknown or down, the possible causes and solutions are as follows: Cause 1: The configuration is not saved after the switch is added to the cluster and reset. Solution: Add the member switch to the cluster again and save the configurations of the command switch and the member switch. Cause 2: The command switch re-establishes a cluster but the command for deleting the original cluster is not delivered to the member switch. This is because the member switch is Down when the cluster is deleted or the command switch is reset without saving the configuration. The new cluster name is different from the original one. Another possible cause is that the super password is configured on the member switch using the super password command. NOTE: S series switches in V200R003 and later versions, and V100R006C05 do not support the super password command. The super password configured on the command switch is copied to member switches when the cluster is created. In this case, you cannot add the member by running the command of re-joining the cluster. The message “Candidate device refused�?is displayed. Solution: Re-establish a cluster using the original cluster name, add the member switch to the cluster again, and save the configuration. Specify the super password to add the member switch to the cluster. Cause 3: The mVLAN configured on the member switch is different from that configured on the command switch. Solution: Change the mVLAN on the member switch to ensure that the mVLANs of all switches in the cluster are the same. NOTE: In this case, you cannot add the member by running the command of re-joining the cluster. The message “Candidate device no response�?or no message is displayed.

Why is no information about members of an IGMP multicast group displayed in the display igmp group command output on a CE series switch

If the display igmp group command output does not display any information, the specified multicast group has no members.

In normal cases, after users join a multicast group dynamically by sending IGMP Report messages, the IGMP multicast group information is displayed in the display igmp group command output. The following is an example:
<HUAWEI> display igmp group
Interface group report information of VPN instance: public net
 Vlanif100(10.1.6.2):
  Total 1 IGMP Group reported
   Group Address   Last Reporter   Uptime      Expires
   225.1.1.2       10.1.6.10       00:02:04    00:01:17
In the command output, Group Address indicates the IP address of the multicast group that users have joined, and Last Reporter indicates the last host that has sent an IGMP Report message.


If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top