Perle Systems 5500320-12 Working with Server Settings, PerleVIEW Server Setting

102
PerleVIEW Server Settings
Working with Server Settings
PerleVIEW provides the following options for Server Settings.
zForce Secure Connections to devices (HTTPS/SSH)
zValidate CA certificates
zConfigure Web Terminal TCP Listening ports
PerleVIEW Server Setting
Force Secure
Connections to
device
(HTTPS/SSH)
Select the Force Secure Connections to device if you want Web Manager
and Web Terminal connections between PerleVIEW and the target device to
be secure connections only. For HTTPS, PerleVIEW will communicate on
TCP port 443 and for SSH communication will be on port 22. The target
devices need to have HTTPS and SSH enabled.
Validate certificate Select this option if you want HTTPS connections to validate certificates. A
valid certificate must be downloaded or exist on the target device (example
MCR-MGT Management module). Common certificate Authorities (CAs)
such as Verisign, COST, GTE, CyberTrust etc. issue certificates that are
normally already stored within your Microsoft Windows Server
environment. If you need to use a self-signed certificate or a CA certificate is
not found within the Window Server environment then you will need add the
CA certificate to your Microsoft Windows Server. See your Microsoft
Windows Server documentation for more information on how to add CA
certificates.
Web Terminal
TCP Listening Ports
The following TCP ports are for internal use only. They do not need to be
changed unless they conflict with other network services on the PerleVIEW
server.
SSH Listening
Port
Default: 4201
Values: 1-65535
Telnet Listening
Port Default: 4200
Values: 1-65535