ECS4100 Series Web Management Guide-R07
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
- Using Cloud Management
- 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
- IPv4 Source Guard
- IPv6 Source Guard
- ARP Inspection
- Application Filter
- Basic Administration Protocols
- Configuring Event Logging
- Link Layer Discovery Protocol
- Power over Ethernet
- 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
- 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 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
- Multicast VLAN Registration for IPv6
- IP Tools
- IP Configuration
- General IP Routing
- Unicast Routing
- Overview
- Configuring the Routing Information Protocol
- Configuring General Protocol Settings
- Clearing Entries from the Routing Table
- Specifying Network Interfaces
- Specifying Passive Interfaces
- Specifying Static Neighbors
- Configuring Route Redistribution
- Specifying an Administrative Distance
- Configuring Network Interfaces for RIP
- Displaying RIP Interface Settings
- Displaying Peer Router Information
- Resetting RIP Statistics
- IP Services
- Appendices
Chapter 13
| Basic Administration Protocols
Ethernet Ring Protection Switching
– 484 –
the second ay ring restore its connections more quickly through protection
switching.
When the MAC addresses are cleared, data traffic may flood onto the major
ring. The data traffic will become stable after the MAC addresses are learned
again. The major ring will not be broken, but the bandwidth of data traffic on
the major ring may suffer for a short period of time due to this flooding
behavior.
◆ Non-ERPS Device Protection – Sends non-standard health-check packets
when an owner node enters protection state without any link down event
having been detected through Signal Fault messages. (Default: Disabled)
■
The RPL owner node detects a failed link when it receives R-APS (SF - signal
fault) messages from nodes adjacent to the failed link. The owner then
enters protection state by unblocking the RPL. However, using this
standard recovery procedure may cause a non-EPRS device to become
isolated when the ERPS device adjacent to it detects a continuity check
message (CCM) loss event and blocks the link between the non-ERPS
device and ERPS device.
CCMs are propagated by the Connectivity Fault Management (CFM)
protocol. If the standard recovery procedure were used as shown in the
following figure, and node E detected CCM loss, it would send an R-APS (SF)
message to the RPL owner and block the link to node D, isolating that non-
ERPS device.
Figure 309: Non-ERPS Device Protection
When non-ERPS device protection is enabled on the ring, the ring ports on
the RPL owner node and non-owner nodes will not be blocked when signal
loss is detected by CCM loss events.
■
When non-ERPS device protection is enabled on an RPL owner node, it will
send non-standard health-check packets to poll the ring health when it
enters the protection state. It does not use the normal procedure of waiting
to receive an R-APS (NR - no request) message from nodes adjacent to the
recovered link. Instead, it waits to see if the non-standard health-check
packets loop back. If they do, indicating that the fault has been resolved,
the RPL will be blocked.
After blocking the RPL, the owner node will still transmit an R-APS (NR, RB -
ring blocked) message. ERPS-compliant nodes receiving this message flush
their forwarding database and unblock previously blocked ports. The ring
is now returned to Idle state.
non-ERPS
A
non-ERPS
RPL
Owner
RPL
XX
blocked blocked
fault
BCDEF