Viavi Xgig, Руководство пользователя

Страница: 21 / 468

Connecting the Xgig Analyzer to a Target System Chapter 1, Introduction
Xgig Analyzer User’s Guide 7
The main TCP port number used to communicate with an Xgig chassis is port 2000. If your IT
department blocks the TCP port 2000 on the network, you can still change it to 52000 or any other
number of your choice. However this change must be done on all client computers and all Xgig
chassis on your network at the same time, otherwise some chassis won't be visible and accessible
from some clients.
On the client side, you can change the default TCP port 2000 by selecting Edit Xgig TCP Port
from the
Start
menu. A dialog appears where you can type in a value for the TCP port. Click
Apply to change the port. You can also change the TCP port for the most recently used chassis by
clicking the chassis name(s) in the Most Recently Used Chassis section of the dialog. Again, you
must update all the clients and chassis on your network at the same time; otherwise the Xgig
applications will not see some chassis.
For sites where Xgig Maestro is not used, it is suggested that the DCOM port remain closed.
Network Address Translation (NAT) is not supported. An Xgig Chassis protected by a firewall that
uses Network Address Translation (NAT) cannot be accessed from Xgig clients outside the
firewall.
Finally, client-initiated chassis upgrades do not work across network firewalls since they use
random TCP port numbers between the client and the chassis. The Xgig client installers
automatically open the Windows Firewall for the syncgroupupgradeutil.exe and
probeupgradeutility.exe, but again, network firewalls will prevent the client-initiated chassis
upgrades from succeeding. In that case, you should always upgrade your chassis from the chassis
Administration web page.