MSTP treats neighbors differently on access ports and trunks - why?
I have been recently playing with MSTP more closely, trying to get better under its hood, and one issue surprised me: when a MSTP-enabled switch detects a RSTP neighbor on an access port, it speaks to it using RSTP as expected. The same behavior can be observed if the neighbor is another MSTP switch that belongs to a different region - the two switches fall back to using RSTP on the link.
However, if the link interconecting the two switches is a trunk then the MSTP reverts to PVST+ operation, not to RPVST+ as I originally expected. Is there any reason for that?
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.