![background image](http://html.mh-extra.com/html/smc-networks/8124pl2/8124pl2_management-manual_1300682101.webp)
Configuring the Switch
3-56
CLI
– This example enables the HTTP secure server and modifies the port number.
Replacing the Default Secure-site Certificate
When you log onto the web interface using HTTPS (for secure access), a Secure
Sockets Layer (SSL) certificate appears for the switch. By default, the certificate that
Netscape and Internet Explorer display will be associated with a warning that the
site is not recognized as a secure site. This is because the certificate has not been
signed by an approved certification authority. If you want this warning to be replaced
by a message confirming that the connection to the switch is secure, you must
obtain a unique certificate and a private key and password from a recognized
certification authority.
Note:
For maximum security, we recommend you obtain a unique Secure Sockets Layer
certificate at the earliest opportunity. This is because the default certificate for the
switch is not unique to the hardware you have purchased.
When you have obtained these, place them on your TFTP server, and use the
following command at the switch's command-line interface to replace the default
(unrecognized) certificate with an authorized one:
Note:
The switch must be reset for the new certificate to be activated. To reset the
switch, type:
Console#reload
Configuring the Secure Shell
The Berkley-standard includes remote access tools originally designed for Unix
systems. Some of these tools have also been implemented for Microsoft Windows
and other environments. These tools, including commands such as
rlogin
(remote
login),
rsh
(remote shell), and
rcp
(remote copy), are not secure from hostile attacks.
The Secure Shell (SSH) includes server/client applications intended as a secure
replacement for the older Berkley remote access tools. SSH can also provide
remote management access to this switch as a secure replacement for Telnet.
When the client contacts the switch via the SSH protocol, the switch generates a
public-key that the client uses along with a local user name and password for access
authentication. SSH also encrypts all data transfers passing between the switch and
SSH-enabled management station clients, and ensures that data traveling over the
network arrives unaltered.
Console(config)#ip http secure-server
4-30
Console(config)#ip http secure-port 441
4-31
Console(config)#
Console#copy tftp https-certificate
4-64
TFTP server ip address: <
server ip-address
>
Source certificate file name: <
certificate file name
>
Source private file name: <
private key file name
>
Private password: <
password for private key
>
Summary of Contents for 8124PL2
Page 1: ...MANAGEMENT GUIDE TigerSwitchTM 10 100 1000 24 Port Managed Switch with PoE SMC8124PL2 ...
Page 2: ......
Page 20: ...xvi Contents ...
Page 27: ...xxiii Figures ...
Page 35: ...Introduction 1 8 1 ...
Page 45: ...Initial Configuration 2 10 2 ...
Page 148: ...Port Configuration 3 103 Figure 3 61 Displaying Etherlike and RMON Statistics ...
Page 473: ...Command Line Interface 4 240 4 ...
Page 477: ...Software Specifications A 4 A ...
Page 489: ...Index Index 4 menu list 3 3 panel display 3 3 ...
Page 490: ......