The protected-instance command configures protected instances in a SEP segment.
The undo protected-instance command deletes the protected instances in a SEP segment.
By default, no protected instance is configured in a SEP segment.
protected-instance { all | { instance-id1 [ to instance-id2 ] } &<1-10> }
undo protected-instance { all | { instance-id1 [ to instance-id2 ] } &<1-10> }
| Parameter | Description | Value |
|---|---|---|
| all | Indicates all protected instances in a SEP segment. |
- |
| instance-id1 [ to instance-id2 ] | Specifies the IDs of protected instances in a SEP segment. The keyword to connecting two instance IDs, indicating an ID range from instance-id1 to instance-id2. The value of instance-id2 must be greater than the value of instance-id1. &<1-10> indicates that the parameter before the sign (&) can be repeated 1 to 10 times. |
The value is an integer in the range 0 to 4094. Each device supports a maximum of 65 instances. |
Usage Scenario
In common SEP networking, a physical ring can be configured with only one SEP segment in which only one interface can be blocked. If an interface in a complete SEP segment is blocked, all service data is transmitted only along the path where the primary edge interface is located. The path where the secondary edge interface is located remains idle, wasting bandwidth.
SEP multi-instance is used to improve bandwidth efficiency, allowing each physical interface on a ring network to be added to two SEP segments. A physical ring can be configured with two logical rings, allowing packets carrying different VLAN IDs to pass through. Load balancing is then implemented between the two logical rings. This implementation requires logical rings to be configured with different protected instances and mappings between protected instances and VLANs to be configured. The protected-instance command can be used to configure protected instances for a SEP segment.
Prerequisites
The protected instance IDs configured for SEP segments do not overlap. If different SEP segments have duplicate protected instance IDs, replan protected instance IDs.
Follow-up Procedure
Run the instance instance-id vlan { vlan-id1 [ to vlan-id2 ] } &<1-10> command to configure mappings between protected instances and VLANs.
The value of instance-id specified in this command must be the same as the value of instance-id specified in the protected-instance command.
Precautions
If you run the protected-instance command multiple times in the same SEP segment, multiple instances are configured.
After the protected-instance command is run to configure different protected instances for SEP segments and mappings between protected instances and VLANs are set, topology changes affect only corresponding VLANs. This ensures reliable data transmission.
Before adding an interface to a SEP segment, ensure that the SEP segment has been configured with protected instances; otherwise, the interface cannot be added to the SEP segment.