Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Skyline Collector Loses Network Configuration After Reboot (76400)

Last Updated: 1/7/2020Categories: TroubleshootingTotal Views: 6807Language:
Chinese (Simplified)JapaneseEnglish

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

After upgrading, or restarting, the Skyline Collector virtual appliance, you are unable to reach the Skyline Collector user interface via a web browser. Additionally, the Skyline Collector appears in a state other than Healthy within Skyline Advisor Collector Health Details page. Finally, the following message is displayed on the Skyline Collector virtual appliance console.

Impact / Risks

This issue could impact the following versions of Skyline Collector after restarting, or upgrading, the Skyline Collector virtual appliance.

Skyline Collector version 2.1

Skyline Collector version 2.2

Skyline Collector version 2.3

Resolution

Please follow the steps in the workaround to resolve this issue until a permanent resolution can be provided.

Workaround

Complete these steps to restore networking to the Skyline Collector virtual appliance.

Within the vSphere Client, open the console for the Skyline Collector virtual appliance virtual machine.

Log in to the Skyline Collector virtual appliance using the 'root' account.

First, restart the networkd service. Restarting the networkd service usually resolves this issue. Multiple restarts of the networkd service may be needed to resolve the issue.  Run the following command to restart the networkd service: systemctl restart systemd-networkd

Sometimes, restarting the networkd service results in a loss of network configuration. If this occurs, run the following command to reconfigure network details for the Skyline ColIector: /opt/vmware/share/vami/vami_config_net

Confirm that the Skyline Collector is available on the network. Try accessing the Skyline Collector user interface via the fully-qualified domain name (FQDN), or IP address within a web browser.

NOTE: The resolution is temporary, as any subsequent restarts of the Skyline Collector virtual appliance could cause the issue to occur again.

Related Information

If your Skyline Collector auto-upgraded to version 2.3.0.1 and is in an Inactive state, please see VMware Knowledge Base Article 76651.

If you are unable to resolve the issue using the steps provided above, please start a discussion in the Skyline Community. A VMware Technical Support Engineer moderating that Community will assist you with resolving the issue. If you are a Premier Support customer, please contact your Support Account Manager.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
Application Remote Collector が再起動後、7.5 から 8.0 に自動的にアップグレードされる (76412)

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Skyline Collector Appliance 2.x

Take Our Survey

Support Assistant