Error monitoring SF300

[sastor1983]

I have errors on ports in Cisco SF300-24p. What tools can I use to see details of errors?

[Tom Watts · Accepted solution]

Can you elaborate?

Packet capture is usually the best tool using something like Wireshark.

-Tom
Please mark answered for helpful posts

[sastor1983]

I described situation here

https://supportforums.cisco.com/thread/2216218?tstart=0

So, I write again:

I have 16 ip cameras, connected to the server with RTSP h264/mpeg4, 1280*720, via Cisco sf300-24p, powered by POE. Sometimes a few cameras suddenly lost packets, then they become unavailable in RTSP, i mean the software like VLC or ivideon don't receive video in RTSP stream at port 554. But web interface GUI still available and video in GUI also comes at web port 80. After 10-300 minutes web interface also becomes unavailable. No ping. But leds on camera and switch flash. After rebooting of the switch or changing port "Up-Down-Up" cameras work again, RTSP available. But 1-30 minutes and the problem come back again. In the port statisctics there are many errors. But I can't see details, in the switch GUI I haven't found tools for understanding. I changed LAN connectors on the cable from both sides, checked with Fluke Microscanner 2, but not sure the problems is on cable.  Connecting to another port doesn't resolve the problem. Changing rtsp to another port, ie 5540, is also unhappy - cameras work, then unavailable. At all time 12-14 cameras are almost work perfect, no errors in port statisctics. But 2-4 cameras have such problems. All they have similar firmware and settings. When I connect them on a short patch-cord they work perfect. Maybe this is a cable problem, but why port 80 work a long time, after then sometimes crash, but port 554 rtsp not available? Maybe switch collect errors and how to see them?

I installed wireshark, set up and at first step I found YAMI malfunction error. I don't understand what is it, because I'm newbie, but would like to know the way I should go. So I attach screenshot.

Also on 5 other ip cameras I have IP checksum errors:

[Tom Watts · Accepted solution]

Hi Alex, have you tried to manually set the port speed to 100 full duplex for all camera and the server they go to?

-Tom
Please mark answered for helpful posts

[sastor1983]

Hi, Tom!

Yes, I've tried to set up 100 full duplex on the most problem camera 10.16.0.214 instead 10 half duplex and now it causes problems. 50% lost ping, video unavailable. Backed up 10 half or full duplex on camera - it works. Others cameras are 100 full duplex. Also the server I changed to 100 instead 1000 and connection via teamviewer became too slow, about 10 seconds for reaction on mouse or buttons. Backed to 1000 - connection and reaction via Teamviewer became faster like realtime.

[Tom Watts]

What is the full product name of these cameras?

Can you move 5 of the camera to power adapter and leave the others on POE?

-Tom
Please mark answered for helpful posts

[sastor1983]

Thank you, Tom! I resolved problem. It was two damaged pairs in the cable, as I supposed. But finding it was difficult and Tom's advicing helped me much.

My method was installing Cisco Find It plugin for IE. Then restarting Windows and starting Find It plugin. Then I logged in the switch. As Tom said I also started Wireshark. In Cisco Statistics feature I got many errors on the problem port for the most trouble camera. Wireshark also showed errors and I started capture for deep packet analisys. The video was unstable and ping also made trouble. Then Tom said to increase the speed on the port, but it was already maximum, so I reduced speed to 10 half duplex. Wow! The video got more stable and ping too. Also I tried to switch off 5 other cameras, but it had no mention, the problem with error packets was still here. But on 10 half it worked so so, but worked. As I know on my experience with SF 300  it is very important to have good connectors and cable, because before I had the same problem connecting Gigabit Ethernet port to the server via patch-cord with damaged connectors. In that previous case I changed 100 connectors, but the problem was in the crimping tool for 10P10C HT2008, it was universal for 8pin and 10 pin, but Cisco SF300 didn't work well with it because there was a little damage in connectors and it was a bad contact. So that time I got a new crimping tool and new connectors and then it worked at Gigabit. So now I guessed the similar problem and one hour with Fluke microscanner helped me to find that some pairs in the cable was damaged - the Fluke showed 108 meters on 3-6 pair, 105.7 meters on 1-2 and 105.8 on 7-8, and 106.2 meters on 4-5 pairs. I played different color combination and also I proposed that most stable pairs was 1-2 and 7-8, it had also similar length (10 cm difference against 2 meters and 0.5 meters in other pairs). So I used that pairs and now cameras work stable, no errors.

Thank you Tom, with your help I started to learn Cisco software and other diagnostics software and methods.