With 802.1d, max number of bridges from host-host was seven. This seemed mainly due to the fact of the amount of time it took to propogate BPDU from root to edge bridge to ensure current BPDU information on edge switch did not age out.
Given that 802.1s handshakes BPDU information every 2 seconds (default) between switches and no longer uses the max-age information, does this mean that the diameter can be safely increased? The capability to now configure max hop count for all instances including IST would seem to suggest this is the case.
IST and MST instances do not use the Message Age and Maximum Age timer settings in the BPDU. IST and MST use a separate hop count mechanism that is very similar to the IP TTL mechanism.
You can configure each MST bridge with a maximum hop count.
The root bridge of the instance sends a BPDU (or M-record) with the remaining hop count that is equal to the maximum hop count.
When a bridge receives a BPDU (or M-record), it decrements the received remaining hop count by one.
The bridge discards the BPDU (M-record) and ages out the information held for the port if the count reaches zero after decrementing.
The nonroot bridges propagate the decremented count as the remaining hop count in the BPDUs (M-records) they generate.
The Message Age and Maximum Age timer settings in the RST portion of the BPDU remain the same throughout the region, and the same values are propagated by the region's designated ports at the boundary.
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.