Problem with ConfigScan in PCM+

[Rune Millerjord]

Hi

I am using PCM+ to manage my network, but scanning for configuration is not possible. When trying to scan, I got a timeout after 2 seconds.

Anyobdy know where to start searching for errors?

Best regards


Rune Millerjord

P.S. This thread has been moved from Switches, Hubs, Modems (Legacy ITRC forum) to PCM. - Hp Forum Moderator

[Ladrouz · Accepted solution]

Hi,
Snmp read community must match between pcm+ and your equipment.
Look at the the authorized manager in yur equipment.
bye

[Ralph Bean_2]

ladrouz's advice is excellent.

On a related note, as you troubleshoot this the 'Test Communication Parameters in PCM' feature is quite helpful.

To find this command, right-click on the problematic device in the Navigation Tree (left-hand display of devices) -> Device Access -> Test Communication Parameters in PCM.

Ralph

[Rune Millerjord]

Hi, and thanks for the reply.

I have just got back to work, and started testing what you said

But I think I got some error here.

The function "Test Communication Parameters in PCM" shows I got read access to SNMP, but not write access.

If I try to re-discover that device, I states I got connection to write parameters, but not when I test.

I have checked the settings in PCM, and they are the same as on the device.

On my HP2650's I got the following snmp-setup:

snmp-server community "narkompriv" Unrestricted
snmp-server community "narkompub" Operator
snmp-server host 10.100.4.251 "narkompriv" All
snmp-server host 10.100.4.251 "narkompub"
snmp-server enable traps Authentication

The host 10.100.4.251 is my PCM-server. I have specified narkompub as read community, and narkompriv as write community.

But still no config-scanning.

Am I missing some?

[Matt Hobbs]

Have you tried deleting the device from PCM and then doing a manual discovery for that device?

[Rune Millerjord]

I just tried deleting the device, and do a manual discovery, but still got no access to write community.

[Ladrouz]

Hi,
Can you try a "sho logging" at the telnet switch prompt and post the result ?
bye

[Rune Millerjord]

Here are the log from the switch.

As you can see I have recently installed this switch, and adjusted the time just a few days ago.

[Rune Millerjord]

By the way, I got 44 switches (mostly 2600's) and can't get this to work on either of them, except one of my 5308's.

But the SNMP-setup is the same on all switches.

[Matt Hobbs]

Have you tried the "Communicaton parameters in PCM" option to set the SNMP community names? There is obviously a mismatch at the moment between what is set on the switch and what PCM believes the community name to be.

[Rune Millerjord]

Yes, I have tried changing settings in PCM, but that does not help.

But now I tried setting Communication Parameters in device, and got an error message. (See in attached image)

Is this the reason it fails?

And in the global SNMP-settings I have to state a username, auth protocol, auth password, priv protocol and priv password. Is this settings for SNMP v3, or is it applicable for SNMPv2 too?

[Ladrouz]

Hi,
Is there a fw filtering system between the procurve manager and the switch ?

Is the PCM+ in the same network as the switch, if not , is route to switch correct from pcm?

I think your better begin with snmp V1 and validate before migrate to higher version.

If the goal is to secure transaction from pcm to switch, than forget snmpV2c and go to V3.

Can you post your switch config file?
bye

[Rune Millerjord]

DAMN!!!

I have been fooling you guys, and my self.

The SNMP-setup I referred to earlier in this thread was the one originally setup on my switches, I got it from a setup file.

But I have replaced all my switches, and there has been an error in the new setup.

An Operator statement have sneaked himself in the setup-file, so I had a statement saying

snmp-server community "narkompriv" Operator Unrestricted

Removing the Operator, and it worked.

I saw it after exporting the setup, so thanks to all of you for helping.

And sorry for misleading you..... :-(

I will close this thread.

[Rune Millerjord]

I am closing this thread.
Solution found. (Config error)