98 16900 Series Logic Analysis Systems Installation Guide
5 Setting Up Multiframe Configurations
Other Multiframe Configuration Notes
Some other things to be aware of when using multiframe configurations:
• The multiframe cable is used for time correlation, cross- triggering, and
multiframe setup; all other inter- frame communication takes place over
LAN.
• Network interfaces need to see a direct path to the DHCP server.
Otherwise, Windows network configuration times will be slow, the
networks will be listed in Windows as having "limited or no network
connectivity" and the logic analysis service may fail to start properly on
individual systems. Use of static IP addressing on all systems can work
if a direct path to the DHCP server is not available, but this method is
complex and requires careful configuration.
• If you are using two or more Network Interface Cards (NICs) in a
frame, each NIC must be wired to a separate subnet so that the NICs
do not directly see each other (as suggested by the multiframe
configuration diagrams in this chapter). If the NICs do directly see each
other, networking will not work well.
I/O in Multiframe Configurations
• Trigger In/Trigger Out must be connected to whichever frame the
Agilent Logic Analyzer application connects to.
Licenses in Multiframe Configurations
If you are using probes, tools, or other application software that requires
a license, and you are using node- locked licenses, install the node- locked
licenses where the Agilent Logic Analyzer application runs:
• In the simple multiframe configurations, install node- locked licenses on
the frame from which you run the Agilent Logic Analyzer application.
• In the performance multiframe configuration, install node- locked
licenses on the performance PC.
If you are using floating licenses, the license server needs to be accessible
from the frame or performance PC on which the Agilent Logic Analyzer
application runs.
To Next Page
Loading...
Need help?
General
