Forum Discussion

MSIMON007_64454's avatar
MSIMON007_64454
Icon for Nimbostratus rankNimbostratus
Jul 21, 2009

Updating Object status

A couple of questions:

 

1.)If we add new VS's, pools, and/or pool members to our F5 should they automatically be discovered by the MP? During testing we added a new pool to the f5, waited 24hrs and the pool never showed up in the SCOM ui. After I ran a discovery the new pool was visible??

 

Is this the expected behavior?

 

 

2.)I failed a pool member. Almost immediately the LTM shows it marked down, but the scom UI shows the pool member with a healthy status. Only after rediscovering the LTM does the status change to red. When I bring the member back online, the SCOM UI still shows the pool member as red until rediscovery of the LTM.

 

 

3.)Also, when I double click an alert "F5.LTM.PoolMember.Monitor.AggregateMonitor" in the SCOM UI I receive the following message "Value cannot be null. Parameter name: input"

 

Note: The following information was gathered when the operation was attempted. The information may appear cryptic but provides context for the error. The application will continue to run.

 

 

System.ArgumentNullException: Value cannot be null.

 

Parameter name: input

 

at System.Text.RegularExpressions.Regex.Replace(String input, String replacement)

 

at Microsoft.EnterpriseManagement.Mom.UI.AlertPropertyDialog.<>c__DisplayClass2.b__0(Object , ConsoleJobEventArgs )

 

at Microsoft.EnterpriseManagement.Mom.Internal.UI.Console.ConsoleJobExceptionHandler.ExecuteJob(IComponent component, EventHandler`1 job, Object sender, ConsoleJobEventArgs args)

 

management
microsoft
scom
  • Dave_Ruddell_79's avatar
    Dave_Ruddell_79
    Historic F5 Account
    Jul 28, 2009
    So to answer 1 & 2, no, this is not the expected behavior. You should be seeing the configuration changes show up in Operations Manager within 30 seconds to a minute. Typically you will have to manually refresh (right-click -> refresh), but the objects should still change.

     

     

    As for 3, I've personally never seen this message and I am unsure what is causing it. I'd like to start trying to resolve these 3 issues, but I will need some more information from you. It looks like your other posting in the support forum may also be related, so first thing we'll need is the complete F5 Monitoring Log. You can send it in any format, but it might be easier as a comma delineated file. Also, if you Click here you can see the other trouble-shooting directions. Follow the two different articles on that page and zip up all 3 files and either post them back here, or email them to ManagementPack(at)f5.com.

     

     

    Thank you,

     

    -Dave
  • Dave_Ruddell_79's avatar
    Dave_Ruddell_79
    Historic F5 Account
    Aug 04, 2009
    Michael,

     

    It would appear that the issues you are hitting with 1 & 2 are actually caused because you are using version 1.0.0.392 of our management pack software. These have been resolved in releases since then, and I would highly recommend that you uninstall your existing copy of the F5 Networks Management Pack and install the latest version. You can find the latest version (1.2.0.579) here: Click here.

     

     

    I hope this resolves the issues you are having with 1 & 2. As far as 3 is concerned, it would appear that you found a possible bug in the SCOM UI, so we have recorded this issue in our bug tracking system and will pass it along to the Operations Manager team.

     

     

    Thanks for your patience.

     

    -Dave