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>

Reminder

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

upgrade

Common Troubleshooting Methods for Low Internet Access Speed for Users Subordinate to ME60

Publication Date:  2013-09-30 Views:  29 Downloads:  0
Issue Description
The following describes common methods of troubleshooting low Internet access speed for users subordinate to ME60.
Handling Process

1. Some users subordinate to an ME60 had low Internet access speed. According to the packet capture results, an IP address and the users established a TCP connection and performed interaction. 20s later, page loading continued. Users with addresses from another address pool accessed the Internet properly. This indicated that the IP address kept scanning and attacking the users on a certain network segment. After the network segment was disabled, the problem was resolved.

2. A customer reported that some users subordinate to an ME60 had low Internet access speed, and pinging the ME60 uplink network-side interface failed. After analysis, it was found that the error packet count increased at the interface. This indicated that the connected switch and Layer 2 links had a fault.

3. Some users subordinate to an ME60 failed to access some websites:

Networking: NE80E-----GSR12416

\ /

3/0/0 \ /2/0/0

ME60

Symptom:

Services on the uplink interface 3/0/0 on the ME60 were normal. The problem occurred after the interface 2/0/0 connecting to the GSR was added for capacity expansion. Internet access speed became normal after the 2/0/0 interface network routes were deleted. Users connecting to multiple boards had low Internet access speed.

Traced websites that users failed to access and found that tracing packets failed to be forwarded. It was concluded that the problem occurred because the GSR device had a fault in route forwarding.

C:\Documents and Settings\Administrator>tracert xxx.75.1.1

Tracing route to 110.75.1.1 over a maximum of 30 hops
1 2 ms 11 ms 8 ms xxx.178.211.65
2 <1 ms <1 ms <1 ms xxx.190.237.25 //ME60 address
3 * * * Request timed out.
4 <1 ms <1 ms <1 ms xxx.190.237.25
5 * * * Request timed out.
6 <1 ms <1 ms <1 ms xxx.190.237.25
7 * * * Request timed out.
C:\Documents and Settings\Administrator>tracert xxx.200.241.26
Tracing route to 124.200.241.26 over a maximum of 30 hops
1 9 ms 10 ms 9 ms xxx.178.211.65
2 <1 ms <1 ms <1 ms xxx.190.237.25
3 * * * Request timed out.
4 <1 ms <1 ms <1 ms xxx.190.237.25
5 * * * Request timed out.
6 <1 ms <1 ms <1 ms xxx.190.237.25
7 * * * Request timed out.

After the route cost of the GSR was changed to a proper value, the problem was resolved.

4. Users subordinate to an ME60 had lower Internet access speed, about 20% ping packets were lost, and the NP also discarded packets.

[MS-AY-TYX-HWME60-001-diag]efu bas diag_cnt query 1 1 2
[diag_cnt] I_DropCnt[328] 83746608 , undefined

After the ME60 was reset, the problem was resolved.
Root Cause

1. For an ME60 that has operated for a long period, there is a high probability that the problem is caused by a hardware fault. Therefore, check hardware first.

2. For a new ME60, check QoS, user table entries (dis access-user user-id), CIR and PIR, QoS configurations under the BAS interface and domain, and ACL configurations.

3. If the hardware is normal and configurations are correct, low Internet access speed is often caused by packet loss. Check whether the physical link is normal by querying statistics about error packets on interfaces, whether the equipment report any alarms, and whether logbuffer records any errors. For connected users, trace their MAC addresses to check whether interaction packets are normal. For uplink equipment, perform ping tests to check link connectivity.

4. Capture packets to check whether packet loss occurs on ME60.

5. If a large number of users subordinate to multiple devices or boards have low Internet access speed, check whether the aggregation node has a fault.
Solution
None
Suggestions
None

END