Heavy Packet Loss with a 4351-ISR and NIM-ES2-4

[Tom.R]

Hello,

I have a 4351-ISR and am experiencing Heavy packet loss with one of the subnets I have uplinked. Is there a command to use in order to look at the health and or logs that the NIM might have which aren't showing on the traditional show commands?

The command I'm using is...

4351#sh hw-module subslot 0/1 ?

!

attribute   Show module attribute information

entity   entity MIB details - not intended for production use
oir   Show oir summary
sensors   Environmental sensor summary
subblock   subblock details - not intended for production use
tech-support   Show subslot information for Tech-Support

!

Entity state for SPA in subslot 0/1
SPA type: (0xC72) NIM-ES2-4
last spa type: (0xC72) NIM-ES2-4
oper_status: (1) ok
card status: (2) full
last trap: spa type: (0xC72) NIM-ES2-4
last trap: oper status: (1) ok
last_spa_env_get_ok: false
last_spa_env_read_time: (28760970478) 4294967295 msecs ago
resync_reqd: false
resync_count: 0

SPA physical index: 1245
SPA container index: 1001

SPA has no transceiver subblock
non-zero port indices:
port 0 has index 1246
port 1 has index 1247
port 2 has index 1248
port 3 has index 1249

non-zero SPA temp sensors:
all temp sensor indices are zero

non-zero SPA volt sensors:
all volt sensor indices are zero

non-zero SPA power sensors:
sensor 0 has index 1302

I don't get much beyond the actual hardware and status.

Here's the packet loss I'm getting...

Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.X.X: bytes=32 time=5ms TTL=252
Reply from 192.168.X.X: bytes=32 time=2ms TTL=252
Request timed out.
Reply from 192.168.X.X: bytes=32 time=2ms TTL=252
Reply from 192.168.X.X: bytes=32 time=2ms TTL=252
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.X.X: bytes=32 time=2ms TTL=252
Reply from 192.168.X.X: bytes=32 time=2ms TTL=252
Reply from 192.168.X.X: bytes=32 time=2ms TTL=252
Reply from 192.168.X.X: bytes=32 time=2ms TTL=252
Reply from 192.168.X.X: bytes=32 time=2ms TTL=252
Request timed out.
Reply from 192.168.X.X: bytes=32 time=2ms TTL=252
Request timed out.
Reply from 192.168.X.X: bytes=32 time=2ms TTL=252
Request timed out.
Reply from 192.168.X.X: bytes=32 time=2ms TTL=252
Request timed out.
Reply from 192.168.X.X: bytes=32 time=8ms TTL=252
Reply from 192.168.X.X: bytes=32 time=2ms TTL=252
Reply from 192.168.X.X: bytes=32 time=8ms TTL=252
Reply from 192.168.X.X: bytes=32 time=2ms TTL=252
Reply from 192.168.X.X: bytes=32 time=2ms TTL=252
Reply from 192.168.X.X: bytes=32 time=10ms TTL=252
Reply from 192.168.X.X: bytes=32 time=2ms TTL=252
Reply from 192.168.X.X: bytes=32 time=2ms TTL=252
Reply from 192.168.X.X: bytes=32 time=2ms TTL=252

[Joseph W. Doherty]

How do you know of your heavy packet loss? Reason I ask, ping loss doesn't always indicate packet loss.

[Tom.R]

Packet loss may not be the right choice of words.. it was heavy intermittent connection loss.

I figured it out. Return traffic was following routes established by EIGRP and with that one of the circuits was having issues and EIGRP was bouncing between the failing circuit and the backup. Had to configure a static route to prevent EIGRP from jumping between the two.