Chapter 29: Internet Protocol Version 4 Packet Routing
342
Section VII: Routing
Routing Interfaces and Management Features
Routing interfaces are primary intended for the IPv4 packet routing
feature. There are, however, a number of management functions that rely
on the presence of at least one routing interface on the switch to operate
properly. The switch uses the IP address of an interface as its source
address when performing the management function. The management
functions are listed here:
Accessing network servers
Enhanced stacking
Remote Telnet, SSH, and web browser management sessions
Pinging a remote device
Accessing DHCP or BOOTP servers
Accessing
Network Servers
A local subnet on the switch must have an interface if the device is using
the subnet to access any of the following types of network servers:
SNTP server for setting the switch’s date and time.
RADIUS or authentication server for manager access
accounts and 802.1x port-based network access control.
Syslog server for storing events from the switch’s event logs.
TFTP server for uploading and downloading files to the switch.
The switch uses the IP address of the interface as its source address
when communicating with a network server. Without a routing interface on
the subnet, the switch will not have a source IP address to include in its
packets. For example, in order to set its date and time using an SNTP
server, the switch must have a routing interface on the local subnet from
where it is reaching the server.
The servers can be located on different routing interfaces on the switch.
For instance, the switch can access an SNTP server through one interface
and a RADIUS authentication server from another. This differs from some
of the earlier versions of the AT-S63 Management Software where all the
servers had to be members of what was referred to as the “management
VLAN.”
If you intend to use the IPv4 routing feature of the switch and assign
routing interfaces to all the local subnets and networks on a switch, this
requirement should not be a issue. However, if you choose not to use the
routing function and so not create interfaces or you have an AT-9400
Switch that only supports one interface, some planning will be necessary
in order to use these features. At a minimum, you must create one routing
interface on the switch and plan your network so that the switch can
access the servers from the subnet of the interface.
Summary of Contents for AT-S63
Page 14: ...Figures 14 ...
Page 18: ...Tables 18 ...
Page 28: ...28 Section I Basic Operations ...
Page 58: ...Chapter 1 Overview 58 ...
Page 76: ...Chapter 2 AT 9400Ts Stacks 76 Section I Basic Operations ...
Page 96: ...Chapter 5 MAC Address Table 96 Section I Basic Operations ...
Page 114: ...Chapter 8 Port Mirror 114 Section I Basic Operations ...
Page 116: ...116 Section II Advanced Operations ...
Page 146: ...Chapter 12 Access Control Lists 146 Section II Advanced Operations ...
Page 176: ...Chapter 14 Quality of Service 176 Section II Advanced Operations ...
Page 196: ...196 Section III Snooping Protocols ...
Page 204: ...Chapter 18 Multicast Listener Discovery Snooping 204 Section III Snooping Protocols ...
Page 216: ...Chapter 20 Ethernet Protection Switching Ring Snooping 216 Section III Snooping Protocols ...
Page 218: ...218 Section IV SNMPv3 ...
Page 234: ...234 Section V Spanning Tree Protocols ...
Page 268: ...268 Section VI Virtual LANs ...
Page 306: ...Chapter 27 Protected Ports VLANs 306 Section VI Virtual LANs ...
Page 320: ...320 Section VII Internet Protocol Routing ...
Page 360: ...Chapter 30 BOOTP Relay Agent 360 Section VII Routing ...
Page 370: ...Chapter 31 Virtual Router Redundancy Protocol 370 Section VII Routing ...
Page 372: ...372 Section VIII Port Security ...
Page 402: ...Chapter 33 802 1x Port based Network Access Control 402 Section VIII Port Security ...
Page 404: ...404 Section IX Management Security ...
Page 436: ...Chapter 36 PKI Certificates and SSL 436 Section IX Management Security ...
Page 454: ...Chapter 38 TACACS and RADIUS Protocols 454 Section IX Management Security ...
Page 462: ...Chapter 39 Management Access Control List 462 Section IX Management Security ...
Page 532: ...Appendix D MIB Objects 532 ...