Figure 4
‑50. System Copy - Summary
k
You can monitor the system copy progress by Clicking on Activities tab under Monitoring section
in the menu bar.
Figure 4
‑51. Monitoring - Activities
Each activity in the copy process has a corresponding line item and a respective log entry. Click on
the particular operation line item to read its corresponding log entry for more details.
VMware Adapter for SAP Landscape Management Administration Guide for LaMa Administrators
48
VMware, Inc.
Figure 4
‑52. Monitoring - Activity Log Entry
Successful completion of this task enables you to copy a source system into a new target system.
Chapter 4 Operations Overview
VMware, Inc.
49
VMware Adapter for SAP Landscape Management Administration Guide for LaMa Administrators
50
VMware, Inc.
Troubleshooting
5
This chapter includes the following topics:
n
“Log Locations,”
on page 51
n
“Log Configurations,”
on page 52
n
“Existing Limitations,”
on page 52
n
“Known Issues,”
on page 53
n
“Possible Misconfigurations / Issues,”
on page 56
Log Locations
Table 5
‑1. Log Locations
Log File Name
Log File Location
vLA application log
/usr/share/apache-tomcat/logs/vla.log
Tomcat server log
/usr/share/apache-tomcat/logs/catalina.out
Tomcat access log
/usr/share/apache-tomcat/logs/access.log
SA server access log file
/vla/tomcat/sa-server/logs/access.sa-server.log
SA server Java log files
/vla/tomcat/sa-server/logs/catalina.sa-server.log
/vla/tomcat/sa-server/logs/localhost.sa-server.log
SA server manager log file
/vla/tomcat/sa-server/logs/manager.sa-server.log
SA server application console log files
/vla/tomcat/sa-server/logs/catalina.sa-server.out
/vla/tomcat/sa-server/logs/sa-api.log
VLA server access log file
/vla/tomcat/vla-server/logs/access.vla-server.log
VLA server Java log files
/vla/tomcat/vla-server/logs/catalina.vla-server.log
/vla/tomcat/vla-server/logs/localhost.vla-server.log
VLA server manager log file
/vla/tomcat/vla-server/logs/manager.vla-server.log
VLA server application console log files
/vla/tomcat/vla-server/logs/catalina.vla-server.out
/vla/tomcat/vla-server/logs/vla.log
VMware, Inc.
51
Log Configurations
Log configuration menu is available in SAP NetWeaver Administrator — Troubleshooting -> Logs and
Traces -> Log Configuration
You can also navigate to — Related Links & Help -> Log Viewer
Figure 5
‑1. LaMa - Log Viewer
In the log configuration menu there are two configurations — Logging catagories and Tracing location
n
Log level is configured at Logging categories
n
Trace level is configured at Tracing location
In Logging categories there is a configuration for the whole adapter —
n
Located in Applications/LVM/InfrastructPlugins
In Tracing location, trace level is configured for each package separately —
n
For VMware Adapter for SAP Landscape Management it is com.vmware.vlvma.*
VMware Adapter for SAP Landscape Management log and trace messages begin with prefix VLVMA, hence
they can be easily filtered in LaMa Log Viewer.
Existing Limitations
Provisioning —
n
A linked clone of a SAP system can be performed to the same data storage only
n
A SAP system can be cloned to a DRS cluster only
n
Customization Specifications having the same Guest Operating System type and number of network
adapters as the Source Virtual Host are available for SAP system cloning
n
For provisioning from virtual host template, a cloned system hostname must be resolvable to an IP
address before executing the operation
n
Network interfaces bonding is not supported by vCenter Server Customization Specifications.
Currently, if the source system has a bond interface (2+ interfaces bonded to 1), it will also be present on
the destination system after the vCenter Server Clone operation. In order to apply a vCenter Server
Customization Specification a user should choose the specification which contains the same number of
network adapters and not the same number of bond interfaces. That is the reason the destination
system contains the same bond interface with the same IP address as the source system. vCenter Server
applies the provided Customization Specification on the slave interfaces which are not being used
outside the bond as far as they are connected to it. So the resulting configuration on the destination
system is not changed as intended.
Migrate —
n
Virtual host can be migrated between DRS clusters only
n
Virtual host can be migrated inside one vCenter Server only
VMware Adapter for SAP Landscape Management Administration Guide for LaMa Administrators
52
VMware, Inc.
Known Issues
1
On huge infrastructure during execution of mass operation, LaMa may hang
n
Solution — Increase the memory for the LaMa JVM
(
https://help.sap.com/saphelp_nwce10/helpdata/en/43/73949862c16fcbe10000000a1553f6/content.ht
m
)
2
During a SAP system cloning operation, the LaMa UI does not allow specifying hostname and IP
address for additional physical interfaces as per the selected customization specification. The number of
additional physical interfaces for which hostname and IP address can be set is limited to one network
adapter. Using the customization specification with three or more network adapters results in an
execution error.
n
Figure 5
‑2. Virtual Host Names and Networks
Solution — There is no solution available at this time
3
Provisioning from virtual host template fails either at the Waiting for host step or at the Adding
resources step due to LaMa exception.
n
Solution — There is no solution available at this time.
Figure 5
‑3. Failure - Provisioning from Virtual Host Template
Chapter 5 Troubleshooting
VMware, Inc.
53
4
After system cloning operation, validation errors may appear for a cloned SAP system — Error
HNMissmatch may be detected for a SAP host during validation.
n
Figure 5
‑4. Error - HNMissmatch
Solution — This issue mainly appears if the DHCP customization specification is used during the
provisioning operation. The reason is that the vCenter Server adds a new record into
the
/etc/hosts
file during the post clone virtual machine customization process. In case the
primary interface does not have an IP address yet (since the primary interface will obtain IP
address only when the network services get started), the next interface which has an IP address
will be used for this record. This results in a wrong mapping of a physical hostname and an IP
address in the
/etc/hosts
file. The LaMa detects this dissonance and warns the user.
5
Error CloneHnChn may be detected for a SAP sub-system during validation.
n
Figure 5
‑5. Error - CloneHnChn
Solution — SAP Note 1366742
VMware Adapter for SAP Landscape Management Administration Guide for LaMa Administrators
54
VMware, Inc.
6
Occasionally the SAP system cloning fails at the Prepare VM clone step. This is seen if the SAP system
has several network interfaces and the Auto IP Address option is set for these additional network
interfaces in the Host names dialog.
n
Figure 5
‑6. Prepare VM Clone Failure
Solution — There is no solution available at this time. The issue is caused by incorrect dialog
context that is provided by the LaMa.
7
VLVMA adapter cannot be added with the Trusted server option enabled because of File Not Found
and Permission denied faults.
n
Solution — Make sure that the cacerts file in the directory
/usr/sap/
ID>/J00/exe/sapjvm_6/jre/lib/security/
has proper access rights (permissions).
8
After cloning a SAP JAVA system the status of AS instance of the cloned system is changed to the Error
state.
n
Figure 5
‑7. SAP JAVA system cloning error state
Solution — This issue is caused due to a missing license. HW key of the cloned system does'nt
match with the installed license. In a SAP JAVA system, the instance is shut down after 30 minutes
if the license is missing. In a SAP ABAP system, the instance keeps running if a license is missing
but only the user sap* can login. All the other users are locked. In addition, the system copy/clone
functionality will not be present.
9
If a clone or copy operation did not complete successfully, the virtual machine will be deleted from the
vCenter Server during the Destroy operation.
n
Solution — You need to delete the virtual machine in vCenter Server manually.
Chapter 5 Troubleshooting
VMware, Inc.
55
10 Offline linked copy of SAP HANA on SLES fails on step Stop
n
Figure 5
‑8. SAP HANA on SLES failure on Stop Operation
Step Error — Database is in Use
Figure 5
‑9. Error - Database is in Use
Solution — Close hdbstudio on the source machine.
Possible Misconfigurations / Issues
Following are some of the Errors that you may encounter along with the possible reasons —
1
Error — peer not authenticated [SSLPeerUnverifiedException], this could occur during a connection test
or infrastructure retrieval
n
Possible reasons are invalid vLA server certificate, disabled Trusted Server option or a certificate
that was changed after the adapter configuration.
Figure 5
‑10. Error — Failed to connect to manager
VMware Adapter for SAP Landscape Management Administration Guide for LaMa Administrators
56
VMware, Inc.
2
Error — Could not execute operation ***
n
Possible reasons are —
n
VMware vRealize Orchestrator is unavailable
n
Check the state of the VMware vRealize Orchestrator server.
n
An overloaded VMware vRealize Orchestrator
n
Check the CPU and Memory utilization for the VMware vRealize Orchestrator server.
3
Error — Could not execute operation ***. Workflow not found
n
Figure 5
‑11. Error —Workflow not found
Possible reasons for the error — Workflow unavailable on VMware vRealize Orchestrator
n
Check the workflow:8443/vla/dashboard "> status in the vLA dashboard -
:8443/vla/dashboard ">https:// :8443/vla/dashboard
n
Check the workflow ID for operation in file
/etc/vla/systemproperties.xml
n
Check the workflow availability on the VMware vRealize Orchestrator
n
Reinstall the VMware vRealize Orchestrator package or corred the vLA config file
4
All actions are unavailable for Virtual Host in Operations / Virtualization. The Details property field
shows up the virtual host status as disconnected under the Virtual Host tab.
n
Figure 5
‑12. Virtual Host - Disconnected
Chapter 5 Troubleshooting
VMware, Inc.
57
Possible reason — ESXi host unavailable
n
Check the ESXi host status on the VMware vCenter Server. Make it available to the
VMware vCenter Server.
5
VMware vCenter Server is not displaying in the LaMa Adapter
n
Possible reason for the error — VMware vCenter Server unavailable to the vLA
n
Check the status of the VMware vCenter Server in the vLA dashboard. Make the
VMware vCenter Server available to the vLA.
n
Not connected / Not ready — means that the vLA cannot connect to the
VMware vCenter Server or vLA is unable to fetch the inventory data or the inventory data
retrieval is in progress.
Figure 5
‑13. Errors —Not connected/Not ready/Configuration missing
n
Configuration ... is missing — means that no credentials was found in the credentials
store for the specified server. Credentials must be added via the
Credentials_add.sh
command on the vLA.
6
Error — HTTP Status Code 401
n
Figure 5
‑14.
Possible reasons — The adapter was configured with the wrong credentials (username or
password) or hostname. Password on the vLA Server was changed after adapter configuration.
n
Correct the password to the application server, or reset it to a known password on the vLA
with the
vla_user.sh
command.
VMware Adapter for SAP Landscape Management Administration Guide for LaMa Administrators
58
VMware, Inc.
7
Alert —Unsupported network is configured on one of the network adapters.
n
Figure 5
‑15. Unsupported Network Alert
Possible reasons — vSphere Distributed Switch Uplink is assigned as a network to VM or assigned
network is related to unsupported third party switch (neither vSS nor vDS switch)
n
Re-assign networks for network adapters on VM. Assign only networks related to vSphere
Standard Switch or vSphere Distributed Switch Portgroup
8
Monitoring Error in LaMa Virtualization pane —
Figure 5
‑16. Monitoring Error
Chapter 5 Troubleshooting
VMware, Inc.
59
Possible reason — You are using an older version of the LaMa adapter (1.3.x or older). VLA and LaMa
communication protocol version mismatch occurs.
n
Update to the latest version of the LaMa adapter (1.4.0 or higher).
VMware Adapter for SAP Landscape Management Administration Guide for LaMa Administrators
60
VMware, Inc.
Index
S
SAP LaMa 5, 6
V
VMware Adapter for SAP Landscape
Management 5
VMware, Inc.
61
VMware Adapter for SAP Landscape Management Administration Guide for LaMa Administrators
62
VMware, Inc.
Document Outline - VMware Adapter for SAP Landscape Management Administration Guide for LaMa Administrators
- Contents
- Introduction to VMware Adapter for SAP Landscape Management
- About This Guide
- Target Audience
- Prerequisites
- Understanding the Organization of this Guide
- Overview of VMware Adapter for SAP Landscape Management: Purpose, Benefits, Architecutre and Components
- Product Overview
- Features and Benefits
- Reference Architecture
- Environment Setup
- Configure SAP Landscape Management (LaMa)
- Configure DNS
- VLA Server Side Configuration
- SAP Landscape Management (LaMa) Side Configuration
- Configure LaMa to use the VMware Adapter for SAP Landscape Management
- Operations Overview
- Operations
- Forced Operations
- Non-Forced Operations
- Activate
- Deactivation / Deactivate
- Suspend
- Migrate
- Provisioning
- Troubleshooting
- Log Locations
- Log Configurations
- Existing Limitations
- Known Issues
- Possible Misconfigurations / Issues
- Index
Dostları ilə paylaş: |