The status is Pending, which means that the ring is configured but not operational. The ring instance may be in one of the following states: Idle, Initializing, Pending, or Failed1. The Pending state indicates that the ring instance is waiting for a trigger event to become operational, such as a link failure or a manual command1. The status does not depend on whether the ring is enabled administratively or not. https://www.arubanetworks.com/techdocs/AOS-CX/10.08/HTML/high_availability/Content/Chp_ERPS/ERPS_cmds/sho-erp-sta4.htm

You can only leak routes between up to three VRFs is not a rule for the setup of multi-protocol BGP to implement dynamic VRF route leaking on an ArubaOS-CX switch. There is no limit on the number of VRFs that can participate in route leaking using multi-protocol BGP. You can configure multiple import and export route targets for each VRF and leak routes between any VRFs that have matching route targets1.

The ArubaOS-CX software is based on the ArubaOS-Switch software and adds data center features is not a correct description of the ArubaOS-CX architecture. The ArubaOS-CX software is a new operating system that is designed for data center and campus networks. It is not based on the ArubaOS-Switch software, which is used for legacy campus switches. The ArubaOS-CX software provides advanced features such as VSX, EVPN, NAE, REST APIs, etc1.

Virtual Switching Extension (VSX) is a high-availability technology that allows two ArubaOS-CX switches to operate as a single logical device. VSX Inter-Switch Link (ISL) is a link between the two VSX switches that is used for both data plane and control plane traffic. It is recommended that the ISL link is a link aggregation with multiple 40GbE links or multiple 100GbE links to provide redundancy and bandwidth1. Therefore, this is a valid guideline for establishing a VSX ISL between two ArubaOS-CX switches.

It enables the switch REST API interface, if disabled is not something that NetEdit 2.0 does after it discovers a switch. NetEdit 2.0 is a tool that provides configuration management and validation for ArubaOS-CX and ArubaOS-Switch devices. NetEdit 2.0 can discover switches using various methods such as IP range scan, LLDP scan, CSV import, etc. However, NetEdit 2.0 cannot discover or communicate with switches that have their REST API interface disabled because NetEdit 2.0 relies on REST API calls to interact with switches1.