erps ring <ringid> instance
Syntax
erps ring <ringid>
instance <id>
Description
On a common ERPS network, a physical ring can be configured with a single ERPS ring, and only one blocked port can be specified in the ring. When the ERPS ring is in normal state, the blocked port prohibits all service packets from passing through. As a result, all service data is transmitted through one path over the ERPS ring, and the other link on the blocked port becomes idle, leading to ineffective use of bandwidth.
To improve link use efficiency, logical rings can be configured in the same physical ring in the ERPS multi-instance. A port may have different roles in different ERPS rings and different ERPS rings use different control VLANs.
An ERPS ring must be configured with an ERP instance, and each ERP instance specifies a range of VLANs. The topology calculated for a specific ERPS ring only takes effect in the ERPS ring. Different VLANs can use separate paths, implementing traffic load balancing and link backup.
The
no
form of this command removes the instance of the ring.
Command context
config-erps-ring-<ringid>
Parameters
<ringid>
Required, specifies the ID of the ring. Range: 1-239
<id>
Required, specifies the ERPS ring instance identifier. Range: 1-2.
Authority
Administrators
Examples
switch(config)# erps ring 3 switch(config-ring-3)# instance 2
switch(config)# erps ring 3 switch(config-ring-3)# no instance 2