29.1.3 Support Specifications
The following table describes the items and specifications supported by the Ring Protocol.
|
Item |
Description |
|
|---|---|---|
|
Applicable layer |
Layer 2 |
OK |
|
Layer 3 |
NG |
|
|
Ring configuration |
Single ring |
OK |
|
Multi-ring |
OK (including multi-ring configurations with shared links) |
|
|
Node |
Master nodes |
OK |
|
Transit node |
OK |
|
|
Shared node |
OK |
|
|
Maximum number of ring IDs per switch |
24*1 (8 when using Ring Protocol and Spanning Tree Protocols or the multiple failure monitoring facility) |
|
|
Ring ports (number of ports per ring ID) |
2 (physical ports or link aggregations) |
|
|
Number of VLANs |
Number of control VLANs per ring ID |
1 (default VLAN cannot be set) |
|
Maximum number of VLAN groups for data transfer per ring ID |
2 |
|
|
Maximum number of VLAN mappings per VLAN group for data transfer |
128 #2 |
|
|
Maximum number of VLANs per VLAN mapping |
1023 However, if the ring contains a stacked node, it shall be set to 511. |
|
|
Health-check frame sending interval |
1 millisecond in the range 200 to 60000 milliseconds |
|
|
Fault monitoring time |
1 millisecond in the range 500 to 300000 milliseconds |
|
|
Load balancing method |
Possible when two VLAN groups for data transfer are used |
|
|
Multi-fault monitoring functionality |
Number of multi-fault monitoring-enabled rings per switch |
4 |
|
Number of multi-fault monitoring VLANs per ring ID |
1 (default VLAN cannot be set) |
|
|
Multi-fault monitoring frame sending interval |
1 millisecond in the range 500 to 60000 milliseconds |
|
|
Multiple failure monitoring time*3 |
1 millisecond in the range 1000 to 300000 milliseconds |
|
Legend: OK: Supported, NG: Not supported
#1: When a stack is configured, the ring ID per stack is the largest.
#2: In a stacked configuration, the recommended total number of VLAN maps used by the Switch as a master node is 128 or less.
#3: Multiple failure monitoring is not supported for rings that contain stacked nodes.