Allied Telesis AT-S63 - Manual (Page 552)

Chapter 32: Internet Protocol Version 4 Packet Routing
552 Section VII: Internet Protocol Routing
Interface Names Many of the IPv4 routing commands have a parameter for an interface
name. An interface name consists of a VLAN and an interface number,
separated by a dash. The VLAN is designated by “vlan” followed by the
VLAN identification number (VID) or the VLAN name.
Here are several examples. The name for a interface in a VLAN with the
VID of 7 and an interface number of 0 is:
vlan7-0
The name for an interface in a VLAN with the VID of 28 and an interface
number of 2 is:
vlan28-2
Here is an example of an interface name that uses the VLAN name
instead of the VID to identify the VLAN. The interface is part of the Sales
VLAN and has an interface number of 5. Note that a dash separates “vlan”
from the VLAN name.
vlan-Sales-5
The following is an example of a command that uses an interface name.
The example uses the ADD IP INTERFACE command to create a new
interface for a subnet in a VLAN with a VID of 28. The interface is
assigned an interface number of 0, an IP address of 149.44.22.22, and a
subnet mask of 255.255.255.0:
add ip interface=vlan28-0 ipaddress=149.44.22.22 mask
255.255.255.0
This command is identical to the previous command, except it identifies
the VLAN by its name, Production:
add ip interface=vlan-Production-0 ipaddress=149.44.22.22
mask 255.255.255.0
Static Routes
In order for the switch to route an IPv4 packet to a remote network or
subnet, there must be a route to the destination in the routing table of the
switch. The route must consist of the IP address of the remote destination
and the IP address of the next hop to reaching the destination.
One type of route to a remote destination is referred to as a static route.
You create static routes by manually entering them into the routing table.
Static routes are never deleted from the routing table by the switch, even
when they are inactive.
When you create a static route, the switch’s management software
automatically adds it to the interface that is a part of the same subnet as
the next hop of the route. Consequently, before you can create a static
route, the switch must have a routing interface that is a member of the
same subnet as the next hop of the route.