Hello, everyone! Today I will share with you how to install FusionCare on Windows.
1. The account used for FusionCare installation must be granted administrator permission for deploying services.
2. Log in to the PC or VM where FusionCare is to be installed and copy the FusionCare installation package to the target directory.
3. Switch to the directory containing the FusionCare-V100R005C00SPC536.zip file, right-click FusionCare-V100R005C00SPC536.zip, and select Extract Here.
4. Switch to the directory containing the FusionCare.tar.gz file, right-click FusionCare.tar.gz, and select Extract Here.
5. Check whether the health check or information collection needs to be performed for FusionSphere OpenStack.
If yes, go to Step 5.a.
If no, go to Step 6.
a. Obtain the following data:
The domain name of the Keystone service and the reverse proxy IP address of the AZ accommodating the Keystone service.
The domain name of the info-collect service and the reverse proxy IP address of the AZ accommodating the info-collect service.
The domain name of the upgrade service and the reverse proxy IP address of the AZ accommodating the upgrade service.
Add domain name and reverse proxy IP address information about the Keystone, info-collect, and upgrade services to the configuration file C:\Windows\System32\drivers\etc\hosts as following patterns:
Reverse proxy IP address of the AZ accommodating the Keystone service, Keystone service domain name
Reverse proxy IP address of the AZ accommodating the info-collect service, Info-collect service domain name
Reverse proxy IP address of the AZ accommodating the upgrade service, Upgrade service domain name
For example, if the reverse proxy IP address of the AZ accommodating the Keystone service 202.1.1.17, the Keystone service domain name is identity.az1.dc1.domainname.com, the reverse proxy IP address of the AZ accommodating the info-collect service is 202.1.1.17, the info-collect service domain name is info-collect.az1.dc1.domainname.com, the reverse proxy IP address of the AZ accommodating the upgrade service is 202.1.1.17, and the upgrade service domain name is upgrade.az1.dc1.domainname.com, add the following information to the /etc/hosts file:
202.1.1.17 identity.az1.dc1.domainname.com
202.1.1.17 info-collect.az1.dc1.domainname.com
202.1.1.17 upgrade.az1.dc1.domainname.com
b. Check whether the FusionSphere OpenStack system has multiple AZs.
If yes, enable domain name resolution for domain names of info-collect and upgrade services in each AZ.
If no, go to Step 5.c.
c. Check whether FusionSphere OpenStack is deployed in cascading mode.
If yes, perform Step 5.b at each cascading layer.
If no, go to Step 6.
6. (Optional) Bind the IP to FusionCare. Switch to the \FusionCare\tomcat\conf directory and open the server.xml file. Add or modify the address attribute for the Connector, and the value is the IP to be bound. Take 192.168.1.160 as an example, as follows:
7. Right click start.bat and run as an administrator.
8. If the PC or VM where FusionCare is installed has multiple NICs and IP addresses, information shown in the following figure is displayed to ask the user to select an IP address that can connect to the environment.
Please, select an IP address which can communicate with the node you add as the ip of the FTPServer. For example, if you enter 1 and press Enter, the first IP address is set to the FTP server IP address.
9. The FusionCare login page will be automatically displayed if FusionCare is successfully installed. It may take a long time for the FusionCare login page to display.
NOTE:
The FusionCare installation directory supports only uppercase letters, lowercase letters, digits and spaces.
To ensure that FusionCare can collect FusionAccess logs, ensures that the node where FusionCare is deployed can communicate with all FusionAccess management nodes, including AD, DNS, DHCP, ITA, WI, HDC, License, and DB nodes. If the management and service planes can communicate with each other, the VM where FusionCare is installed can have only one NIC. Otherwise, the VM where FusionCare is installed must have at least two NICs, and the management and service planes are configured to communicate with one another.
To ensure that FusionCare can collect FusionSphereOpenStack logs, ensures that the FTPServer IP of the node where FusionCare is deployed can communicate with the external_om or external_api plane of FusionSphere OpenStack. If the external_om and external_api plane of FusionSphereOpenStack can communicate with each other, please select the OM plane IP as the IP of the FTP Server at the first place.
To ensure system security, do not connect the node where FusionCare is deployed to insecure networks.
Thanks!
