<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: [CCNA] Desafio 1 da Semana 1 - Novembro de 2009</title>
	<link>http://blog.ccna.com.br/2009/11/02/ccna-desafio-1-semana-1-novembro-de-2009/</link>
	<description>Blog focado no mercado e nas certificações de T.I.</description>
	<pubDate>Sat, 11 Feb 2012 00:08:23 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.1</generator>

	<item>
		<title>By: Marco Filippetti</title>
		<link>http://blog.ccna.com.br/2009/11/02/ccna-desafio-1-semana-1-novembro-de-2009/#comment-12150</link>
		<author>Marco Filippetti</author>
		<pubDate>Mon, 14 Dec 2009 12:28:55 +0000</pubDate>
		<guid>http://blog.ccna.com.br/2009/11/02/ccna-desafio-1-semana-1-novembro-de-2009/#comment-12150</guid>
		<description>Pessoal, desculpe a demora em postar a resposta! A alternativa correta para esta questão é mesmo a alternativa "A". Para os que desejarem saber mais, segue, do site da Cisco:

Late Collisions

To allow collision detection to work properly, the period in which collisions are detected is restricted (512 bit-times). For Ethernet, this is 51.2us (microseconds), and for Fast Ethernet, 5.12us. For Ethernet stations, collisions can be detected up to 51.2 microseconds after transmission begins, or in other words up to the 512th bit of the frame.

When a collision is detected by a station after it has sent the 512th bit of its frame, it is counted as a late collision.

Late collisions are reported by these error messages:

    %AMDP2_FE-5-LATECOLL: AMDP2/FE 0/0/[dec], Late collision 
    %DEC21140-5-LATECOLL: [chars] transmit error 
    %ILACC-5-LATECOLL: Unit [DEC], late collision error 
    %LANCE-5-LATECOLL: Unit [DEC], late collision error 
    %PQUICC-5-LATECOLL: Unit [DEC], late collision error 
    %PQUICC_ETHER-5-LATECOLL: Unit [DEC], late collision error 
    %PQUICC_FE-5-LATECOLL: PQUICC/FE([DEC]/[DEC]), Late collision    
    %QUICC_ETHER-5-LATECOLL: Unit [DEC], late collision error

The exact error message depends on the platform. You can check the number of excessive collisions in the output of a show interface ethernet [interface number] command.

    router#show interface ethernet 0
    Ethernet0 is up, line protocol is up 
      Hardware is Lance, address is 0010.7b36.1be8 (bia 0010.7b36.1be8)
      Internet address is 10.200.40.74/22
      MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, 
         reliability 255/255, txload 1/255, rxload 1/255
      Encapsulation ARPA, loopback not set
      Keepalive set (10 sec)
      ARP type: ARPA, ARP Timeout 04:00:00
      Last input 00:00:00, output 00:00:06, output hang never
      Last clearing of "show interface" counters never
      Input queue: 1/75/1/0 (size/max/drops/flushes); Total output drops: 0
      Queueing strategy: random early detection(RED)
      Output queue :0/40 (size/max)
      5 minute input rate 1000 bits/sec, 2 packets/sec
      5 minute output rate 0 bits/sec, 0 packets/sec
         2058015 packets input, 233768993 bytes, 1 no buffer
         Received 1880947 broadcasts, 0 runts, 0 giants, 1 throttles
         3 input errors, 0 CRC, 0 frame, 0 overrun, 3 ignored
         0 input packets with dribble condition detected
         298036 packets output, 32280269 bytes, 0 underruns
         0 output errors, 10 collisions, 0 interface resets
         0 babbles, 0 late collision, 143 deferred
         0 lost carrier, 0 no carrier
         0 output buffer failures, 0 output buffers swapped out

