Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Log & Event Manager (LEM) > New LEM hostname is appearing as a non-agent node and the appliance name still displays as swi-lem in the Web Console

New LEM hostname is appearing as a non-agent node and the appliance name still displays as swi-lem in the Web Console

Created by Jason Dee, last modified by MindTouch on Jun 23, 2016

Views: 1,025 Votes: 1 Revisions: 4

Overview

After deploying LEM and changing the hostname, you notice the follow:

  • swi-lem is still the one and only appliance listed under Manage > Appliances and it would not let you change the name manually.
  • All of your incoming events show swi-lem in their Manager fields.
  • You may have a new non-agent node under Manage > Nodes that shows the new hostname for your LEM.

Environment

All LEM versions

Cause 

Certain system files were not updated with the new hostname properly when the hostname was changed. This is supposed to be an automated process.

Resolution

Contact SolarWinds Support to resolve this.

 

Last modified

Tags

Classifications

Public