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
- 246 -
6.6 BOOTP/DHCP Relay
Dynamic Host Configuration Protocol (DHCP), described in RFC 1541, is an extension of the Bootstrap
Protocol (BOOTP). DHCP allows hosts on a TCP/IP network to dynamically obtain basic configuration
information. When a DHCP client starts, it broadcasts a DHCP Request packet, looking for DHCP
servers. DHCP servers respond to this packet with a DHCP Response packet. The client then chooses a
server to obtain TCP/IP configuration information, such as its own IP address.
Since DHCP uses a broadcast mechanism, a DHCP server and its client must physically reside on the
same subnet. However, it is not practical to have one DHCP server on every subnet; in fact in many
cases, DHCP/BOOTP clients and their associated DHCP/BOOTP server(s) do not reside on the same IP
network or subnet. In such cases, a third-party agent is required to transfer BOOTP messages between
clients and servers.
BOOTP/DHCP Relay, described in RFC 1542, enables a host to use a BOOTP or DHCP server to obtain
basic TCP/IP configuration information, even if the servers do not reside on the local subnet. When an
Switch BOOTP/DHCP Relay Agent receives a DHCP Request packet destined for a BOOTP/DHCP
server, it inserts its own IP address into the DHCP Request packet so the server knows the subnet
where the client is located. Then, depending on the configuration setup, the switch either:
• Forwards the packet to a specific server as defined in the switch’s configuration using unicast routing,
or
• Broadcasts the DHCP Request again to another directly attached IP subnet specified in the switch
configuration for the receiving IP subnet.
When the DHCP server receives the DHCP request, it allocates a free IP address for the DHCP client
from its scope in the DHCP client’s subnet, and sends a DHCP Response back to the DHCP Relay
Agent. The DHCP Relay Agent then broadcasts this DHCP Response packet received from the DHCP
server to the appropriate client.