No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


FAQ-What Are the Common Troubleshooting Methods of DAA Problems on an ME60?

Publication Date:  2019-04-19 Views:  39 Downloads:  0
Issue Description
What are the common troubleshooting methods of DAA problems on an ME60?

The troubleshooting methods of DAA problems are as follows:

DAA does not take effect:

1. Check whether a license is loaded and whether the license contains DSG. The display license command output is as follows:

LME0SSGF01  Function  YES  DSG Function


2. Check whether the accounting-service-policy daa command is run globally.

3. Check whether the rate limit configuration is correct and whether the qos-profile and flow-queue-shaping configurations are performed.

4. Check whether the user group is configured correctly. If not, a route distribution failure may occur.

5. Check whether the traffic-separate enable command is run for the policy template. If the basic bandwidth is 10 Mbit/s and the internal network bandwidth is 50 Mbit/s, the actual maximum rate is 10 Mbit/s with the traffic-separate enable command not run.


Accounting problems:

1. If a customer wants no accounting on the internal network, run the tariff-level-cfg 1 accounting off command to disable accounting.

2. If the accounting together command is run, an accounting stop packet of the value-added service is sent upon user logout even if the level-1 accounting is disabled.

3. If the customer is concerned about whether DAA packets are sent by a device, run the trace command. The focus is on the accounting ID. An accounting ID example is as follows:

[Acct-Session-Id(44)] [34] [WLMQ-D00000SSG000004ae5756000081]

Here, SSG000004 indicates a level-5 accounting packet.



Key configurations:

value-added-service policy a000 daa

accounting-scheme acct1

user-group pppoe

traffic-separate enable

tariff-level 1 qos-profile 100M

tariff-level 1 flow-queue-shaping inbound 100000 outbound 100000

tariff-level-cfg 1 accounting off

tariff-level 2 qos-profile 10M

tariff-level 2 flow-queue-shaping inbound 10000 outbound 10000


Important query commands:

1. Check whether the value-added service is generated.

<BAS-CDLGDX-ME60-X16>display value-added-service user user-id 233741


User access index           : 233741

State                       : Used

User name                   : ~ghca95A3BB68E3035058ab7e5a28606b17afCD02885201

User service number         : 2

COPS server name            : --


The used VAS service id table are:

(233741,    1)  (233741,    2)----If the two items are contained in the command output, the value-added service is generated.



2. Locate the DAA service.

[ME60-1-diag]display vas global


gulNpsSynPosition                       : 0

g_ulVSMIfSmooth                         : 0

g_ucVSMIfLocalAcctEnable                : 0

g_ulVSML4SKIP                           : 0

g_usSigGroup                            : 0

g_ulVsmVasEnable                        : 1-----Whether the value-added service is enabled.

g_ulVsmSynFlow                          : 0

g_ulVsmlicenable                        : 1-----Whether the license is loaded.

g_ulVsmFunEnable                        : 0

g_ulVsmFlowEnable                       : 0

g_ulVsmUsedFlowNum                      : 0

g_ulFlowQueryTimeLen                    : 2

g_ulVsmMultiSerEnable                   : 0


3. Check whether the test traffic is about the DAA service.

[BAS-Home]display value-added-service user user-id 20890 daa tariff-level 1


Daa user service table:


Service user id                              : 20890

Service type                                 : Default dsg

Service IP type                              : IPv4

Service policy                               : daa-8m

Account method                               : None

Account start time                           : --

Normal-server-group                          : --

Flow up packets(high,low)                    : (0,374556)--------Check whether these traffic statistics keep increasing. Such traffic statistics indicate DAA traffic.

Flow up bytes(high,low)                      : (0,27621460)

Flow down packets(high,low)                  : (0,753459)

Flow down bytes(high,low)                    : (0,1147297367)

IPV6 Flow up packets(high,low)               : (0,0)

IPV6 Flow up bytes(high,low)                 : (0,0)

IPV6 Flow down packets(high,low)             : (0,0)

IPV6 Flow down bytes(high,low)               : (0,0)

Up committed information rate< kbps>         : 20480

Up Peak information rate< kbps>              : 20480

Up committed burst size< bytes>              : 3829760

Up Peak burst size< bytes>                   : 3829760

Down committed information rate <kbps>       : 20480

Down Peak information rate< kbps>            : 20480