i will post it but after 12 hours when i take it frome switch

thank you very much for quick replay

no error message appears to me

this is the port status during problem

now i think it mis match duplex because i see the port is half duplex and indigo vision is full duplex

but this problem doesnot appeare permenant

it is some times only

FastEthernet1/0/28 is up, line protocol is up (connected)

Hardware is Fast Ethernet, address is 0022.bea4.f720 (bia 0022.bea4.f720)

MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,

reliability 255/255, txload 1/255, rxload 1/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Half-duplex, 100Mb/s, media type is 10/100BaseTX

input flow-control is off, output flow-control is unsupported

ARP type: ARPA, ARP Timeout 04:00:00

Last input never, output 00:00:01, output hang never

Last clearing of "show interface" counters never

Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 362000 bits/sec, 62 packets/sec

5 minute output rate 17000 bits/sec, 32 packets/sec

43827 packets input, 35284048 bytes, 0 no buffer

Received 0 broadcasts (0 multicasts)

0 runts, 0 giants, 0 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

0 watchdog, 0 multicast, 0 pause input

0 input packets with dribble condition detected

37089 packets output, 2783410 bytes, 0 underruns

0 output errors, 65 collisions, 1 interface resets

0 babbles, 0 late collision, 0 deferred

0 lost carrier, 0 no carrier, 0 PAUSE output

0 output buffer failures, 0 output buffers swapped ou

no error message appears to me

this is the port status during problem

now i think it mis match duplex because i see the port is half duplex and indigo vision is full duplex

but this problem doesnot appeare permenant

it is some times only

FastEthernet1/0/28 is up, line protocol is up (connected)

Hardware is Fast Ethernet, address is 0022.bea4.f720 (bia 0022.bea4.f720)

MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,

reliability 255/255, txload 1/255, rxload 1/255

Encapsulation ARPA, loopback not set

Keepalive set (10 sec)

Half-duplex, 100Mb/s, media type is 10/100BaseTX

input flow-control is off, output flow-control is unsupported

ARP type: ARPA, ARP Timeout 04:00:00

Last input never, output 00:00:01, output hang never

Last clearing of "show interface" counters never

Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 362000 bits/sec, 62 packets/sec

5 minute output rate 17000 bits/sec, 32 packets/sec

43827 packets input, 35284048 bytes, 0 no buffer

Received 0 broadcasts (0 multicasts)

0 runts, 0 giants, 0 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

0 watchdog, 0 multicast, 0 pause input

0 input packets with dribble condition detected

37089 packets output, 2783410 bytes, 0 underruns

0 output errors, 65 collisions, 1 interface resets

0 babbles, 0 late collision, 0 deferred

0 lost carrier, 0 no carrier, 0 PAUSE output

0 output buffer failures, 0 output buffers swapped ou

now it,s ok

no collision

and led is green

what is the reason for collision ????

In a half duplex Ethernet network, a collision is the result of two devices on the same Ethernet network attempting to transmit data at exactly the same time. The network detects the "collision" of the two transmitted packets and discards them both. Collisions are a natural occurrence on Ethernets. Ethernet uses Carrier Sense Multiple Access/ Collision Detect (CSMA/CD) as its method of allowing devices to "take turns" using the signal carrier line. When a device wants to transmit, it checks the signal level of the line to determine whether someone else is already using it. If it is already in use, the device waits and retries, perhaps in a few seconds. If it isn't in use, the device transmits. However, two devices can transmit at the same time in which case a collision occurs and both devices detect it. Each device then waits a random amount of time and retries until successful in getting the transmission sent.

The best remedy for collisions is to upgrade to a full duplex switched environment.

Hope this addresses your questions

Hi Lavramov,

Indigo Vision CCTV Racks are 10/100/1000 ethernet adapter and the adapters of the Indigo VIsion racks are working in auto-sense.

I also had the same problem with input/crc and output error when I fixed the speed to 100 and duplexing to full.

Do not fixe the speed and duplex anymore. Set both to auto and the issue will disappear.

Regards.