Web Management Guide-R07
Table Of Contents
- How to Use This Guide
- Contents
- Figures
- Tables
- Getting Started
- Introduction
- Key Features
- Description of Software Features
- Configuration Backup and Restore
- Authentication
- Access Control Lists
- Port Configuration
- Rate Limiting
- Port Mirroring
- Port Trunking
- Storm Control
- Static MAC Addresses
- IP Address Filtering
- IEEE 802.1D Bridge
- Store-and-Forward Switching
- Spanning Tree Algorithm
- Virtual LANs
- IEEE 802.1Q Tunneling (QinQ)
- Traffic Prioritization
- Quality of Service
- IP Routing
- Address Resolution Protocol
- Multicast Filtering
- Link Layer Discovery Protocol
- System Defaults
- Introduction
- Web Configuration
- Using the Web Interface
- Basic Management Tasks
- Displaying System Information
- Displaying Hardware/Software Versions
- Configuring Support for Jumbo Frames
- Displaying Bridge Extension Capabilities
- Managing System Files
- Setting the System Clock
- Configuring the Console Port
- Configuring Telnet Settings
- Displaying CPU Utilization
- Configuring CPU Guard
- Displaying Memory Utilization
- Resetting the System
- Using Cloud Management
- Interface Configuration
- VLAN Configuration
- Address Table Settings
- Spanning Tree Algorithm
- Congestion Control
- Class of Service
- Quality of Service
- VoIP Traffic Configuration
- Security Measures
- AAA (Authentication, Authorization and Accounting)
- Configuring User Accounts
- Web Authentication
- Network Access (MAC Address Authentication)
- Configuring HTTPS
- Configuring the Secure Shell
- Access Control Lists
- Filtering IP Addresses for Management Access
- Configuring Port Security
- Configuring 802.1X Port Authentication
- DoS Protection
- DHCP Snooping
- IPv4 Source Guard
- ARP Inspection
- Basic Administration Protocols
- Configuring Event Logging
- Link Layer Discovery Protocol
- Power over Ethernet
- Simple Network Management Protocol
- Configuring Global Settings for SNMP
- Setting the Local Engine ID
- Specifying a Remote Engine ID
- Setting SNMPv3 Views
- Configuring SNMPv3 Groups
- Setting Community Access Strings
- Configuring Local SNMPv3 Users
- Configuring Remote SNMPv3 Users
- Specifying Trap Managers
- Creating SNMP Notification Logs
- Showing SNMP Statistics
- Remote Monitoring
- Switch Clustering
- Setting a Time Range
- LBD Configuration
- Smart Pair Configuration
- Multicast Filtering
- Overview
- Layer 2 IGMP (Snooping and Query for IPv4)
- Configuring IGMP Snooping and Query Parameters
- Specifying Static Interfaces for a Multicast Router
- Assigning Interfaces to Multicast Services
- Setting IGMP Snooping Status per Interface
- Filtering IGMP Query Packets and Multicast Data
- Displaying Multicast Groups Discovered by IGMP Snooping
- Displaying IGMP Snooping Statistics
- Filtering and Throttling IGMP Groups
- MLD Snooping (Snooping and Query for IPv6)
- Filtering and Throttling MLD Groups
- Filtering MLD Query Packets on an Interface
- IP Tools
- IP Configuration
- General IP Routing
- Unicast Routing
- Overview
- Configuring the Routing Information Protocol
- Configuring General Protocol Settings
- Clearing Entries from the Routing Table
- Specifying Network Interfaces
- Specifying Passive Interfaces
- Specifying Static Neighbors
- Configuring Route Redistribution
- Specifying an Administrative Distance
- Configuring Network Interfaces for RIP
- Displaying RIP Interface Settings
- Displaying Peer Router Information
- Resetting RIP Statistics
- IP Services
- Appendices
- Glossary
Chapter 12
| Security Measures
Configuring the Secure Shell
– 270 –
To use the SSH server, complete these steps:
1. Generate a Host Key Pair – On the SSH Host Key Settings page, create a host
public/private key pair.
2. Provide Host Public Key to Clients – Many SSH client programs automatically
import the host public key during the initial connection setup with the switch.
Otherwise, you need to manually create a known hosts file on the management
station and place the host public key in it. An entry for a public key in the
known hosts file would appear similar to the following example:
10.1.0.54 1024 35 15684995401867669259333946775054617325313674890836547254
15020245593199868544358361651999923329781766065830956 10825913212890233
76546801726272571413428762941301196195566782
595664104869574278881462065194174677298486546861571773939016477935594230357741
309802273708779454524083971752646358058176716709574804776117
3. Import Client’s Public Key to the Switch – See “Importing User Public Keys” on
page 274 to copy a file containing the public key for all the SSH client’s granted
management access to the switch. (Note that these clients must be configured
locally on the switch via the User Accounts page as described on page 252.) The
clients are subsequently authenticated using these keys. The current firmware
only accepts public key files based on standard UNIX format as shown in the
following example for an RSA key:
-----BEGIN RSA PUBLIC KEY-----
MIIBCgKCAQEAmk9QvzWeYFgvjInC/jyvalribLTmx5ncPJcnC0RHsAgbuzefGRhV
RSdcx63mRUXiG968LksVXPKJeEa6cX02xZoLwbg96VPoarLTrnI8UC55XFw4c32I
q0FERXUIVQPfSt2XgPqOHi+uIaokeKJ6SV3V05CmdXwRYmSr4ZGQB2SjOp4cMpmy
TKIIfHxQ0L7WfSKJnBMgsk9ZyzvD1pZxXoHKdG87k4k9gn8d+fcV9d7xHf2255jI
1xNwPOZDHy57yjC63sO4xoYcTE7TBrCM5vqJwr17R8ioNXorpRvWZ1ump2FZTZHE
nyuoYvSJMaR8iTtboFIjEonqVX6gsLFwhwIDAQAB
-----END RSA PUBLIC KEY-----
4. Set the Optional Parameters – On the SSH Settings page, configure the optional
parameters, including the authentication timeout and the number of retries.
5. Enable SSH Service – On the SSH Settings page, enable the SSH server on the
switch.
6. Authentication – One of the following authentication methods is employed:
Password Authentication (for SSH V2 Clients)
a. The client sends its password to the server.
b. The switch compares the client's password to those stored in memory.
c. If a match is found, the connection is allowed.
Note:
To use SSH with only password authentication, the host public key must still
be given to the client, either during initial connection or manually entered into the
known host file. However, you do not need to configure the client’s keys.