Web Management Guide-R03
Table Of Contents
- How to Use This Guide
- Contents
- Figures
- Tables
- Getting Started
- Web Configuration
- Basic Management Tasks
- Displaying System Information
- Displaying Hardware/Software Versions
- Configuring Support for Jumbo Frames
- Displaying Bridge Extension Capabilities
- Managing System Files
- Setting the System Clock
- Configuring the Console Port
- Configuring Telnet Settings
- Displaying CPU Utilization
- Displaying Memory Utilization
- Resetting the System
- Interface Configuration
- VLAN Configuration
- Address Table Settings
- Spanning Tree Algorithm
- Congestion Control
- Class of Service
- Quality of Service
- VoIP Traffic Configuration
- Security Measures
- AAA Authorization and Accounting
- Configuring User Accounts
- Web Authentication
- Network Access (MAC Address Authentication)
- Configuring HTTPS
- Configuring the Secure Shell
- Access Control Lists
- Setting A Time Range
- Showing TCAM Utilization
- Setting the ACL Name and Type
- Configuring a Standard IPv4 ACL
- Configuring an Extended IPv4 ACL
- Configuring a Standard IPv6 ACL
- Configuring an Extended IPv6 ACL
- Configuring a MAC ACL
- Configuring an ARP ACL
- Binding a Port to an Access Control List
- Configuring ACL Mirroring
- Showing ACL Hardware Counters
- ARP Inspection
- Filtering IP Addresses for Management Access
- Configuring Port Security
- Configuring 802.1X Port Authentication
- DoS Protection
- IP Source Guard
- DHCP Snooping
- Basic Administration Protocols
- Configuring Event Logging
- Link Layer Discovery Protocol
- Power over Ethernet
- Simple Network Management Protocol
- Configuring Global Settings for SNMP
- Setting the Local Engine ID
- Specifying a Remote Engine ID
- Setting SNMPv3 Views
- Configuring SNMPv3 Groups
- Setting Community Access Strings
- Configuring Local SNMPv3 Users
- Configuring Remote SNMPv3 Users
- Specifying Trap Managers
- Creating SNMP Notification Logs
- Showing SNMP Statistics
- Remote Monitoring
- Switch Clustering
- IP Configuration
- IP Services
- Multicast Filtering
- Overview
- Layer 2 IGMP (Snooping and Query)
- Configuring IGMP Snooping and Query Parameters
- Specifying Static Interfaces for a Multicast Router
- Assigning Interfaces to Multicast Services
- Setting IGMP Snooping Status per Interface
- Filtering Multicast Data at Interfaces
- Displaying Multicast Groups Discovered by IGMP Snooping
- Displaying IGMP Snooping Statistics
- Filtering and Throttling IGMP Groups
- MLD Snooping (Snooping and Query for IPv6)
- Multicast VLAN Registration
- Basic Management Tasks
- Appendices
- Glossary
- Index
Chapter 15
| IP Services
Dynamic Host Configuration Protocol
– 463 –
management VLAN or a non-management VLAN, it will add option 82 relay
information and the relay agent’s address to the DHCP request packet, and
then unicast it to the DHCP server.
■
If a DHCP relay server has been set on the switch, when the switch receives
a DHCP request packet with option 82 information from the management
VLAN or a non-management VLAN, it will process it according to the
configured relay information option policy:
■
If the policy is “replace,” the DHCP request packet’s option 82 content
(the RID and CID sub-option) is replaced with information provided by
the switch. The relay agent address is inserted into the DHCP request
packet, and the switch then unicasts this packet to the DHCP server.
■
If the policy is “keep,” the DHCP request packet's option 82 content will
be retained. The relay agent address is inserted into the DHCP request
packet, and the switch then unicasts this packet to the DHCP server.
■
If the policy is “drop,” the original DHCP request packet is flooded onto
the VLAN which received the packet but is not relayed.
◆ DHCP reply packets received by the relay agent are handled as follows:
When the relay agent receives a DHCP reply packet with Option 82 information
over the management VLAN, it first ensures that the packet is destined for it.
■
If the RID in the DHCP reply packet is not identical with that configured on
the switch, the option 82 information is retained, and the packet is flooded
onto the VLAN through which it was received.
■
If the RID in the DHCP reply packet matches that configured on the switch,
it then removes the Option 82 information from the packet, and sends it on
as follows:
■
If the DHCP packet’s broadcast flag is on, the switch uses the circuit-id
information contained in the option 82 information fields to identify
the VLAN connected to the requesting client and then broadcasts the
DHCP reply packet to this VLAN.
■
If the DHCP packet’s broadcast flag is off, the switch uses the circuit-id
information in option 82 fields to identify the interface connected to
the requesting client and unicasts the reply packet to the client.
◆ DHCP packets are flooded onto the VLAN which received them if DHCP relay
service is enabled on the switch
and any of the following situations apply
:
■
There is no DHCP relay server set on the switch, when the switch receives a
DHCP packet.