cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2435
Views
0
Helpful
11
Replies

intermittent ping drop out. But can still receive multicast from the host

Ajaysea
Level 1
Level 1

Hi all,

I got access to an existing network to investigate an issue.

There is a core switch and numbers of edge switches connected to it.

There are numbers of VLAN setup in the network. All the VLAN interface are setup correctly on both Core switch and Edge Switches. And there's no issue to ping each other. 

There are cameras setup assigned in 4 different VLAN and connect to the edge switches. All the cameras are setup as multi-casting. 

I have no issue to receive multicast stream from any one of the cameras on workstation. And I have no issue to ping the gateway of any VLAN on workstation.

However, I can not ping to some of the cameras of VLAN2 from the workstation intermittently. And I can not ping some of them from the Core Switch intermittently neither. So I checked the configuration from core switch. And the VLAN Interface is setup with correct IP in there. 

 

Have you any advice on how can I get the ping working again and where should I check to see what happened?

 

much appreicated

 

 

11 Replies 11

Hi

Verify the STP root for those VLANs, also check the cabling.




>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<

Hi Julio,

 

Thanks for advice, I will check the STP root. But the cable is definitely fine. I don't see any drop out when I ping the device from the workstation assigned to VLAN2.

 

 

I've checked stp root for all swtiches including the core switch. They all correct.

Hello,

 

what type/model are the cameras ?

it is the Panasonic camera. But I don't think that matters since the same camera on other vlan can be pinged at all time. Even the two cameras patch one next to another on the same switch and setup in the same vlan. I can ping one of them but not another. And after 30 minutes the ping suddenly works for them.

jmperlewitz
Level 1
Level 1

What does your multi-cast setup?  Are you using a flat multicast design or are you using PIM?  Have you explicitly set your IGMP querier?

Hi jmperlewitz,

I don't understand the difference, how I can i check that?

Following command has been placed in the CS:

ip pim rp-address 1.1.1.1

no ip pim dm-fallback

ip pim register-rate-limit 100000

 

Hello
Are these POE devices?
Do they cos mark their traffic?
Are they hardcoded for speed/duplex?
What type of lan are you running on? -collapsed core/distribution - stacked/vss etc...make/model?

Can you post the following on a couple of camera ports:
show interface x/x
show interface x/x switchport
show interface x/x controllers

show interface x/x counters
show interface x/x counters errors
show interfaces err-disabled
traceroute mac <scr mac> <dst mac> 
test cable-diagnostics tdr interface x/x (
causes a bit outage to interface)
show cable-diagnostics tdr


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

I start to think it is purely routing problem. Here's the result from the command you suggest.

 

