Super frame errors

super frame errors

From: Franky Lin Aborting the current read attempt on the superframe also removes the packet from the pipeline. janranjan said: 6th October 2010. Unhappy No one Know what are Super Frame Errors. Hi what happen did no one know about these SUPER FRAME ERRORS. Frames were duplicated (no interpolation), playback was fine. But since v17 the rendered files are corrupted. There are wrong frames in the.

Solved: Super frame errors

Header content-type image/jpeg error
Super frame errors
BUFFER I/O ERROR ON DEVICE SDC
Canon pixma mp150 error code e27
IR1200 CLEANING ERRORS

Related Videos

How to Make a BAD GREEN LANTERN Movie

Configure Jumbo/Giant Frame Support on Catalyst Switches

Introduction

This document describes how to configure a jumbo/giant frame support on Cisco Catalyst Switches.

Note: This article does not address interfaces such as Super frame errors Transfer Mode (ATM), Packet over SONET (POS), nor Token Ring.

Prerequisites

Requirements

Ensure that you meet these requirements before you attempt this configuration:

  • Understand MTU.

  • Have knowledge of jumbo and baby giants.

Components Used

The information in this super frame errors is based on these software and hardware versions:

  • Catalyst 6x00 / Cisco 7600 OSR Series

  • Catalyst 4000/4500 Series

  • Catalyst 3750/3560 Series

  • Catalyst 3550 Series

  • Catalyst 2970/2960 Series

  • Catalyst 2950 Series

  • Catalyst 2940 / Catalyst Super frame errors 500 Series

  • Catalyst 2900XL/3500XL Super frame errors 2948-L3/4908G-L3 Series

  • Catalyst 1900/2800 Series

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration, super frame errors. If your network is live, ensure that you understand the potential impact of any command.

Note: In all the examples in this document, unless specifically mentioned, all values that quote MTU in bytes omit the 18 bytes for the Ethernet header and Frame Check Sequence (FCS).

Conventions

Refer to the Cisco Technical Tips Conventions for more information on document conventions.

Background Information

This section describes the basic terminology that this document uses. This section also explains the background theory for the configurations in this document.

Term Definitions

  • MTU: MTU is short for Maximum Transmission Unit, the largest physical packet size, measured in bytes, that a network can transmit. Any messages larger than the MTU are divided into smaller packets before transmission.

  • Jumbo: Jumbo frames are frames that are bigger than the standard Ethernet frame size, which is 1518 bytes (this includes Layer 2 (L2) header and FCS). The definition of frame size is vendor-dependent, as these are not part of the IEEE standard.

  • Baby giants: The baby giants feature super frame errors a switch to pass or forward packets that are slightly larger than the IEEE Ethernet MTU. Otherwise, super frame errors, the switch declares big frames as oversize and discards them.

Background Theory

In order to transport traffic across switched-networks, ensure that transmitted traffic MTU does not exceed the MTU that the switch platforms support. Here are the reasons why the MTU size of certain frames is truncated:

  • Vendor-specific requirements: Applications and some Network Interface Cards (NICs) can specify an MTU size outside of the standard 1500 bytes, super frame errors. Much of this drive has been due to studies undertaken, which prove that an increase in the size of an Ethernet frame can increase average throughput.

  • Trunking: In order to carry VLAN-ID information between switches error 1418 sql server other network devices, trunking has been employed to augment the standard Ethernet frame, super frame errors. The current, most common forms of trunking are Cisco proprietary InterSwitch Link (ISL) encapsulation and IEEE 802.1q. Refer to these documents for more information on trunking:

  • MultiProtocol Label Switching (MPLS): When you enable MPLS on an interface, super frame errors, MPLS can also augment the frame size of a packet, based on the number of labels in the Label stack for an MPLS-tagged packet. The total size of a label is four bytes, super frame errors. The total size of a label stack is n x 4 bytes. If a label stack is formed, the frames can exceed the MTU.

