Issued critical alert for rule 'Device Down! Due to no ICMP response

[JWHolm81891]

So, there was fiber being done prior to these going down. These are IE-4000-4GC4GP4G-E switches inside traffic light control cabinets and they are daisy-chained. The switch prior to this one was down, but then came back up but isn't showing the downstream switch as a neighbor any longer, as it should be showing it on Gi1/2, but here we I am only seeing the upstream swtich: 

sw-street-name1#sh cdp neigh
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
S - Switch, H - Host, I - IGMP, r - Repeater, P - Phone,
D - Remote, C - CVTA, M - Two-port Mac Relay

Device ID Local Intrfce Holdtme Capability Platform Port ID
sw-street-name0.wl.in.gov
Gig 1/1 139 S I IE-3000-4 Fas 2/1

From switch "name1" (the one that came back up) I can see the port Gi1/2 is up:

sw-sreet-name1#sh ip int br
Interface IP-Address OK? Method Status Protocol
Vlan1 unassigned YES NVRAM administratively down down
Vlan254 10.7.254.126 YES NVRAM up up
GigabitEthernet1/1 unassigned YES unset up up
GigabitEthernet1/2 unassigned YES unset up up
GigabitEthernet1/3 unassigned YES unset administratively down down
GigabitEthernet1/4 unassigned YES unset administratively down down
GigabitEthernet1/5 unassigned YES unset administratively down down
GigabitEthernet1/6 unassigned YES unset administratively down down
GigabitEthernet1/7 unassigned YES unset administratively down down
GigabitEthernet1/8 unassigned YES unset administratively down down
GigabitEthernet1/9 unassigned YES unset up up
GigabitEthernet1/10 unassigned YES unset up up
GigabitEthernet1/11 unassigned YES unset down down
GigabitEthernet1/12 unassigned YES unset up up

However, I cannot ping it or run a traceroute to it. 

I went out to the switch "name2" (the first switch in the daisy-chain that's down, and consoled into it, and see it Up/Up. I feel like there's an ICMP issue between the name1 and name2 switches, but I can't get my head around what it exactly would be. Any suggestions?

[MHM Cisco World]

L2 interface you try to ping it?
anyway 
check 
show spanning tree 
are this port is forward or BLK ?

[JWHolm81891]

As I mentioned, ping did not work. 

#sh spaning tree

Interface Role Sts Cost Prio.Nbr Type
------------------- ---- --- --------- -------- --------------------------------
Gi1/1 Desg FWD 19 128.1 P2p
Gi1/2 Desg FWD 19 128.2 P2p

[MHM Cisco World]

Vlan254 10.7.254.126 YES NVRAM up up <<- this only IP in SW 
you ping same subnet or different ?
if different then you need 
A- default route if the ip routing run in SW
B- default GW if the ip routing not run 

if you ping same subnet 
check the SVI IP of other SW

[JWHolm81891]

Something I noticed were CRC errors on the port out to the "ICMP down" switch which tells me when they were workign on the fiber, maybe fiber got cut to that switch?:

sw-sreet-name1#sh int Gi1/2
GigabitEthernet1/2 is up, line protocol is up (connected)
Hardware is Gigabit Ethernet, address is cc16.7eab.b282 (bia cc16.7eab.b282)
Description: Downlink sw-street-name2
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 not set
Full-duplex, 100Mb/s, link type is auto, media type is 100BaseLX-FE SFP
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input 6d03h, 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 0 bits/sec, 0 packets/sec
5 minute output rate 2000 bits/sec, 4 packets/sec
2736674 packets input, 357630685 bytes, 0 no buffer
Received 1203650 broadcasts (1080255 multicasts)
0 runts, 0 giants, 0 throttles
494 input errors, 494 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 1080255 multicast, 0 pause input
0 input packets with dribble condition detected
5875794 packets output, 525080621 bytes, 0 underruns
0 output errors, 0 collisions, 1 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

[MHM Cisco World · Accepted solution]

I think you hit this issue 

[Georg Pauwen]

Hello,

just out of curiosity, how did you resolve this ? Did you change/replace the cable, or did you change the UDLD mode ?

[JWHolm81891]

I'm reaching out to our Type 2 (fiber owner we lease from) to have them check their fiber.