HP J9091A Switch 8212zl - fail to SSH

[FixitDave]

We are unable to gather info from a HP J9091A Switch 8212zl with software revision K.15.09.0012

SNMP & SSH fails.

We are scanning the switch with our NMS using the same SNMP and telnet and all is ok.

SSH error is
Scanning SSH..
SSH server: SSH-2.0-Mocana SSH 5.3.1
Error: Unknown error


If I change the password so it's incorrect I get the following;

Scanning SSH..
SSH server: SSH-2.0-Mocana SSH 5.3.1
Error: A supplied password or user name is incorrect.


For the SNMP I get the following no matter what I put;
Scanning SNMP..
SNMP disabled or wrong community


All other switches can be scanned using SNMP with no issues.

[Hemoco]

We received this latest message via email as well. Just as an FYI for anyone else reading this topic, we're posting the reply we sent:

Lansweeper will indeed ignore all SNMP replies that are not sent from the IP address it was expecting, this was added to fix a problem with certain types of switches. The solution is to scan the IP address the switch is using to reply (192.168.36.1).

[FixitDave]

While taking a packet capture I noticed the packets were being sent to the management IP of x.x.33.1 but the core switch is replying on the vlan gateway the server is on x.x.36.1


GetIf accepts the response of UDP packets as it only looks at the source port, whereas the DeviceTester must be looking at the source port and source IP address. As the source address doesn't match it fails.

[Hemoco]

Please contact support@lansweeper.com and provide the information below. We will follow up via email.
- Link to this forum thread.
- Program Files (x86)\Lansweeper\Service\Errorlog.txt, as present on your Lansweeper server.
- Screenshot of the switch page.
- Screenshot of a DeviceTester test performed to the switch with the timeout value set to 30 and the "Version 1" SNMP version option selected. Show us the entire test window.
- Screenshot of a DeviceTester test performed to the switch with the timeout value set to 30 and the "Version 2.c" SNMP version option selected. Show us the entire test window.

[FixitDave]

Still fails, the whole test process takes about 3 seconds for the Done message.

[Hemoco]

Could you try increasing the timeout value to 30.

We would also recommend verifying whether you are running the latest Lansweeper release, in the Lansweeper web console under Configuration/Scanning Setup/Your License. Update instructions can be found on page 176 and beyond of our online documentation: http://www.lansweeper.com/documentation.pdf
If your installation does require an update, you can find the new DeviceTester in Program Files (x86)\Lansweeper\Actions on your Lansweeper server after the update.

If the issue persists, please contact support@lansweeper.com and provide:
- Link to this forum thread.
- Program Files (x86)\Lansweeper\Service\Errorlog.txt, as present on your Lansweeper server.
- Screenshot of the switch page.
- Screenshot of a DeviceTester test performed to the switch with the timeout value set to 30 and the "Version 1" SNMP version option selected. Show us the entire test window.
- Screenshot of a DeviceTester test performed to the switch with the timeout value set to 30 and the "Version 2.c" SNMP version option selected. Show us the entire test window.

[FixitDave]

I've tested v1 and v2 separately and get the same result

[Hemoco]

Could you try the "Version 1" and "Version 2.c" SNMP version options in the DeviceTester and verify whether the output is the same.

[FixitDave]

GetIf works fine with current SNMP credentials, I've also added public which also works with GetIf but it always fails with Lansweeper device tester...this is all from the Lansweeper server.

[Hemoco]

SSH scanning is only supported for *nix based systems like Linux, Unix, BSD and OS X. Other devices are preferably scanned with SNMP. The SNMP error you are seeing indicates that either:
- SNMP is disabled on the device.
- Your SNMP credential is incorrect.
- SNMP traffic is being redirected.

We recommend performing a test with Getif, another SNMP tool. Most likely it won't be able to access SNMP either. Make sure you run any tests on your Lansweeper server and with the same SNMP credential used in DeviceTester.exe.