Allied Telesis AT-S63 - Manual (Page 42)

Chapter 1: Overview
42 Section I: Basic Operations
Stack IP Address
A stack does not need an IP address to forward network packets through
the ports of the switches. However, it does need an address if it will be
performing any of the following management functions:
ˆ Remote Telnet management
ˆ Sending event messages to a syslog server
ˆ Sending or receiving TCP/IP pings
ˆ Uploading or downloading files to the master switch’s file system from
a TFTP server
To assign an IP address to the stack you have to create an IPv4 routing
interface. The stack uses the routing interface’s IP address as its address
when performing the functions listed above. You can create only one
routing interface on a stack because a stack does not support the IPv4 IP
routing feature in the AT-S63 Management Software. For further
information on routing interfaces, refer to the AT-S63 Management
Software Features Guide.
Here are the general steps to assigning an IP address to the stack:
1. Create a virtual LAN (VLAN) on the stack. The VLAN must include the
port(s) from where the stack will communicate with the remote servers
or the Telnet clients. You can skip this step if you will be using the
Default_VLAN for the remote management sessions. The commands
for creating VLANs are in Chapter 17, “Port-based and Tagged VLAN
Commands” on page 261.
2. Add an IPv4 routing interface to the VLAN. The command for creating
a new IPv4 routing interface is “ADD IP INTERFACE” on page 280. If
the IP addresses of the routing interface and the remote servers or
Telnet clients are part of different subnets, the subnets must be
connected with Layer 3 routing devices.
3. To manage the stack from a remote Telnet client, designate the
routing interface as the stack’s local interface with “SET IP LOCAL
INTERFACE” on page 290. This instructs the management software to
monitor the subnet of the interface for the remote management
packets from the Telnet client.