Hello
I havnt worked a lot with nexus to be honest but given it compatibility with iOS stp (802.1s mst) you shouldn't have not a lot of heart ache as in "theory" your just attaching another "switch" provisionally as a mst client
Prior to attaching the nexus I would defiantly define the mst region etc on it and also all it's stp port types And assuming your running vtp2 on the network also suggest reverting the vtp revision number to 0 prior to attaching and let the existing vtp core propergate the vlan database and then once thats completed revert the nexus to transparent
note vtp3. - allows the mst region to be sync to all switches in its vtp domain thus its mst config is shared automatically. Thus it provides a more secure way of negating the vtp database from being over wrote .
The interconnect between the 6500 and the nexus will be aggregated if not I would advise not to manually prune with mst as you would want both msti's to work accordingly.
I would say then once all the access switches and l3 has been migrated you can change the mst root
res
paul
Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.
Kind Regards
Paul
