Black Box ACR1000A-CTL-24 Manual page 68

iPATH Agility Controller
Problem: iPATH Agility Controller cannot locate working Agility units.
There are a few possible causes:
• The Agility units must be reset back to their zero config IP addresses for iPATH Agility Controller discovery. If you have a
working network of Agility unit's without iPATH Agility Controller and then add iPATH Agility Controller to the network, the
iPath manager will not discover the Agility units until they are reset to the zero config IP addresses.
• This could be caused by Layer 2 Cisco switches that have Spanning Tree Protocol (STP) enabled but do not also have portfast
enabled on the ports to which Agility units are connected. Without portfast enabled, Agility units will all be assigned the same
zero config IP address at reboot and iPATH Agility Controller will only acquire them one at a time on a random basis.
You can easily tell whether portfast is enabled on a switch that is running STP: When you plug the link cable from a working
Agility unit into the switch port, check how long it takes for the port indicator to change from orange to green. If it takes
roughly one second, portfast is on; if it takes roughly thirty seconds then portfast is disabled.
Remedies:
• Ensure that the Agility units and the iPATH Agility Controller manager are located within the same subnet. iPATH Agility
Controller cannot cross subnet boundaries.
Manually reset
• the Agility units to their zero config IP addresses.
• Enable portfast on all switch ports that have Agility units attached to them or try temporarily disabling STP on the switches
while iPATH Agility Controller is attempting to locate Agility units.
Page 68
724-746-5500 | blackbox.com