User Rate Limiting Does Not Take Effect
Symptom
User rate limiting does not take effect.
Possible Causes
- The user rate limit is incorrectly configured.
- Entries are not delivered to the forwarding module.
Troubleshooting Procedure
- Check whether the user rate limit is correctly configured.
The user rate limit can be configured using one of the following methods. Check whether the user rate limit is correctly configured accordingly.
- After traffic policing is configured in a traffic profile, rate limiting can be configured for upstream and downstream traffic of all STAs or a single STA on a VAP to which the traffic profile is bound.
Check whether the rate limits are correctly configured in the traffic profile. Run the display traffic-profile { all | name profile-name } command to check the rate limits configured for upstream and downstream of STAs on the VAP in the traffic profile.
- After traffic policing is configured in a user profile, a QoS CAR profile can be bound to the user profile to limit rates of STAs on a VAP to which this user profile is bound.
Check whether the rate limits are correctly configured in the user profile. Run the display user-profile { all | name profile-name } command to check the user profile configuration.
- In Portal or 802.1X authentication scenarios, the user rate limit configuration is delivered by the authorization server.
Run the display access-user command to check whether user information contains rate limit configuration information.
<AC6605> display access-user user-id 5 ... User inbound CAR CIR : 454545 User inbound CAR PIR : 456454 User inbound CAR CBS : 81818125 User inbound CAR PBS : 81818125 User inbound data flow(Packet) : 5466545 User inbound data flow(Byte) : 21542214 User outbound CAR CIR : 214533 User outbound CAR PIR : 215451 User outbound CAR CBS : 40143125 User outbound CAR PBS : 40143125 User outbound data flow(Packet) : 5454122 User outbound data flow(Byte) : 24515664 ...
If similar information to the preceding command output is displayed, the authorization server has delivered the user rate limit configuration. If the user rate limit configuration has been delivered by the authorization server but is not contained in the user information, check the server configuration.
- After traffic policing is configured in a traffic profile, rate limiting can be configured for upstream and downstream traffic of all STAs or a single STA on a VAP to which the traffic profile is bound.
- Check whether the user rate limit configuration is correctly delivered.
- Check whether the STA-based rate limit configuration in a traffic profile is correctly delivered.
- Log in to the AP and check MAC addresses of online STAs in the diagnostic view.
<Huawei> system-view [Huawei] diagnose [Huawei-diagnose] display station assoc-info all ============================================================== MAC Radio Vap SSID -------------------------------------------------------------- b019-c683-e32a 1 16 test ============================================================== Cur online sta : 1
- Check the CAR IDs of the STA with a specified MAC address in the forwarding table. The ICAR field indicates the upstream rate limit and the ECAR field indicates the upstream rate limit.
[Huawei-diagnose] display cap table usf dest-mac b019-c683-e32a USFMAC table data parse ISERVICEVLAN : 100 ICAR : 17920 AUTH STATUS : 1 USF_USER_BC_CAR_EN : 1 USF_USER_BC_CAR_ID : 17921 USER_PUSH_PORTAL_DOWN_EN: 1 User error information: There is no error
- Check whether the delivered rate limit configuration exists in the forwarding table based on the CAR ID.
[Huawei-diagnose] display cap table car car-id 17920 CAR table data parse Valid : 1 PktNumOrPktLen : 0 CarType : 2 Cir Hi : 0x00000000 Cir Lo : 0x002fbd2f Cbs Hi : 0x000493e0 Cbs Lo : 0x00000000 Pir Hi : 0x00000000 Pir Lo : 0x00000000 Pbs Hi : 0x00000000 Pbs Lo : 0x00000000 Cir : 00000777 Cbs : 00150000 Pir : 00000001 Pbs : 00000000 ...... ......
- Log in to the AP and check MAC addresses of online STAs in the diagnostic view.
- Check whether the rate limit configuration in the QoS CAR profile bound to the user profile is correctly delivered.
The check procedure is similar to that in Check whether the STA-based rate limit configuration in a traffic profile is correctly delivered.
- In Portal or 802.1X authentication scenarios, check whether the authorization server has correctly delivered the user rate limit configuration.
Run the following commands to check whether the user information contains the user rate limit configuration. If the user rate limit configuration has been delivered by the authorization server but is not contained in the user information, check the authorization server configuration. If the user information contains the user rate limit configuration, troubleshoot the fault by referring to Check whether the STA-based rate limit configuration in a traffic profile is correctly delivered.
[AC6605-diagnose] display access-user ------------------------------------------------------------------------------ UserID Username IP address MAC Status ------------------------------------------------------------------------------ 78 d0ff98b231fd 10.99.99.54 d0ff-98b2-31fd Open ------------------------------------------------------------------------------ Total: 1, printed: 1 [AC6605-diagnose] display access-user user-id 78 Basic: User ID : 78 User name : d0ff98b231fd Domain-name : - User MAC : d0ff-98b2-31fd User IP address : 10.99.99.54 User vpn-instance : - User IPv6 address : - User access Interface : Wlan-Dbss2 User vlan event : Open QinQVlan/UserVlan : 0/1000 User vlan source : user request User access time : 2017/10/15 21:35:39 User accounting session ID : AC660500000000001000fb****000004e User access type : None AP name : 5c1a-6f8b-d5a0 Radio ID : 1 AP MAC : 5c1a-6f8b-d5a0 SSID : dir Online time : 30(s) AAA: User authentication type : None Current authentication method : None Current authorization method : Local Current accounting method : None
- Check whether the STA-based rate limit configuration in a traffic profile is correctly delivered.