HP FlexFabric Virtual Switch 5900v Troubleshooting Guide

HP FlexFabric Virtual Switch 5900v
Troubleshooting Guide
Part number: 5998-4546
Document version: 6W100-20131220
© Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained
herein is subject to change without notice. The only warranties for HP products and services are
set forth in the express warranty statements accompanying such products and services. Nothing
herein should be construed as constituting an additional warranty. HP shall not be liable for
technical or editorial errors or omissions contained herein.
Contents
Troubleshooting overview ············································································································································ 1 HP 5900v architecture ····················································································································································· 1 Other HP products cooperating with the HP 5900v ····································································································· 1 General troubleshooting process····································································································································· 2 Troubleshooting basics ····················································································································································· 3 Contacting HP Support ····················································································································································· 6 Tools for troubleshooting ············································································································································· 7 Global configuration page ·············································································································································· 7 Operation logs ·································································································································································· 7 Syslog ················································································································································································· 8 VFE commands ·································································································································································· 8 Problems with VCE installation ···································································································································· 9 Symptom ············································································································································································ 9 Solution ·············································································································································································· 9 Problems with licenses ··············································································································································· 10 Failure to upload the formal license file ······················································································································ 10 Failure to configure any function on the HP 5900v tab ···························································································· 10 Error message displayed when operations are performed on the 5900v after VCE deployment ························ 11 VFE batch installation page does not respond ··········································································································· 11 Incorrect VFE license state caused by ESXi host CPU number change ···································································· 12 Failure to register the product after the VCE is vMotioned to another ESXi host ···················································· 12 Problems with VFE installation and removal ············································································································ 13 Incorrect VDS status after a host is added to the VDS ······························································································· 13 ESXi operating incorrectly ············································································································································· 13 Incorrect VFE status when the VFE page is refreshed ································································································· 14 Failure to remove a VFE ················································································································································ 14 Failure to uninstall the VFE after a host is removed from the VDS ············································································ 15 Problems with the global configuration page ·········································································································· 16 The global configuration page displays no contents after the VCE is restarted ······················································ 16 Failure to configure vCenter Server connection ·········································································································· 16 Failure to install the VMware plug-in ··························································································································· 17 Failure to remove the plug-in ········································································································································ 17 Failure to delete vCenter Server connection················································································································ 17 Failure to obtain the MAC address of the host where the VCE resides ··································································· 18 Failure to connect the VCE to the vCenter Server after the vCenter Server is reinstalled ······································· 18 Problems with VMware plug-in ································································································································· 20 Failure to display the configuration tabs on the vSphere client ················································································ 20 Failure to correctly display the 5900v configuration tabs on the vSphere client ···················································· 20 Plug-in display error ······················································································································································· 21 Failure to enter VDS management page ····················································································································· 21 Problems with VDS creation and deletion ················································································································ 23 Failure to create or delete a VDS ································································································································· 23 Error message displayed when a VDS is created or deleted ···················································································· 23 Error message displayed for the host VDS networking information ········································································· 23 Incorrect VDS name on the vSphere Client ················································································································· 24 i
Problems with port group ·········································································································································· 25 Failure to configure VDP for a port group ··················································································································· 25 VLAN configuration loss ················································································································································ 25 Failure to restore the port group configuration after the VCE is rebooted ······························································· 25 Failure to display VDP information for a port group ·································································································· 26 Failure to automatically refresh the number of port groups on the VDS page ························································ 26 Failure to automatically refresh the port group of a VDS when the VDS changes ················································· 27 Failure to the restore the VFE configuration after the VCE is restarted ····································································· 27 Any port group to which online VSIs belong can be removed from the VMware vSphere Client ························ 28 Problems with traffic forwarding ······························································································································· 29 Communication failure between VMs even if the vNICs are bound to a port group ············································· 29 Failure to remove part of broadcast traffic information in the flow table ································································ 30 Incorrect host information caused by changing the IP address of a host in VDS···················································· 30 Problems with EVB ····················································································································································· 31 VSIs cannot get online after the EVB port on the physical switch is manually brought up ···································· 31 The VSI gets offline when you migrate the storages of two VMs at the same time················································· 31 Contacting HP Support ·············································································································································· 33 Contacting HP Support ·················································································································································· 33 Gathering information ··················································································································································· 33 ii
Troubleshooting overview
HP 5900v architecture
The HP5900v virtual switch includes the following components: Virtual Control Engine (VCE), Virtual
Forwarding Engine (VFE), and VMware plug-in. For more information, see HP FlexFabric Virtual Switch
5900v Installation Guide.
When you troubleshoot the HP 5900v, you need to identify the component that might be causing the
symptoms first, and then gather information to resolve the problems.
Other HP products cooperating with the HP 5900v
Being familiar with other products cooperating with the HP 5900v helps you learn about the operating
mechanism of the 5900v so that you can quickly locate problems.
IMC
HP Intelligent Management Center (IMC) provides easy-to-use network management functions such as
topology, fault, performance, configuration and security management. In addition, IMC guides users
through detailed configuration steps, providing granular network management software.
1
Figure 1 IMC and HP 5900v
IMC
VAN Connection Manager
VMware vCenter Server
HP 5900v VCE
vCenter Server Plug-in
Management Switch
App
App
App
App
App
App
VM1
VM2
VM3
VM1
VM2
VM3
HP 5900v VFE
(vSwitch)
HP 5900v VFE
(vSwitch)
ToR 5900/5920
The HP 5900v must connect to an IMC server to implement virtual connection management and network
policy application. If the 5900v does not connect to an IMC server, or the IP address, port number,
username, or password of the IMC server is incorrect, the VDP information cannot be configured on the
VMware plug-in on the 5900v, and the VSIs of the virtual machine (VM) connected to the 5900v cannot
get online.
For IMC configuration, see the IMC help.
EVB switch
An EVB switch is an important part of the HP Edge Virtual Bridging (EVB) solution. The HP 5920&5900
Switch Series can serve as an EVB switch. The EVB feature can be applied only when the server where
the 5900v resides connects to an EVB switch, and the physical port or aggregation interface that
connects the EVB switch to the server is enabled with EVB.
For more information about EVB switch configuration, see HP 5920&5900 Switch Series Configuration
Guides.
General troubleshooting process
General troubleshooting process
To troubleshoot your network, follow these general steps:
2
1.
Gather information that defines the symptoms, such as configuration information, VCE and VFE
log information, current traffic information, and VSI online and offline information.
2.
Gather information about IMC and HP 5920&5900 switches that might be causing the symptoms.
3.
Locate potential problems that might be causing the symptoms.
4.
Resolve the problems until the symptoms disappear.
Best practices
To ensure correct operation of your network, HP recommends the following best practices:
•
Make sure all HP 5900v virtual switches, including VCEs and VFEs, deployed in the network use the
same software version.
•
See the release notes for your HP 5900v release for the latest features, limitations, and cautions.
•
Make sure you are aware of the impacts to the network before any configuration, and verify any
configuration changes after implementing the change.
Troubleshooting basics
Troubleshooting guidelines
Answer the following questions before locating a problem:
•
Is this a newly deployed system or a system that has been running for a period of time?
•
Has the host where the HP 5900v is installed correctly connected to the network?
•
Are you trying to solve an existing system performance problem (too slow, too high latency,
excessively long response time) or did the problem appear recently?
•
What configuration changes happen in the system before the problems appear?
Gathering information
Gather the following information to correctly locate problems:
•
•
HP 5900v information:
{
Product version
{
Log information
Information about other products cooperating with the HP 5900v:
{
IMC version
{
Switch model, software version, and configuration information for EVB switches.
{
vCenter Server, vShpere Client, and ESXi version information
{
Server model and hardware configuration information
Verifying server NICs
•
The correct media, copper or fiber is being used, and the fiber type is correct.
•
The media is not broken or damaged.
3
•
Verify that the NICs are operating correctly by examining the server console, or by examining
upstream switches.
Verifying Layer 2 connectivity
•
Verify that all necessary ports are in the same VLAN.
•
Verify that the aggregation configurations for the ports on the server side and EVB switch side are
the same.
For more information about how to verify aggregation configuration, see "Verifying link
aggregation configuration."
Verifying Layer 3 connectivity
•
Verify that a correct IP address and reachable routes are configured for each device.
•
Verify that no firewall or QoS configuration restricts the access of an IP address of the server at the
EVB switch side.
If these two items are verified, you can use the ping or tracert command to verify Layer 3 connectivity.
Verifying vCenter Server connectivity
The VCE on the HP 5900v can operate only when connected to the vCenter Server. The VDSs and port
groups configured on the VCE are saved on the vCenter Server. Before using the 5900v, make sure the
VCE has been connected to the vCenter Server on the global configuration page. The
that the VCE has been connected to the vCenter Server. The
disconnected from the vCenter Server.
icon indicates
icon indicates that the VCE has been
Verifying IMC server configuration
1.
Display IMC server configuration on the global configuration page, as shown in Figure 2.
2.
Make sure the IP address, port number, username, and password configured on the 5900v and
the IMC server are the same.
Figure 2 IMC server configuration
Verifying VMware plug-in installation
Verify that the VMware plug-in has been successfully installed on the global configuration page, as
shown in Figure 3.
4
Figure 3 Plug-in registration status
The
icon indicates that the plug-in has been successfully installed. The
plug-in has been removed. To install the plug-in, click Install.
icon indicates that the
Verifying link aggregation configuration
1.
Verify the physical NICs that connect the server to the EVB switch, and the ports that connect the
EVB switch to the server.
2.
On the server side, enter the link aggregation configuration page on the vSphere client to verify
link aggregation configurations of the ports on the server, as shown in Figure 4:
{
Verify that the link aggregation mode is Static.
{
Verify that the load balancing mode is Source MAC or Destination MAC.
{
Verify that all aggregation interfaces are the same type and same rate.
{
Verify that all physical ports to be aggregated are selected.
Figure 4 Link aggregation configuration page
3.
On the EVB switch, execute the display link-aggregation verbose command in system view to
verify aggregation interface configuration:
<Sysname> display link-aggregation verbose
Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing
Port Status: S -- Selected, U -- Unselected
Flags:
A -- LACP_Activity, B -- LACP_Timeout, C -- Aggregation,
D -- Synchronization, E -- Collecting, F -- Distributing,
G -- Defaulted, H -- Expired
Aggregate Interface: Bridge-Aggregation100
Aggregation Mode: Static
Loadsharing Type: Shar
Port
Status
Priority Oper-Key
-------------------------------------------------------------------------------XGE1/0/15
S
32768
4
XGE1/0/29
S
32768
4
5
The output shows that XGE1/0/15 and XGE1/0/29 connect to vmnic2 and vmnic3, respectively.
A port in S state indicates the port is a selected port. Make sure all ports connecting to the server
are selected.
Contacting HP Support
If you cannot solve a problem after using the troubleshooting suggestions in this guide, contact HP
Support for help. For more information, see "Contacting HP Support."
6
Tools for troubleshooting
Global configuration page
1.
Enter http://VCEIP:8090 in the browser. The HP 5900v login page appears.
2.
Enter the username admin and password admin, and click Login.
On the global configuration page, you can display and modify IMC server and vCenter Server
configuration.
Figure 5 VCE global configuration page
Operation logs
Operation logs save all user operations such as operation time, content, and result. You can view
configuration changes before a problem occurs and display operation results when you locate problems.
To view operation logs, select Operation Log from the navigation tree on the global configuration page.
Figure 6 Viewing operation logs
7
Syslog
The HP 5900v is running on the Ubuntu system. For folder and file operations on the console, see the
Ubuntu system user manual.
Displaying VCE logs
Open the VCE console, and enter the /var/log/floodlight directory. You can also collect VCE logs on the
system management page.
Displaying VFE logs
Log in to the ESXi host through SSH, and enter the /var/log directory.
VFE commands
You can use the CLI on the VFE of the HP 5900v for troubleshooting:
•
dpctl dump-flows
•
dpctl dump-ports
•
dpctl dump-tables
•
dpctl show
For more information about the commands, see System Management > VFE Management in HP 5900v
Help.
8
Problems with VCE installation
Before installing a VCE, make sure the IP address of the VCE does not conflict with other devices in the
network.
Symptom
Start the VM after the VCE is deployed. The system displays "Property IP Address must be configured for
the VM to power on.".
Solution
This symptom occurs because some deployment information is not provided.
To resolve the problem:
1.
Right-click a VM where the VCE resides on the vSphere Client, and select Edit Settings from the
short-cut menu.
2.
Click the Options tab from the menu, and click Properties.
3.
Enter all information as required in the area to the right of the page, and click OK. Then power on
the VM.
4.
If the problem persists, contact HP Support.
9
Problems with licenses
Failure to upload the formal license file
Symptom
Start the VCE, register the product, and upload the license file. The system displays an error message:
"Invalid MAC address. Upload a new license file.".
Solution
To resolve the problem:
1.
Verify that the VCE has been connected to the vCenter Server on the VCE global configuration
page.
2.
If no connection exists between the VCE and vCenter Server, click Connect. The
displayed.
3.
Upload the license file. If the problem persists, the license file is incorrect.
4.
Download the system software image again to obtain the formal license file, and upload the
license file again.
5.
If the problem persists, contact HP Support.
icon is
Failure to configure any function on the HP 5900v
tab
Symptom
Start the VCE, register the license file, and refresh the Port Group page. The system displays an error
message: "Invalid MAC address. Upload a new license file.".
Solution
To resolve the problem:
1.
Verify that the current vCenter Server is the one that can manage the VM where the VCE resides.
Otherwise, perform the following steps on the VCE global configuration page:
a. Uninstall the plug-in and disconnect the VCE from the vCenter Server.
b. Remove the current vCenter Server information.
c. Add the correct vCenter Server.
d. Install the plug-in and connect the VCE to the vCenter Server.
2.
Verify that the VCE has been connected to the vCenter Server on the VCE global configuration
page.
10
3.
If no connection exists between the VCE and vCenter Server, click Connect. The
displayed.
4.
Refresh the configuration page.
5.
If the problem persists, contact HP Support.
icon is
Error message displayed when operations are
performed on the 5900v after VCE deployment
Symptom
The system displays an error message "License error: VCE VM's location changed" when operations are
performed on the 5900v after VCE deployment, even if the VCE is restarted.
Solution
To resolve the problem:
1.
Specify an IP address not used by other VMs on the vCenter Server for the VCE when deploying
the VCE.
2.
If the problem persists, contact HP Support.
VFE batch installation page does not respond
Symptom
1.
Select multiple ESXi hosts where the number of CPUs has exceeded the license limit to install VFEs.
2.
Click Install, and then switch to another page.
The system displays an error message: "License error, exceed authorization number of CPU.".
3.
Return to the VFE installation page. The page does not respond.
Solution
This symptom occurs because you switch to another window when VFEs are being installed or removed
in batches.
To resolve the problem:
1.
Minimize the window and close the error prompt window.
2.
If the problem persists, contact HP Support.
11
Incorrect VFE license state caused by ESXi host CPU
number change
Symptom
Increase the number of CPUs on an ESXi host where the VFE has been licensed. When the CPU number
exceeds the license limit, Authorized
is displayed for the license status of the host. Click the warning
icon, and the system displays "Authorized but the number of CPUs exceeded the limit.".
Solution
To resolve the problem:
1.
Remove the increased CPUs.
Do not increase the number of CPUs on a licensed host. To do so, remove the licenses, increase
CPUs, obtain required licenses, and then license the CPUs.
2.
If the problem persists, contact HP Support.
Failure to register the product after the VCE is
vMotioned to another ESXi host
Symptom
After the VCE is vMotioned to another ESXi host, the license registration process starts again when you
register the product. In this case, the MAC address in the registered license file is different from the MAC
address in the host, and the system displays an error message: "License error. Please re-upload the
license file.".
Solution
To resolve the problem:
1.
Move the VCE to its original host.
2.
Register the product.
3.
Move the VCE to the destination host.
Do not register the product again after the VCE is vMotioned to another host.
4.
If the problem persists, contact HP Support.
12
Problems with VFE installation and removal
Incorrect VDS status after a host is added to the VDS
Symptom
Add a host to the VDS, refresh the VFE configuration page, and view VDS information for the host. The
VDS column displays Handling.
Solution
To resolve the problem:
1.
Wait several seconds and then refresh the page. Processing takes several seconds.
2.
If the problem persists, contact HP Support.
ESXi operating incorrectly
Symptom
The ESXi is operating incorrectly.
Solution
The VFE was not removed correctly. To resolve the problem:
1.
Change the VDS name in the Helium script to the name of the VDS that you have created.
~ # /etc/init.d/helium stop
/opt/hp/sbin/he-destroy.sh
/opt/hp/sbin/ he-unload.sh
/opt/hp/sbin/he-uninstall.sh
2.
Perform the following steps:
a. Execute the net-dvs command in kernel mode to view the current virtual switch.
b. Remove the virtual switch configuration by using these commands:
net-dvs –Y switchname
net-dvs –D –p 3 switchname
net-dvs –D –p 2 switchname
net-dvs –D –p 1 switchname
net-dvs –D –p 0 switchname
net-dvs –d switchname
c. Execute the esxcfg-vswitch –l command in user mode to view the current virtual switch.
d. Remove the virtual switch configuration by using the esxcfg-vswitch –d switchname command.
3.
If the VDS has been removed from the vCenter Server but not from the ESXi, do the following:
13
a. Log in to the ESXi.
b. Click the Configuration tab, select Networking on the left navigation tree, and select vSphere
Distributed Switch in the View field.
c. Click Remove.
4.
If the problem persists, contact HP Support.
Incorrect VFE status when the VFE page is refreshed
Symptom
Display license information for the host. The license information shows that the CPU of the host is under
management. Refresh the page, and the page displays that the host is not licensed.
Solution
To resolve the problem:
1.
Use one of the following methods:
{
{
2.
Method 1:
−
Select the host and click Uninstall.
−
Select the host on the VFE page, and click Install.
Method 2: Select the host and click Install.
If the problem persists, contact HP Support.
Failure to remove a VFE
Symptom
On the vCenter Server corresponding to a VCE, bind an ESXi host to a VDS, and then add the ESXi host
to the vCenter Server corresponding to another VCE. Remove the VFE on the ESXi host on the first VCE.
The system displays an error message: "Fail to uninstall VFE.".
Solution
To resolve the problem:
1.
Remove the ESXi host from the VDS and try again.
2.
If the problem persists, contact HP Support.
14
Failure to uninstall the VFE after a host is removed
from the VDS
Symptom
1.
Remove an ESXi host from a VDS and do not add it to any other VDS.
2.
Remove the VFE on the ESXi host.
The system displays an error message: "Failed to uninstall the VFE.".
Solution
To resolve the problem:
1.
Uninstall the VFE after one hour or restart the ESXi host and uninstall the VFE.
2.
If the problem persists, contact HP Support.
15
Problems with the global configuration page
The global configuration page displays no contents
after the VCE is restarted
Symptom
1.
Restart the VCE, and access the global configuration page.
The global configuration page displays no contents.
2.
Log in to the vCenter Server on the vSphere Client, and access the VDS tab and port group tab.
The VDS tab and port group tab display no contents.
Solution
To resolve the problem:
1.
Log in to the VCE from the VCE console or through SSH.
2.
Verify that the Postgres process is not started by using the ps aux | grep postgres command.
3.
Enter the /var/log/floodlight directory.
4.
Remove the postmaster.pid file from the system.
5.
Restart the VCE.
6.
If the problem persists, contact HP Support.
Failure to configure vCenter Server connection
Symptom
Configure a vCenter Server connection on the VCE global configuration page. The system displays an
error message: "Please configure the controller first."
Solution
Because a VCE connects to the vCenter Server through its own IP address, you must specify an IP address
for the VCE before connecting it to the vCenter Server.
To resolve the problem:
1.
Verify that an IP address has been assigned to the VCE.
2.
Add VCE configuration on the global configuration page.
3.
Add vCenter Server configuration on the global configuration page.
4.
If the problem persists, contact HP Support.
16
Failure to install the VMware plug-in
Symptom
Click Install on the VCE global configuration page to install the VMware plug-in, the system displays an
error message: "Please connect vCenter Server first.".
Solution
To resolve the problem:
1.
Verify that the vCenter Server connection configuration is correct on the global configuration
page.
2.
Click Connect to connect the VCE to the vCenter Server. The
connected.
3.
Click Install to install the plug-in. The
4.
If the problem persists, contact HP Support.
icon is displayed after they are
icon is displayed after the plug-in is successfully installed.
Failure to remove the plug-in
Symptom
Click Uninstall on the VCE global configuration page to remove the plug-in. The system displays an error
message: "Please connect vCenter Server first.".
Solution
To resolve the problem:
1.
Verify that the VCE has been connected to the vCenter Server.
2.
If it is not connected to the vCenter Server, click Connect. The
connected.
3.
Click Install to install the plug-in. The
4.
If the problem persists, contact HP Support.
icon is displayed after they are
icon is displayed after the plug-in is successfully installed.
Failure to delete vCenter Server connection
Symptom
Delete an existing vCenter Server connection on the VCE global configuration page. The system displays
an error message: "vCenter cannot be deleted when it is being connected.".
17
Solution
To resolve the problem:
1.
Verify that the VCE has been disconnected from the vCenter Server.
2.
If it has not been disconnected from the vCenter Server, click Disconnect. The
3.
Click the Delete icon
4.
If the problem persists, contact HP Support.
icon is displayed.
for the target vCenter Server connection.
Failure to obtain the MAC address of the host
where the VCE resides
Symptom
Change the vCenter Server IP address of the host on the global configuration page, and connect to the
vCenter Server again. The system displays an error message: "No host MAC address.".
Solution
To resolve the problem:
1.
Add the ESXi host installed with VCE to the new vCenter Server.
2.
Disconnect the vCenter Server, and connect it again on the global configuration page.
3.
If the problem persists, contact HP Support.
Failure to connect the VCE to the vCenter Server
after the vCenter Server is reinstalled
Symptom
1.
Reinstall the vCenter Server without deleting the vCenter Server information on the VCE global
configuration page.
2.
Configure the vCenter Server with the same IP address, username, and password as you
configured before.
3.
Connect the VCE to the vCenter Server on the VCE global configuration page.
The system displays an error message: "Failed to connect the vCenter Server. Please verify vCenter
Server configurations.".
Solution
To resolve the problem, open the VCE console and perform the following steps:
1.
Execute the cd/opt/hp command.
18
2.
Execute the ./recovery.sh command to restore the default settings of the VCE.
3.
Execute the reboot command to restart the VCE.
4.
Add the vCenter Server on the VCE global configuration page, and connect the VCE to the vCenter
Server.
5.
If the problem persists, contact HP Support.
19
Problems with VMware plug-in
Failure to display the configuration tabs on the
vSphere client
Symptom
The configuration tabs for the HP 5900v cannot be displayed on the vSphere client.
Solution
To resolve the problem:
1.
See "Verifying VMware plug-in " to verify that the VMware plug-in has been successfully installed.
2.
Restart the vSphere client.
3.
Select Plug-in > Plug-in Management from the navigation tree to verify that the plug-in is enabled.
If it is not enabled, right-click the plug-in, and select Enable from the short-cut menu.
4.
If the problem persists, contact HP Support.
Failure to correctly display the 5900v configuration
tabs on the vSphere client
Symptom
Configure VDS or port group. The system displays an error message: "This program cannot display the
webpage.".
Solution
To resolve the problem:
1.
Log in to the VCE global configuration page to verify that the virtual switch where the VCE resides
is operating correctly.
2.
On the vSphere client, select Plug-in > Plug-in Management from the navigation tree to verify that
the plug-in is enabled. If it is not enabled, right-click the plug-in, and select Enable from the short-cut
menu.
3.
Identify whether a proxy server is set in the Internet Options menu. If it is, clear Use a proxy server
for your LAN, and try again.
4.
If the problem persists, contact HP Support.
20
Plug-in display error
Symptom
After the VCE is successfully installed, the VMware plug-in cannot be correctly displayed, and the plug-in
name is displayed as null on the vSphere client.
Solution
This symptom occurs because you remove a VCE from the host without removing the VMware plug-in.
VCE IP addresses are saved in the vCenter Server as plug-in keywords. If the new VCE you deploy uses
the same IP address as the removed one, so the new plug-in cannot be correctly displayed.
To resolve the problem:
1.
Enter https://VC-IPaddress/mob, where VC-IPaddress is the IP address of the vCenter Server.
2.
Enter the username and password for logging in to the vCenter Server.
3.
In the Properties area, click content.
4.
In the Properties area, click ExtensionManager.
5.
Record the keyword of the plug-in, in the format of HP-VCEIP, and click UnregisterExtension in the
Methods area.
6.
Enter the plug-in keyword in the VALUE field, and click Invoke Method.
The execution result will be displayed.
7.
Close the window and display the ExtensionManager page. The VCE plug-in keyword has been
deleted.
8.
Install the plug-in again on the global configuration page, and restart the vSphere Client.
9.
If the problem persists, contact HP Support.
Failure to enter VDS management page
Symptom
Click the name of a datacenter on the vSphere Client, and click the HP 5900v tab. The system displays
an error message: "The datacenter where the VDS resides has been removed.".
Solution
To resolve the problem:
1.
Log in to the VCE and perform the following steps:
a. Execute the cd /opt/hp command.
b. Execute the ./recovery.sh command to restore the default settings of the VCE.
2.
Add the vCenter Server, connect the VCE to the vCenter Server, and install the plug-in again on the
VCE global configuration page.
3.
Restart the vSphere Client.
21
4.
If the problem persists, contact HP Support.
22
Problems with VDS creation and deletion
Failure to create or delete a VDS
Symptom
Create or delete a VDS on the HP 5900v Configuration tab. The system displays an error message:
"Please connect vCenter first.".
Solution
To resolve the problem:
1.
See "Verifying vCenter Server connectivity" to verify the connection between the VCE and vCenter
Server.
2.
If the problem persists, contact HP Support.
Error message displayed when a VDS is created or
deleted
Symptom
Create or delete a VDS. The system displays an error message. However, the VDS has been successfully
created or deleted.
Solution
The message occurs because of network timeout (2 minutes). The VDS you create can operate correctly.
Error message displayed for the host VDS
networking information
Symptom
View VDS networking information for the host. The system displays the following error message:
"No physical adapters from this host are connected to vSphere distributed switch. Virtual machines
running on this host that are connected to this vSphere distributed switch will have some networking
issues. To resolve these issues, add at least one physical adapter to this vSphere distributed switch."
23
Solution
This symptom occurs because no physical ports are elected when a host is added to the VDS.
To resolve the problem:
1.
Right-click the VDS name, and select Manage Hosts from the short-cut menu.
2.
Select the host to be managed, and click Next.
3.
Select physical ports.
4.
If the problem persists, contact HP Support.
Incorrect VDS name on the vSphere Client
Symptom
After a VDS is created, restart the VCE, click the HP 5900v tab, and then click Refresh. The VDS name
changes, but it is not the name of the newly created VDS.
Solution
This symptom occurs because a VCE that uses the same IP address as the new VCE exists in the system,
and a VDS has been created on the existing VCE. When you delete a VCE, you do not delete the VDS
created on the VCE.
To resolve the problem:
1.
Delete the VDS with incorrect name.
If the VDS cannot be deleted, verify that the VDS to be deleted is created on a VCE with the same
version as the current VCE. If it is not, install a VCE whose version is compatible with the VDS, and
then delete the VDS.
2.
Restart the VCE, and display the VDS name.
3.
Repeat Step 1 until a correct VDS name is displayed.
4.
If the problem persists, contact HP Support.
24
Problems with port group
Failure to configure VDP for a port group
Symptom
Click VDP Configuration in the Port Group area on the HP 5900v tab. The system displays an error
message: "IMC connection timed out.".
Solution
To resolve the problem:
1.
See "Verifying IMC server configuration" to verify that a connection has been established between
the VCE and IMC before VDP configuration.
2.
If the problem persists, contact HP Support.
VLAN configuration loss
Symptom
Click VDP Configuration in the Port Group area on the HP 5900v tab. The configured VLAN cannot be
displayed.
Solution
To resolve the problem:
1.
See "Verifying vCenter Server connectivity" to verify that the VCE has been connected to the
vCenter Server.
2.
Configure the VLAN again on the HP 5900v tab.
3.
If the problem persists, contact HP Support.
Failure to restore the port group configuration after
the VCE is rebooted
Symptom
Close the vCenter Server and restart the VCE after a port group is created. The configuration of the port
group is lost.
25
Solution
To resolve the problem:
1.
Restart the vCenter Server first, and then restart the VCE.
2.
Click Refresh to view information about the created port group. If you can see the port group
information, the configuration is restored.
3.
If the problem persists, contact HP Support.
Failure to display VDP information for a port group
Symptom
After VDP configuration for a port group, VSI type can be displayed for the port group. Then, click the VSI
type name, and no VDP information is displayed.
Solution
To resolve the problem:
1.
If the VSI type has been deleted from the IMC server:
a. Configure the VSI type again on the IMC server.
b. Configure VDP information for the port group on the 5900v configuration page, and save the
configuration.
Or, if the IP address of the IMC server has been changed:
a. Enter the VCE global configuration page.
b. Remove the IMC server configuration, and add correct IMC server login information.
c. Configure VDP information for the port group on the 5900v configuration page, and save the
configuration.
2.
If the problem persists, contact HP Support.
Failure to automatically refresh the number of port
groups on the VDS page
Symptom
1.
Create a VDS.
2.
Create two port groups on the VDS.
3.
Return to the VDS page, and the number of port groups cannot be automatically refreshed.
26
Solution
This symptom occurs because the system does not provide the automatic refresh function to avoid
affecting smooth page switching.
To resolve the problem:
1.
Click Refresh on the page.
2.
If the problem persists, contact HP Support.
Failure to automatically refresh the port group of a
VDS when the VDS changes
Symptom
Do the following, and the port group for the VDS is not automatically created:
•
Create a VDS.
•
Add a port group to the VDS.
•
Remove the VDS.
•
Create a new VDS.
Solution
To resolve the problem:
1.
Click Refresh on the page.
2.
If the problem persists, contact HP Support.
Failure to the restore the VFE configuration after the
VCE is restarted
Symptom
Restart the VCE, and view the port configurations in the Port Group area on the HP 5900v tab. The system
does not display the port configurations.
Solution
This symptom occurs because the vCenter Server is disabled or the network is unreachable when you
restart the VCE.
To resolve the problem:
1.
Restart the VCE after the vCenter Server operates correctly.
2.
If the problem persists, contact HP Support.
27
Any port group to which online VSIs belong can be
removed from the VMware vSphere Client
Symptom
1.
Bind an ESXi host to a VDS, and connect 10 vNICs on the host to the VDS.
2.
Disconnect the ESXi host from the VMware vSphere Client.
3.
Remove the ESXi host.
4.
Add the ESXi host to the vCenter Server again, and bind the ESXi host to the VDS.
5.
View the 10 vNICs on the VDS configuration page. The page does not display the vNICs,
although they are operating correctly.
6.
Remove any one of the port groups to which the 10 vNICs were added, even if the port group has
online VSIs. The operation succeeds.
Solution
To resolve the problem:
1.
Add the 10 vNICs to the port groups again.
2.
If the problem persists, contact HP Support.
28
Problems with traffic forwarding
Communication failure between VMs even if the
vNICs are bound to a port group
Symptom
The vNICs of VMs have been added to the port groups. Test connectivity between the VMs with a virtual
ping tool, and they cannot communicate with each other.
Solution
To resolve the problem:
1.
Verify the VLAN and VDP configurations for the port group on the Port Group Management >
VLAN Configuration and Port Group Management > EVB Configuration pages.
2.
Identify whether the VLAN configured for the port group is in the VLAN Trunk list of the uplink port.
If they are not, add the VLAN to the list.
3.
Verify the VDP status:
a. Click the port group name on the HP Port Group tab.
The VDP State column displays the VDP status of the vNICs of the port group. WAIT_SYS_CMD
indicates that the VDP is operating correctly. INIT indicates that the VDP is operating
incorrectly.
b. Execute the display evb vsi command on the EVB switch to display VSI information.
<Sysname> display evb vsi
Status: A -- Association, P -- Pre-association
VSI
VTID
interface
Type
Instance
Status
version
ID
SCH-AGG100:1.0
5
1
8635f3726e2807ac14f...
A
SCH-AGG100:1.1
5
1
fb3cf4c517c9bfdf44d...
A
SCH-AGG100:1.2
5
1
d63f84c0f08f650c5d0...
A
The number of VSIs must be the same as the number of vNICs configured with VDP on the VDS.
If the status of a VSI is A, it indicates that the VSI is operating correctly. If the number of VSIs
is smaller than the number of vNICs configured with VDP, or the status of a VSI is P, it indicates
that the vNIC corresponding to the VSI does not get online.
Incorrect operation of the VDP might be caused by network flapping. To resolve the problem,
add the vNIC to the port group again.
4.
See "Verifying link aggregation configuration" to verify link aggregation information. If the port
that connects the EVB switch to the server is not added to a correct port group, packets might be
sent through another port according to the load balancing algorithm.
5.
Execute the dpctl dump-tables command to display the number of flow tables on a VFE:
~ # dpctl dump-tables
0x768a5defd040e902
29
Flowtable stats:
active_count = 2.
If the maximum number of flow tables on a VFE is reached, no new flow table can be created, and
VM communications might be affected. You can wait for flow table aging, or remove vNICs not in
use from the VDS to remove redundant flow tables.
6.
If the problem persists, contact HP Support.
Failure to remove part of broadcast traffic
information in the flow table
Symptom
Restart the VCE when there is broadcast traffic, and unbind a vNIC from the VDS. Then execute the dpctl
dump-flows command on the VFE to display flow table information. Part of broadcast traffic information
still exists in the flow table.
Solution
This symptom occurs because flow table information before the VCE is restarted cannot be saved on the
VFE after the VCE is restarted. When you unbind a vNIC, the corresponding flow table on the VFE
cannot be removed.
To resolve the problem:
1.
Wait until the flow table ages out, because the flow table on the VFE has an aging timer.
2.
If the problem persists, contact HP Support.
Incorrect host information caused by changing the
IP address of a host in VDS
Symptom
Change the IP address of a host, and display all hosts on the VDS. The system displays an error message:
"Incomplete host data.".
Solution
This symptom occurs because you change the IP address of a host when the host has been added to a
VDS.
To resolve the problem:
1.
Remove the host from the VDS, and add it to the VDS again.
Or restart the VCE.
2.
If the problem persists, contact HP Support.
30
Problems with EVB
VSIs cannot get online after the EVB port on the
physical switch is manually brought up
Symptom
Enable EVB on the port or aggregate interface connecting the physical switch to the ESXi host. After the
VSIs have been registered on the VM, shut down the port or aggregate interface on the physical switch
by using the shutdown command. When the VSIs time out and get offline, one of the following failures
occurs:
•
Bring up the port on the physical switch, and only some VSIs can get online.
•
Bring up the aggregate interface on the physical switch, and no registered VSIs can get online.
Solution
By default, STP is enabled on the physical switch port. When the port state changes from down to up, the
port performs STP negotiation with the remote port. The physical network card interface on the ESXi host
does not support STP, so the negotiation fails. During the negotiation period, the STP port is in discarding
state and does not accept user packets, so the VSIs on the VM cannot be registered.
To resolve the problem:
1.
Configure the port or aggregate interface connecting the physical switch to the ESXi host as an STP
edge port by executing the stp edged-port command in Layer 2 Ethernet interface view or Layer 2
aggregate interface view.
2.
If the problem persists, contact HP Support.
The VSI gets offline when you migrate the storages
of two VMs at the same time
Symptom
1.
Bind the vNICs of two VMs to a port group.
2.
After the VSI gets online, migrate the storages of the two VMs at the same time.
The VSI gets offline.
Solution
To resolve the problem:
1.
Migrate the VMs one by one.
31
2.
If the problem persists, contact HP Support.
32
Contacting HP Support
Contacting HP Support
If you cannot solve a problem by using the troubleshooting suggestions in this guide, contact HP Support
for help and further instructions. Before you call, have the following information ready to help your
service provider assist you as quickly as possible:
•
Software version of the HP 5900v that you are using
•
VMware vSphere version, including ESXi version and vCenter Server version
•
Contact phone number
•
Brief description of the problem
•
Brief description of the operations you have performed to resolve the problem
•
Information gathered through the operations described in "Gathering information."
Gathering information
Gathering VCE information
1.
Select Log Collection from the navigation tree on the global configuration page.
2.
Select Collect System Logs or Collect Operation Logs.
3.
Click Collect.
Figure 7 Gathering VCE logs
Gathering VFE information
Log in to the ESXi host through SSH, and then execute the hvsw-support command to save the VFE
information to the specified file:
~ # hvsw-support
Log is collecting, please wait...
hvsw-support/
hvsw-support/hvsw-syslog.log
hvsw-support/hvsw-vmkernel.log
33
hvsw-support/syslog.0.gz
hvsw-support/syslog.7.gz
hvsw-support/syslog.6.gz
hvsw-support/syslog.5.gz
hvsw-support/syslog.4.gz
hvsw-support/syslog.3.gz
hvsw-support/syslog.2.gz
hvsw-support/syslog.1.gz
hvsw-support/vmkernel.0.gz
hvsw-support/vmkernel.7.gz
hvsw-support/vmkernel.6.gz
hvsw-support/vmkernel.5.gz
hvsw-support/vmkernel.4.gz
hvsw-support/vmkernel.3.gz
hvsw-support/vmkernel.2.gz
hvsw-support/vmkernel.1.gz
Generating hvsw-support-2012-03-17_00:51:08.tar.gz
Table 1 Command output
Field
Description
hvsw-syslog.log
Current system logs of the OpenFlow data plane agent.
hvsw-vmkernel.log
Current system logs of the OpenFlow data plane kernel.
syslog.*.gz
History system logs of the OpenFlow data plane agent.
They are saved in the format of .gz. An asterisk
represents the number of the file.
vmkernel.*.gz
History system logs of the OpenFlow data plane kernel.
They are saved in the format of .gz. An asterisk
represents the number of the file.
hvsw-support-2012-03-17_00:51:08.tar.gz
Log file that contains all OpenFlow data plane logs
during this operation. 2012-03-17_00:51:08
represents the log collection time.
Gathering ESXi server information
1.
Launch the vSphere Client, and select an ESXi host from the navigation tree.
2.
Click the Configuration tab, as shown in Figure 8.
34
Figure 8 Displaying ESXi server information
Gathering IMC information
Gathering IMC version information
1.
Log in to IMC.
2.
Click About on the upper right corner, as shown in Figure 9.
The About the HP Intelligent Management Center page appears.
35
Figure 9 Displaying IMC version
Gathering device management information
Select Resource > Device View.
36
Figure 10 Displaying device management information
Gathering EVB switch information
Access the CLI on the EVB switch, and execute the display diagnostic-information command.
37