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
– 501 –
for old messages still circulating on the ring to expire. (Range: 10-2000
milliseconds, in steps of 10 milliseconds)
The guard timer duration should be greater than the maximum expected
forwarding delay for an R-APS message to pass around the ring. A side-effect of
the guard timer is that during its duration, a node will be unaware of new or
existing ring requests transmitted from other nodes.
◆ WTB Timer – The Wait to Block (WTB) timer is used when clearing Forced
Switch (FS) and Manual Switch (MS) commands. As multiple FS commands are
allowed to co-exist in a ring, the WTB timer ensures that clearing of a single FS
command does not trigger re-blocking of the RPL. When clearing an MS
command, the WTB timer prevents the formation of a closed loop due to
possible a timing anomaly where the RPL owner node receives an outdated
remote MS request during the recovery process.
When recovering from an FS or MS command, the delay timer must be long
enough to receive any latent remote FS or MS commands. This delay timer
called the WTB timer is defined to be 5 seconds longer than the guard timer.
This is enough time to allow a reporting ring node to transmit two R-APS
messages and allow the ring to identify the latent condition.
This delay timer is activated on the RPL owner node. When the relevant delay
timer expires, the RPL owner node initiates the reversion process by
transmitting an R-APS (NR, RB) message. The delay timer, (i.e., WTR or WTB) is
deactivated when any higher priority request preempts this delay timer.
The delay timers (i.e. WTR and WTB) may be started and stopped by the system.
A request to start running the delay timer does not restart the delay timer. A
request to stop the delay timer stops the delay timer and resets its value. The
Clear command (Configure Operation page) can be used to stop the delay
timer.
◆ WTR Timer – The wait-to-restore timer is used to verify that the ring has
stabilized before blocking the RPL after recovery from a signal failure.
(Range: 5-12 minutes)
If the switch goes into ring protection state due to a signal failure, after the
failure condition is cleared, the RPL owner will start the wait-to-restore timer
and wait until it expires to verify that the ring has stabilized before blocking the
RPL and returning to the Idle (normal operating) state.
◆ WTB Expire – The time before the wait-to-block timer expires.
◆ WTR Expire – The time before the wait-to-restore timer expires.
◆ West/East – Connects to next ring node to the west/east.
Each node must be connected to two neighbors on the ring. For convenience,
the ports connected are referred to as east and west ports. Alternatively, the
closest neighbor to the east should be the next node in the ring in a clockwise
direction, and the closest neighbor to the west should be the next node in the
ring in a counter-clockwise direction.