locked
The agent computer IP is not changing in SCOM console, after the agent computer has been migrated to new IP... RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    In our environment, we have cloud platform and we have migrated some amount of Unix/Linux servers to cloud platform from On-prem

    The issue is, In SCOM console the Unix/Linux agent computers IPs are still showing as On-prem IP.

    Built the separate management servers and Created the separate resource pool for Cloud platform.

    SCOM agents have been configured to monitor the cloud migrated server both Windows and Unix/Linux computers.

    Unix/Linux agent computers having the issue that Cloud platform IPs are not showing in SCOM console still showing as On-prem IPs

     

    Thanks, Shiva ravichandran.

    Friday, February 22, 2019 6:50 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    Finally it's working ... removed from SCOM and re-added....

    Thanks, Shiva ravichandran.

    Tuesday, March 26, 2019 8:16 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    How long did you wait?

    Cheers

    Sam (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" wherever applicable. Thanks!) Blog:AnalyticOps Insights Twitter:Sameer Mhaisekar

    Friday, February 22, 2019 7:01 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    It's been several days....

    Thanks, Shiva ravichandran.

    Friday, February 22, 2019 7:02 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    For most of the servers it's looking good, the issue is for some of the servers

    Thanks, Shiva ravichandran.

    Friday, February 22, 2019 7:06 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    You should try flushing the console cache. Apart from IP mismatch, is there any other consequence of this? Like errors, grey agents, etc?

    Cheers

    Sam (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" wherever applicable. Thanks!) Blog:AnalyticOps Insights Twitter:Sameer Mhaisekar

    Friday, February 22, 2019 7:07 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I couldn't see like any other error or grayed agents... I'll try the console cache flush and update the status...

    Thanks, Shiva ravichandran.

    Friday, February 22, 2019 7:15 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    No Luck... after cleared the cache also the IPs are still showing as same....

    Thanks, Shiva ravichandran.

    Friday, February 22, 2019 8:15 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Have you noticed any pattern on affected servers like all are in same location, same resource group etc. 

    Give a try to restart Health service on all VMs and all SCOM MS that are in resource pool. <<<Built the separate management servers and Created the separate resource pool for Cloud platform.>>>


     

    Cheers, Gourav Please remember to mark the replies as answers if it helped.

    Saturday, February 23, 2019 2:51 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    This is there in Azure migrated servers that are placed in SCOM monitoring 

    Separate management server has been built and separate resource pool also created already...

    The issue is resolving only when we removing and re-adding the particular server in SCOM...

    Thanks, Shiva ravichandran.

    Tuesday, February 26, 2019 3:21 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    I can understand how troublesome it can be. Just to be clear, do the servers that do not update the IP's go grey? And how did you clear the console cache?

    Cheers

    Sam (Please take a moment to "Vote as Helpful" and/or "Mark as Answer" wherever applicable. Thanks!) Blog:AnalyticOps Insights Twitter:Sameer Mhaisekar

    Tuesday, February 26, 2019 3:30 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    No, those servers are in healthy state only - Green

    I've cleared the console cache using -  "D:\Program Files\Microsoft System Center 2016\Operations Manager\Console\Microsoft.EnterpriseManagement.Monitoring.Console.exe" /clearcache

    Thanks, Shiva ravichandran.

    Tuesday, February 26, 2019 4:47 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Shiva,

    Clear cache of Agents. take a look to following link

    https://social.technet.microsoft.com/Forums/en-US/5c8ae68d-678a-42e6-b08f-a0386ee89ae0/scom-performance-data-for-one-server-does-not-present?forum=operationsmanagergeneral

    Regards,

    Monday, March 18, 2019 1:08 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Finally it's working ... removed from SCOM and re-added....

    Thanks, Shiva ravichandran.

    Tuesday, March 26, 2019 8:16 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I found you can put them in maintenance mode and then back out and the new ip shows up
    Wednesday, January 29, 2020 3:05 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hey what is solution for this apart from removing and re-adding ? i still see same issue with IP changed server Linux windows are working fine 

    thanks,

    Yasar

    Friday, August 21, 2020 10:47 PM