01-20-2009 05:25 PM - edited 03-06-2019 03:32 AM
Hi Netpro.
anyone who has encountered this before ?
Jan 12 09:32:09.701 CCT: %DHCPD-4-PING_CONFLICT: DHCP address conflict: server pinged 192.168.29.118.
Jan 12 18:04:07.159 CCT: %DHCPD-4-DECLINE_CONFLICT: DHCP address conflict: client 0100.1d72.8439.b9 declined 192.168.29.86.
Jan 19 03:07:53.777 CCT: %SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id 4126 on Port-channel1 VLAN30.
Jan 19 03:07:53.777 CCT: %PM-3-INTERNALERROR: Port Manager Internal Software Error (vlanid >=0 && vlanid < PM_MAX_VLANS: ../switch/pm/pm_vlan.c: 584:
pm_vlan_get_vlan_data)
-Traceback= 280E24 2B52BC 2C1350 33A940 33DE60 30D97C 30E91C 1D2310 1CC7E0
Jan 19 03:07:53.777 CCT: %SPANTREE-2-BLOCK_PVID_LOCAL: Blocking Port-channel1 on VLAN0030. Inconsistent local vlan.
Jan 19 03:08:08.781 CCT: %SPANTREE-2-UNBLOCK_CONSIST_PORT: Unblocking Port-channel1 on VLAN0030. Port consistency restored.
Jan 20 16:21:54.751 CCT: %STANDBY-6-STATECHANGE: Vlan10 Group 1 state Standby -> Active
Jan 20 16:21:54.799 CCT: %STANDBY-6-STATECHANGE: Vlan10 Group 1 state Active -> Speak
Jan 20 20:50:57.722 CCT: %STANDBY-6-STATECHANGE: Vlan10 Group 1 state Standby -> Active
Jan 20 20:50:57.734 CCT: %STANDBY-6-STATECHANGE: Vlan10 Group 1 state Active -> Speak
your reply will be highly appreciated.
thanks.
regards,
jack
01-21-2009 01:19 PM
In general, trackback might indicate a software issue. But it might be cosmetic and won't impact the performace/operation. Can you post "show ver" here?
01-21-2009 01:43 PM
Hello Jack,
on a trunk port portchannel 1 an inconsistent BPDU is received with an external vlan tag different from the vlan field inside the BPDU itself (Cisco PVST+ BPDU format on trunks).
This event normally should only trigger the events of blocking the port for vlan 30 and later to unblock.
in your case instead we see a software error event:
Jan 19 03:07:53.777 CCT: %PM-3-INTERNALERROR: Port Manager Internal Software Error (vlanid >=0 && vlanid < PM_MAX_VLANS: ../switch/pm/pm_vlan.c: 584:
pm_vlan_get_vlan_data)
-Traceback= 280E24 2B52BC 2C1350 33A940 33DE60 30D97C 30E91C 1D2310 1CC7E0
as you can see a C procedure contained in file pm_vlan.c returned an illegal code and a traceback has been produced as a result of the SW error.
If this doesn't happen anymore you should be fine otherwise you should consider to perform an IOS upgrade in your switch.
As we can see the SW error hadn't blocked events cycle: the port has been put in STP blocking for vlan 30
When the offending BPDU stopped to be received (it was only one) the port has been put again in unblocking.
Hope to help
Giuseppe
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide