Couple of PCM+ problems

[Miika Räisänen]

Hi

We are currently using PCM+ version B.01.607AA and we have couple of problems.

1. HP9300 (SW version 07.7.01) and traffic graphs

For some reason reading traffic stats from 9300 does not work. Other info can be read just fine (VLANs, SW version etc...).

There are two types of error messages in events.
-No device found for segment switch_name.domain.net_port_GigabitEthernet3/2! Unable to enable sampler.
-Device at address "HP9300_IP" is not responding to SNMP requests!

MRTG is works fine with this switch and I also tried PRTG traffic grapher with success on same host where PCM runs, so problem cant be in switch's SNMP access.

2.PCM+ does not map HP3424 (SW M.08.62 and M.08.54) devices to map

We have three of these. Two are un-mapped, one is mapped with some other swithes but this group is apart from main group. It should be connected to others via HP9300. And one these unmapped devices should be connected to others via HP4100.

Any ideas or hints? :)

[André Beck]

Hi Miika,

> We are currently using PCM+ version
> B.01.607AA and we have couple of problems.

Sounds familar ;)

> There are two types of error messages in
> events.
> -No device found for segment
> switch_name.domain.net_port_GigabitEthernet3/2
> Unable to enable sampler.
> -Device at address "HP9300_IP" is not
> responding to SNMP requests!

Seeing similar problems with other plattforms as well. With 3400cl boxen I'm even seeing ASN.1 errors. The tendency for trafficd is to eventually start up correctly, work for a while and then to slowly decay. Increasing amount of error messages, inability to access the data (with the ubiquitous message "Expected data from server not received" after half a minute of progressbaring "Retrieving data"), flooding the event log with superfluous but unstoppable messages about RMON selections and sometimes sampler problems etc pp. Then again, it sometimes suddenly just works...

Have you tried to use just stats instead of the sampler? This would correspond better with your ability to MRTG the ports, however there is a difference, MRTG is usually shot on the MIB2 interface counters while trafficd stats uses RMON counters as well.

> 2.PCM+ does not map HP3424 (SW M.08.62
> and M.08.54) devices to map

Yep. There are at least two issues here:

a) 3400cl introduced LLDP and no longer transmits CDP. It can listen to CDP and populate its LLDP tables from it, but not the other way around, CDP neighbors just don't see LLDP neighbors. Topology discovery goes way harder when 3400cl are in contact with older gear that talks CDP only, but usually succeeds anyway.

b) Problems to map trunk ports correctly. I've got connections with 3400cls isolated in every VLAN map but the default one. If you have trunks between 3400cl and 4100gl you would probably see the same problems. With another platform (9300) in the game, maybe it becomes even worse and you lose topology altogether.

Waiting for 2.0 to be released,
Andre.