The protected-vlan command configures a list of protected VLANs in an RRPP domain.
The undo protected-vlan command deletes the list of protected VLANs in an RRPP domain.
protected-vlan reference-instance { all | { { instance-id1 [ to instance-id2 ] } &<1-10> } }
undo protected-vlan reference-instance { all | { { instance-id1 [ to instance-id2 ] } &<1-10> } }
| Parameter | Description | Value |
|---|---|---|
| reference-instance | Indicates the instance imported by a specified RRPP domain. |
- |
| all | Indicates that VLANs in all the instances are protected VLANs. all can be configured successfully only when instances 0 to 64 are created. This task is performed to create an instance and configure the mapping between the instance and VLANs. |
- |
| instance-id1 to instance-id2 | Specifies the ID of a protected instance.
|
The value is an integer that ranges from 0 to 4094. |
Usage Scenario
The control VLAN transmits RRPP protocol packets and the data VLAN transmits data packets. The control VLAN and data VLANs must be configured as the protected VLANs so that RRPP takes effect for these VLAN packets. Otherwise, VLAN packets may cause broadcast storms on the ring network. This will cause the network to be unavailable.
Precautions
When you configure the list of protected VLANs, note the following points:
Protected VLANs must be configured before you configure an RRPP ring.
You can delete or change existing protected VLANs before configuring an RRPP ring. The protected VLANs cannot be changed after the RRPP ring is configured.
In the same physical topology, the control VLAN of a domain cannot be configured as a protected VLAN of another domain.
The control VLAN must be configured as a protected VLAN; otherwise, the RRPP ring cannot be configured.
The control VLAN can be mapped to other instances before the RRPP ring is created. After the RRPP ring is created, the mapping cannot be changed unless you delete the RRPP ring.
When an RRPP domain is deleted, the protected VLANs in the RRPP domain are deleted automatically.
When the mapping between an instance and VLANs changes, the protected VLANs of the RRPP domain also change.
All the VLANs allowed by an RRPP interface must be configured as protected VLANs.
If the protected-vlan command is run more than once, all configurations take effect.