H3C VNF Manager APP Troubleshooting Guide-5W301

HomeSupportResource CenterSDNH3C VNF ManagerH3C VNF ManagerTechnical DocumentsMaintainTroubleshootingH3C VNF Manager APP Troubleshooting Guide-5W301
Download Book
Table of Contents
Related Documents

 

H3C VNF Manager App

Troubleshooting Guide

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Document version: 5W301-20190828

 

Copyright © 2019 New H3C Technologies Co., Ltd. All rights reserved.

No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of New H3C Technologies Co., Ltd.

Except for the trademarks of New H3C Technologies Co., Ltd., any trademarks that may be mentioned in this document are the property of their respective owners.

The information in this document is subject to change without notice.



Introduction

This document provides information about troubleshooting common software and hardware problems with the H3C VNF manager app.

General guidelines

To help identify the cause of the problem, collect system and configuration information, including:

·     VNF manager app version and VCF controller version.

·     Symptom, time of failure, and configuration.

·     Log messages and diagnostic information. For more information, see "Collecting diagnostic log messages."

·     Steps you have taken and their effects.

Collecting diagnostic log messages

To collect diagnostic log messages of the VCF controller and the VNF manager app:

1.     Enter the URL of the controller in the address bar of a browser (for example, Chrome) to enter the VCF controller login page.

The URL is in the format of https://controller_ip_address:8443/vcf/ui/app/index. If HTTPS is not available due to policy limitations, you can enter the URL in the format of http://controller_ip_address/vcf/ui/app/index or http://controller_ip_address:8080/vcf/ui/app/index to log in to the controller through HTTP.

2.     On the VCF controller login page, enter the username and password, and click Log in.

3.     Click ASSURANCE on the top navigation bar, select Logs from the navigation pane, and click the Diagnosis Information tab to enter the diagnosis information page, as shown in Figure 1.

Figure 1 Diagnosis information page

 

4.     Click Local export or Export. Click Local export in this example.

The Export Local Diagnosis Information dialog box appears.

5.     Select one or more controllers and click Export.

The exported diagnosis information for the controllers is saved to a local file. To export a controller's diagnosis information for the second time, close the dialog box, and then click Export on the diagnosis information page again.

Figure 2 Export Local Diagnosis Information dialog box

 

Contacting technical support

If you cannot resolve a problem after using the troubleshooting procedures in this document, contact H3C Support.

The following is the contact information for H3C Support:

·     Telephone number—400-810-0504.

·     E-mailservice@h3c.com.


Troubleshooting NETCONF

This section provides troubleshooting information for common NETCONF problems.

Failure to display the CPU usage and memory usage of a VNF

Symptom

On the VNF Manager page, the CPU usage and memory usage of a VNF are displayed as three hyphens (---).

Solution

To resolve the problem:

1.     Verify that the VNF and the VNF manager app communicate with each other properly:

a.     Log in to the system of the VCF controller, and verify that you can ping the VNF.

b.     Log in to the VNF, and verify that you can ping the VCF controller.

2.     Verify that the NETCONF settings are consistent on the VNF and the VNF manager app:

a.     Make sure NETCONF over SOAP over HTTPS is enabled on the VNF.

b.     Make sure the VNF and the VNF manager app are configured with the same username and password.

If any inconsistency occurs, modify the NETCONF settings on the VNF.

3.     Verify that a NETCONF session can be established between the VNF and the VNF manager app.

There is a limit on the number of NETCONF sessions that can be established on the VNF. If the upper limit has been reached, the VNF cannot establish a NETCONF session with the VNF manager app. In this case, delete the existing NETCONF sessions or increase the NETCONF session limit to ensure that a NETCONF session can be established between VNF and the VNF manager app.

4.     If the problem persists, contact H3C Support.


Troubleshooting the VNF manager app

This section provides troubleshooting information for the VNF manager app.

VNF manager app page or function exception

Symptom

The VNF manager app page is exceptional or the function is exceptional.

Solution

1.     Clear the cache of the browser and log in to the VNF manager app page again. Identify whether the page is displayed properly and the function is available.

2.     Identify whether the VNF manager app software version is compatible with the VCF controller version. If they are incompatible, replace the VNF manager app or VCF controller version. For the version compatibility matrix, see H3C VNF Manager App Release Notes.

3.     If the problem persists, contact H3C Support.

Failure to create a VNF

Symptom

An error occurs when you create a VNF.

Solution

To resolve the problem:

1.     Verify that the VCF controller is operating properly, the VNF manager app is properly deployed, and the VNF manager license is successfully activated.

2.     Verify that the VNF manager app and the host can reach each other, and the username and password of the host configured on the VNF manager app are correct.

3.     Verify that the host quantity meets the requirements.

A VNF in HA mode requires a minimum of two independent hosts for creating VMs.

4.     Verify that the host has sufficient resources to meet the requirements of the VNF flavor.

The CPU, memory, and storage resources that are required to create the VNF are defined by the VNF flavor.

5.     If the problem persists, contact H3C Support.

Failure to manage a VNF

Symptom

The VNF manager app cannot connect to and manage a VNF that is in Active state.

Solution

To resolve the problem:

1.     Verify that the VNF manager app and the VNF can reach each other.

2.     Access the CLI of the VNF through the console to verify that the VNF has started.

3.     Verify that the IP address of each VM interface has been manually configured or obtained from the IP address pool.

4.     Verify that the management IP address has been manually configured or obtained from the address pool for a VNF in HA mode.

5.     If the problem persists, contact H3C Support.