VTP domain migration

Question

Hi,
we're having a problem with the migration of VTP domaing .
For the moment our server switches are vtp server in domain X . Our distribution switches are vtp client in domain X and the access switches are in transparent mode .
The goal is to make our distribution switches VTP server and access switches vtp client .
We already did this successfully for several distrib switches and now we're trying to migrate the main building .( about 21 access switches )
When configuring the distrib switch as vtp server we loose our connection with the access switches and it doesn't come up again . In the past we had a outage of about 30 sec for spanning-tree .
We get the following message on our access switches
Aug 11 16:41:53.182 CEST: %SPANTREE-7-RECV_1Q_NON_TRUNK: Received 802.1Q BPDU on non trunk FastEthernet0/3 VLAN20.
Aug 11 16:41:53.182 CEST: %SPANTREE-7-BLOCK_PORT_TYPE: Blocking FastEthernet0/3 on VLAN0020. Inconsistent port type.
Aug 11 16:42:11.282 CEST: %SPANTREE-7-RECV_1Q_NON_TRUNK: Received 802.1Q BPDU on non trunk FastEthernet0/4 VLAN20.
Aug 11 16:42:11.282 CEST: %SPANTREE-7-BLOCK_PORT_TYPE: Blocking FastEthernet0/4 on VLAN0020. Inconsistent port type.
Aug 11 16:43:38.381 CEST: %LINK-3-UPDOWN: Interface FastEthernet0/4, changed state to down
on the website it says that link should be restored automatically .
Our ports are configured as trunks with native vlans defined
switchport access vlan 20
switchport trunk encapsulation dot1q
switchport trunk native vlan 20
switchport trunk allowed vlan 1,20,700-799
no ip address
duplex full
Does anybody have an idea about this ? My guess is that it gets stuck with recalculating the spanning-tree .I checked the bugs but nothing seems to match this case.

Answer 1

No its not the same..
Please see this :
Error Message SPANTREE-2-RECV_1Q_NON_1QTRUNK: Received 802.1Q BPDU on non 802.1Q trunk [char] [char].
Explanation A Shared Spanning Tree Protocol (SSTP) bridge protocol data unit (BPDU) was received on the listed interface. The interface was in trunk mode but was not using 802.1Q encapsulation. is The interface ID is char.
Recommended Action Verify that the configuration and operational state of the listed interface and that of the interface to which it is connected are in the same mode (access or trunk). If the mode is trunk, verify that both interfaces have the same encapsulation (ISL or 802.1Q). Once these parameters are consistent, spanning tree automatically unblocks the interface as appropriate.
http://www.cisco.com/en/US/products/hw/switches/ps663/products_system_message_guide_chapter09186a00800dea21.html#1186226
again please paste the config of the switches.
regards,
-amit singh