DX Infrastructure Manager

Expand all | Collapse all

VMWare Probe Configuration Problem

Stephen Danseglio03-15-2017 01:07 PM

  • 1.  VMWare Probe Configuration Problem

    Posted 03-14-2017 03:34 PM

    We have deployed the vmware probe in our testing lab and are trying to configure it.  When we select the "configuration" option while in the Admin console.  The probe opens in the configuration screen; has a lock on it and says "Resource is in read only mode."  Is this the reason why we are not able to deploy / query our vCenters?  (We currently have SysEDGE AIMs installed on these vCenters and they populate the guest info fine).

     

    If this is the problem; has anyone determine how to remove the "resource is in read only mode" message?  All our licenses don't expire until Jun 2018.

     

    Thanks,

     

    RJ Jones



  • 2.  Re: VMWare Probe Configuration Problem

    Posted 03-14-2017 06:24 PM

    Could you please post a screen shot of the error please? This could be a issue with the probe security settings 



  • 3.  Re: VMWare Probe Configuration Problem

    Broadcom Employee
    Posted 03-14-2017 06:56 PM

    Resource = an item on the vm side, so perhaps the read only just means it can be monitored but not changed. In general it is better to use templates. Enabling items under Resources sets a static monitor and Templates are dynamic. This can be important since vm farms often change and as that happens you can end up with a lot of alarms for failures to monitor a resource that is no longer there but set under a static monitor.

     

    Current version of the probe is 6.82 released middle last month.



  • 4.  Re: VMWare Probe Configuration Problem

    Posted 03-15-2017 12:02 PM

    Hey David, thanks for responding.  You are probably correct about the resource being set in "read only mode" on our vcenters; but at this time we are not connecting to the vcenters and still getting the "resource is in read only mode" response.  Please see the screen shot below.

     

    Thanks,

     

    RJ



  • 5.  Re: VMWare Probe Configuration Problem

    Posted 03-15-2017 12:00 PM

    Thanks for your response.  Here is a screen shot of the probe.   Previously we had tried to configure it to talk to one of our vcenters;; but removed the configuration when we started to see some memory issues.

     



  • 6.  Re: VMWare Probe Configuration Problem

    Posted 03-15-2017 12:12 PM

    Robert,

     

    Have you tried configured in IM.

     

    Please change the below too and try once.

    Increase java memory for the vmware probe, for example using raw Configure increase the min/max memory values to:

    <startup>
    options = -Xms2048m -Xmx4096m -Duser.language=en -Duser.country=US
    </startup>

     

    Thanks,



  • 7.  Re: VMWare Probe Configuration Problem

    Posted 03-15-2017 01:02 PM

    Made the change recommended.  Will see what happens.

     

    Thank you.



  • 8.  Re: VMWare Probe Configuration Problem

    Broadcom Employee
    Posted 03-15-2017 12:41 PM

    So that could be that the probe needs 'admin' privilege.

    Have you checked the security settings for vmware under "Probe Security"

    It should display these settings.

     

     



  • 9.  Re: VMWare Probe Configuration Problem

    Posted 03-15-2017 01:03 PM

    Stephen,

     

    Where is this configuration located.  I can't find it.

     

    RJ



  • 10.  Re: VMWare Probe Configuration Problem

    Broadcom Employee
    Posted 03-15-2017 01:07 PM

    Admin Console

     



  • 11.  Re: VMWare Probe Configuration Problem

    Posted 03-15-2017 01:18 PM

    Ah so.  Got it.  Mine is setup for Admin access.  Should it be higher?   (I see suprt as the next level).

     

    After making the change; should I restart the probe?

     

    Thanks again for your help.

     

    RJ



  • 12.  Re: VMWare Probe Configuration Problem

    Broadcom Employee
    Posted 03-15-2017 01:31 PM

    Then that should be fine. I would try a cold start of the vmware probe. Deactivate it, wait for the port and pid to disappear, then Activate it. I just upgraded to the same version 6.82 and I don't see that message. You might also want to set loglevel to 5 and logsize to 30000 before you cold start. See if you see the same message in the log then copy and paste the message with a little bit of the 'before and after' log entries.



  • 13.  Re: VMWare Probe Configuration Problem

    Posted 03-15-2017 01:35 PM

    Alright!  I  have deactivated.  Will let you know what happens after the cold start.

     

    Thanks.

     

    RJ



  • 14.  Re: VMWare Probe Configuration Problem

    Posted 03-16-2017 10:00 AM

    Made the change and the probe is still listed as "Resource is in read only mode."

     

    Here is the info from the logs you mentioned to include.

     

    RJ

     

          Mar 15 13:18:06:478 [main, vmware] ****************[ Starting ]**************** Mar 15 13:18:06:478 [main, vmware] 6.82 Mar 15 13:32:59:358 [main, vmware] ****************[ Stopped ]**************** Mar 15 13:34:43:662 [main, vmware] ****************[ Booting ]**************** Mar 15 13:34:43:663 [main, vmware] version 6.82 Mar 15 13:34:44:856 [main, vmware] ****************[ Starting ]**************** Mar 15 13:34:44:856 [main, vmware] 6.82 Mar 15 15:28:06:748 [main, vmware] ****************[ Stopped ]**************** Mar 16 09:49:48:866 [main, vmware] Services: Registered internal probe services are: Mar 16 09:49:48:868 [main, vmware] Services: com.nimsoft.pf.common.ctd.service.IGraphProviderService -> com.nimsoft.probe.common.ctd.service.common.DefaultGraphProviderService Mar 16 09:49:48:869 [main, vmware] Services: com.nimsoft.pf.common.graph.GraphFactory -> com.nimsoft.vm.VmGraphFactory Mar 16 09:49:48:869 [main, vmware] Services: com.nimsoft.pf.common.service.IGraphDiagnosticService -> com.nimsoft.pf.common.service.dflt.DefaultGraphDiagnosticService Mar 16 09:49:48:869 [main, vmware] Services: com.nimsoft.pf.common.service.IMetricInstanceIdFactoryService -> com.nimsoft.pf.common.service.dflt.DefaultInstanceUUIDMetricInstanceIdFactoryService Mar 16 09:49:48:869 [main, vmware] Services: com.nimsoft.pf.common.service.INimRequestFactoryService -> com.nimsoft.pf.common.service.dflt.DefaultNimRequestFactoryService Mar 16 09:49:48:869 [main, vmware] Services: com.nimsoft.pf.common.service.IPerformanceDiagnosticService -> com.nimsoft.pf.common.service.dflt.DefaultPerformanceDiagnosticService Mar 16 09:49:48:869 [main, vmware] Services: com.nimsoft.pf.common.service.IRunningProbeInformationService -> com.nimsoft.pf.common.service.dflt.DefaultRunningProbeInformationService Mar 16 09:49:48:869 [main, vmware] Services: com.nimsoft.pf.common.service.IWorkingDirectoryService -> com.nimsoft.pf.common.service.dflt.DefaultWorkingDirectoryService Mar 16 09:49:48:869 [main, vmware] Services: com.nimsoft.probe.common.bc.apply.IAlarmInjectorService -> com.nimsoft.probe.common.ctd.DefaultAlarmInjectionService Mar 16 09:49:48:869 [main, vmware] Services: com.nimsoft.probe.common.bc.service.IBcEngineFactoryService -> com.nimsoft.probe.common.bc.service.common.DefaultBcEngineFactoryService Mar 16 09:49:48:869 [main, vmware] Services: com.nimsoft.probe.common.bc.service.IBcEngineService -> com.nimsoft.probe.common.bc.engine.DefaultBcEngine Mar 16 09:49:48:869 [main, vmware] Services: com.nimsoft.probe.common.bc.service.IBcStateService -> com.nimsoft.probe.common.bc.BcServiceFactory$BcStateServiceInstance Mar 16 09:49:48:870 [main, vmware] Services: com.nimsoft.probe.common.cipher.IProbeCipherService -> com.nimsoft.probe.common.cipher.DefaultProbeCipherService Mar 16 09:49:48:870 [main, vmware] Services: com.nimsoft.probe.common.cipher.IProbeCipherUtf8ConfigurationUpdateService -> com.nimsoft.probe.common.cipher.LegacyIsoCipherUtf8ConfigurationUpdateService Mar 16 09:49:48:870 [main, vmware] Services: com.nimsoft.probe.common.ctd.IProbeGraphProvider -> com.nimsoft.probe.application.vmware.VmwareCallbackHandler Mar 16 09:49:48:870 [main, vmware] Services: com.nimsoft.probe.common.ctd.ProfileDefinitionsCreator -> com.nimsoft.probe.common.ctd.ProfileDefinitionsCreator Mar 16 09:49:48:870 [main, vmware] Services: com.nimsoft.probe.common.disco.service.IDiscoveryPublisherEngineService -> com.nimsoft.probe.common.disco.engine.DefaultDiscoveryPublisherEngineService Mar 16 09:49:48:870 [main, vmware] Services: com.nimsoft.probe.common.disco.service.IDiscoveryPublisherFactoryService -> com.nimsoft.probe.application.vmware.disco.service.VmwareDiscoveryPublisherFactoryService Mar 16 09:49:48:870 [main, vmware] Services: com.nimsoft.probe.common.disco.service.IDiscoveryPublisherQueueService -> com.nimsoft.probe.common.disco.service.common.DefaultDiscoveryPublisherQueueService Mar 16 09:49:48:870 [main, vmware] Services: com.nimsoft.probe.common.disco.service.IDiscoveryPublisherService -> com.nimsoft.probe.common.disco.service.common.DefaultDiscoveryPublisherService Mar 16 09:49:48:870 [main, vmware] Services: com.nimsoft.probe.common.disco.service.IDiscoveryPublisherStateService -> com.nimsoft.probe.common.disco.service.common.DefaultDiscoveryPublisherStateService Mar 16 09:49:48:870 [main, vmware] Services: com.nimsoft.probe.common.disco.service.IDiscoveryWorkingDirectoryService -> com.nimsoft.probe.common.disco.service.common.DefaultDiscoveryWorkingDirectoryService Mar 16 09:49:48:871 [main, vmware] Services: com.nimsoft.probe.common.service.IBaseProbeConfigOptionsService -> com.nimsoft.probe.application.vmware.VmwareConfigOptionsService Mar 16 09:49:48:871 [main, vmware] Services: com.nimsoft.probe.common.service.IBaseProbeService -> com.nimsoft.probe.application.vmware.VmwareProbe Mar 16 09:49:48:871 [main, vmware] Services: com.nimsoft.probe.common.service.IGeneralStateService -> com.nimsoft.probe.common.service.DefaultGeneralStateService Mar 16 09:49:48:871 [main, vmware] Services: com.nimsoft.probe.common.service.ITypeNameService -> com.nimsoft.probe.application.vmware.cfg.VmwareTypeNameService Mar 16 09:49:48:871 [main, vmware] Services: com.nimsoft.vm.IProbeResourceProvider -> com.nimsoft.probe.application.vmware.VmwareProbe Mar 16 09:49:48:871 [main, vmware] Services: com.nimsoft.vm.sender.Sender -> com.nimsoft.vm.sender.BulkSender Mar 16 09:49:48:875 [main, vmware] ****************[ Booting ]**************** Mar 16 09:49:48:875 [main, vmware] version 6.82 Mar 16 09:49:50:110 [main, vmware] nimsoft-SDK 8.5.0, nimclient-core 1.6.7, commons-io 2.4, commons-lang 2.4, log4j-api 2.2, log4j-slf4j-impl 2.2, jcl-over-slf4j 1.7.12, jackson-module-jaxb-annotations 2.6.3, ctd-transform 2.9.8, commons-logging 1.1.3, jettison 1.3.3, log4j-core 2.2, commons-csv 1.1, javassist 3.16.1-GA, template-applier 2.0.5, concurrentlinkedhashmap-lru 1.4.1, log4j-1.2-api 2.2, joda-time 2.3, commons-collections 3.2.2, vm 2.5.7, httpcore 4.3.2, commons-configuration 1.6, snappy-java 1.1.0.1, jackson-module-afterburner 2.6.3, jackson-annotations 2.6.3, pf-common 2.8.1, slf4j-simple 1.6.2, opencsv 2.3, jackson-core 2.6.3, bootstrap 1.0.4, vmware-probe 6.8.2, slf4j-api 1.7.12, nimclient-model 1.6.7, commons-codec 1.6, jackson-datatype-json-org 2.6.3, json 20090211_1, jul-to-slf4j 1.7.12, orientdb-core 2.1.8, log4j 1.2.17, nimpool 1.1.6, hibernate-jpa-2.0-api 1.0.0.Final, jackson-databind 2.6.3, cm_common 7.6.1, orientdb-object 2.1.8, template-migrator 2.0.5, quartz 2.2.1, derived-metrics-co e 1.0.7, template-creator 2.0.5, ctdgraph 2.8.1, mapdb 1.0.7, derived-metrics-config 1.0.7, commons-lang3 3.3.2, guava 18.0, cloning 1.9.0, httpclient 4.3.5, zip4j 1.3.2 Mar 16 09:49:50:112 [main, vmware] DefaultBcEngine.start: Checking to see if bulk configuration is enabled. Mar 16 09:49:50:112 [main, vmware] DefaultBcEngine.start: Bulk configuration is disabled. Mar 16 09:49:50:113 [main, vmware] DefaultDiscoveryPublisherEngineService.start: Discovery publishing is running in PUBLISH_INDIVIDUAL_DEVICE_UPDATE_GRAPHS mode. Mar 16 09:49:50:127 [Discovery Publisher(Managed - 0), vmware] DiscoveryPublisherEngineThread.run: Starting Discovery Publisher which will run continuously. Mar 16 09:49:50:144 [main, vmware] ****************[ Starting ]**************** Mar 16 09:49:50:144 [main, vmware] 6.82 Mar 16 09:49:50:144 [main, vmware] CA Technologies Mar 16 09:49:50:177 [main, vmware] port=48033 Mar 16 09:49:50:375 [main, vmware] Login to NimBUS is OK Mar 16 09:49:50:404 [main, vmware] idname.cfg could not be loaded. No vmware.cfg update required Mar 16 09:49:50:565 [main, vmware] (90) Configuration error, java.io.FileNotFoundException: idname.cfg (The system cannot find the file specified): idname.cfg (The system cannot find the file specified)      at com.nimsoft.nimbus.NimConfig.readCfgString(NimConfig.java:1408)      at com.nimsoft.nimbus.NimConfig.reset(NimConfig.java:240)      at com.nimsoft.nimbus.NimConfig.setFilename(NimConfig.java:197)      at com.nimsoft.nimbus.NimConfig.<init>(NimConfig.java:120)      at com.nimsoft.probe.application.vmware.tools.updater.CfgUpdater.<init>(CfgUpdater.java:63)      at com.nimsoft.probe.application.vmware.tools.updater.CfgUpdater.<init>(CfgUpdater.java:55)      at com.nimsoft.probe.application.vmware.VmwareProbe.updateCfgFile(VmwareProbe.java:184)      at com.nimsoft.probe.application.vmware.VmwareProbe.init(VmwareProbe.java:148)      at com.nimsoft.vm.BaseProbe.initOnTimer(BaseProbe.java:450)      at com.nimsoft.nimbus.NimProbe.doForever(NimProbe.java:418)      at com.nimsoft.vm.BaseProbe.execute(BaseProbe.java:358)      at com.nimsoft.probe.application.vmware.VmwareProbe.main(VmwareProbe.java:72) Caused by: java.io.FileNotFoundException: idname.cfg (The system cannot find the file specified)      at java.io.FileInputStream.open0(Native Method)      at java.io.FileInputStream.open(FileInputStream.java:195)      at java.io.FileInputStream.<init>(FileInputStream.java:138)      at com.nimsoft.nimbus.NimConfig.readCfgString(NimConfig.java:1397)      ... 11 more   Mar 16 09:49:50:566 [main, vmware] Version in cfg file is up to date. No update necessary Mar 16 09:49:50:615 [main, vmware] BEGIN -- NimRequest for 'get_info', against 'controller' Mar 16 09:49:50:622 [main, vmware] END   -- NimRequest for 'get_info', against 'controller' Mar 16 09:49:50:998 [main, vmware] BEGIN -- NimRequest for 'probe_list', against 'controller' Mar 16 09:49:51:009 [main, vmware] END   -- NimRequest for 'probe_list', against 'controller' Mar 16 09:49:51:009 [main, vmware] BEGIN -- NimRequest for 'get_info', against 'cdm' Mar 16 09:49:51:025 [main, vmware] END   -- NimRequest for 'get_info', against 'cdm' Mar 16 09:49:51:137 [main, vmware] Bootstrapping IProbeFailoverDataService as new instance of DefaultRunningProbeInformationService. Mar 16 09:49:51:553 [main, vmware] Creating profile ConfigDef: vm-2.57.com.nimsoft.probe.common.ctd.984631f0aff2f978dd4ca265c0ce3b3f=Profile Setup  ProfileDefinition  ctdProfile Mar 16 09:49:52:060 [main, vmware] SCHEDULER: using scheduler_thread_pool_size = 3 Mar 16 09:52:28:671 [attach_socket, vmware] Callback get_ctd_configuration received with args: ctdObjectId 'null', depth '0', includeScheme 'null' Mar 16 09:52:28:678 [attach_socket, vmware] Entering handleGetCtdConfiguration with '{"additional_arguments":"{\"aclPermissions\":{\"Edit Maintenance Mode Schedules\":\"1\",\"USM Modify Individual Monitors for Computer Systems\":\"1\",\"List Designer\":\"1\",\"SLM Admin\":\"1\",\"Reassign\":\"1\",\"USM Modify Shared Alarm Filters\":\"1\",\"Discovery Pie\":\"1\",\"Launch URL Actions\":\"1\",\"Manage Profiles\":\"1\",\"Probe Template Basic\":\"1\",\"Dashboard Designer\":\"1\",\"Alarm Management\":\"1\",\"Dashboard Download\":\"1\",\"WASP\":\"1\",\"License Management\":\"1\",\"QoS Access\":\"1\",\"Account Administration\":\"1\",\"Dashboard Upload\":\"1\",\"NFA View ToS\":\"1\",\"Program Options\":\"1\",\"Probe Configuration\":\"1\",\"Discovery Management\":\"1\",\"NFA Run Reports\":\"1\",\"List Viewer\":\"1\",\"Dynamic Views States\":\"1\",\"USM Automatic Robot Installation\":\"1\",\"Accept\":\"1\",\"Acknowledge\":\"1\",\"Modify Profiles\":\"1\",\"Report Scheduler\":\"1\",\"NFA Manage Reports\":\"1\",\"Discove y\":\"1\",\"User Monitoring\":\"1\",\"NFA View Conversations\":\"1\",\"Unassign\":\"1\",\"Manage ACL\":\"1\",\"Web Service\":\"1\",\"Custom Dashboards\":\"1\",\"Probe Basic\":\"1\",\"Distribution\":\"1\",\"Web Publish\":\"1\",\"Unified Reports\":\"1\",\"Execution Level 3\":\"1\",\"Execution Level 2\":\"1\",\"Cloud UE Monitor\":\"1\",\"NetFlow Configuration\":\"1\",\"Execution Level 1\":\"1\",\"SLO Access\":\"1\",\"Probe Template Management\":\"1\",\"Automation - View Items\":\"1\",\"USM Edit Monitoring Station Groups\":\"1\",\"Automation - Manage Workflows\":\"1\",\"Dashboard Design\":\"1\",\"NetFlow\":\"1\",\"Edit Maintenance Mode Devices\":\"1\",\"Policy Basic\":\"1\",\"Alarm Summary\":\"1\",\"Invisible Alarms\":\"1\",\"Management Tools\":\"1\",\"USM Group Modification\":\"1\",\"User Customization\":\"1\",\"Dynamic Views Dashboards\":\"1\",\"Alarm History\":\"1\",\"Service Desk\":\"1\",\"Maintenance Mode\":\"1\",\"Basic Management\":\"1\",\"Automation - Change configuration items\":\"1\",\"Probe Security\ :\"1\",\"Automation - Create and Modify Workflows\":\"1\",\"Default Customization\":\"1\",\"Alarm Details\":\"1\",\"USM Edit Monitoring Templates\":\"1\",\"Edit URL Actions\":\"1\",\"Dynamic Views\":\"1\",\"Custom Reports\":\"1\",\"USM Monitoring Configuration Service\":\"1\",\"Extended Security\":\"1\",\"USM Geo View Modification\":\"1\",\"Archive Management\":\"1\",\"Dashboard Publish\":\"1\",\"Policy Management\":\"1\",\"User Administration\":\"1\",\"Portal Administration\":\"1\",\"USM Basic\":\"1\",\"USM Self Service Monitoring\":\"1\",\"SLM View\":\"1\",\"Assign\":\"1\",\"Change Password\":\"1\",\"Dynamic Views Reports\":\"1\",\"Report Designer\":\"1\",\"NFA View Protocols\":\"1\",\"NFA View Hosts\":\"1\"},\"isAdmin\":false,\"sid\":\"8JuWkCZQWDl+Oiycm6Ff+AADMTQ4OTY5Mzk0OAFXVjFJVENBQVAwMVRfaHViATABMTAuNTYuMTI3LjEwNwEBMAFhZG1pbmlzdHJhdG9yATQBfDEwLjU2LjEyNy4xMDd8MDowOjA6MDowOjA6MDoxfAE=\"}","callback_name":"get_ctd_configuration","depth":"-1","ctd_version":"2.7;2.6;2.5;2.4;2.3;2.2","ctd_object_id":"","pro e_address":"/WV1ITCAAP01T_domain/WV1ITCAAP01T_hub/WV1ITCAAP01T/vmware","include_scheme":"true"}' Mar 16 09:52:28:682 [attach_socket, vmware] Entering extractPartialGraph with args: ctdObjectId='null'  depth='2'  includeScheme='true' Mar 16 09:52:29:068 [attach_socket, vmware] Leaving cbGetCtdConfiguration

     

         


  • 15.  Re: VMWare Probe Configuration Problem

    Posted 03-16-2017 10:16 AM

    Can you please try to connect a esx server from vmware probe and see whether you can discover the resources. 



  • 16.  Re: VMWare Probe Configuration Problem

    Posted 03-16-2017 10:44 AM

    Well, I did what you asked and guess what?  This time we were able to connect to the vcenter and discovered the resources (hosts) there.  The only difference that I can recall in this effort was that after creating the configuration; I selected "SAVE".  

     

    Could the "SAVE" been the magic bullet to make this all work?

     

    RJ

         


  • 17.  Re: VMWare Probe Configuration Problem

    Broadcom Employee
    Posted 03-16-2017 11:04 AM

    Yes, and I can see how that might not be obvious.



  • 18.  Re: VMWare Probe Configuration Problem

    Posted 03-16-2017 11:36 AM

    Looks like because the vmware probe is still in "read only mode", I can't make setup any monitoring / make changes to configurations.  Is there a config file I can modify so I can have write access to this probe?  I don't see this message for any of the other probes I am using.

     

    RJ

     



  • 19.  Re: VMWare Probe Configuration Problem

    Broadcom Employee
    Posted 03-16-2017 12:52 PM

    boy reading the log was a bit painful but after putting in all the line breaks found this:

    Mar 16 09:49:50:375 [main, vmware] Login to NimBUS is OK Mar 16 09:49:50:404 [main, vmware] idname.cfg could not be loaded. No vmware.cfg update required
    Mar 16 09:49:50:565 [main, vmware] (90) Configuration error, java.io.FileNotFoundException: idname.cfg (The system cannot find the file specified): idname.cfg (The system cannot find the file specified)      

     

    from the console remove the probe

    from disk remove the vmware probe folder

    deploy the probe

     

    and hopefully that will resolve this.



  • 20.  Re: VMWare Probe Configuration Problem

    Posted 03-16-2017 01:05 PM

    Alrighty then.

     

    I deactivated the probe.  Removed it from the console and deleted the probe folder.  I then downloaded the probe again and deploy it.  The "read only mode" and locks are now gone.  What cause this to occur so I know what to look for when we move from our test to production environment.  Looks like I can set thresholds / monitoring as with the other probes.   Thanks for hanging in there with me.  It is greatly appreciated.  (*__*)

     

    RJ



  • 21.  Re: VMWare Probe Configuration Problem

    Broadcom Employee
    Posted 03-17-2017 09:36 AM

    no idea what caused it. Just going off the message 'FileNotFoundException: idname.cfg ' seemed to indicate the deployment did not complete. So remove / deploy, seemed like the best next step.



  • 22.  Re: VMWare Probe Configuration Problem

    Broadcom Employee
    Posted 07-11-2018 10:00 AM

    Hi All,

     

    I found this issue too, and seems that if MCS has deployed the probe, there is a key in the <SETUP> section that references mcs_control. If you set this to false, the read only mode changes to be manageable.

    <setup>
         mcs_control = false
    </setup>

    This may help someone.