Last updated on: 2023-03-14 02:16:22.
Troubleshooting and support tips and tricks guide¶
The following topic discusses tips and tricks for troubleshooting deployments, and submitting issues and enhancements to the F5 VNFM team.
|Error type||Recommended resolution|
|Can’t load license, may not be operational.||Indicates an expired BIG-IQ license and/or pool licenses for your BIG-IP VEs. Using the floating IP (OpenStack) assigned to your BIG-IQ, log into your BIG-IQ, click the Reactivate twice.blade, and then click|
|Expiring VIM passwords||If you have running VNFM deployments, and your VIM password is expiring and you must change it, then you must first change the related VNFM secret, BEFORE executing any workflows. F5 recommends changing the VNFM secret, and then changing the VIM password to match. Related secrets include vsphere_password for VMware and keystone_password for OpenStack. If you do NOT change the related VNFM secret first BEFORE executing workflows, then your VNF Manager will become non-responsive.|
|Failed inputs file upload||Inputs file is YAML, and tabs are not valid characters for YAML. Change all tabs to spaces.|
|Detect when and what caused a heal and scale workflow.||You can receive Nagios logs for heal and scale events in VNF Manager. In the VNF Manager console, click the Deployments Events/Logs pane (add events/logs widget). You can also pull these heal and scale Nagios log entries using the VNFM API.that was healed or scaled, and then scroll to the|
|A node (primary or secondary) in a VNF group fails to obtain a license.||NTP server fails to synchronize your BIG-IP due to network congestion, resulting in your BIG-IP failing to obtain a license. This is a known issue with BIG-IP. To avoid this issue, use an NTP server that is local to your management network. Or, you can uninstall and reinstall the blueprint.|
||This appears in the CIDR notation on a later deployment stage; node cgnat_config. To avoid this error, you MUST specify the IP range using two IP addresses separated by a dash and no spaces (for example, ‘192.168.1.100-192.168.1.150’).|
|After changing password using the console, error message:
||To resolve this error on any version of VNFM, run the following:
|For vSphere v6.5 and earlier deploying image from your Content Library, Deployed an OVF with NVRAM is not supported error message.||Received when deploying an image uploaded to your Content Library. Edit the
Submit issues and enhancement requests¶
Use the VNFM public GitHub repo to submit issues and request enhancements:
- Point your browser to https://github.com/F5Networks/f5-nfv-solutions.
- Click the Issues tab, and then click New Issue.
- Select one of the following, and then click Get Started:
- Bug report
- Feature request
- Enter a Title, and in the text box enter a description and include the following information:
- VNFM version used
- Hypervisor version used
- Plugin versions used (if different from VNFM version)
- Blueprint type used
- Click Submit new issue.