Overview
General information
Port objects are children of card slot objects. Port objects appear below the card slot after the card is configured. Properties forms for port objects are accessed using the NFM-P navigation tree.
QoS protection schemes for Ethernet ports
You can configure the following QoS protection schemes on Wavence Ethernet ports:
-
A traffic storm occurs when packets flood a LAN creating excessive traffic and degrading network performance. You can use traffic storm control to prevent Ethernet ports from being disrupted by a broadcast, multicast, or unicast traffic storm on the physical interfaces, and limit the impact of VLAN misconfigurations.
Traffic storm control monitors the incoming traffic levels over a 1-s interval and, during the interval, compares the traffic level with the traffic storm control level that you configure on NFM-P. The traffic storm control level is a percentage of the total available bandwidth of the Ethernet port. For example, if traffic storm control is enabled for ingress traffic and it reaches the configured level on the port with the interval, the traffic is dropped until the traffic storm control interval ends.
-
You can use port rate limiting to protect the Radio-side bandwidth from being overloaded by an ingress or egress port. A common application for port rate limiting is when a Wavence provides the microwave backhaul service for multiple 7705 SAR devices whose queues do not have the visibility of the bandwidth available of the Radio side.
-
You can use dot1q VLAN rate limiting to protect the Radio side bandwidth on the Wavence from being overloaded by an ingress port when transporting IP/MPLS over MPR transport services on dot1q VLANs. A common application of the VLAN rate limiting feature is to monitor the microwave backhaul services providing transport to multiple 7705 SAR devices whose queues could individually exceed the available Radio bandwidth.
Traffic storm control, port rate limiting, and dot1q VLAN rate limiting are supported on the Core-E and 4+4 × Ethernet (EAS) cards on Wavence nodes. Port rate limiting is supported on MSS-4/8 cards on Wavence nodes Release 23 or later. Up to 1G values are supported on Wavence nodes Release 23 or earlier; 1G, 2.5G, and 10G is supported on nodes Release 23A or later.
See To configure Wavence Ethernet ports for information about enabling traffic storm control, port rate limiting, and dot1q VLAN rate limiting on the Wavence.
Monitoring Wavence ports using 802.3ah EFM OAM remote loopbacks
You can monitor Wavence Ethernet or SFP ports using the 802.3ah EFM OAM remote loopback diagnostic test on Core-E, CorEvo, EASv1, and EASv2 cards, and on an MSS-1 or MSS-O shelf. See To configure 802.3ah EFM OAM remote loopbacks on Wavence ports.
Note: The link monitoring and fault signaling operational aspects of the 802.3ah EFM OAM diagnostic test are not supported on the Wavence.
When enabled, the remote loopback allows a local DTE to locate a remote DTE and put it into a state whereby all inbound traffic is immediately reflected back onto the link. The 802.3ah EFM OAM remote loopback information is carried by the OAMPDUs. OAMPDUs contain the control and status information to monitor, test, and troubleshoot OAM-enabled links.
2.5 Gb/s SFP port on CorEvo cards
NFM-P supports the configuration of the 2.5 Gb/s speed on the SFP ports of the CorEvo cards. See To configure 2.5 Gb/s speed on the SFP port of CorEvo card for more information about how to configure 2.5 Gb/s speed on the SFP ports of the CorEvo cards.