66
NOTE:
•
When you configure existing VLANs as control VLANs, the system prompts errors.
•
To ensure proper forwarding of RRPPDUs, do not enable QinQ or VLAN mapping on the control
VLANs.
•
To ensure that RRPPDUs can be sent and received correctly, do not configure the default VLAN of a port
accessing an RRPP ring as the primary control VLAN or the secondary control VLAN.
•
To transparently transmit RRPPDUs on a device not configured with RRPP, you must ensure that only the
two ports connecting the device to the RRPP ring permit the packets of the control VLANs. Otherwise, the
packets from other VLANs may go into the control VLANs in transparent transmission mode and strike
the RRPP ring.
Configuring protected VLANs
Before configuring RRPP rings in an RRPP domain, first configure the same protected VLANs for all nodes
in the RRPP domain. All VLANs that the RRPP ports are assigned to should be protected by the RRPP
domains.
Perform this configuration on all nodes in the RRPP domain to be configured.
Follow these steps to configure protected VLANs:
To do…
Use the command…
Remarks
Enter system view
system-view
—
Enter RRPP domain view
rrpp domain
domain-id
—
Configure protected VLANs for the
RRPP domain
protected-vlan reference-instance
instance-id-list
Required
By default, no protected VLAN is
configured for an RRPP domain.
NOTE:
When configuring load balancing, you must configure different protected VLANs for different RRPP
domains.
Configuring RRPP rings
When configuring an RRPP ring, you must make some configurations on the ports connecting each node
to the RRPP ring before configuring the nodes.
NOTE:
•
RRPP ports—connecting devices to an RRPP ring—must be Layer-2 Ethernet ports or Layer-2 aggregate
ports, and they cannot be member ports of any aggregation group, service loopback group, or smart
link group.
•
After configuring a Layer-2 aggregate port as an RRPP port, you can still assign ports to or remove ports
from the aggregation group corresponding to the port.