Web Management Guide-R01
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
- 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
- DHCP Snooping
- DHCPv6 Snooping
- ND 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
- UDLD Configuration
- LBD 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 Packets on an Interface
- Displaying Multicast Groups Discovered by IGMP Snooping
- Displaying IGMP Snooping Statistics
- Filtering and Throttling IGMP Groups
- MLD Snooping (Snooping and Query for IPv6)
- Configuring MLD Snooping and Query Parameters
- Setting Immediate Leave Status for MLD Snooping per Interface
- Specifying Static Interfaces for an IPv6 Multicast Router
- Assigning Interfaces to IPv6 Multicast Services
- Filtering MLD Query Packets on an Interface
- Showing MLD Snooping Groups and Source List
- Displaying MLD Snooping Statistics
- Filtering and Throttling MLD Groups
- Multicast VLAN Registration for IPv4
- IP Tools
- IP Configuration
- General IP Routing
- IP Services
- Appendices
Chapter 13
| Basic Administration Protocols
Ethernet Ring Protection Switching
– 470 –
request) message indicating they have no local request. When the RPL owner
receives an R-APS (NR) message it starts the Wait-To-Recover (WTR) timer. Once
WTR timer expires, the RPL owner blocks the RPL and transmits an R-APS (NR, RB -
ring blocked) message. Nodes receiving this message flush the forwarding
database and unblock their previously blocked ports. The ring is now returned to
Idle state.
Figure 308: ERPS Ring Components
Multi-ring/Ladder Network – ERPSv2 also supports multipoint-to-multipoint
connectivity within interconnected rings, called a “multi-ring/ladder network”
topology. This arrangement consists of conjoined rings connected by one or more
interconnection points, and is based on the following criteria:
◆ The R-APS channels are not shared across Ethernet Ring interconnections.
◆ On each ring port, each traffic channel and each R-APS channel are controlled
(e.g., for blocking or flushing) by the Ethernet Ring Protection Control Process
(ERP Control Process) of only one ring.
◆ Each Major Ring or Sub-Ring must have its own RPL.
Figure 309 on page 471 (Normal Condition) depicts an example of a multi-ring/
ladder network. If the network is in normal operating condition, the RPL owner
node of each ring blocks the transmission and reception of traffic over the RPL for
that ring. This figure presents the configuration when no failure exists on any ring
link.
In the figure for the Normal Condition there are two interconnected rings. Ring
ERP1 is composed of ring nodes A, B, C and D and the ring links between these
nodes. Ring ERP2 is composed of ring nodes C, D, E and F and the ring links C-to-F,
F-to-E, E-to-D. The ring link between D and C is used for traffic on rings ERP1 and
ERP2. On their own ERP2 ring links do not form a closed loop. A closed loop may be
formed by the ring links of ERP2 and the ring link between the interconnection
nodes that is controlled by ERP1. ERP2 is a sub-ring. Ring node A is the RPL owner
node for ERP1, and ring node E is the RPL owner node for ERP2. These ring nodes (A
and E) are responsible for blocking the traffic channel on the RPL for ERP1 and ERP2
respectively. There is no restriction on which ring link on an ring may be set as the
RPL. For example the RPL of ERP1 could be set as the link between ring node C and
D.
East Port
West Port
RPL Owner
CC Messages
RPL
x
CC Messages
(Idle State)