I. Version
Report server version | JAR package | New version update |
|---|---|---|
| 10.0 | - | For Local Machine Information Authentication, user need to export the registration information of each node in turn |
| 10.0 | 2019-05-20 | Local Machine Information Authentication supports exporting the registration information of all nodes under one node |
II. Concept introduction
Cluster : The English name is cluster. In layman's terms, cluster is a technology that connects multiple systems together so that multiple servers can work like one machine or look like one machine.
Dual-system hot backup : specifically refers to the hot backup (or high availability) based on two servers in a high-availability system. Because two-machine high availability is used more in China, it is named dual-system hot backup.
One system with multiple servers : The user has developed a system that needs to be deployed to multiple users. The same system can be installed directly. Or if the customer has three machines, two of which are backup machines. If there is a problem with the machine currently in use, the application will be automatically transferred to the backup machine.
III. Registration method
| Registration method | Introduction | Reference documents |
|---|---|---|
| Local machine information authentication | Support this registration method Just under one node in the cluster environment, you can export the rif registration information of all nodes with one click A set of clusters corresponds to a lic file, and the lic only needs to be uploaded once on a node to register successfully Finally, the registration fee is based on the number of cluster nodes Note 1: If exporting the registration information is unsuccessful, you can email a screenshot of the version information page to the business. Note 2: Please make sure that the logged-in node can communicate with all nodes, otherwise all node information cannot be exported at one time. | Local Machine Info AUTH |
| Private cloud Authentication | Support this registration method Only one authorization server is needed to authorize multiple nodes All nodes and authorization servers need to be mutually accessible The number of authorizations under the authorization server must be greater than or equal to the number of nodes | Private Cloud AUTH |
| Public cloud Authentication | Support this registration method All nodes need to be able to access FanRuan public cloud authentication server The maximum registerable amount needs to be greater than or equal to the number of nodes | Public Cloud AUTH |
| Encryption lock authentication | The cluster does not support this registration method | - |
IV. Registration failed
If the registration fails, a pop-up window will appear on the page, as shown in the figure below:
Click onreturnYou can view the reason for the registration failure, and perform troubleshooting based on the specific failure reason, as shown in the following figure:
1. Reasons for failure of local information authentication
1) Overall failure
| Reason for failure | Specific information |
|---|---|
| The certificate has expired | Expiration time: 2019-02-22 |
| Version mismatch | Certified application version: 9.0 Local application version: 10.0 |
2) Node failure
| Nodes that failed to register | Reason for failure | Specific information |
|---|---|---|
| node-47-1 | MAC address does not match | Authentication MAC address: xxx Local MAC address: xxx |
| node-47-1 | Machine code does not match | Authentication machine code: xxx Local machine code: xxx |
| node-47-1 | Application name does not match | Certified application name: xxx Local application name: xxx |
| node-47-1 | The maximum number of authorizations has been reached | The certificate has been used by other projects on the same server |
| node-47-1 | Project content does not match | Authentication project content: xxx Local project content: xxx |
2. Reasons for Private Cloud Authentication Failure
1) Overall failure
| Reason for failure |
|---|
| Incorrect data format |
| Version mismatch |
| The certificate has expired |
| The authorization server has been uninstalled, please apply again |
2) Node failure
| Nodes that failed to register | Reason for failure |
|---|---|
| node-47-1 | The maximum number of authorizations has been reached |
| node-47-1 | IP is not in the allowed range |
| node-47-1 | The domain name is not within the allowed range |
| node-47-1 | The application name is not within the allowed range |
| node-47-1 | The machine is not authorized to unbind (this prompt appears when unbinding, indicating that this machine does not need to be unbound because it is not authorized) |
3. Reasons for failure of public cloud Authentication
1) Overall failure
| Reason for failure |
|---|
| Incorrect data format |
| The parameters you entered are incorrect |
| The account and password are not authorized |
| Version mismatch |
| Account status is abnormal |
| The certificate has expired |
2) Node failure
| Nodes that failed to register | Reason for failure |
|---|---|
| node-47-1 | Error inserting data into REDIS database |
| node-47-1 | IP is not in the allowed range |
| node-47-1 | The domain name is not within the allowed range |
| node-47-1 | The application name is not within the allowed range |
| node-47-1 | Error updating MYSQL database |
| node-47-1 | The maximum number of authorizations has been reached |
| node-47-1 | The machine is not authorized to unbind (this prompt appears when unbinding, indicating that this machine does not need to be unbound because it is not authorized) |
Note: In addition to the failure reasons other than the above, other unified error: the content of the certificate is incorrect
4. Other instructions
1) When there are multiple failure reasons for a single node, they will all be displayed on the platform.
For example, when the machine code does not match the MAC address:
| node-47-1 | The machine code does not match, the MAC address does not match | Authentication machine code: xxx Local machine code: xxx Authentication MAC address: xxx Local MAC address: xxx |
2) When there are both reasons for the overall registration failure and single-node registration failure, only the reasons for the overall registration failure are displayed.
For example, if the certificate has expired and the machine code of node-47-1 does not match, only the certificate is expired, and the machine code does not match, the display is:
The certificate has expired
Expiration time: 2019-02-22
