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 13
| Basic Administration Protocols
Ethernet Ring Protection Switching
– 497 –
◆ 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.
The node identifier may also be used for debugging, such as to distinguish
messages when a node is connected to more than one ring.
◆ R-APS with VC – Configures an R-APS virtual channel to connect two
interconnection points on a sub-ring, allowing ERPS protocol traffic to be
tunneled across an arbitrary Ethernet network. (Default: Enabled)
■
A sub-ring may be attached to a primary ring with or without a virtual
channel. A virtual channel is used to connect two interconnection points
on the sub-ring, tunneling R-APS control messages across an arbitrary
Ethernet network topology. If a virtual channel is not used to cross the
intermediate Ethernet network, data in the traffic channel will still flow
across the network, but the all R-APS messages will be terminated at the
interconnection points.
■
Sub-ring with R-APS Virtual Channel – When using a virtual channel to
tunnel R-APS messages between interconnection points on a sub-ring, the
R-APS virtual channel may or may not follow the same path as the traffic
channel over the network. R-APS messages that are forwarded over the
sub-ring’s virtual channel are broadcast or multicast over the
interconnected network. For this reason the broadcast/multicast domain of
the virtual channel should be limited to the necessary links and nodes. For
example, the virtual channel could span only the interconnecting rings or
sub-rings that are necessary for forwarding R-APS messages of this sub-