FusionCompute V100R003C10 Routine Maintenance and Troubleshooting

FusionCompute Routine
Maintenance and
Troubleshooting
www.huawei.com
Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved.

Objectives
 Upon completion of this course, you will be able to:

 Maintain FusionCompute.
 Collect information of FusionCompute.
 Handle FusionCompute faults.
Copyright © 2014 Huawei Technologies Co., Ltd. All rights reserved. Page 2
Contents
1. Basic Maintenance Operations
2. Information Collection
3. Troubleshooting
Contents

 FusionCompute Portal
 VM Management
 Account Management
 Alarm Management
 Backup and Restoration
Logging In to the FusionCompute Portal
To log in to the FusionCompute portal, enter the following address in the address box of the local
browser:
http://IP address of the Virtualization Resource Management (VRM) node
FusionCompute provides a unified operation and maintenance (O&M) management platform, allowing O&M engineers
to log in to the FusionCompute system from a web user interface (WebUI) to perform O&M operations.
You must change the default password and configure the browser upon your first login to the FusionCompute system.
Contents

 VM Management
VM Management
VM management includes creating a VM, managing various VM operations,
modifying VM specifications, creating a VM template, and creating a snapshot.
VM Management – VM Creation Methods
VM Management – Creating a VM
Procedure
1. Select VM location.
2. Configure VM properties.
3. Configure network interface cards (NICs) and disks.
4. Create a VM.
VM Management – Adjusting VM Specifications
You can modify CPU attributes, adjust memory specifications, expand disk capacity, attach
a disk to a VM, detach a disk from a VM, add a NIC, and delete a NIC.
VM Management – Modifying VM CPU Attributes
The conditions in which CPU attributes modification takes effect vary depending on
whether the CPU hot add policy is enabled.
Disable CPU hot add: The operation performed to modify CPU resource control policies
takes effect without VM restart. The operations performed to increase or reduce the number
of CPUs take effect after the VM is restarted.
Enable CPU hot add: The operations performed to add the number of CPUs and modify CPU
resource control policies take effect without VM restart. The operation performed to reduce
the number of CPUs takes effect after the VM is restarted.
VM Management – Adjusting VM Memory
Specifications
The operation performed to modify memory resource control policies takes
effect without VM restart. The operation performed to adjust memory size
takes effect after the VM is restarted.
VM Management – Adjusting VM Disk Capacity
Only disks using resources from Local Pome, virtualized storage area network (SAN)
storage, virtualized network attached storage (NAS) storage, or FusionStorage, support
capacity expansion.
• If disks use resources from the NAS storage and the disk type is set to Common, online
disk capacity expansion is not supported.
• If disks use resources from FusionStorage, online disk capacity expansion is supported
and will take effect upon VM restart.
• If disks use resources from Local Pome, virtualized SAN storage, and NAS storage,
online disk capacity expansion is supported and will take effect without VM restart when
the VM runs Windows Server 2003, Windows Server 2008, Windows XP, or Windows 7
OS. If the VM runs other OSs, the online disk capacity expansion will take effect after
the VM is restarted.
VM Management – Attaching or Detaching a VM
Disk
Disks using shared storage dedicated for raw device mapping (RDM) devices can be attached
only to Linux VMs. If attached to Windows VMs, these disks cannot be identified.
To detach a disk from a VM, ensure that the VM is in the Stopped state.
VM Management – VM Management Operations
VM operations include starting, hibernating, waking up, stopping, migrating, and deleting
VMs as well as attaching VMs to hosts.
VM Management – Creating a Template
Methods of creating a template: VM to template conversion, VM to template cloning, and
template to template cloning.
Procedure
1. Create a VM.
-To create a Windows VM, see Configuring the VM SID and Configuring Windows VM Specifications Attributes in
the FusionCompute Product Documentation.
-To create a Linux VM, see Configuring Linux VM Specifications Attributes and Configuring Linux VM NICs in the
FusionCompute Product Documentation.
2. Convert the VM to a template.
To clone a VM to a template or clone a template, set a location and attributes for the template as shown in the
following figure.
VM Management – Creating a VM Snapshot
A snapshot is taken to save information of all disks on a VM at a certain point for restoring VM data.
Multiple snapshots can be created for one VM. If a VM is being restored using a snapshot, other snapshots
of the VM are not affected.
VM Management – Restoring a VM Using a
Snapshot
Pay attention to the following when restoring a VM using a snapshot:
1. The VM must be in the Stopped or Hibernated state before restoration.
2. If a new disk is attached to the VM for which a snapshot has been taken, the new disk
automatically detaches from the VM when the VM is restored using the snapshot. You
can also detach the disk from the VM when necessary.
3. If a disk of the VM is not affected by snapshots, the disk data will not be backed up or
restored when the VM is backed up or restored using a snapshot. After the snapshot is
taken, if the disk is detached from the VM, the VM restored by the snapshot is attached
to the disk again, but disk data is not restored.
4. After the snapshot is taken, the disk cannot be found on the VM restored using the
snapshot if the disk is deleted.
Contents

 VM Management
Account Management – Role Management
The Role Management module in the FusionCompute system defines the operation
permissions granted to each role.
Account Management – User Management
The User Management module of the FusionCompute system is used to create users, define
roles of users, and assign operation permissions to users.
Account Management – Password Policies
In the Rights Management module of the FusionCompute system, you can set password policies for an
administrator account to log in to the FusionCompute portal. Password policies define password character
length, complexity, validity period, and account lockout duration.
Contents

 VM Management