Configure

In this section, super frame errors, you super frame errors presented with super frame errors information to configure the features described in this document.

Configurations

This document uses these configurations:

  • Catalyst 6x00 / Cisco 7600 OSR Series

  • Catalyst 4000/4500 Series

  • Catalyst 3750/3560 Series

  • Catalyst 3550 Series

  • Catalyst 2970/2960 Series

  • Catalyst 2950 Series

  • Catalyst 2940 super frame errors Catalyst Express 500 Series

  • Catalyst 2900XL/3500XL Series

  • Catalyst 2948-L3/4908G-L3 Series

  • Catalyst 1900/2800 Series

Catalyst Support for Super frame errors Frame Sizes

The ability of the various Catalyst switches to support various frame sizes depends on many factors that can include hardware and software, super frame errors. Notice that certain modules can support super frame errors frame sizes than others, super frame errors, even within the same platform. Additionally, maximum frame size support can also change based on the software version you use.

Catalyst 6000/6500 / Cisco 7600 OSR Series

The Catalyst 6000 series and 7600 Optical Services Router (OSR) platform can support jumbo frame sizes as of release 6.1(1) of CatOS, and 12.1(1)E for Native Cisco IOS, super frame errors. However, this is dependent on the type of line cards that super frame errors use. There are generally no restrictions to enable the jumbo frame size feature. You can use this feature with trunking/non-trunking and channeling/non-channeling.

The default MTU size is 9216 bytes after you enable jumbo super frame errors support on super frame errors individual port. However, an Application Specific Integrated Circuit (ASIC) limitation requires that you limit the MTU size to 8092 bytes on these 10/100-based line cards:

  • WS-X6248-RJ-45

  • WS-X6248A-RJ-45

  • WS-X6248-TEL

  • WS-X6248A-TEL

  • WS-X6348-RJ-45

  • WS-X6348-RJ-45V

  • WS-X6348-RJ-21

The WS-X6516-GE-TX is also affected at 100 Mbps. At 10/1000 Mbps, up to 9216 bytes can be supported. However, the WS-X6548-RJ-45 line card is not affected, as this line card uses newer ASICs.

Note: Jumbo frame support is available on WS-X6101 ATM modules.

Configure Native Cisco IOS

7609(config)#int gigabitEthernet 1/1 7609(config-if)#mtu ? <1500-9216> MTU size in bytes 7609(config-if)#mtu 9216

Verify in Native Cisco IOS

7609#show interfaces gigabitEthernet 1/1 GigabitEthernet1/1 is up, line protocol is up (connected) Hardware is C6k 1000Mb 802.3, address is 0007.0d0e.640a (bia 0007.0d0e.640a) MTU 9216 bytes, BW 1000000 Kbit, DLY 10 usec, reliability 255/255, txload 1/255, rxload 1/255

The port ASICs on the Catalyst 6000 count as oversized, super frame errors, which are those frames greater than 1548 bytes but less than the configured jumbo MTU. It uses the rxOversizedPkts counter to track these frames in the output from the show counter <mod/port> command. In this case, the ifInErrors counter value increments and can equal the number of rxOversizedPkts packets value in the show counter <mod/port> command output. On a Catalyst 6000 that runs Cisco Integrated Cisco IOS (Native Mode), super frame errors, use the show interface <interface-id> command to check whether the input errors counter increments along with giant counters on the interface that receives these frames.

Note: There is no relationship between the MTU value that you can specify in the VLAN database and the mtu command in the interface configuration mode. With the VLAN database setting, the switch checks for an MTU value greater than 1500. If the switch detects a higher value, super frame errors, puts the VLAN in a non-operational state. Therefore, to support large frames, you only need to change the interface MTU value and not the VLAN database MTU value. If SVI is used, then in order to support large frames, you must increase the MTU on the SVI to route the traffic between VLANs. Refer to the Jumbo Frame Support section of   Catalyst 6500 Release 12.2SX Software Configuration Guide    for more information about Jumbo Frame support on the Catalyst 6500.

