Allied Telesis AT-S63 - Manual (Page 385)

AT-S63 Management Software Features Guide
Section VII: Routing 385
As an example, assume you decided not to implement the IPv4 routing
feature on a switch that had four local subnets, but you wanted the switch
to send its events to a syslog server and have access to a RADIUS
authentication server. Assume also that you wanted to use a TFTP server
to upload and download files to the device. This would require that you
plan your network so that the switch could reach the syslog, RADIUS, and
TFTP servers from the same local subnet on the unit. You would also need
to assign an interface to the subnet. The switch, having only one interface,
would not route IPv4 packets among its local subnets and directly
connected networks, but would use the interface’s IP address to
communicate with the servers.
Enhanced
Stacking
The enhanced stacking feature simplifies the task of managing the Allied
Telesis switches in your network by allowing you to easily transition among
the switches in a stack during a management session.
The switches of an enhanced stack must be interconnected by a common
VLAN and the VLAN must be assigned a routing interface on each of the
switches. Furthermore, the routing interface in the common VLAN on the
master switch must be designated as the local interface, as described in
“Local Interface” on page 387.
There is an important difference between the need for interfaces with
enhanced stacking versus network servers, as explained in the previous
subsection. Network servers can be reached by the switch through
different interfaces in different subnets, simultaneously. In contrast, the
switches of an enhanced stack must share a common VLAN and subnet.
For background information and guidelines on the enhanced stacking
feature, refer to Chapter 3, “Enhanced Stacking” on page 81.
Remote Telnet,
SSH, and Web
Browser
Management
Sessions
Remote Telnet and SSH management sessions of the switch must be
transacted through a subnet that has a routing interface on the switch.
Furthermore, the interface must be designated as the switch’s local
interface. Only workstations that can reach the switch through the subnet
of the local interface can manage the unit. This rule applies to isolated
devices (that is, switches that are not a part of an enhanced stack) and a
master switch of an enhanced stack. This does not apply to a slave
switches of an enhanced stack.
For background information and guidelines on remote management, refer
to the Starting an AT-S63 Management Session Guide.