Interaction With Other Features
Configuring ERP
page 11-10
OmniSwitch AOS Release 7 Network Configuration Guide
June 2013
Example:
To configure an untagged R-APS channel for ring 1
On all nodes, a default or untagged VLAN must be configured on the ring ports:
-> vlan 4000
-> vlan 4000 members port 1/1-2 untagged
-> erp-ring 1 port1 1/1 port2 1/2 service-vlan 4000 level 2
Interaction With Other Features
This section contains important information about interaction of ERP with other OmniSwitch features.
Refer to the specific chapter for each feature to get more detailed information about how to configure and
use the feature.
Multicast
•
IP multicast switching (IPMS) treats the ERP Service VLAN the same as any other configured VLAN
on the switch. The ERP Service VLAN may carry data traffic, and if enabled and configured to do so,
IPMS will perform regular multicast snooping on that VLAN.
•
Disabling IPMS on the ERP Service VLAN is recommended if IP multicast routing or multicast snoop-
ing is enabled for the switch.
Spanning Tree
STP is automatically disabled when ERP is enabled on any port.
VLAN Stacking
ERP has the following interactions with VLAN Stacking:
•
ERP is supported on Network Network Interface (NNI) ports; it is not supported on UNI ports.
•
Tunneling of STP BPDUs across UNI ports is supported in a VLAN stacking configuration.
See
“Configuring ERP with VLAN Stacking NNIs” on page 11-16
for more information.
Source Learning
The ERP protocol determines and performs the MAC address flushing per port.
QoS Interface
The interaction between ERP and QoS is for the purpose so that R-APS PDUs can be handled
appropriately by the switch.
MVRP
ERP NI must provide blocking or forwarding state of ERP ports to MVRP.