Black Box iPATH ACR1000A-CTL-24 User Manual page 69

Agility controller
Hide thumbs Also See for iPATH ACR1000A-CTL-24:
Table of Contents

Advertisement

PROBLEM: THE MOUSE POINTER OF THE AGILITY REMOTE IS SLOW OR SLUGGISH WHEN MOVED ACROSS
THE SCREEN.
This issue is often related to either using dithering on the video output of one or more transmitting computers or using VGA-to-DVI
video converters.
Dithering is used to improve the perceived quality and color depth of images by diffusing or altering the color of pixels between video
frames. This practice is commonly used on Apple Mac computers using ATI or Nvidia graphics cards. VGA-to-DVI converters
unwittingly produce a similar issue by creating high levels of pixel background noise.
Agility units attempt to considerably reduce network traffic by transmitting only the pixels that change between successive video
frames. When dithering is enabled and/or VGA-to-DVI converters are used, this can have the effect of changing almost every pixel
between each frame, thus forcing the Agility local to send the whole of every frame: resulting in greatly increased network traffic
and what's perceived as sluggish performance.
REMEDIES:
• Linux PCs
Check the video settings on the PC. If the Dither video box option is enabled, disable it.
• Apple Mac with Nvidia graphics
Use the Black Box utility for Mac's – Contact technical support.
• Apple Mac with ATI graphics
Use the Agility Dual series unit with Magic Eye dither removal feature.
• Windows PCs
If you suspect these issues with PC's, contact technical support for assistance.
• Replace old VGA adapters on host computers with DVI video cards.
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.
1.877.877.2269
BLACKBOX.COM
NEED HELP?
LEAVE THE TECH TO US
LIVE 24/7
TECHNICAL
SUPPORT
1.877.877.2269
69

Advertisement

Table of Contents
loading

Table of Contents