Manual
Table Of Contents
- Contents
- Figures
- Tables
- Preface
- Section I
- Basic Operations
- Chapter 1
- Starting a Web Browser Management Session
- Chapter 2
- Basic Switch Parameters
- Configuring the Switch’s Name, Location, and Contact
- Changing the Manager and Operator Passwords
- Setting the System Date and Time
- Rebooting a Switch
- Pinging a Remote System
- Returning the AT-S63 Management Software to the Factory Default Values
- Displaying the IP Address of the Local Interface
- Displaying System Information
- Chapter 3
- Enhanced Stacking
- Chapter 4
- SNMPv1 and SNMPv2c
- Chapter 5
- Port Parameters
- Chapter 6
- MAC Address Table
- Chapter 7
- Static Port Trunks
- Chapter 8
- Port Mirroring
- Section II
- Advanced Operations
- Chapter 9
- File System
- Chapter 10
- File Downloads and Uploads
- Chapter 11
- Event Logs and Syslog Servers
- Chapter 12
- Classifiers
- Chapter 13
- Access Control Lists
- Chapter 14
- Class of Service
- Chapter 15
- Quality of Service
- Chapter 16
- Denial of Service Defense
- Chapter 17
- IGMP Snooping
- Section III
- SNMPv3
- Chapter 18
- SNMPv3
- Configuring the SNMPv3 Protocol
- Enabling or Disabling SNMP Management
- Configuring the SNMPv3 User Table
- Configuring the SNMPv3 View Table
- Configuring the SNMPv3 Access Table
- Configuring the SNMPv3 SecurityToGroup Table
- Configuring the SNMPv3 Notify Table
- Configuring the SNMPv3 Target Address Table
- Configuring the SNMPv3 Target Parameters Table
- Configuring the SNMPv3 Community Table
- Displaying SNMPv3 Tables
- Section IV
- Spanning Tree Protocols
- Chapter 19
- Spanning Tree and Rapid Spanning Tree Protocols
- Chapter 20
- Multiple Spanning Tree Protocol
- Section V
- Virtual LANs
- Chapter 21
- Port-based and Tagged VLANs
- Chapter 22
- GARP VLAN Registration Protocol
- Section VI
- Port Security
- Chapter 23
- MAC Address-based Port Security
- Chapter 24
- 802.1x Port-based Network Access Control
- Section VII
- Management Security
- Chapter 25
- Encryption Keys, PKI, and SSL
- Chapter 26
- Secure Shell (SSH)
- Chapter 27
- TACACS+ and RADIUS Protocols
- Chapter 28
- Management Access Control List
- Index

Chapter 1: Starting a Web Browser Management Session
30 Section I: Basic Operations
Planning for Remote Management
There are a number of factors that need to be considered before you can
begin to remotely manage an AT-9400 Series switch with the Telnet
application protocol, the Secure Shell (SSH) protocol, or a web browser.
As explained in this section, these factors include whether the switch is an
isolated device (that is, not a member of an enhanced stack) or part of an
enhanced stack, and, if the latter, whether the switch is the master switch
of the stack or a slave switch.
Here are the main points:
An isolated or master switch must have at least one routing interface.
The routing interface must be designated as the local interface.
The master switch and slave switches of an enhanced stack must be
interconnected by a common VLAN of the local interface on the master
switch.
The remote management workstation must be able to reach an
isolated switch or a master switch through the subnet of the local
interface of the switch.
A key element in this discussion is the routing interface which first
appeared on the AT-9400 Series switches with the introduction of Layer 3
routing. An interface represents a logical connection to a network or
subnet local to the switch. The switch uses interfaces to route packets
among its local (i.e. directly connected) networks and subnets. An
interface consists of an IP address and subnet mask of a local subnet, and
the identification number (VID) of the VLAN on the switch where the
subnet resides.
Though interfaces are primarily intended for routing IPv4 packets, there
are several AT-S63 management features that require at least one
interface on a switch for the feature to function properly. The common
denominator is the need of the switch to have an IP address. Remote
management is one of those features. To remotely manage a switch you
have to be able to specify its IP address. This is true whether you are
using the Telnet application protocol, the SSH protocol, or a web browser.
(For a discussion of the other management functions that require a routing
interface, refer to Chapter 32, “Internet Protocol Version 4 Packet
Routing,” in the AT-S63 Management Software Command Line Interface
User’s Guide.
Also important to remote management is what’s referred to as the local
interface. A switch’s CPU can monitor only one local subnet for remote
management packets at a time. This makes it necessary for you to specify
the local subnet on the switch from where your remote management
station is reaching the unit. You do that by designating the subnet’s
interface as the local interface. This instructs the switch’s management