Packet loss frequntly

[rindika7966]

CCTV camera not working properly ,,, frequently disconnecting.

it's connected with cisco access switch 

[Leo Laohoo]

What is the model of the switch? 
What is the firmware of the switch?

[rindika7966]

cisco WS-C3650-48PS (MIPS) processor with 4194304K bytes of physical memory.
Processor board ID FDO1903E0EU
4 Virtual Ethernet interfaces
52 Gigabit Ethernet interfaces
2048K bytes of non-volatile configuration memory.
4194304K bytes of physical memory.
250456K bytes of Crash Files at crashinfo:.
1609272K bytes of Flash at flash:.
0K bytes of Dummy USB Flash at usbflash0:.
0K bytes of  at webui:.

Base Ethernet MAC Address          : 74:a2:e6:f7:11:00
Motherboard Assembly Number        : 73-15131-05
Motherboard Serial Number          : FDO19030PVN
Model Revision Number              : D0
Motherboard Revision Number        : A0
Model Number                       : WS-C3650-48PS
System Serial Number               : FDO1903E0EU

Switch Ports Model              SW Version        SW Image              Mode   
------ ----- -----              ----------        ----------            ----   
*    1 52    WS-C3650-48PS      03.06.00E         cat3k_caa-universalk9 INSTALL

Configuration register is 0x102

has context menu

[rindika7966]

May 27 2024 12:12:28.445 AST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/38, changed state to down
May 27 2024 12:12:30.445 AST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/38, changed state to up
May 27 2024 12:12:41.888 AST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/36, changed state to down
May 27 2024 12:12:43.887 AST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/36, changed state to up
May 27 2024 12:12:55.287 AST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/38, changed state to down
May 27 2024 12:12:57.286 AST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/38, changed state to up
May 27 2024 12:13:08.798 AST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/36, changed state to down
May 27 2024 12:13:09.468 AST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/38, changed state to down
May 27 2024 12:13:10.799 AST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/36, changed state to up
May 27 2024 12:13:11.466 AST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/38, changed state to up
May 27 2024 12:13:14.047 AST: %DOT1X-5-FAIL: Authentication failed for client (0006.6840.2afa) on Interface Gi1/0/2 AuditSessionID AC12C3A20000590E5A28B144
May 27 2024 12:13:14.067 AST: %MAB-5-FAIL: Authentication failed for client (0006.6840.2afa) on Interface Gi1/0/2 AuditSessionID AC12C3A20000590E5A28B144
May 27 2024 12:13:23.086 AST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/36, changed state to down
May 27 2024 12:13:25.088 AST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/36, changed state to up
May 27 2024 12:13:27.439 AST: %DOT1X-5-FAIL: Authentication failed for client (0050.1a38.78a2) on Interface Gi1/0/38 AuditSessionID AC12C3A20000669663E44B9E
May 27 2024 12:13:40.838 AST: %DOT1X-5-FAIL: Authentication failed for client (0050.1a38.78f2) on Interface Gi1/0/36 AuditSessionID AC12C3A20000669763E480E6
May 27 2024 12:14:03.406 AST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/38, changed state to down
May 27 2024 12:14:05.409 AST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/38, changed state to up
May 27 2024 12:14:24.565 AST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/36, changed state to down
May 27 2024 12:14:26.565 AST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/36, changed state to up
May 27 2024 12:14:30.266 AST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/38, changed state to down
May 27 2024 12:14:30.276 AST: %DOT1X-5-FAIL: Authentication failed for client (0006.6840.2afa) on Interface Gi1/0/2 AuditSessionID AC12C3A20000590E5A28B144
May 27 2024 12:14:30.300 AST: %MAB-5-FAIL: Authentication failed for client (0006.6840.2afa) on Interface Gi1/0/2 AuditSessionID AC12C3A20000590E5A28B144
May 27 2024 12:14:32.265 AST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/38, changed state to up
May 27 2024 12:14:44.515 AST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/38, changed state to down
May 27 2024 12:14:46.526 AST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/38, changed state to up
May 27 2024 12:14:51.478 AST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/36, changed state to down
May 27 2024 12:14:53.476 AST: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet1/0/36, changed state to up
PEARL-QATAR-DIST-SW#                                

has context menu

[Leo Laohoo]

And which port is the CCTV connected to?

[rindika7966]

nterface GigabitEthernet1/0/38

