SLOW SPEED ISSUES CERTAIN FACTS

PREPARED BY

MULTIPLAY NOC

BANGALORE

Factors which hamper the speed are

1. Virus infected PC2. Low SNR ratio due to poor line condition/improper punching at

the MDF side3. Wrong line profile attached to the DSLAM port for high speed

plans4. Packet loss at the connected Network element5. Low Power in the RPR ring6. Cascading of the OCLANs/ DSLAMs which may in turn affect

the uplink traffic of master OCLAN7. Wrong AAA policy attached in the LDAP 8. High DNS resolution time9. IP pool/ gateway chocking10. High latency at MPLS

Point No 1 -3 is for individual customer & Point 4-9 will affect a bulk of customers

FACTORS HAMPERING THE BROWSING SPEED

1. Virus Infected PCCheck for the virus infection. Scan thoroughly to remove complete traces of virus. Make sure that the system is virus free and not performing in a sluggish way without connecting to the internet

2. LOW SNR Line attention is in relation to the "loop loss" on the copper

line. The further you are away from the exchange the higher your attenuation figure will be as the signal loss increases. The lower your attenuation figure the more chance you have of getting the faster speeds. In general higher Signal To Noise Ratio will result in less error..

SNR MARGIN REMARK

6db or low Bad and will experience no line synchronization or intermittent synchronization problems.

7db – 10 db Fair but does not leave much room for variances in conditions.

11db – 20 db Good with little or no synchronization problems

20db – 28db Excellent

29db or above Outstanding

3. Wrong ADSL Line profile attached in DSLAM port for high speed plan

1. Check for the correctness of the Speed profile attached to the connected port at DSALM.

2. Normally ADSL ports are configured with 2Mbps default profile.

3. For high speed plans , the port should be manually configured with high speed profiles.

4. Packet loss at the connected Network element1. Packet loss at the connected network element impart slow

speed to the customers connected from the concerned Network element.

2. Ping with certain packet size for checking packet loss. Ex: Ping 10.10.10.10 1000 size 1500.

3. Check the media/connectivity .

4. Make sure that the no packet loss are incurred.

5. Low power in the RPR ring

1. Low power in the RPR ring may inversely affect the speed. Ensure the power levels are well with in the limits.

Threshold power levels set for RPR rings

Ring Threshold set

1 G Ring -10 TO -22 db

10 G Ring -9 TO -14 db

6. Cascading of OCLANs

1. Many OCLANs are cascaded with out master OCLAN Uplink media up gradation to GE. Many places the master OCLAN uplink is still FE and cascading is done with out taking in consideration that the traffic from the cascaded OCLANs also will flow through the Master OCLAN UPLINK.

2. Calculate the expected traffic which will flow through the master OCLAN UPLINK after cascading and go for the media up gradation . Cascading of too many OCLANs with out proper planning will definitely hamper the service.

7. Wrong AAA policy attached in LDAP

1. Check for the correctness of the AAA policy assigned in LDAP for the customer.

2. AAA policy in turn will define the speed

3. If the AAA policy is not assigned as per the plan , speed may vary.

4. Consult with NOC for the correctness of the AAA policy as per the Plan

8. High DNS resolution time

1. Resolution time may be high in case of the connected DNS failure/ DNS overloading.

2. Will affect all the customers connected to the concerned DNS.

3. perform ‘nslookup’ from the field as a first level trouble shooting .

4. Inform to NOC in case of any issue or change the DNS in LAN setting to some other working DNS.

9. IP pool/ gateway chocking1. slow speed can arise due to the chocking of subscriber IP pool defined in BNG

2. check the reachability of the BNG Pools/ subscriber IP from Outside world.

3. Use http://network-tools.com/

4. Trace the pool/IP from the site mentioned above and report to MPLS NOC/MP NOC in case of any high latency.

5. Eg: 117.192.0.1 is the general subscriber pool allotted for Bangalore east 01 BNG

6. see the response from http://network-tools.com/ as given in the next slide.

10. High latency at MPLS

1. Check the latency from one hop to another hop using traceroute command for the problematic/popular sites like google.com, gmail,facebook,youtube etc.,

2. Latency of 350- 450 ms are permissible between two hops.

3. In form MPLS NOC/ MP NOC in case of any abnormality/High latency.

4. The Snapshots of tracert / nslookup /ping to popular sites may please be forwarded to bbmpnoc@gmail.com bm@bsnl.co.in mplsnms@gmail.com to quickly identify the point of error which is causing slow speed in the Broadband Multiplay Network.

THANK YOU