Catalyst 4000/4500 Series

You can classify the Catalyst 4000/4500 series switches into two groups in relation to jumbo or baby giant support:

  • Devices that run CatOS system software

  • Devices that run Cisco Super frame errors system software

Devices that Run the CatalystOS System Software

This group includes the Catalyst 4000/4500 devices with Supervisor I and Supervisor II, WS-C2948G, WS-C2980G, and the WS-C4912G fixed-configuration switches also. Due to an ASIC limitation, there is no support for baby giants.

Workaround

As a workaround, you can enable a port for trunking in order to support baby giants. When you enable a port for 802.1q trunking, super frame errors, the switch automatically assumes that an extra four bytes of data are appended on and increments the frame size of the L2 packet. Notice that ISL encapsulation is not supported on these platforms.

Therefore, for implementations that require exactly one tag to be carried (either 802.1q or MPLS, but not both), you can configure the port as a trunk port to force the switchport to accept an extra four bytes of data. If the port were to carry multiple VLANs for VLAN-ID tagging or 802.1p prioritization, configure the port as a 802.1q trunk. However, super frame errors, even if VLAN tagging is not necessary, but you want the increased four-byte support, super frame errors, you can configure the port as a 802.1q trunk. Change the Native VLAN to be the one desired to carry the traffic. When you do so, you can accommodate an extra four bytes of data.

Devices that Run Cisco IOS System Software

The Cisco Catalyst 4000/4500 devices with Supervisors, which run only Cisco IOS, currently support baby giants up to 1600 byte-sized frames and jumbo frames. Refer to Troubleshooting Baby Giant/Jumbo Frames in Catalyst 4000/4500 with Supervisor III/IV for more information.

Catalyst 3750/3560 Series

Catalyst 3750/3560 Series switches support an MTU of 1998 bytes for all 10/100 interfaces. All Gigabit Ethernet interfaces support jumbo frames up to 9000 bytes, super frame errors. The default MTU and jumbo frame size is 1500 bytes. You cannot change the MTU on an individual interface. You must set the MTU globally. Reset the switch afterwards for the MTU change to take effect.

Configure

Use the system mtu command to change the MTU for all 10/100 interfaces. This command only effects 10/100 interfaces.

3750(config)#system mtu 1546 3750(config)# exit 3750# reload

Use the system mtu jumbo command to change the MTU for all Gigabit Intel raid 1 error occurred interfaces. This command only effects Gigabit Ethernet Interfaces.

3750(config)#system mtu jumbo 9000 3750(config)# exit 3750# reload

Note: Gigabit Ethernet ports are not affected by the system mtu command; 10/100 ports are not affected by the system mtu jumbo command. If you do not configure the system mtu jumbo command, the set of the system mtu command applies to all Gigabit Ethernet interfaces.

Verify

Use the show system mtu command to view the mtu sizes after reload.

Switch#show system mtu System MTU size is 1546 bytes System Jumbo MTU size is 9000 bytes

Note: If Gigabit Ethernet interfaces are configured to accept frames greater than the 10/100 interfaces, jumbo frames that ingress on a Gigabit Ethernet interface and egress on a 10/100 interface are dropped.

Note: When you use dot1q on trunk interface on the Cat3750/3560, you can see runts in the show interface command output because Cat3750/3560 counts valid dot1q encapsulated packets that are 61-64 bytes and that includes the q-tag as undersized frames, even when these packets are forwarded correctly. In addition, these packets are not reported in the appropriate category (unicast, super frame errors, multicast, broadcast) in receive statistics.

Catalyst 3550 Series

You can classify the Catalyst 3550 series Layer 3 (L3) switches into two major groups, where the Gigabit Ethernet versions support up to 2000 bytes and the Fast Ethernet versions support up to 1546 bytes. These models support up to 2000 bytes:

  • WS-C3550-12G

  • WS-C3550-12T

