A customer reached out to disccuss their TASKalfa machines 4501i and 6501i sporadically dropping off the network. They have noted that the machines may go down once a day or sometimes 3 times a day. They have also noted that the machines have been going down more frequently lately.
The boss went with a senior tech last week and the tech performed a reset. After that it seemed to be fine, for a day. I was asked to go on-site (I am IT/Networking) to determine if it could be the customer network. My diagnostic route was as follows:
During my examination with the customer right next to me, the machine became unresponsive to the network, meaning the NIC lights on both the copier and my laptop went out, ping was unresponsive and Command Center did not load pages. This is exactly what the customer has been noting with their tickets to us. They also noted that when this happens they simply unplug the NIC from the copier and plug it back in, so I did the same and lights came back on from the copier and laptop, but ping responses were still a mess.
I set the copier NIC from AUTO to 1000Mbps FULL and restarted the network stack. This only caused Ping Timeouts momentarily and the ping mess started all over again. So now I decided to test their network. First connected back to the wall port, performed a ping test to their router, consistently <1ms. Ping test to the DHCP server, consistently <1ms. Ping test to google, yahoo, msn, all consistent and within reasonable ranges. I performed a speed test with iperf3 for a short and long run, both showed averages about 945Mbps in both directions. Using a Fluke CableIQ I certified the cable run from the copier to the patch panel for the switchport. It showed the cable was a Cat5e which is older but sufficient for their needs.
Thinking of the copier now as a computer (since it is a Unix variant) I started to ask myself "what could cause this ping mess and even shut down the NIC?" and I remembered that one thing can be the source of this pain. Given all the variables I have experienced this with a few computers when the HDD begins to fail. As there is no way to perform a SMART diagnostic report on the copier, I want to assume this may be the case.
Has anyone else had any similar scenarios? Also while I don't think this is related, I am curious, can anyone explain to me why there are 2 HDD's in the copier?
Thanks.
The boss went with a senior tech last week and the tech performed a reset. After that it seemed to be fine, for a day. I was asked to go on-site (I am IT/Networking) to determine if it could be the customer network. My diagnostic route was as follows:
- Connect to the customer network with laptop using DHCP in order to acquire network information
- Set my laptop to static IP with the DHCP information
- Direct connect laptop NIC to copier NIC via Ethernet
- Begin constant ping of copier in one window
- Noted that latency was initially high and all over the place between 161ms and 4863ms and jumping with every response
- Connected with Command Center to verify no settings were incorrect
- Verified no sleep mode was enabled
During my examination with the customer right next to me, the machine became unresponsive to the network, meaning the NIC lights on both the copier and my laptop went out, ping was unresponsive and Command Center did not load pages. This is exactly what the customer has been noting with their tickets to us. They also noted that when this happens they simply unplug the NIC from the copier and plug it back in, so I did the same and lights came back on from the copier and laptop, but ping responses were still a mess.
I set the copier NIC from AUTO to 1000Mbps FULL and restarted the network stack. This only caused Ping Timeouts momentarily and the ping mess started all over again. So now I decided to test their network. First connected back to the wall port, performed a ping test to their router, consistently <1ms. Ping test to the DHCP server, consistently <1ms. Ping test to google, yahoo, msn, all consistent and within reasonable ranges. I performed a speed test with iperf3 for a short and long run, both showed averages about 945Mbps in both directions. Using a Fluke CableIQ I certified the cable run from the copier to the patch panel for the switchport. It showed the cable was a Cat5e which is older but sufficient for their needs.
Thinking of the copier now as a computer (since it is a Unix variant) I started to ask myself "what could cause this ping mess and even shut down the NIC?" and I remembered that one thing can be the source of this pain. Given all the variables I have experienced this with a few computers when the HDD begins to fail. As there is no way to perform a SMART diagnostic report on the copier, I want to assume this may be the case.
Has anyone else had any similar scenarios? Also while I don't think this is related, I am curious, can anyone explain to me why there are 2 HDD's in the copier?
Thanks.
Comment