Owner manual
Table Of Contents
- Contents
- Figures
- Tables
- Preface
- Section I
- Basic Operations
- Chapter 1
- Overview
- Chapter 2
- Enhanced Stacking
- Chapter 3
- SNMPv1 and SNMPv2c
- Chapter 4
- MAC Address Table
- Chapter 5
- Static Port Trunks
- Chapter 6
- LACP Port Trunks
- Chapter 7
- Port Mirror
- Section II
- Advanced Operations
- Chapter 8
- File System
- Chapter 9
- Event Logs and the Syslog Client
- Chapter 10
- Classifiers
- Chapter 11
- Access Control Lists
- Chapter 12
- Class of Service
- Chapter 13
- Quality of Service
- Chapter 14
- Denial of Service Defenses
- Chapter 15
- Power Over Ethernet
- Section III
- Snooping Protocols
- Chapter 16
- IGMP Snooping
- Chapter 17
- MLD Snooping
- Chapter 18
- RRP Snooping
- Chapter 19
- Ethernet Protection Switching Ring Snooping
- Section IV
- SNMPv3
- Chapter 20
- SNMPv3
- Section V
- Spanning Tree Protocols
- Chapter 21
- Spanning Tree and Rapid Spanning Tree Protocols
- Chapter 22
- Multiple Spanning Tree Protocol
- Section VI
- Virtual LANs
- Chapter 23
- Port-based and Tagged VLANs
- Chapter 24
- GARP VLAN Registration Protocol
- Chapter 25
- Multiple VLAN Modes
- Chapter 26
- Protected Ports VLANs
- Chapter 27
- MAC Address-based VLANs
- Section VII
- Routing
- Chapter 28
- Internet Protocol Version 4 Packet Routing
- Supported Platforms
- Overview
- Routing Interfaces
- Interface Names
- Static Routes
- Routing Information Protocol (RIP)
- Default Routes
- Equal-cost Multi-path (ECMP) Routing
- Routing Table
- Address Resolution Protocol (ARP) Table
- Internet Control Message Protocol (ICMP)
- Routing Interfaces and Management Features
- Local Interface
- AT-9408LC/SP AT-9424T/GB, and AT-9424T/SP Switches
- Routing Command Example
- Non-routing Command Example
- Upgrading from AT-S63 Version 1.3.0 or Earlier
- Chapter 29
- BOOTP Relay Agent
- Chapter 30
- Virtual Router Redundancy Protocol
- Section VIII
- Port Security
- Chapter 31
- MAC Address-based Port Security
- Chapter 32
- 802.1x Port-based Network Access Control
- Section IX
- Management Security
- Chapter 33
- Web Server
- Chapter 34
- Encryption Keys
- Chapter 35
- PKI Certificates and SSL
- Chapter 36
- Secure Shell (SSH)
- Chapter 37
- TACACS+ and RADIUS Protocols
- Chapter 38
- Management Access Control List
- Appendix A
- AT-S63 Management Software Default Settings
- Address Resolution Protocol Cache
- Boot Configuration File
- BOOTP Relay Agent
- Class of Service
- Denial of Service Defenses
- 802.1x Port-Based Network Access Control
- Enhanced Stacking
- Ethernet Protection Switching Ring (EPSR) Snooping
- Event Logs
- GVRP
- IGMP Snooping
- Internet Protocol Version 4 Packet Routing
- MAC Address-based Port Security
- MAC Address Table
- Management Access Control List
- Manager and Operator Account
- Multicast Listener Discovery Snooping
- Public Key Infrastructure
- Port Settings
- RJ-45 Serial Terminal Port
- Router Redundancy Protocol Snooping
- Server-based Authentication (RADIUS and TACACS+)
- Simple Network Management Protocol
- Simple Network Time Protocol
- Spanning Tree Protocols (STP, RSTP, and MSTP)
- Secure Shell Server
- Secure Sockets Layer
- System Name, Administrator, and Comments Settings
- Telnet Server
- Virtual Router Redundancy Protocol
- VLANs
- Web Server
- Appendix B
- SNMPv3 Configuration Examples
- Appendix C
- Features and Standards
- 10/100/1000Base-T Twisted Pair Ports
- Denial of Service Defenses
- Ethernet Protection Switching Ring Snooping
- Fiber Optic Ports (AT-9408LC/SP Switch)
- File System
- DHCP and BOOTP Clients
- Internet Protocol Multicasting
- Internet Protocol Version 4 Routing
- MAC Address Table
- Management Access and Security
- Management Access Methods
- Management Interfaces
- Management MIBs
- Port Security
- Port Trunking and Mirroring
- Spanning Tree Protocols
- System Monitoring
- Traffic Control
- Virtual LANs
- Virtual Router Redundancy Protocol
- Appendix D
- MIB Objects
- Index

Chapter 28: Internet Protocol Version 4 Packet Routing
318 Section VII: Routing
Equal-cost Multi-path (ECMP) Routing
The routing table uses ECMP to store multiple routes to a remote
destination so that the switch can distribute the traffic load over several
routes. This can improve network performance by increasing the available
bandwidth for traffic flows. It can also provide route redundancy.
The routing table permits up to 32 routes to the same remote destination,
with up to eight of the routes as active at one time. The routes can be all
static routes, RIP routes, or a combination of the two. Routes to the same
destination must have different next hops. The routing table will not permit
two entries to the same remote destination with the same next hop.
When the routing table contains eight or less routes to the same
destination, all the routes can be active and available to route packets.
The distribution of the traffic among the active routes is controlled through
a hash that combines the packet source and destination IP addresses to
select a route for packets from a source node. The traffic from a specific
source and destined for a specific remote destination is assigned a route
and all traffic to that remote destination from that source is forwarded
using that route. The assignment of a route does not change except if the
path is lost (for instance, the status of an interface changes from up to
down), in which case its traffic is redirected to one of the remaining routes.
When there are more than eight routes in the table to the same
destination, the active routes are selected by preference value, metric
value, and age, in that order. The routes with the eight lowest preference
values are selected as the active routes. Where routes have the same
preference value, selection is based on the lowest metric values.
Otherwise, the selections are based on when the routes were added to the
routing table, with older routes given preference over newer routes.
Those routes not selected as active routes are placed in a standby mode.
The selection of the active destination routes by the switch is dynamic and
can change as routes are added and deleted from the routing table, and
when they change status. For instance, if a new static or RIP route is
added to the routing table when there are already eight active routes to the
same destination, the new route will replace an existing active route if it
has a lower preference value, forcing one of the active routes to change to
the standby mode.
Furthermore, an interface must be physically up with at least one active
port in the VLAN for any of its routes to be considered as available for use.
If an interface is down, meaning there are no active ports in the VLAN, the
routes of the interface are considered inactive and are not assigned any
traffic. For example, if there are eight routes to the same destination, but
two of the routes reside in an interface that is down, those routes are not
used, leaving six available routes.