Web Management Guide-R04
Table Of Contents
- How to Use This Guide
- Contents
- Figures
- Tables
- Getting Started
- Web Configuration
- Using the Web Interface
- 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
- Configuring CPU Guard
- Displaying Memory Utilization
- Resetting the System
- Interface Configuration
- VLAN Configuration
- Address Table Settings
- Spanning Tree Algorithm
- Congestion Control
- Class of Service
- Layer 2 Queue Settings
- Layer 3/4 Priority Settings
- Setting Priority Processing to IP Precedence/DSCP or CoS
- Mapping Ingress DSCP Values to Internal DSCP Values
- Mapping CoS Priorities to Internal DSCP Values
- Mapping Internal DSCP Values to Egress CoS Values
- Mapping IP Precedence Values to Internal DSCP Values
- Mapping IP Port Priority to Internal DSCP Values
- Quality of Service
- VoIP Traffic Configuration
- Security Measures
- AAA Authentication, Authorization and Accounting
- Configuring User Accounts
- Web Authentication
- Network Access (MAC Address Authentication)
- Configuring HTTPS
- Configuring the Secure Shell
- Access Control Lists
- Filtering IP Addresses for Management Access
- Configuring Port Security
- Configuring 802.1X Port Authentication
- DoS Protection
- DHCPv4 Snooping
- DHCPv6 Snooping
- IPv4 Source Guard
- IPv6 Source Guard
- ARP Inspection
- Application Filter
- Basic Administration Protocols
- Configuring Event Logging
- Link Layer Discovery Protocol
- Simple Network Management Protocol
- Configuring Global Settings for SNMP
- Setting Community Access Strings
- Setting the Local Engine ID
- Specifying a Remote Engine ID
- Setting SNMPv3 Views
- Configuring SNMPv3 Groups
- Configuring Local SNMPv3 Users
- Configuring Remote SNMPv3 Users
- Specifying Trap Managers
- Creating SNMP Notification Logs
- Showing SNMP Statistics
- Remote Monitoring
- Switch Clustering
- Setting a Time Range
- Ethernet Ring Protection Switching
- OAM Configuration
- Connectivity Fault Management
- Configuring Global Settings for CFM
- Configuring Interfaces for CFM
- Configuring CFM Maintenance Domains
- Configuring CFM Maintenance Associations
- Configuring Maintenance End Points
- Configuring Remote Maintenance End Points
- Transmitting Link Trace Messages
- Transmitting Loop Back Messages
- Transmitting Delay-Measure Requests
- Displaying Local MEPs
- Displaying Details for Local MEPs
- Displaying Local MIPs
- Displaying Remote MEPs
- Displaying Details for Remote MEPs
- Displaying the Link Trace Cache
- Displaying Fault Notification Settings
- Displaying Continuity Check Errors
- OAM Configuration
- UDLD Configuration
- LBD Configuration
- Smart Pair Configuration
- Multicast Filtering
- Overview
- Layer 2 IGMP (Snooping and Query for IPv4)
- 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 IGMP Query Packets and Multicast Data
- 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 for IPv4
- Multicast VLAN Registration for IPv6
- Basic IP Functions
- IP Configuration
- General IP Routing
- IP Services
- Appendices
- Glossary
Chapter 17
| General IP Routing
IP Routing and Switching
– 687 –
If the destination belongs to a different subnet on this switch, the packet can be
routed directly to the destination node. However, if the packet belongs to a subnet
not included on this switch, then the packet should be sent to the next hop router
(with the MAC address of the router itself used as the destination MAC address, and
the destination IP address of the destination node). The router will then forward the
packet to the destination node through the correct path. The router can also use
the ARP protocol to find out the MAC address of the destination node of the next
hop router as necessary.
Note:
In order to perform IP switching, the switch should be recognized by other
network nodes as an IP router, either by setting it as the default gateway or by
redirection from another router via the ICMP process.
When the switch receives an IP packet addressed to its own MAC address, the
packet follows the Layer 3 routing process. The destination IP address is checked
against the Layer 3 address table. If the address is not already there, the switch
broadcasts an ARP packet to all the ports on the destination VLAN to find out the
destination MAC address. After the MAC address is discovered, the packet is
reformatted and sent out to the destination. The reformat process includes
decreasing the Time-To-Live (TTL) field of the IP header, recalculating the IP header
checksum, and replacing the destination MAC address with either the MAC address
of the destination node or that of the next hop router.
When another packet destined to the same node arrives, the destination MAC can
be retrieved directly from the Layer 3 address table; the packet is then reformatted
and sent out the destination port. IP switching can be done at wire-speed when the
destination address entry is already in the Layer 3 address table.
If the switch determines that a frame must be routed, the route is calculated only
during setup. Once the route has been determined, all packets in the current flow
are simply switched or forwarded across the chosen path. This takes advantage of
the high throughput and low latency of switching by enabling the traffic to bypass
the routing engine once the path calculation has been performed.
Routing Path
Management
Routing Path Management involves the determination and updating of all the
routing information required for packet forwarding, including:
◆ Updating the routing table
◆ Updating the Layer 3 switching database
Routing Protocols The switch supports static 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.