Zero-Touch Deployment Considerations

Connections may cause loops, especially if the CB is running Layer 2 protocols such as STP or RSTP.

To prevent loops when the CB is running Layer 2 protocols such as STP or RSTP, configure dedicated Campus Fabric ports as SPX ports or as SPX LAGs.

Multiple links between any two units cause loops until they are converted to an SPX LAG.

Loops may cause high CPU usage if looped packets are trapped to the CPU.

The zero-touch utility does not run if the CPU use level is greater than 96 percent. Instead, the utility issues a warning that suggests using the SPX interactive-setup utility.

The SPX interactive-setup utility can run under high CPU conditions, but the utility may not find all links.

Loops should be resolved once the zero-touch or SPX interactive-setup utility has converted multiple links between any two units to SPX LAGs.

After new units become PEs and join the Campus Fabric domain, check for loops by entering the clear statistics and then the show statistics brief commands on the CB. The packet counts displayed should be low. If packet counts are high, there may still be loops in the system.