Allied Telesis AT-S63 - Manual (Page 558)

Chapter 32: Internet Protocol Version 4 Packet Routing
558 Section VII: Internet Protocol Routing
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 an TFTP
server to upload and download files to the device. To accomplish this, you
would need to plan your network so that the switch could reach the syslog,
RADIUS, and TFTP servers from the same local subnet on the unit, and
you would need to assign an interface to the subnet. The switch, having
only one interface, would not route IPv4 packets among its local subnets,
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
Telesyn switches in your network by allowing you to easily transition
among the switches in a stack during a management session.
The master switch of a stack must have an interface on the common
VLAN and subnet that interconnects the switches of the stack.
Furthermore, the interface must designated as the local interface,
described in “Local Interface” on page 559.
There is important an important difference between the need for interfaces
for enhanced stacking versus network servers, as explained in the
previous subsection. As previously explained, a switch can reach network
servers through different interfaces of different subnets, simultaneously. In
contrast, the switches of an enhanced stack must share a common VLAN
and subnet, and the interface on the common subnet must be designated
as the local interface on the master switch.
For background information and guidelines on the enhanced stacking
feature, refer to the AT-S63 Management Software Menus Interface
User’s Guide.
Remote Telnet, SSH, and Web Browser Management Sessions
To remotely manage a switch using a Telnet or SSH client, or a web
browser application, the remote management workstation must access the
switch through a subnet that has a routing interface. Furthermore, the
interface must be designated as the local interface on the switch. Only a
workstation that can reach the switch through the subnet of the local
interface can manage the unit. This rule applies to an isolated device (that
is, a switch that is not a part of an enhanced stack) and a master switch of
a stack. This does not apply to a slave switch of a stack.
For background information and guidelines on remote management, refer
to the AT-S63 Management Software Menus Interface User’s Guide.