3750x shows no input packets on connected interface

[Matthew Matheus]

This is the second 3750x that we've had this problem with.  One is running 15.0(1)SE2 and the other is running 12.2(55)SE3.

 5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 712000 bits/sec, 184 packets/sec
     0 packets input, 0 bytes, 0 no buffer
     Received 0 broadcasts (0 multicasts)
     0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 0 multicast, 0 pause input
     0 input packets with dribble condition detected
     182689 packets output, 66062162 bytes, 0 underruns
     0 output errors, 0 collisions, 0 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

Now, obviously this isn't correct.  The interface is connected, it has negotiated speed/duplex, and the switch appears to be sending traffic out to the device.  Rebooting the switch corrects the issue for a while (last time it was a few months), but there seems to be an issue with this particular model of switch, and it doesn't seem to be code related.  

Anyone have any similar experiences or any tips?  Both switches are just over 1 year old (what a coincidence, right?), which seems far too soon to be seeing  hardware issues. 

[InayathUlla Sharieff]

Is the issue with only one port or all the ports on the switch?

[Matthew Matheus]

No, it's more than one port, but usually no more than 3 or 4.

[rleite]

Are you still experiencing this issue?  I have the same problem on various ports on a 2 separate closet vlans with 1 stack of 4 switches and 1 stack of 5.  They are both using 3750-X switches running (C3750E-UNIVERSALK9-M), Version 12.2(58)SE2. 

Thanks

[Matthew Matheus]

Nothing?  This simply cannot be a fluke on a nearly new $10,000 switch.

[Matthew Matheus]

Thought I should mention that the devices connected are actually not working, as they can't get a DHCP address (likely due to the problem with the port).  Moving to a different port on the same switch allows the client to function properly.