Configure

3550(config)#system mtu ? <1500-2000> MTU size in bytes 3550(config)#system mtu 2000 Changes to the System MTU will not take effect until the next reload is done.

Verify

3550#show system mtu System MTU size is 2000 bytes

In versions earlier than 12.1(9)EA1, an MTU of 2025 was configurable on these mentioned switches. Due to an ASIC limitation, the configurable MTU has been brought down to 2000 bytes.

These models support up to 1546 bytes:

  • WS-C3550-24

  • WS-C3550-24-DC-SMI

  • WS-C3550-24-EMI

  • WS-C3550-24-SMI

  • WS-C3550-48-EMI

  • WS-C3550-48-SMI

Configure

3550(config)#system mtu ? <1500-1546> MTU size in bytes 3550(config)#system mtu 1546 Changes to the System MTU will not take effect until the next reload is done.

Verify

3550#show system mtu System MTU size is 1546 bytes

Note: The 508 error blackberry size of 1546 does not include the 18 bytes of the standard Ethernet header and FCS. Therefore, these switches actually support Ethernet frames up to 1564 bytes.

Catalyst 2970/2960 Series

The default maximum transmission unit (MTU) size for frames received and transmitted on all interfaces on the switch is 1500 bytes, super frame errors. You can increase the MTU size for all interfaces that operate at 10 or 100 Mbps with the system mtu global configuration command. You can increase the MTU size to support jumbo frames on all Gigabit Ethernet interfaces with the system mtu jumbo global configuration command.

Gigabit Ethernet ports are not affected by the system mtu command; 10/100 ports are not affected by the system mtu jumbo command. If you do not configure the system mtu jumbo command, super frame errors, the setting of the system mtu< /strong> command applies to all Gigabit Ethernet interfaces.

You cannot set the MTU size for an individual interface; you set it for all 10/100 or all Gigabit Ethernet interfaces on the switch, super frame errors. When you change the system or jumbo MTU size, you must reset the switch before the new configuration takes effect.

Frame sizes that can be received by the switch CPU are limited to 1998 bytes, no matter what value was entered with the system mtu or system mtu jumbo commands, super frame errors. Although frames that are forwarded are typically not received by the CPU, in some cases, packets are sent to the CPU, such as traffic sent to control traffic, SNMP, or Telnet.

If Gigabit Ethernet interfaces are configured to accept frames greater than the 10/100 interfaces, super frame errors, jumbo frames received on a Gigabit Ethernet interface and sent on a 10/100 super frame errors are dropped.

Configure

Use the system mtu command to change the MTU for all 10/100 interfaces. This command only affects 10/100 interfaces.

2970(config)#system mtu 1998 2970(config)# exit 2970# reload

Use the system mtu jumbo command to change the MTU for all Gigabit Ethernet interfaces. This command only affects Gigabit Ethernet Interfaces.

2970(config)#system mtu jumbo 9000 2970(config)# exit 2970# reload

Verify

Use the show system mtu command to view the MTU sizes after reload.

2970#show system mtu System MTU size is 1998 bytes System Jumbo MTU size is 9000 bytes

Catalyst 2950/2955 Series

You can classify the Catalyst 2950/2955 Series switches into two major groups, where one supports baby giants (up to 1530 bytes), but the other does not. However, this refers to traffic that error 40 sql server through the switch. Packets destined to the management (VLAN) interface can support only 1500 bytes.

These models of 2950 switches support only 1500 bytes:

  • WS-C2950-12

  • WS-C2950-24

  • WS-C2950-48

  • WS-C2950C-24

  • WS-C2950T-24

