Collision detection in my WAN

There is a few time, my ISP told me that he noticed thath there are lot off collision in my wan network. As i see the cacti graph, every thing is fine in the bandwith. Some time, there are some pic but i identife the clients who are responsible.but the traffic is allowed. So i need help to how can i know that there are lot of collision. Is there a network monitor witch can help me ?
Who is Participating?
Nothing out of the ordinary.  Since you are charting bandwidth and have snmp set up, you could use a SNMP monitor to record interface errors, etc.   Try but there are many more out there.
Look at the interface(s) of the router for CRC or input ouput erros

Link to management software list
beke_josueAuthor Commented:
i have a cisco asa 5510, can you explain me the step ?
On-Demand: Securing Your Wi-Fi for Summer Travel

Traveling this summer?Check out our on-demand webinar to learn about the importance of Wi-Fi security and 3 easy measures you can start taking immediately to protect your private data while using public Wi-Fi. Follow us today to learn more!

If ethernet hand off, check the WAN interface, are you running full duplex?  If yes, i would have the ISP check their hand off for half duplex.  A fiber to copper transceiver could also not negotiate properly and negotiate to half duplex.
beke_josueAuthor Commented:
See below the show interface commande for my routeur. Can you confirme that there is not collision? Or can you give me an explicit interpretation?
Interface Ethernet0/0 "x", is up, line protocol is up
  Hardware is i82546GB rev03, BW 1000 Mbps, DLY 10 usec
      Auto-Duplex(Full-duplex), Auto-Speed(1000 Mbps)
      MAC address 0023.5e25.4612, MTU 1500
      IP address 172.x.x.x, subnet mask x.x.x.x
      9070802038 packets input, 11664249371572 bytes, 0 no buffer
      Received 5 broadcasts, 0 runts, 0 giants
      11 input errors, 0 CRC, 0 frame, 11 overrun, 0 ignored, 0 abort
      0 L2 decode drops
      7863652186 packets output, 3158970316258 bytes, 0 underruns
      0 output errors, 0 collisions, 0 interface resets
      0 babbles, 0 late collisions, 0 deferred
      0 lost carrier, 0 no carrier
      input queue (curr/max packets): hardware (1/33) software (0/0)
      output queue (curr/max packets): hardware (0/84) software (0/0)
  Traffic Statistics for "MTL-INT":
      9070800587 packets input, 11498391870738 bytes
      7863652186 packets output, 2993833563110 bytes
      245673 packets dropped
      1 minute input rate 375 pkts/sec,  41602 bytes/sec
      1 minute output rate 1456 pkts/sec,  874366 bytes/sec
      1 minute drop rate, 0 pkts/sec
      5 minute input rate 415 pkts/sec,  65137 bytes/sec
      5 minute output rate 1457 pkts/sec,  843084 bytes/sec
      5 minute drop rate, 0 pkts/sec
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.