As we're building out our g.8032 rings we've hit a snag in quickly forcing loops to test our remediation plans. Anyone care to share methodologies of how to break things on purpose?
Usually, what we do to cause a loop in the ring is the following:
1. With the ring in the Idle state, apply a Forced Switch (FS) on a ring port anywhere other than at the RPL owner. This unblocks the RPL owner.
2. Set the Admin State of the Protection Group where the FS is applied to Locked to Disable. This essentially disables protection at that node, causing the port that is blocked due to the FS to be unblocked. Because the protection group is disabled, no RAPS message will be transmitted to the other ring members, so they will remain unblocked. At this point, you'll have a loop.
3. If you have the Loop Detection feature enabled, this feature should detect the loop, force a blocking point, and raise an alarm.
One thing you can do is turn off RSTP and MSTP on the ports of your edge device. Put both ports in service. VLANs will need to be on both ports. You'll have a nice loop on your network.
Thanks immensely for such a clean and simple method. Looking forward to some break testing this week to see how well it works
Retrieving data ...