These models of 2950/2955 switches support up to 1530 bytes:

  • WS-C2950G-12-EI

  • WS-C2950G-24-EI

  • WS-C2950G-24-EI-DC

  • WS-C2950G-48

  • WS-C2950G-48-EI

  • All models super frame errors 2950 Error smb2 ubuntu 10.04 Series switches

  • All models of 2955 Series switches

For those switches that support up to 1530 bytes, the default MTU value is 1500, super frame errors. If you want to change this, use the global configuration command that is available for versions of software that are 12.1(6)EA2 or later. Here is sample configuration and verification:

Configure

2950G(config)#system mtu ? <1500-1530> MTU size in bytes 2950G(config)#system mtu 1530

Verify

2950G#show system mtu System MTU size is 1530 bytes

Catalyst 2940 / Catalyst Express 500 Series

The System MTU can only be set to 1500 bytes, the default. You cannot set the MTU on a per-interface basis.

Catalyst 2900XL/3500XL Series

The Catalyst 2900XL/3500XL series switches are able to support up to the MTU size of 2018 bytes as of version 12.0(5.2)XU. There is no support for a full jumbo frame. You can configure the MTU size on a per-interface basis. You can perform this configuration on all 10/100/1000 interfaces.

Configure

3500XL(config)#int fastEthernet 0/3 3500XL(config-if)#mtu ? <1500-2018> MTU size in bytes 3500XL(config-if)#mtu 2018

Verify

3500XL#sh interfaces fastEthernet 0/3 FastEthernet0/3 is up, super frame errors, line protocol is up Hardware is Fast Ethernet, address is 0007.85b8.6983 (bia 0007.85b8.6983) MTU 2018 bytes, BW 0 Kbit, DLY 100 usec, reliability 255/255, txload 1/255, rxload 1/255

Note: Currently, the Catalyst 2900LRE-XL switches do no support frame sizes larger than 1536 bytes signaling connection due to limitations on the CPE device.

A Super frame errors 2900XL reports oversized frames when Catalyst 2900XL receives a legal max-size Ethernet frame encapsulated or tagged for ISL/802.1Q but cannot forward the frame to any other ports. There are many valid reasons why a port receives a packet but does not forward the packet to any other ports. For example, packets that a port blocked by Spanning Tree Protocol (STP) receives are not forwarded. This issue is a cosmetic bug with 'Cisco bug ID CSCdm34557'.

Note: Only registered Cisco Clients can access tools and bug information.

Catalyst 2948G-L3/4908G-L3 Series

The Catalyst 2948G-L3 and 4908G-L3 series switches do not support a configurable MTU on either 10/100 or 1000. The MTU is therefore the default, which is 1500 bytes.

Configure

2948G-L3(config)#int gig 49 2948G-L3(config-if)#mtu 2000 % Interface GigabitEthernet49 does not support user settable mtu.

Verify

2948G-L3#sh interfaces gigabitEthernet 49 GigabitEthernet49 is up, line protocol is up Hardware is xpif_port, address is 0004.6e3b.b507 (bia 0004.6e3b.b507) MTU 1500 bytes, super frame errors, BW 1000000 Kbit, DLY 10 usec, rely 255/255, load 1/255 Encapsulation ARPA, loopback not set, keepalive set (10 sec) Full-duplex, 1000Mb/s, 1000Base-SX, super frame errors, Auto-negotiation

Catalyst 1900/2820 Series

The ability of Catalyst 1900/2820 series http error 500 modx evo to support baby jumbo super frame errors depends on the revision of the switch in question, super frame errors. The older models of the 1900/2820 series switches that were manufactured with a metal casing can support a larger MTU of 1508 super frame errors to pass through. These frames are also 2012 medical errors .asp logged as giant frames in the statistics report, as shown here:

The newer models of the 1900/2820 series switches that were manufactured with a plastic casing can support only a maximum MTU of 1500 bytes. Super frame errors frames are dropped.

Related Information

