Understanding Mismatched Configuration Digests in MSTP
Question
You have recently configured MSTP on two switches in your network to participate in the same MSTP region. You issue the show spanning-tree mstp configuration command on both switches and notice that the configuration digests do not match. What does this mismatch indicate?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.D
The configuration digests in MSTP are used to ensure that all switches in the MSTP region have the same MSTP configuration. When the configuration digests do not match, it indicates that there is a problem with the MSTP configuration that needs to be resolved. Therefore, option A is incorrect.
Option B suggests that the max-age and hello timers should be equal on both switches. While it is important to ensure that the timers are configured correctly, a mismatch in the configuration digests indicates a more fundamental problem with the MSTP configuration. Therefore, option B is incorrect.
Option C suggests that the bridge IDs and priority values should be unique on both switches. This is an important aspect of configuring MSTP. If the bridge IDs and priority values are not unique, it can cause problems with the MSTP convergence process. Therefore, option C is a plausible answer.
Option D suggests that the MSTIs and their VLAN IDs should be equal on both switches. This is also an important aspect of configuring MSTP. If the MSTIs and VLAN IDs are not equal on both switches, it can cause problems with the forwarding of traffic across the network. Therefore, option D is also a plausible answer.
In conclusion, the correct answer depends on the specific details of the MSTP configuration. It is important to carefully review the configuration of both switches to identify the source of the configuration digest mismatch and to take appropriate action to resolve the issue.
