Allied Telesis AT-S63 - Manual (Page 394)

Chapter 32: Internet Protocol Version 4 Packet Routing
394 Section VII: Routing
Non-routing Command Example
This example illustrates how to assign an IP address to a switch by
creating just one interface. This example is appropriate in cases where
you want to implement the management functions described in “Routing
Interfaces and Management Features” on page 384 but without IPv4
packet routing. This section is also appropriate for the AT-9400 Layer 2+
Switches, which do not support packet routing.
The first step is to select the VLAN and subnet on the switch for the
interface. The appropriate VLAN for the master switch of an enhanced
stack is the common VLAN of the switches in the stack. The appropriate
VLAN for remote management or for remote access to a network server is
the VLAN where the remote device is located.
Let’s assume for the purposes of this example that the switch will be
remotely managed from a Telnet, SSH, or web browser management
workstation on the network. Consequently, the appropriate VLAN would
be the VLAN on the switch where the remote management workstation is
located. Assume that the VID of the VLAN is 12 and the IP address of the
subnet of the VLAN is 149.44.55.0 with a subnet mask of 255.255.255.0.
The following command assigns an interface to the VLAN. It identifies the
VLAN by its VID of 12 and assigns it the interface number 0. The interface
is given the IP address 149.44.55.22 to make it a member of the subnet:
add ip interface=vlan12-0 ipaddress=149.44.55.22
netmask=255.255.255.0
In order to manage the switch remotely, the interface must be designated
as the local interface so that the management software monitors the
subnet for management packets. Here is the command for designating the
interface as the local interface:
set ip local interface=vlan12-0
As the final part of the example, assume that the management software on
the switch must communicate with a network device, such as
management workstation, syslog server, or RADIUS server, that is not a
member of the same subnet as the interface. For this, you need to define a
default route. The route will specify the next hop to reaching the remote
subnet. The switch will use the default route whenever it needs to send a
management packet to a remote network device that resides on a different
subnet than its local interface.
The next hop in the route must specify the IP address of a routing interface
on a router in the network. Furthermore, the IP address of the routing
interface must be a member of the same subnet as the interface on the
switch.