Email Subscription Notifications Suspended Temporarily
We are in the process of making navigation in the Servers and Operating Systems forums simpler and more direct. While doing this, we have to temporarily suspend email notifications for subscriptions. If you are subscribed to one or more discussion boards or blogs in the community, please check them daily to see new content. Notifications will be turned back on in a few days. We apologize for any inconvenience this may cause. Thanks, Warren_Admin
Switches, Hubs, and Modems
cancel
Showing results for 
Search instead for 
Did you mean: 

PCM+2.0 Network Consistancy Check

Preston Gallwas
Valued Contributor

PCM+2.0 Network Consistancy Check

I'm seeing odd reports. See attached
The VLAN one concerns me, since the VLAN settings in both switches are the same
(152.157.19.48)
vlan 1
name "DEFAULT_VLAN"
untagged 1-50
ip address dhcp-bootp
ip igmp
exit
(152.157.19.82)
vlan 1
name "DEFAULT_VLAN"
untagged 1-26
ip address dhcp-bootp
ip igmp
exit

4 REPLIES
Jonathan Axford
Trusted Contributor

Re: PCM+2.0 Network Consistancy Check

I get the same errors for VLAN 1 in my report, But i am not using VLAN 1 at all!

All ports that are tagged are in other VLAN's so there might be something funny with the way the software works.
Where there is a will there is a way...
lamdor
Occasional Visitor

Re: PCM+2.0 Network Consistancy Check

Yeh..

Event I have got the same problem. But I have tried to rediscover the devices which and then produced the report then it shows properly. I think the PCM discovery should have latest data of the network before running the network consistency reports.

If we use the PCM for changing VLAN tagging insted of using CLI on the device this will work properly with out re-discovering the devices.

Preston Gallwas
Valued Contributor

Re: PCM+2.0 Network Consistancy Check

Another question, will this report show blocked RSTP ports?

If there are blocked ports, is there a way to see them if it does not?
Anders_35
Regular Advisor

Re: PCM+2.0 Network Consistancy Check

I think a previous thread in this forum mentioned something about PCM not properly updating it's information about the switches, so the "rediscover"-solution sounds plausible.

I don't remember which thread, unfortunately, but the statement came from an HP engineer, I think.