Interface GigabitEthernet1/0/36

we have 2 Cameras

if I connect with another switch , it's working fine

I change the port in same witch (with working one) also the same issue

Mac address whitelisted 

cable ok  and the camera ok 

[Leo Laohoo]

Do the following

test cable tdr interface G1/0/36
test cable tdr interface G1/0/38

Wait for about 15 seconds and then continue with the following commands: 

show cable tdr interface G1/0/36
show cable tdr interface G1/0/38
sh interface G1/0/36
sh interface G1/0/38

[rindika7966]

PEARL-QATAR-DIST-SW#show cable tdr int gi1/0/38
TDR test last run on: May 27 12:39:22

Interface Speed Local pair Pair length        Remote pair Pair status
--------- ----- ---------- ------------------ ----------- --------------------
Gi1/0/38  100M  Pair A     0    +/- 1  meters Pair B      Normal              
                Pair B     0    +/- 1  meters Pair A      Normal              
                Pair C     14   +/- 1  meters N/A         Short               
                Pair D     15   +/- 1  meters N/A         Short               
PEARL-QATAR-DIST-SW#test cable tdr int gi1/0/36
Link state may be affected during TDR test
TDR test started on interface Gi1/0/36
A TDR test can take a few seconds to run on an interface
Use 'show cable-diagnostics tdr' to read the TDR results.
PEARL-QATAR-DIST-SW#show cable tdr int gi1/0/36
TDR test last run on: May 27 12:41:51

Interface Speed Local pair Pair length        Remote pair Pair status
--------- ----- ---------- ------------------ ----------- --------------------
Gi1/0/36  100M  Pair A     0    +/- 1  meters Pair B      Normal              
                Pair B     0    +/- 1  meters Pair A      Normal              
                Pair C     16   +/- 1  meters N/A         Short               
                Pair D     17   +/- 1  meters N/A         Short               
PEARL-QATAR-DIST-SW#sh int gi1/0/36
GigabitEthernet1/0/36 is up, line protocol is up (connected) 
  Hardware is Gigabit Ethernet, address is 74a2.e6f7.1124 (bia 74a2.e6f7.1124)
  MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec, 
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Full-duplex, 100Mb/s, media type is 10/100/1000BaseTX
  input flow-control is off, output flow-control is unsupported 
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:16, output never, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: fifo
  Output queue: 0/40 (size/max)
  5 minute input rate 1000 bits/sec, 1 packets/sec
  5 minute output rate 1000 bits/sec, 2 packets/sec
     485373 packets input, 83617098 bytes, 0 no buffer
     Received 71337 broadcasts (57405 multicasts)
     0 runts, 0 giants, 0 throttles 
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 57405 multicast, 0 pause input
     0 input packets with dribble condition detected
     1503843 packets output, 141872175 bytes, 0 underruns
     0 output errors, 0 collisions, 3 interface resets
     0 unknown protocol drops
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier, 0 pause output
     0 output buffer failures, 0 output buffers swapped out
PEARL-QATAR-DIST-SW#sh int gi1/0/38
GigabitEthernet1/0/38 is up, line protocol is up (connected) 
  Hardware is Gigabit Ethernet, address is 74a2.e6f7.1126 (bia 74a2.e6f7.1126)
  MTU 1500 bytes, BW 100000 Kbit/sec, DLY 100 usec, 
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Full-duplex, 100Mb/s, media type is 10/100/1000BaseTX
  input flow-control is off, output flow-control is unsupported 
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:35, output never, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: fifo
  Output queue: 0/40 (size/max)
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     592798 packets input, 129831736 bytes, 0 no buffer
     Received 318687 broadcasts (206164 multicasts)
     0 runts, 0 giants, 0 throttles 
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 206164 multicast, 2 pause input
     0 input packets with dribble condition detected
     1255602 packets output, 128311300 bytes, 0 underruns
     0 output errors, 0 collisions, 7 interface resets
     0 unknown protocol drops
     0 babbles, 0 late collision, 0 deferred
     0 lost carrier, 0 no carrier, 0 pause output
     0 output buffer failures, 0 output buffers swapped out

has context menuComposeParagraph

[Leo Laohoo]

I think the cameras are failing.

[MHM Cisco World]

check storm control level you see in port 

MHM

[rindika7966]

noted with thanks 

I advise to replace the camera to CCTV Team.