- This topic has 8 replies, 4 voices, and was last updated 1 year, 7 months ago by
.
- Posts
I have an SM200C that has worked fine for over a year, but recently I’ve been unable to talk to it and I am not sure why.
It was mounted in our ceiling on a broader LAN, so I pulled it down and direct connected over the 10Gb fiber at my desk. If I try to use Spike, it doesn’t see any device. If I monitor the connection over wireshark though, I see my machine issue an ARP request, and the SH respond with the proper MAC address, so it “sees” it….
Is there anything I can do to get it out of this weird state short of attempting to re-flash the firmware?
If you connect the SM to the PC via the USB 2.0 cable, you can go to the “SM Network Configuration” menu item in the Utilities drop down in Spike (the device must be “disconnected” in Spike for this menu item to appear). This will allow you to poll the device for what it thinks it’s current network settings are. I don’t know how the network settings would have changed but this would allow you to at least verify everything is as expected.
Have you ruled out the SFP+ transceivers or fiber cables? We’ve definitely seen these go bad before.
Do you have any other equipment that can be easily swapped or ruled out? Do you use one of the QNAP adapters? NICs?
Does the LED do anything when attempting to connect in Spike?
In the Network Settings utility, did you press the “List devices” button? That should list the network settings for all SM200Cs that are connected to the PC.
Do you happen to have a windows PC you could install Spike on and try the USB config?
I definitely trust that the Windows implementation of the USB network config to work 100%. When plugged in via USB to a Windows PC, it should also show up in the device manager as an SM200C in the Universal serial bus controllers tab in Windows (as long as you have installed Spike which installs the USB driver for the SM200C).
If on Windows you also get the device not found message in the network config dialog, or it’s not showing up in the device manager, it could be hardware failure.
When connecting in Spike, it should be toggling red/green on a ~1 second cycle, so definitely something not right.
If none of the above helps, email aj@signalhound.com and we can determine the next step. We might have to dig deeper into the FW and what might be happening.
You probably just need to update Spike, you should see the picture below.
Did this ever get resolved? I am having the same issue on a brand new one.
EHackett, if you are having this issue on a brand new unit, and followed the network configuration / troubleshooting guide without success, definitely reach out to our support team. We should be able to either help you resolve the issue or set up an RMA.
You must be logged in to reply to this topic.