Procurve Manager 3.2 / HP Procurve 4200vl and 2810-48G

[Adam Dodwell]

We have 6 Procurve 4200vl and 7 Procure 2810-48G switches on our LAN which are not showing traffic data in Procurve Manager. All of our other (older) HP switches are showing fine.

We have been using PCM 3.1 with a 50 node license, but we also get the same problem with the free trial of PCM 3.2

On the traffic screen there is no data, just a message 'awaiting data'.

Any assistance would be appreciated.

P.S. This thread has been moevd from Switches, Hubs, Modems (Legacy ITRC forum) to ProCurve / ProVision-Based. - Hp Forum Moderator

[Tool]

Is SNMP onfigured correctly onto the 4200vl and 2810-48G switches?
HP Procurve uses the read/write community string for configuring sflow.

[Adam Dodwell]

Thanks for the reply. Can you expand on 'SNMP being configured correctly'.

We have tested the SNMP communication, and the SNMP Read Community and Write Community have 'restricted access'.

How do we change this?

thanks

[Steve Britt]

Adam,

Is PCM trying to collect sFlow traffic from these switches or statistics data? Are you getting sFlow data from the older devices (which you said seem to be working) or just statistics?

The reason I ask is that sFlow requires UDP port 6343 to be opened in any firewalls that might be between your PCM agent and the devices sending the sFlow (including a firewall on the agent system itself); if you're already getting sFlow from the older devices then this is obviously not the case, but if you're not getting any sFlow anywhere this could possibly be the issue.

Regards,

SVB

[Konstantin Dimitrovski]

Have you managed to solve this problem.
I'm also experiencing the same on ProCurve Manager 3.2 and 2910al-48g.
I've checked the SNMP and CLI configurations on the switch and in PCM and everything seem OK. Even PCM says SUCCESS to everything when I run the Test Communication Parameters.

Thanks in advance!

Konstantin

[Adam Dodwell]

We still haven't got this fixed, even though we have checked everything suggested so far.

We have an engineer coming on site on Thursday to look at this, so if we get an answer I will post it here!

[abdullah.shboull]

make sure that you have run the latest fixed update of PCM+, and also upgrade your switches firmware.
one more thing is restart all PCM services and make sure there is no firewall block the sFlow traffic such as antivirus application.

[Konstantin Dimitrovski]

Well my PCM verison is 3.20.1741. On this website: http://h10144.www1.hp.com/customercare/support/software/network_management.htm i couldn't find any updates for PCM 3.20.
Also I updated the 2910al-48G switch to the newest sw version: W.14.49.
Any other suggestions?

PS. Adam I would really apreciate if you post your findings with the support engineer.

[Konstantin Dimitrovski]

I just want to update this thread.
I managed to somehow get the traffic monitor to work on the 2910.
I don't know what exactly helped for this.
I did an auto update of the PCM and it did find some 3.20.1741_1 update so I installed it. After this I also fiddeled with the SNMP setting, but notting special.
Not sure what helped...

[Konstantin Dimitrovski]

Adam, could you please tell us what happened? Did you solve the problem with the engineer?

[Stuart Knetsch]

I had the same problem with one of my 2810 switches. We had purchased and installed two units at the same time on the same network. One was working with PCM, one did not.

To enable SFlow on the none-functioning unit, I had to set the snmp-server community **** to manager with unrestricted Write access.

Then I had to delete the device from PCM and rediscover it.

After rediscovery, PCM was monitoring the device. You can verify the SFlow status on the switch by typing "show sflow all" in configure mode. You should see sflow enabled and the destination address of your PCM host. If sflow is disabled, it means PCM cannot configure it due to a snmp community permission or name mismatch used in the discovery.