The conditions of JDK of FusionInsight


The server and client support only built-in Oracle JDK (version: 1.8) and therefore a JDK replacement is not allowed.Customers' applications that need to reference the JAR packages of SDK to run in the application processes supprt Oracle JDK and IBM JDK.Oracle JDK versions: 1.7 and 1.8.Recommended IBM JDK versions:,, and

Other related questions:
Conditions for enabling IEEE 1588v2
To use the IEEE 1588v2 function on a BITS V3 device, PNSU or TODU boards must be configured in the master subrack. If the master subrack is fully configured with boards, you need to migrate the clock output service to the extended subrack first. Pay attention to the following configuration requirements: 1. You need to configure the PNSU boards to support output of IEEE 1588v2 clocks, but cannot configure 1:1 or 1+1 protection on the boards. 2. You must configure the PNSU boards in the master subrack. 3. You must configure a fan tray assembly in the master subrack. 4. You must configure a cabinet with a depth of 600 mm, for example, N63E-22. 5. The minimum version requirements for related software are as follows: PNSU/TODU: 102 or later MITU: 180 or later SRCU: 138 or later SYNLOCK centralized maintenance terminal: 3.30 (V300R002C20SPC030) or later Remarks: Clock boards support time source query since the previous versions.

ODUk SNCP protection switching conditions
ODUk SNCP is classified into SNC/I, SNC/N, and SNC/S. The difference between the three protection schemes lies in that they have different monitoring capabilities and therefore have different trigger conditions.

Whether LP_UNEQ is a condition for SNCP switching
Question: According to ITU-T suggestions, the standard LP_UNEQ alarm is inserted if no lower-order service is configured. However, some OSN devices cannot detect the LP_UNEQ alarm for triggering SNCP switching. Why? Analysis: Board hardware restrictions. Some boards can be upgraded to resolve the problem, whereas some cannot. Answer: No version of SSN1GXCSA, SSN1EXCSA, or SSQ1CXL supports LP_UNEQ detection.

Can Subnets Communicate with Each Other?

Subnets belong to VPCs. Subnets in the same VPC can communicate with each other. Subnets in different VPCs cannot communicate with each other by default. However, you can create VPC peering connections to enable subnets in different VPCs to communicate with each other.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top