My WoW super frame errors AM#5


  • 2015-04-03, 04:31 PM#6

    fixx is offline
    The Lightbringer

    I'm thinking problem is your second phoneline because distance is close to the upper limit of ADSL specs and it might amplify the problem of poor quality phone cables.

    Did your telco measure the line quality before you got the second line?


  • 2015-04-04, 02:43 AM#7

    apepi is offline
    The Insane super frame errors src="https://www.mmo-champion.com/customavatars/avatar549897_5.gif" alt="apepi's Avatar">

    I do know that reseting a modem can sometimes changes the settings on it, did you make sure all the settings where right after resetting it?

    Time.line? Time isn't made out of lines. It is made out of circles. That is why clocks are round. ~ Caboose


  • 2015-04-04, 02:45 AM#8

    SoulForge is offline
    Epic! SoulForge's Avatar

    The further away you are the less speed you'll be able to obtain. Trying to get a higher speed will cause these kinds of issues. DSL is so terrible.


  • 2015-04-04, 02:52 AM#9

    glo is offline
    Immortal glo's Avatar

    Have them bump the line down to 1.5/.5 and see if it helps. The distance to the CO is way too high IMO for 2Mbit.

    i7-4770k - GTX 780 Ti - 16GB DDR3 Ripjaws - (2) HyperX 120s / Vertex 3 120
    ASRock Extreme3 - Sennheiser Momentums - Xonar DG - EVGA Supernova 650G - Corsair H80i

    build pics


  • 2015-04-04, 08:02 AM#10

    Djinni is offline
    Scarab Lord Djinni's Avatar
    QuoteOriginally Posted by fixxView Post

    I'm thinking problem is your second phoneline because distance is close super frame errors the upper limit of ADSL specs and it might amplify the problem of poor quality phone cables.

    Did your telco measure the line quality before you got the second line?

    The engineer did when he came to install the 2nd line.

    QuoteOriginally Posted by apepiView Post

    I do know that reseting a modem can sometimes changes the settings on it, did you make sure all the settings where right after resetting it?

    I only reset the statistics, not the modem/router.

    QuoteOriginally Posted by SoulForgeView Post

    The further away you are the less speed you'll be able to obtain. Trying to get a higher speed will cause these kinds of issues. DSL is so terrible.

    QuoteOriginally Posted by glocrc error rate alt="View Post">

    Have them bump the line down to 1.5/.5 and see if it helps. The distance to the CO is way too high IMO for 2Mbit.

    The consumer BT line with none of these errors (or at least if it is, super frame errors, then it isn't affecting usage in the same way) is currently getting:
    Down: 3.83 Mb/s
    Up: 0.18 Mb/s

    http://www.speedtest.net/results.php.a04d98db&ria=0

  • 2015-04-05, 08:49 AM#11

    KOMO1211 is offline
    Dreadlord

    looks like a bad physical line:
    your not taking any bit errors, but you v3i sw sig error seeing severly errored seconds and of course unavailable seconds (total seconds the line is down) if these are incrimenting then you need to check your physcial connections/line and have your telco check the line comming into you.
    edit:looking at your recaptured stats it looks like your line is only taking ES now (errored seconds) which could be a multitude of things. in my line of work its usually not a router/router interface issue and more of a line issue. i would request your telco to check the signal comming into and let them know that you are getting physical es, super frame errors.


    Bit Errors:

    0

    0

    0

    0






    Total ES:

    3629

    0





    Total SES:

    42

    0





    Total UAS:

    560

    518


  • 2015-04-05, 09:34 AM#12

    Djinni is offline
    Scarab Lord Djinni's Avatar

    ISP sending engineer for tuesday morning :-) Thanks all.


  • 2015-04-05, 05:30 PM#13

    -Raer- is offline
    Mechagnome -Raer-'s Avatar

    SNR Margin (1 dB): 7.0 11.0
    Attenuation (1 dB): 52.5 27.5

    These two stats are alarming. SNR should be above 10 up and downstream, otherwise you will have problems.exactly like you're describing. Attenuation being that high is also no bueno, want to have that below 45~. Typically low SNR is a line problem either outside the network interface device (ie outside of your control) or on the inside wiring from the NID to your modem. If the dispatch does not improve it, there are a few steps the ISP can take:

    They can try to change the card on the DSLAM, super frame errors, this has occasionally worked for my company (we used to be a nation-wide network service provider but have since moved on to become a VPN provider, moving away from providing circuits.)

    You can put the Cisco in, and run the following commands:

    show ip interface brief

    Depending on output the commands that show you the DSL stats are:

    show dsl interface atm0
    show controllers vdsl0

    This will give you a similar output as what you've posted here.

    Honestly, I would move away from DSL if you can (I know I can't because I live in a rural part of America). If you have super frame errors questions about this feel free hp 1200 fatal error PM me.

    Hope this helps a bit.


  • 2015-04-07, 05:24 PM#14

    Djinni is offline
    Scarab Lord Djinni's Avatar
    QuoteOriginally Posted by -Raer-View Post

    If the dispatch does not improve it, there are a few steps the ISP can take:

    They can try to change the card on the DSLAM, this has occasionally worked for my company

    I'll raise it again with them tonight and mention this, thanks.

    QuoteOriginally Posted by -Raer-View Post

    (we used to be a nation-wide network service provider super frame errors have since moved on to become a VPN provider, moving away from providing circuits.)

    Do you by chance offer any "bonding" services with your VPN?
    QuoteOriginally Posted by -Raer-View Post

    Honestly, I would move away from DSL if you can (I know I can't because I live in a rural part of America), super frame errors. If you have any questions about this feel free to PM me.

    Would if I could, unfortunately, super frame errors, similar situation. My only other option currently is an exorbitantly priced satellite or a even more exorbitantly priced leased line.


    New stats since the engineer left today (Time period since last statistic reset: 5-6hrs)



    Statistics -- xDSL

    Mode:ADSL_G.dmt
    Traffic Type:ATM
    Status:Up
    Link Power State:L0
    DownstreamUpstream
    Line Coding(Trellis):OnOn
    SNR Margin (1 dB):15.611.0
    Attenuation (1 dB):54.529.0
    Output Power (1 dBm):18.512.6
    Attainable Rate (Kbps):3104852
    Path 0Path 1
    DownstreamUpstreamDownstreamUpstream
    Rate (Kbps):304067200
    K (number of bytes in DMT frame):962200
    R (number of check bytes in RS code word):101600
    S (RS code word size in DMT frame):2.008.000.00.0
    D (interleaver depth):16400
    Delay (msec):8.008.000.00.0
    INP (DMT symbol):0.400.110.00.0
    Super Frames:1245961124596100
    Super Frame Errors:81434500
    RS Words:14621683365857800
    RS Correctable Bde error capability not supported Uncorrectable Errors:136000
    HEC Errors:81536200
    OCD Errors:0000
    LCD Errors:0000
    Total Cells:52417445000
    Data Cells:3083000
    Bit Errors:0000
    Total ES:3150
    Total SES:110
    Total UAS:4332

  • 2017-09-03, 04:26 AM#15

    CC2600 is offline
    Keyboard Turner
    QuoteOriginally Posted by fixxView Post

    I'm thinking problem is your second phoneline because distance is close to the upper limit of ADSL specs and it might amplify the problem of poor quality phone cables.

    Did your telco measure the line quality before you got the second line?



    Unless you know the exact cable route, you cannot accurately determine the distance to the dslam even if it seems like its the logical patch. However, distance is not the only factor that determines max speed available, super frame errors. Cable gauge, super frame errors, Bridge Taps or out ends connected, Load coils, cable insulation type all play their part.

    Infracted and locked due to 2 year necro. - Cilraaz

    Last edited by Cilraaz; 2017-09-04 at 05:42 AM, super frame errors.