Alarm Management
The system displays alarms in real time. You can view, handle, clear or mask them as needed.
Alarm Management – Setting Alarm Thresholds
When a key performance indicator (KPI) reaches a threshold, the system automatically
generates an alarm.
Alarm Management – Masking an Alarm
You can mask alarms that do not require handling so that these alarms will not be displayed on the
Real-Time Alarm page. You can query them in the historical alarms using search criteria.
Contents

 VM Management
Automatic Backup
 The FusionCompute system performs automatic backup at 2 o'clock every day. A

maximum of seven backup files (including automatic and manual backups) are
retained by default.
 Directories for storing backup files
- /var/backup/[YYYY]-[MM]-[DD]_sn/DATA for storing database backup files
- /var/backup/[YYYY]-[MM]-[DD]_sn/DB for storing configuration backup files
Manual Backup of the FusionCompute Data
Before performing an important operation, such as system upgrade or critical data modification, for
the VRM node, manually back up data of the VRM node. The data backup can be used to restore the
system if an exception occurs or the operation has not achieved the expected result.
Procedure:
Start
1. Use PuTTY to log in to the VRM node as user
gandalf. Determine the
deployment mode of the
2. Run the following command and enter the VRM node.
Active/standby mode
password of user root to switch to user root: Single-node mode
Log in to the VRM node. Log in to the active VRM node.

su - root
3. Run the following command to back up Back up data for the VRM node
locally.
management data of the VRM node:
Check the backup files stored
cronBackupUpload on the local storage device.
4. Switch to the /var/backup directory and check Determine No

whether to back up data
whether it contains the latest folder named in the to a third-party backup
server.
YYYY-MM-DD_sn format. Yes
Check the backup files stored on

If yes, the backup is successful.
- the third-party backup server.
If no, the backup fails.

-
End
Manual Restoration of the FusionCompute Data
After an important operation, such as system upgrade, critical data modification, or capacity expansion, is
performed for FusionCompute, roll back the system if an exception occurs or the operation has not
achieved the expected result. During the rollback, data restoration is required.
Before data restoration, stop the processes on

Start
the VRM nodes as follows:
Determine the
1. Use PuTTY to log in to the active VRM node. deployment mode of
the VRM node.
Ensure that the management plane floating IP address and
username gandalf are used to establish the connection. Single-node mode Active/standby mode
Stop processes on the
Stop processes on the
active and standby VRM
2. Run the following command and enter the password of user VRM node.
nodes.
root to switch to user root:
su - root Copy required data to the Copy required data to the
3. Run the following command to disable logout on timeout: VRM node. active VRM node.
TMOUT=0
4. Run the following command to stop the software monitoring
Restore data for the VRM Restore data for the active
processes on the active VRM node: node. VRM node.
service watchdog stop
Start the processes on the
The processes are stopped if the following information is Start the processes on the
active and standby VRM
VRM node.
displayed: nodes.
End
Contents
3. Troubleshooting
Information Collection
Information to be collected for fault identification is as follows:

1. Run logs of the active and standby VRMs
- Real-time logs: stored in the /var/locallog directory
- Backed-up logs: stored in the /var/backuplog/galaxenginelog/ directory
2. Run logs of the CNA node

- Real-time logs: stored in the /var/log/galaxenginelog/ directory of each CNA node
- Backed-up logs: stored in the /opt/cnalog directory on FusionManager every 15 minutes.
3. Real-time of the system

Back up the system running data and download the data. For details about how to back up data,
see the section "Backup and Recovery" in the FusionCompute V100R003C00 Product
Documentation.
Contents
3. Troubleshooting
Troubleshooting Procedure
Procedure
1. Collect fault information.
2. Identify faults.
3. Locate faults.
4. Troubleshoot faults.
Common Methods of Locating a Fault
The general methods of locating a fault are as follows:

1. View alarms on the management web client.
2. Check whether the monitoring information is normal on the management web client.
3. View operation logs to check whether the operation process is correct.
4. Check whether the configuration data is correct on the management web client.
5. Observe device indicators to check whether the devices are running properly.
Find out the exact cause that leads to the fault from multiple possible causes using
analyzing, comparing, and other possible methods.
Thank you
www.huawei.com

FusionCompute V100R003C10 Routine Maintenance and Troubleshooting

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

FusionCompute V100R003C10 Routine Maintenance and Troubleshooting

Caricato da

Copyright:

Formati disponibili

FusionCompute Routine

Copyright © 2010 Huawei Technologies Co., Ltd. All rights reserved.

 Upon completion of this course, you will be able to:

 Collect information of FusionCompute.

 Handle FusionCompute faults.

1. Basic Maintenance Operations

1. Basic Maintenance Operations

 Backup and Restoration

1. Basic Maintenance Operations

 Backup and Restoration

1. Basic Maintenance Operations

 Backup and Restoration

1. Basic Maintenance Operations

 Backup and Restoration

1. Basic Maintenance Operations

 Backup and Restoration

 The FusionCompute system performs automatic backup at 2 o'clock every day. A

Log in to the VRM node. Log in to the active VRM node.

4. Switch to the /var/backup directory and check Determine No

Check the backup files stored on

If no, the backup fails.

Before data restoration, stop the processes on

1. Basic Maintenance Operations

Information to be collected for fault identification is as follows:

2. Run logs of the CNA node

3. Real-time of the system

1. Basic Maintenance Operations

The general methods of locating a fault are as follows:

Potrebbero piacerti anche