ECS4510 Series Web Management Guide-R03
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
- Displaying Memory Utilization
- Stacking
- 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
- 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
- IPv4 Source Guard
- IPv6 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
- 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
- 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
- IP Configuration
- IP Services
- 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
- Appendices
- Glossary
- Index
Chapter 13
| Basic Administration Protocols
Ethernet Ring Protection Switching
– 466 –
c. The acceptance of the R-APS (NR, RB) message causes all ring
nodes to unblock any blocked non-RPL that does not have an
SF condition. If it is an R-APS (NR, RB) message without a DNF
indication, all Ethernet Ring Nodes flush their FDB. This action
unblocks the ring port which was blocked as a result of an
operator command.
■
Recovery with non-revertive mode is handled as follows:
a. The RPL Owner Node, upon reception of an R-APS (NR)
message and in the absence of any other higher priority
request does not perform any action.
b. Then, after the operator issues the Clear command (Configure
Operation page) at the RPL Owner Node, this ring node blocks
the ring port attached to the RPL, transmits an R-APS (NR, RB)
message over both ring ports, informing the ring that the RPL is
blocked, and flushes its FDB.
c. The acceptance of the R-APS (NR, RB) message triggers all ring
nodes to unblock any blocked non-RPL which does not have an
SF condition. If it is an R-APS (NR, RB) message without a DNF
indication, all ring nodes flush their FDB. This action unblocks
the ring port which was blocked as result of an operator
command.
◆ Major Domain – The ERPS ring used for sending control packets.
This switch can support up to six rings. However, ERPS control packets can only
be sent on one ring. This parameter is used to indicate that the current ring is a
secondary ring, and to specify the major ring which will be used to send ERPS
control packets.
The Ring Protection Link (RPL) is always the west port. So the physical port on a
secondary ring must be the west port. In other words, if a domain has two
physical ring ports, this ring can only be a major ring, not a secondary ring (or
sub-domain) which can have only one physical ring port. The major domain
therefore cannot be set if the east port is already configured.
◆ Node ID – A MAC address unique to the ring node. The MAC address must be
specified in the format xx-xx-xx-xx-xx-xx or xxxxxxxxxxxx. (Default: CPU MAC
address)
The ring node identifier is used to identify a node in R-APS messages for both
automatic and manual switching recovery operations.
For example, a node that has one ring port in SF condition and detects that the
condition has been cleared, will continuously transmit R-APS (NR) messages
with its own Node ID as priority information over both ring ports, informing its
neighbors that no request is present at this node. When another recovered
node holding the link blocked receives this message, it compares the Node ID
information with its own. If the received R-APS (NR) message has a higher
priority, this unblocks its ring ports. Otherwise, the block remains unchanged.