Note: The station that reports the late collision merely indicates the problem; it is generally not the cause of the problem. Possible causes are usually incorrect cabling or a non-compliant number of hubs in the network. Bad network interface cards (NICs) can also cause late collisions.</description>
		<content:encoded><![CDATA[<p>Pessoal, desculpe a demora em postar a resposta! A alternativa correta para esta questão é mesmo a alternativa &#8220;A&#8221;. Para os que desejarem saber mais, segue, do site da Cisco:</p>
<p>Late Collisions</p>
<p>To allow collision detection to work properly, the period in which collisions are detected is restricted (512 bit-times). For Ethernet, this is 51.2us (microseconds), and for Fast Ethernet, 5.12us. For Ethernet stations, collisions can be detected up to 51.2 microseconds after transmission begins, or in other words up to the 512th bit of the frame.</p>
<p>When a collision is detected by a station after it has sent the 512th bit of its frame, it is counted as a late collision.</p>
<p>Late collisions are reported by these error messages:</p>
<p>    %AMDP2_FE-5-LATECOLL: AMDP2/FE 0/0/[dec], Late collision<br />
    %DEC21140-5-LATECOLL: [chars] transmit error<br />
    %ILACC-5-LATECOLL: Unit [DEC], late collision error<br />
    %LANCE-5-LATECOLL: Unit [DEC], late collision error<br />
    %PQUICC-5-LATECOLL: Unit [DEC], late collision error<br />
    %PQUICC_ETHER-5-LATECOLL: Unit [DEC], late collision error<br />
    %PQUICC_FE-5-LATECOLL: PQUICC/FE([DEC]/[DEC]), Late collision<br />
    %QUICC_ETHER-5-LATECOLL: Unit [DEC], late collision error</p>
<p>The exact error message depends on the platform. You can check the number of excessive collisions in the output of a show interface ethernet [interface number] command.</p>
<p>    router#show interface ethernet 0<br />
    Ethernet0 is up, line protocol is up<br />
      Hardware is Lance, address is 0010.7b36.1be8 (bia 0010.7b36.1be8)<br />
      Internet address is 10.200.40.74/22<br />
      MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,<br />
         reliability 255/255, txload 1/255, rxload 1/255<br />
      Encapsulation ARPA, loopback not set<br />
      Keepalive set (10 sec)<br />
      ARP type: ARPA, ARP Timeout 04:00:00<br />
      Last input 00:00:00, output 00:00:06, output hang never<br />
      Last clearing of &#8220;show interface&#8221; counters never<br />
      Input queue: 1/75/1/0 (size/max/drops/flushes); Total output drops: 0<br />
      Queueing strategy: random early detection(RED)<br />
      Output queue :0/40 (size/max)<br />
      5 minute input rate 1000 bits/sec, 2 packets/sec<br />
      5 minute output rate 0 bits/sec, 0 packets/sec<br />
         2058015 packets input, 233768993 bytes, 1 no buffer<br />
         Received 1880947 broadcasts, 0 runts, 0 giants, 1 throttles<br />
         3 input errors, 0 CRC, 0 frame, 0 overrun, 3 ignored<br />
         0 input packets with dribble condition detected<br />
         298036 packets output, 32280269 bytes, 0 underruns<br />
         0 output errors, 10 collisions, 0 interface resets<br />
         0 babbles, 0 late collision, 143 deferred<br />
         0 lost carrier, 0 no carrier<br />
         0 output buffer failures, 0 output buffers swapped out</p>
<p>Note: The station that reports the late collision merely indicates the problem; it is generally not the cause of the problem. Possible causes are usually incorrect cabling or a non-compliant number of hubs in the network. Bad network interface cards (NICs) can also cause late collisions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gilvan</title>
		<link>http://blog.ccna.com.br/2009/11/02/ccna-desafio-1-semana-1-novembro-de-2009/#comment-12060</link>
		<author>Gilvan</author>
		<pubDate>Sun, 15 Nov 2009 04:15:54 +0000</pubDate>
		<guid>http://blog.ccna.com.br/2009/11/02/ccna-desafio-1-semana-1-novembro-de-2009/#comment-12060</guid>
		<description>Já pequei esse problema, e sulucionei após reconfigurar o Switch com speedy 100 duplex full nas 2 pontas.
Aposto na opção A.
Inconsistência no duplex</description>
		<content:encoded><![CDATA[<p>Já pequei esse problema, e sulucionei após reconfigurar o Switch com speedy 100 duplex full nas 2 pontas.<br />
Aposto na opção A.<br />
Inconsistência no duplex</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mollo</title>
		<link>http://blog.ccna.com.br/2009/11/02/ccna-desafio-1-semana-1-novembro-de-2009/#comment-12054</link>
		<author>Mollo</author>
		<pubDate>Fri, 13 Nov 2009 17:44:17 +0000</pubDate>
		<guid>http://blog.ccna.com.br/2009/11/02/ccna-desafio-1-semana-1-novembro-de-2009/#comment-12054</guid>
		<description>letra “A” Inconcistência no Duplex 
Testking</description>
		<content:encoded><![CDATA[<p>letra “A” Inconcistência no Duplex<br />
Testking</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ricardo Bernardo</title>
		<link>http://blog.ccna.com.br/2009/11/02/ccna-desafio-1-semana-1-novembro-de-2009/#comment-12046</link>
		<author>Ricardo Bernardo</author>
		<pubDate>Thu, 12 Nov 2009 15:42:20 +0000</pubDate>
		<guid>http://blog.ccna.com.br/2009/11/02/ccna-desafio-1-semana-1-novembro-de-2009/#comment-12046</guid>
		<description>O modo Full Duplex utiliza um par de fios para recepção e outro para transmissão, que o corre de modo simultâneo e o protocolo de acesso ao meio - CSMA/CD - não opera neste caso e por isso não deveriam o correr colisões muito menos colisões tardias, ou seja, o problema esta sendo gerado por uma inconsistência no duplex. Letra "A".</description>
		<content:encoded><![CDATA[<p>O modo Full Duplex utiliza um par de fios para recepção e outro para transmissão, que o corre de modo simultâneo e o protocolo de acesso ao meio - CSMA/CD - não opera neste caso e por isso não deveriam o correr colisões muito menos colisões tardias, ou seja, o problema esta sendo gerado por uma inconsistência no duplex. Letra &#8220;A&#8221;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

