FusionAccess Planning and Deployment · Topic 2 of 2
FusionAccess Installation and Initial Configuration
Learn the FusionAccess install order on FusionCompute, component install and HA, then link ITA to FusionCompute, the AD domain and the vAG and vLB.
- 5 min
- Prepare FusionCompute first: DVS, port groups, datastores and an interface account with the administrator role.
- AD, DNS and DHCP must exist before FusionAccess is configured.
- Infrastructure VMs run Linux, get Tools installed, and then receive the components.
What it is
FusionAccess installation builds the infrastructure VMs on FusionCompute and installs the management components on them. Initial configuration is the first work in the ITA management portal that connects FusionAccess to FusionCompute, the AD domain and the access gateway.
After both are done, the system is ready for templates and desktop provisioning, which are covered in the next chapter.
How it works
Step 1: prepare FusionCompute
FusionAccess uses FusionCompute for every VM, so FusionCompute is prepared first.
| Task in FusionCompute | Why |
|---|---|
| Create the DVS and port groups | Give the management and service planes their VLANs |
| Add datastores | Provide storage for infrastructure VMs and desktops |
| Create an interface account | A FusionCompute interface interconnection user with the administrator role that ITA uses to call FusionCompute |
The interface account is easy to forget. Without it, ITA cannot create or control desktop VMs.
Step 2: build the domain services
If the customer has no AD, a Windows Server VM is created and set up as the domain controller with DNS and DHCP.
| Service | Configuration |
|---|---|
| AD | Create the domain, the OUs for desktops, user accounts and a domain account for FusionAccess |
| DNS | Forward and reverse lookup zones for the domain |
| DHCP | A scope with address range, gateway, DNS server, domain name and lease time |
Step 3: create the infrastructure VMs
The management components run on Linux infrastructure VMs created on FusionCompute. The FusionAccess installation image is mounted to the VM, the operating system installs from it, and the administrator then sets the VM's IP address, mask and gateway.
Next, Tools is installed in each infrastructure VM. Tools is FusionCompute's driver package that improves VM I/O and lets FusionCompute see the VM's state, and the VM restarts afterward.
Step 4: install the components
The installer offers a choice of what to install on each VM.
| Installer choice | Result |
|---|---|
| All components | All in one: every component on this VM |
| All except vAG and vLB | The core VM: ITA, HDC, WI, GaussDB, License |
| Custom | Pick components, for example only vAG and vLB on the gateway VM |
The first VM of a pair is installed as a new node. The second is installed and added to the existing node.
Step 5: configure high availability
HA is configured for each component group by entering the local IP, the peer IP and the floating IP. The same settings are made on the peer VM.
When every component shows a normal HA state, installation is complete.
Step 6: initial configuration in ITA
The administrator opens the ITA portal in a browser, logs in, and completes the initial settings. Change default passwords at the first login.
| Setting | What you enter |
|---|---|
| Virtualization environment | Type FusionCompute, the VRM floating IP and the FusionCompute interface account |
| Domain | Domain name, the domain account for FusionAccess, the AD and DNS server addresses |
| Access gateway | The vLB floating IP and the vAG address; in all in one mode these are on the core VM |
| License | Import the license file, or point to the License server |
| Default policy | Enable it, so new desktops start with a working baseline of peripheral and session settings |
ITA connects to the VRM, not to single CNA hosts. VRM manages all hosts and clusters, so one connection gives ITA the whole FusionCompute site.
A worked example
An engineer installs a small lab. She creates the DVS, port groups and a datastore in FusionCompute, adds an interface account with the administrator role, and builds one Windows VM for AD, DNS and DHCP.
She then creates two Linux VMs, installs Tools, installs all components on the first as a new node and on the second as an added node, and configures HA with a floating IP. In ITA she enters the VRM floating IP and the interface account, the domain details and the gateway address, and every service turns normal.
How the exam asks about this
- "Which address is entered in ITA to connect FusionAccess to FusionCompute?" -> The VRM floating IP address.
- "Which components are installed when the installer option all except vAG and vLB is chosen?" -> ITA, HDC, WI, GaussDB and License.
- "What must be installed in an infrastructure VM before the FusionAccess components?" -> Tools, followed by a restart.
What to remember for the exam
- Prepare FusionCompute first: DVS, port groups, datastores and an interface account with the administrator role.
- AD, DNS and DHCP must exist before FusionAccess is configured.
- Infrastructure VMs run Linux, get Tools installed, and then receive the components.
- The first VM of a pair is a new node and the second joins it; HA uses local, peer and floating IP addresses.
- In ITA, connect to FusionCompute through the VRM floating IP, then set the domain, gateway and license.
ITA uses a FusionCompute interface account to manage VMs. If that account is missing or lacks the administrator role, the connection fails and no desktops can be created.
Common mistakes
Connecting ITA to a CNA host. ITA talks to VRM, which manages all hosts; a single CNA address is wrong.
Skipping Tools. Without Tools the infrastructure VM lacks the optimized drivers and FusionCompute cannot fully monitor it.
Treating the domain as optional. Desktop provisioning joins VMs to AD and WI checks users against AD, so the domain settings must be right from the start.
Check yourself
Why does FusionAccess need an interface account in FusionCompute?
ITA uses it to call FusionCompute through VRM, so it can create, start and manage desktop VMs.
What three IP addresses are entered when configuring HA for a component pair?
The local IP, the peer IP and the floating IP that users and other components connect to.
Why is the default policy enabled during initial configuration?
It gives new desktops a baseline of peripheral and session settings, so devices used from the client work before any custom policy is made.
Topic 2 of 2 in FusionAccess Planning and Deployment
Test yourself on FusionAccess Planning and Deployment
The full Huawei H13-511 question bank has 600 questions, with timed practice exams and an explanation for every answer.
This study guide is independent and is not affiliated with, endorsed by, or sponsored by Huawei. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.