R1AS#sh int g2/0/14
GigabitEthernet2/0/14 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is 58ac.xxxx.420e (bia 58ac.xxxx.420e)
MTU 9198 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 5/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 never, output 00:00:00, 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 2087000 bits/sec, 307 packets/sec
5 minute output rate 1000 bits/sec, 2 packets/sec
15743052580 packets input, 13406945400248 bytes, 0 no buffer
Received 2765018224 broadcasts (2765014891 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 2765014891 multicast, 0 pause input
0 input packets with dribble condition detected
155963402 packets output, 12498346756 bytes, 0 underruns
0 output errors, 0 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 out


R1AS#sh int g2/0/14 switchport
Name: Gi2/0/14
Switchport: Enabled
Administrative Mode: static access
Operational Mode: static access
Administrative Trunking Encapsulation: negotiate
Operational Trunking Encapsulation: native
Negotiation of Trunking: Off
Access Mode VLAN: 2 (Camera2)
Trunking Native Mode VLAN: 1 (default)
Administrative Native VLAN tagging: enabled
Voice VLAN: none
Administrative private-vlan host-association: none
Administrative private-vlan mapping: none
Administrative private-vlan trunk native VLAN: none
Administrative private-vlan trunk Native VLAN tagging: enabled
Administrative private-vlan trunk encapsulation: dot1q
Administrative private-vlan trunk normal VLANs: none
Administrative private-vlan trunk associations: none
Administrative private-vlan trunk mappings: none
Operational private-vlan: none
Trunking VLANs Enabled: ALL
Pruning VLANs Enabled: 2-1001
Capture Mode Disabled
Capture VLANs Allowed: ALL

Protected: false
Unknown unicast blocked: disabled
Unknown multicast blocked: disabled
Appliance trust: none


R1AS#sh int g2/0/14 controller
GigabitEthernet2/0/14 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is 58ac.xxxx.420e (bia 58ac.xxxx.420e)
MTU 9198 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 5/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 never, output 00:00:00, 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 2073000 bits/sec, 310 packets/sec
5 minute output rate 2000 bits/sec, 3 packets/sec
15743327840 packets input, 13407177413203 bytes, 0 no buffer
Received 2765291511 broadcasts (2765287860 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 2765287860 multicast, 0 pause input
0 input packets with dribble condition detected
155967007 packets output, 12498660180 bytes, 0 underruns
0 output errors, 0 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 out

Transmit GigabitEthernet2/0/14 Receive
3908728660 Bytes 2585020621 Bytes
40960420 Unicast frames 93134466 Unicast frames
49615133 Multicast frames 2765288483 Multicast frames
65391484 Broadcast frames 3651 Broadcast frames
0 Too old frames 2702030672 Unicast bytes
0 Deferred frames 4177430541 Multicast bytes
0 MTU exceeded frames 526704 Broadcast bytes
0 1 collision frames 0 Alignment errors
0 2 collision frames 0 FCS errors
0 3 collision frames 0 Oversize frames
0 4 collision frames 0 Undersize frames
0 5 collision frames 0 Collision fragments
0 6 collision frames
0 7 collision frames 3167292064 Minimum size frames
0 8 collision frames 1743196566 65 to 127 byte frames
0 9 collision frames 238010003 128 to 255 byte frames
0 10 collision frames 370084354 256 to 511 byte frames
0 11 collision frames 598022505 512 to 1023 byte frames
0 12 collision frames 1036788404 1024 to 1518 byte frames
0 13 collision frames 0 Overrun frames
0 14 collision frames 0 Pause frames
0 15 collision frames
0 Excessive collisions 0 Symbol error frames
0 Late collisions 0 Invalid frames, too large
0 VLAN discard frames 0 Valid frames, too large
0 Excess defer frames 0 Invalid frames, too small
120766368 64 byte frames 0 Valid frames, too small
25275657 127 byte frames
6322819 255 byte frames 0 Too old frames
3579056 511 byte frames 0 Valid oversize frames
645 1023 byte frames 0 System FCS error frames
22492 1518 byte frames 0 RxPortFifoFull drop frame
0 Too large frames
0 Good (1 coll) frames
0 Good (>1 coll) frames


R1AS#sh int g2/0/14 counters

Port InOctets InUcastPkts InMcastPkts InBcastPkts
Gi2/0/14 13407192317757 93134604 15650207147 3651

Port OutOctets OutUcastPkts OutMcastPkts OutBcastPkts
Gi2/0/14 12498684446 40960566 49615214 65391499

R1AS#sh int g2/0/14 counters errors

Port Align-Err FCS-Err Xmit-Err Rcv-Err UnderSize OutDiscards
Gi2/0/14 0 0 0 0 0 0

Port Single-Col Multi-Col Late-Col Excess-Col Carri-Sen Runts Giants
Gi2/0/14 0 0 0 0 0 0

R1AS#traceroute mac 64-00-6a-6c-56-6a 08-00-23-e8-fd-31
Error: Source and destination macs are on different vlans.
Layer2 trace aborted.

R1AS#sh cable-diagnostics tdr int g2/0/14
TDR test last run on: August 02 17:32:19

Interface Speed Local pair Pair length Remote pair Pair status
--------- ----- ---------- ------------------ ----------- --------------------
Gi2/0/14 100M Pair A N/A N/A N/A
Pair B N/A N/A N/A
Pair C N/A N/A N/A
Pair D N/A N/A N/A

R1AS#traceroute ip 10.10.72.75
//10.10.72.75 device is patched to G2/0/14 the ping start working all of sudden but with
latency

Reply from 10.10.72.75: bytes=32 time=6ms TTL=63
Reply from 10.10.72.75: bytes=32 time=4ms TTL=63
Reply from 10.10.72.75: bytes=32 time=3ms TTL=63
Reply from 10.10.72.75: bytes=32 time<1ms TTL=63
Reply from 10.10.72.75: bytes=32 time=7ms TTL=63
Reply from 10.10.72.75: bytes=32 time=5ms TTL=63
Reply from 10.10.72.75: bytes=32 time=3ms TTL=63
Reply from 10.10.72.75: bytes=32 time=2ms TTL=63
Reply from 10.10.72.75: bytes=32 time<1ms TTL=63
Reply from 10.10.72.75: bytes=32 time=8ms TTL=63
Reply from 10.10.72.75: bytes=32 time=6ms TTL=63
Reply from 10.10.72.75: bytes=32 time=4ms TTL=63
Reply from 10.10.72.75: bytes=32 time=2ms TTL=63
Reply from 10.10.72.75: bytes=32 time=10ms TTL=63
Reply from 10.10.72.75: bytes=32 time=8ms TTL=63
Reply from 10.10.72.75: bytes=32 time=6ms TTL=63
Reply from 10.10.72.75: bytes=32 time=4ms TTL=63
Reply from 10.10.72.75: bytes=32 time=2ms TTL=63
Reply from 10.10.72.75: bytes=32 time=10ms TTL=63
Reply from 10.10.72.75: bytes=32 time=8ms TTL=63
Reply from 10.10.72.75: bytes=32 time=6ms TTL=63
Reply from 10.10.72.75: bytes=32 time=5ms TTL=63
Reply from 10.10.72.75: bytes=32 time=2ms TTL=63
Reply from 10.10.72.75: bytes=32 time=10ms TTL=63

Type escape sequence to abort.
Tracing the route to 10.10.72.75

1 10.10.101.1 9 msec 0 msec 0 msec
2 10.10.72.75 8 msec 9 msec 8 msec


R1AS#traceroute ip 10.10.72.72
//this one patched to G2/0/11 and the ping doesn't work.

Type escape sequence to abort.
Tracing the route to 10.10.72.72

1 10.10.101.1 0 msec 8 msec 0 msec
2 * * *
3 * * *

I've attached the file here. I start to think it's routing problem.

Hello

 

gig2/0/14 is hardcoded 100mbs, whats the reasoning for this?, Have you tired making both sides between switch and camera auto-negotiate?


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: