Gigabit Ethernet Switch User's Manual
Table Of Contents
- Chapter 1. Introduction
- Chapter 2. Installing the Switch
- Chapter 3. Switch Management
- Chapter 4. Console Interface
- 4.1 Login Screen
- 4.2 Main Menu
- 4.3 System Information Menu
- 4.4 Management Setup Menu
- 4.5 Device Control Menu
- 4.5.1 Setting the System Operation Mode
- 4.5.2 Layer 2 Menu
- 4.5.3 Using the Bridge Menu
- 4.5.4 Configuring Virtual LANs
- 4.5.5 Configuring IGMP Snooping
- 4.5.6 Configuring IP Settings
- 4.5.7 Security Menu
- 4.5.8 Jumbo Packet Configuration
- 4.6 Monitoring the Switch
- 4.6.1 Displaying Port Statistics
- 4.6.2 Layer 2 Address Tables
- 4.6.3 Displaying Bridge Information
- 4.6.4 Displaying VLAN Information
- 4.6.5 IP Multicast Registration Table
- 4.6.6 IP Address Table
- 4.7 Resetting the System
- 4.8 Logging Off the System
- Chapter 5. Web Interface
- 5.1 Web-Based Configuration and Monitoring
- 5.2 Navigating the Web Browser Interface
- 5.3 Panel Display
- 5.4 Main Menu
- 5.5 System Information Menu
- 5.6 Management Setup Menu
- 5.7 Device Control Menu
- 5.7.1 Layer 2 Menu
- 5.7.2 Using the Bridge Menu
- 5.7.3 Configuring Virtual LANs
- 5.7.4 Configuring IGMP Snooping
- 5.7.5 Configuring IP Settings
- 5.7.6 Configuring Security Filters
- 5.7.7 Jumbo Packet Configuration
- 5.8 Monitoring the Switch
- 5.9 Resetting the System
- Chapter 6.Advanced Topics
- Appendix A Troubleshooting
- Appendix B Pin Assignments
- GLOSSARY

WGS3 Layer 3 Switch User’s Manual
- 235 -
single network. These nodes must therefore use a smaller subnet mask than that used by the switch or
other relevant network devices.
Note that extensive use of Proxy ARP can adversely affect the performance of the switch because it may
lead to increased ARP traffic and increased search time for larger ARP address tables.
6.2.6 Routing Protocols
The switch supports both static and dynamic routing.
• Static routing requires routing information to be stored in the switch, either manually or when a
connection is set up by an application outside the switch.
• Dynamic routing uses a routing protocol to exchange routing information, calculate routing tables, and
respond to changes in the status or loading of the network.
Dynamic routing involves the determination and updating of all the routing information required for packet
forwarding.
• Handling routing protocols
• Updating the routing table
• Updating the Layer 3 switching database
The switch supports RIP and RIP-2 dynamic routing protocols.
6.2.6.1 RIP and RIP-2 Dynamic Routing Protocols
The RIP protocol is the most widely used routing protocol. The RIP protocol uses a distance
vector-based approach to routing. Routes are determined on the basis of minimizing the distance vector,
or hop count, which serves as a rough estimate of transmission cost. Each router broadcasts its
advertisement every 30 seconds, together with any updates to its routing table. This allows all routers on
the network to learn consistent tables of next hop links which lead to relevant subnets. Just as Layer 2
switches use the Spanning Tree Algorithm to prevent loops, routers also use methods for preventing
loops that would cause endless retransmission of data traffic. RIP utilizes the following three methods to
prevent loops from occurring:
• Split horizon— never propagate routes back to an interface port from which they have been acquired.
• Poison reverse— propagate routes back to an interface port from which they have been acquired, but
set the distance vector metrics to infinity. (This provides faster convergence.)
• Triggered updates— whenever a route gets changed, broadcast an update message after waiting for a
short random delay, but without waiting for the periodic cycle.
RIP-2 is a compatible upgrade to RIP. RIP-2 adds useful capabilities for plain text authentication, multiple
independent RIP domains, variable length subnet masks, and multicast transmissions for route
advertising (RFC 1388).
There are several serious problems with RIP that you should consider before deciding which routing
protocol to use for your network. First of all, RIP (version 1) has no knowledge of subnets, both RIP
versions can take a long time to converge on a new route after the failure of a link or router during which
time routing loops may occur, and its small hop count limitation of 15 restricts its use to smaller networks.