11 Replies Latest reply on May 25, 2010 9:54 AM by ctanner

    Data not being collected on DMX arrays

    marc.day@fil.com

      Hi

      I have the SMI-S provider working and can see 4 DMX arrays, (all zoned and has 6 gatekeepers for each array) running SMI-S provider 4.1 for smi-s 1.4

        S Y M M E T R I X

                                             Mcode    Cache      Num Phys  Num Symm
          SymmID       Attachment  Model     Version  Size (MB)  Devices   Devices

          000190104109 Local       DMX4-24   5773      131072         6      9447
          000190105567 Local       DMX4-24   5773      147456         6     13708
          000290301405 Local       DMX4-6    5773       32768         9      1276
          000290301408 Local       DMX4-6    5773       32768         8      1263


      However the data does not seem to be getting into profiler

      The agent logs are showing the following

      24 May 2010 13:19:41 - Data limit exceeded, removing oldest entry with key '          ' from 103_perf (deleted: true)
      24 May 2010 13:19:41 - Data limit '268435456' reached for mod.sys.smis.Smis_1.0, sending notification to server
      24 May 2010 13:19:45 - Data ready for mod.sys.smis.Smis_1.0, sending notification to server
      24 May 2010 13:19:54 - CimClientProxy(102 strg).notifyGPMForParser(): notifying that data is ready. (DOTimeStamp: 1274702418080, isDone: false, cache used: 1000 out of 1000) for-->CIM_StorageSetting
      24 May 2010 13:19:58 - CimClientProxy(103 perf).gatherData(): sent data gathering completed trap: Scheduled data collection for perf
      24 May 2010 13:19:58 - CimClientProxy(103 perf).gatherData():  time taken to gather perf data-->476 secs
      24 May 2010 13:19:58 - CimClientProxy(103 perf).notifyGPMForParser(): notifying that data is ready. (DOTimeStamp: 1274703122420, isDone: true, cache used: 351 out of 1000) for-->.Qualifier_CIM_BlockStatisticsCapabilities
      24 May 2010 13:20:04 - Data limit exceeded, removing oldest entry with key '          ' from 103_strg (deleted: true)
      24 May 2010 13:20:05 - CimClientProxy(27 perf).notifyGPMForParser(): notifying that data is ready. (DOTimeStamp: 1274702401751, isDone: false, cache used: 1000 out of 1000) for-->CIM_MemberOfCollection
      24 May 2010 13:20:37 - Data limit exceeded, removing oldest entry with key '          ' from 102_perf (deleted: true)
      24 May 2010 13:20:37 - Data limit '268435456' reached for mod.sys.smis.Smis_1.0, sending notification to server
      24 May 2010 13:20:40 - Data ready for mod.sys.smis.Smis_1.0, sending notification to server
      24 May 2010 13:21:07 - CimClientProxy(102 perf).gatherData(): identifier (000290301405) and key value (symmetrix+000290301408) do not match, device treated as invalid
      24 May 2010 13:21:07 - CimClientProxy(102 perf).gatherData(): sent data gathering completed trap: Scheduled data collection for perf
      24 May 2010 13:21:07 - CimClientProxy(102 perf).gatherData():  time taken to gather perf data-->509 secs
      24 May 2010 13:21:07 - CimClientProxy(102 perf).notifyGPMForParser(): notifying that data is ready. (DOTimeStamp: 1274703158015, isDone: true, cache used: 795 out of 1000) for-->.Qualifier_CIM_BlockStatisticsCapabilities
      24 May 2010 13:21:29 - Data limit exceeded, removing oldest entry with key '        ' from 4_perf (deleted: true)
      24 May 2010 13:21:29 - Data limit '268435456' reached for mod.sys.smis.Smis_1.0, sending notification to server
      24 May 2010 13:21:32 - CimClientProxy(4 strg).notifyGPMForParser(): notifying that data is ready. (DOTimeStamp: 1274702369215, isDone: false, cache used: 1000 out of 1000) for-->CIM_ProtocolControllerForUnit
      24 May 2010 13:21:33 - Data ready for mod.sys.smis.Smis_1.0, sending notification to server
      24 May 2010 13:21:54 - Data limit exceeded, removing oldest entry with key '          ' from 102_strg (deleted: true)
      24 May 2010 13:21:59 - Data limit exceeded, removing oldest entry with key '          ' from 103_perf (deleted: true)
      24 May 2010 13:21:59 - Data limit '268435456' reached for mod.sys.smis.Smis_1.0, sending notification to server
      24 May 2010 13:23:24 - Data limit exceeded, removing oldest entry with key '        C' from 27_perf (deleted: true)
      24 May 2010 13:23:24 - Data limit '268435456' reached for mod.sys.smis.Smis_1.0, sending notification to server
      24 May 2010 13:23:27 - Data ready for mod.sys.smis.Smis_1.0, sending notification to server
      24 May 2010 13:25:09 - CimClientProxy(4 perf).notifyGPMForParser(): notifying that data is ready. (DOTimeStamp: 1274702224775, isDone: false, cache used: 1000 out of 1000) for-->CIM_MemberOfCollection
      24 May 2010 13:25:26 - Data limit exceeded, removing oldest entry with key '         ' from 4_strg (deleted: true)
      24 May 2010 13:25:26 - Data limit '268435456' reached for mod.sys.smis.Smis_1.0, sending notification to server
      24 May 2010 13:25:28 - Data ready for mod.sys.smis.Smis_1.0, sending notification to server
      24 May 2010 13:26:16 - CimClientProxy(27 perf).notifyGPMForParser(): notifying that data is ready. (DOTimeStamp: 1274702401751, isDone: false, cache used: 1000 out of 1000) for-->CIM_MemberOfCollection
      24 May 2010 13:26:47 - Data limit exceeded, removing oldest entry with key '        ' from 4_perf (deleted: true)
      24 May 2010 13:26:47 - Data limit '268435456' reached for mod.sys.smis.Smis_1.0, sending notification to server
      24 May 2010 13:26:50 - Data ready for mod.sys.smis.Smis_1.0, sending notification to server
      24 May 2010 13:26:51 - CimClientProxy(27 strg).notifyGPMForParser(): notifying that data is ready. (DOTimeStamp: 1274702349032, isDone: false, cache used: 1000 out of 1000) for-->CIM_ProtocolControllerForUnit
      24 May 2010 13:26:58 - Data limit exceeded, removing oldest entry with key '          ' from 102_perf (deleted: true)
      24 May 2010 13:27:28 - Data limit exceeded, removing oldest entry with key '          ' from 103_perf (deleted: true)
      24 May 2010 13:27:28 - Data limit '268435456' reached for mod.sys.smis.Smis_1.0, sending notification to server
      24 May 2010 13:27:28 - Data ready for mod.sys.smis.Smis_1.0, sending notification to server
      24 May 2010 13:27:29 - Data limit exceeded, removing oldest entry with key '          ' from 103_perf (deleted: true)

      There is no data for any array.  The test option works from the wrench, and all arrays are set to active.

      Cheers

      Marc

        • Re: Data not being collected on DMX arrays
          animelov

          Judging from this log, it looks like there is a problem with the collector on the server-side.  Can you check the services on the Profiler server and make sure the ProfilerCollector service is running?

            • Re: Data not being collected on DMX arrays
              marc.day@fil.com

              All the services on the collector server side are up and running.

              I have tried performing a reboot of both servers, (confirmed the services are running.)

                • Re: Data not being collected on DMX arrays
                  animelov

                  Can you post the last 30 (or so) lines from the Kernel.log file from the agent here?

                    • Re: Data not being collected on DMX arrays
                      marc.day@fil.com

                      kernel from profile server

                      24 May 2010 15:00:12 [INFO] - Attempting to send notification to 10.166.97.79
                      24 May 2010 15:00:12 [INFO] - Call to placeTrapOrder(1.3.6.1.4.1.10089.10089.10089) succeeded
                      24 May 2010 15:00:12 [INFO] - Attempting to send notification to 10.166.97.79
                      24 May 2010 15:00:12 [INFO] - Call to placeTrapOrder(1.3.6.1.4.1.10089.10089.10089) succeeded
                      24 May 2010 15:00:12 [INFO] - Attempting to send notification to 10.166.97.79
                      24 May 2010 15:00:12 [INFO] - Call to placeTrapOrder(1.3.6.1.4.1.10089.10089.10089) succeeded
                      24 May 2010 15:00:14 [INFO] - Incoming 'GET' request for '/module.data' from 10.166.97.79
                      24 May 2010 15:00:14 [INFO] - Handle request started [10.166.97.79]: GET /module.data
                      24 May 2010 15:00:14 [INFO] - Writing entry: mod.sys.perf.cpu.CPUPerf_1.0-win_cpu_perf-0.bean
                      24 May 2010 15:00:14 [INFO] - Writing entry: mod.sys.perf.disk.DiskPerf_1.0-win_disk_perf-0.bean
                      24 May 2010 15:00:14 [INFO] - Writing entry: mod.sys.perf.net.NetPerf_1.0-win_net_perf-0.bean
                      24 May 2010 15:00:14 [INFO] - Handle request complete [10.166.97.79]: GET /module.data
                      24 May 2010 15:00:14 [INFO] - Incoming 'POST' request for '/module.data' from 10.166.97.79
                      24 May 2010 15:00:14 [INFO] - Handle request started [10.166.97.79]: POST /module.data
                      24 May 2010 15:00:14 [INFO] - Purging archive indexes:
                      24 May 2010 15:00:14 [INFO] -   mod.sys.perf.cpu.CPUPerf_1.0-win_cpu_perf: 0
                      24 May 2010 15:00:14 [INFO] -   mod.sys.perf.net.NetPerf_1.0-win_net_perf: 0
                      24 May 2010 15:00:14 [INFO] -   mod.sys.perf.disk.DiskPerf_1.0-win_disk_perf: 0
                      24 May 2010 15:00:14 [INFO] - Total time to collect/purge 3 archives: 0.062 secs
                      24 May 2010 15:00:14 [INFO] - Handle request complete [10.166.97.79]: POST /module.data
                      24 May 2010 15:00:22 [INFO] - Attempting to send notification to 10.166.97.79
                      24 May 2010 15:00:22 [INFO] - Call to placeTrapOrder(1.3.6.1.4.1.10089.10090.10090) succeeded
                      24 May 2010 15:01:12 [INFO] - Attempting to send notification to 10.166.97.79
                      24 May 2010 15:01:12 [INFO] - Call to placeTrapOrder(1.3.6.1.4.1.10089.10089.10089) succeeded
                      24 May 2010 15:01:12 [INFO] - Attempting to send notification to 10.166.97.79
                      24 May 2010 15:01:12 [INFO] - Call to placeTrapOrder(1.3.6.1.4.1.10089.10089.10089) succeeded
                      24 May 2010 15:01:12 [INFO] - Attempting to send notification to 10.166.97.79
                      24 May 2010 15:01:12 [INFO] - Call to placeTrapOrder(1.3.6.1.4.1.10089.10089.10089) succeeded
                      24 May 2010 15:01:14 [INFO] - Incoming 'GET' request for '/module.data' from 10.166.97.79
                      24 May 2010 15:01:14 [INFO] - Handle request started [10.166.97.79]: GET /module.data
                      24 May 2010 15:01:14 [INFO] - Writing entry: mod.sys.perf.cpu.CPUPerf_1.0-win_cpu_perf-0.bean
                      24 May 2010 15:01:14 [INFO] - Writing entry: mod.sys.perf.disk.DiskPerf_1.0-win_disk_perf-0.bean
                      24 May 2010 15:01:14 [INFO] - Writing entry: mod.sys.perf.net.NetPerf_1.0-win_net_perf-0.bean
                      24 May 2010 15:01:14 [INFO] - Handle request complete [10.166.97.79]: GET /module.data
                      24 May 2010 15:01:14 [INFO] - Incoming 'POST' request for '/module.data' from 10.166.97.79
                      24 May 2010 15:01:14 [INFO] - Handle request started [10.166.97.79]: POST /module.data
                      24 May 2010 15:01:14 [INFO] - Purging archive indexes:
                      24 May 2010 15:01:14 [INFO] -   mod.sys.perf.cpu.CPUPerf_1.0-win_cpu_perf: 0
                      24 May 2010 15:01:14 [INFO] -   mod.sys.perf.net.NetPerf_1.0-win_net_perf: 0
                      24 May 2010 15:01:14 [INFO] -   mod.sys.perf.disk.DiskPerf_1.0-win_disk_perf: 0
                      24 May 2010 15:01:14 [INFO] - Total time to collect/purge 3 archives: 0.078 secs
                      24 May 2010 15:01:14 [INFO] - Handle request complete [10.166.97.79]: POST /module.data
                      24 May 2010 15:01:24 [INFO] - Attempting to send notification to 10.166.97.79
                      24 May 2010 15:01:24 [INFO] - Call to placeTrapOrder(1.3.6.1.4.1.10089.10090.10090) succeeded
                      24 May 2010 15:01:24 [INFO] - Attempting to send notification to 10.166.97.79
                      24 May 2010 15:01:24 [INFO] - Call to placeTrapOrder(1.3.6.1.4.1.10089.10089.10089) succeeded
                      24 May 2010 15:01:29 [INFO] - Incoming 'GET' request for '/module.data' from 10.166.97.79
                      24 May 2010 15:01:29 [INFO] - Handle request started [10.166.97.79]: GET /module.data
                      24 May 2010 15:01:29 [INFO] - Writing entry: mod.sys.strg.Storage_1.0-strg-0.bean
                      24 May 2010 15:01:29 [INFO] - Handle request complete [10.166.97.79]: GET /module.data
                      24 May 2010 15:01:29 [INFO] - Incoming 'POST' request for '/module.data' from 10.166.97.79
                      24 May 2010 15:01:29 [INFO] - Handle request started [10.166.97.79]: POST /module.data
                      24 May 2010 15:01:29 [INFO] - Purging archive indexes:
                      24 May 2010 15:01:29 [INFO] -   mod.sys.strg.Storage_1.0-strg: 0
                      24 May 2010 15:01:29 [INFO] - Total time to collect/purge 1 archives: 0.047 secs
                      24 May 2010 15:01:29 [INFO] - Handle request complete [10.166.97.79]: POST /module.data

                      kernel from agent

                       

                      24 May 2010 15:05:18 [WARN] - Error removing fragment:
                      com.virtualmachinery.btree.exceptions.BTreeInformationException: Record for deletion not found
                       at com.virtualmachinery.btree.supportimplementation.DataPage.deleteData(Unknown Source)
                       at com.virtualmachinery.btree.core.BasicBTree.remove(Unknown Source)
                       at com.virtualmachinery.btree.core.BasicBTree.remove(Unknown Source)
                       at com.tektools.kernel.persist.PersistorImpl.remove(PersistorImpl.java)
                       at com.tektools.kernel.persist.PersistorImpl.remove(PersistorImpl.java)
                       at com.tektools.kernel.persist.PersistorImpl.collect(PersistorImpl.java)
                       at com.tektools.kernel.persist.PersistorService.writePersistors(PersistorService.java)
                       at com.tektools.kernel.persist.PersistorService.writePersistors(PersistorService.java)
                       at com.tektools.kernel.http.DataHandler.getArchiveData(DataHandler.java)
                       at com.tektools.kernel.http.DataHandler.getDataRequest(DataHandler.java)
                       at com.tektools.kernel.http.DataHandler.handle(DataHandler.java)
                       at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
                       at org.mortbay.http.HttpContext.handle(HttpContext.java:1434)
                       at org.mortbay.http.HttpServer.service(HttpServer.java:896)
                       at org.mortbay.http.HttpConnection.service(HttpConnection.java:814)
                       at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:984)
                       at org.mortbay.http.HttpConnection.handle(HttpConnection.java:831)
                       at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)
                       at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:345)
                       at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:538)
                      24 May 2010 15:05:18 [WARN] - Error removing fragment:
                      com.virtualmachinery.btree.exceptions.BTreeInformationException: Record for deletion not found
                       at com.virtualmachinery.btree.supportimplementation.DataPage.deleteData(Unknown Source)
                       at com.virtualmachinery.btree.core.BasicBTree.remove(Unknown Source)
                       at com.virtualmachinery.btree.core.BasicBTree.remove(Unknown Source)
                       at com.tektools.kernel.persist.PersistorImpl.remove(PersistorImpl.java)
                       at com.tektools.kernel.persist.PersistorImpl.remove(PersistorImpl.java)
                       at com.tektools.kernel.persist.PersistorImpl.collect(PersistorImpl.java)
                       at com.tektools.kernel.persist.PersistorService.writePersistors(PersistorService.java)
                       at com.tektools.kernel.persist.PersistorService.writePersistors(PersistorService.java)
                       at com.tektools.kernel.http.DataHandler.getArchiveData(DataHandler.java)
                       at com.tektools.kernel.http.DataHandler.getDataRequest(DataHandler.java)
                       at com.tektools.kernel.http.DataHandler.handle(DataHandler.java)
                       at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
                       at org.mortbay.http.HttpContext.handle(HttpContext.java:1434)
                       at org.mortbay.http.HttpServer.service(HttpServer.java:896)
                       at org.mortbay.http.HttpConnection.service(HttpConnection.java:814)
                       at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:984)
                       at org.mortbay.http.HttpConnection.handle(HttpConnection.java:831)
                       at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)
                       at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:345)
                       at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:538)
                      24 May 2010 15:05:18 [WARN] - Error removing fragment:
                      com.virtualmachinery.btree.exceptions.BTreeInformationException: Record for deletion not found
                       at com.virtualmachinery.btree.supportimplementation.DataPage.deleteData(Unknown Source)
                       at com.virtualmachinery.btree.core.BasicBTree.remove(Unknown Source)
                       at com.virtualmachinery.btree.core.BasicBTree.remove(Unknown Source)
                       at com.tektools.kernel.persist.PersistorImpl.remove(PersistorImpl.java)
                       at com.tektools.kernel.persist.PersistorImpl.remove(PersistorImpl.java)
                       at com.tektools.kernel.persist.PersistorImpl.collect(PersistorImpl.java)
                       at com.tektools.kernel.persist.PersistorService.writePersistors(PersistorService.java)
                       at com.tektools.kernel.persist.PersistorService.writePersistors(PersistorService.java)
                       at com.tektools.kernel.http.DataHandler.getArchiveData(DataHandler.java)
                       at com.tektools.kernel.http.DataHandler.getDataRequest(DataHandler.java)
                       at com.tektools.kernel.http.DataHandler.handle(DataHandler.java)
                       at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
                       at org.mortbay.http.HttpContext.handle(HttpContext.java:1434)
                       at org.mortbay.http.HttpServer.service(HttpServer.java:896)
                       at org.mortbay.http.HttpConnection.service(HttpConnection.java:814)
                       at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:984)
                       at org.mortbay.http.HttpConnection.handle(HttpConnection.java:831)
                       at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244)
                       at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:345)
                       at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:538)

                • Re: Data not being collected on DMX arrays
                  animelov

                  Ok, go ahead and do this:

                   

                  ON THE AGENT SIDE:

                  1)  Stop the Agent

                  2)  Go to <install path>\systemic\mod.sys.smis.Smis_1.0

                  3)  Delete the data folder

                  4)  Restart the agent.

                   

                  It may take about 15 minutes for data to start coming back in, and doing this will not make you lose any historical data either.  Let me know if this works!

                    • Re: Data not being collected on DMX arrays
                      marc.day@fil.com

                      The asset information is now showing as 40 mins but there is no storage information for any of the 4 arrays.

                        • Re: Data not being collected on DMX arrays
                          animelov

                          Considering you've got 4 DMX arrays, I'd give it time at this point.  DMX's are usually large and slow, multiply that times 4 and it doesn't surprise me at all that it is taking time.  Good to hear that there is asset data though, so, give it at least another hour or so, and if you still don't see anything, go ahead and reply to this thread and we'll work on another angle (though i think you're good at this point).

                            • Re: Data not being collected on DMX arrays
                              marc.day@fil.com

                              I have downgraded the SMI-S provider to 4.0 for SMI-S 1.3 and things are looking  a bit better.

                              I think  adding 4 DMX arrays in one hit was too much for the boxes I am running profiler  on. 

                              Currently  the Profiler is running on a VM, (high spec'ed VM mind!!)

                              Processor  Count/Type:

                               1 / 586  AuthenticAMD AMD64 Family 16 Model 2 Stepping 3 2210  MHz

                              Memory  Physical/Swap:

                               3071 / 1346 MB

                              I have  the SMI agent running on a physical box 

                              Processor  Count/Type:

                               4 / 586  AuthenticAMD x86 Family 15 Model 33 Stepping 2 2405  MHz

                              Memory  Physical/Swap:

                               16215 / 24326  MB 

                               The  Agent and the SMI-S agent seem to absolutely crucify the processor!! 

                               I have  resorted to adding one array at a time.  I can only get one DMX (working then it doesnt colelct the data after the first collection.  Notice the agent had crashed too....

                               

                              ---------------------------------------------------------------------------------------

                              FATAL ERROR ENCOUNTERED IN KERNEL ON Tue May 25 10:31:41 BST 2010

                               

                              Error Message:

                              Java heap space

                               

                              Stack Trace:

                              java.lang.OutOfMemoryError: Java heap space

                               

                              Total Memory: 518979584 bytes

                               

                              Free Memory: 108776 bytes

                               

                              Threads Information [Current Thread: Kernel Thread]:

                              com.tektools.kernel.Kernel$1[name=Kernel Thread Group,maxpri=10]

                                  Thread[Kernel Thread,5,Kernel Thread Group]

                                  Thread[SnmpLoadingDock,5,Kernel Thread Group]

                                  Thread[SnmpLoadingDock Timeout,5,Kernel Thread Group]

                                  Thread[SnmpShipper,5,Kernel Thread Group]

                                  Thread[Clerk Cleanup,4,Kernel Thread Group]

                                  Thread[Acceptor ServerSocket[addr=0.0.0.0/0.0.0.0,port=0,localport=4319],5,Kernel Thread Group]

                                  SocketListener0-0

                                  Thread[com.tektools.kernel.load.Loader,10,Kernel Thread Group]

                                  Thread[com.tektools.kernel.load.Loader,10,Kernel Thread Group]

                                  SocketListener0-2

                                  com.tektools.kernel.load.ModuleController$ContextThreadGroup[name=mod.adm.control.Control thread group,maxpri=5]

                                      Thread[Status Monitor,5,mod.adm.control.Control thread group]

                                  com.tektools.kernel.load.ModuleController$ContextThreadGroup[name=mod.adm.mu.MiscUtils thread group,maxpri=5]

                                  com.tektools.kernel.load.ModuleController$ContextThreadGroup[name=mod.sys.perf.net.NetPerf thread group,maxpri=5]

                                      Thread[ParserMessageReader_mod.sys.perf.net.win.WinNetPerf,5,mod.sys.perf.net.NetPerf thread group]

                                  com.tektools.kernel.load.ModuleController$ContextThreadGroup[name=mod.sys.perf.cpu.CPUPerf thread group,maxpri=5]

                                      Thread[ParserMessageReader_mod.sys.perf.cpu.win.WinCPUPerf,5,mod.sys.perf.cpu.CPUPerf thread group]

                                  com.tektools.kernel.load.ModuleController$ContextThreadGroup[name=mod.sys.perf.disk.DiskPerf thread group,maxpri=5]

                                  com.tektools.kernel.load.ModuleController$ContextThreadGroup[name=mod.sys.asset.Asset thread group,maxpri=5]

                                      Thread[mod.sys.asset.Asset starter,5,mod.sys.asset.Asset thread group]

                                  com.tektools.kernel.load.ModuleController$ContextThreadGroup[name=mod.sys.support.Support thread group,maxpri=5]

                                  com.tektools.kernel.load.ModuleController$ContextThreadGroup[name=mod.sys.strg.Storage thread group,maxpri=5]

                                      Thread[mod.sys.strg.Storage starter:ParserThread_ttDiskUsageRT,5,mod.sys.strg.Storage thread group]

                                  com.tektools.kernel.load.ModuleController$ContextThreadGroup[name=mod.sys.uptime.Uptime thread group,maxpri=5]

                                      Thread[ParserMessageReader_mod.sys.uptime.win.WinUptime,5,mod.sys.uptime.Uptime thread group]

                                  com.tektools.kernel.load.ModuleController$ContextThreadGroup[name=mod.sys.perf.typeperf.TypePerf thread group,maxpri=5]

                                      Thread[mod.sys.perf.typeperf.TypePerf starter,5,mod.sys.perf.typeperf.TypePerf thread group]

                                      Thread[ParserThread_ttWmiPerf,5,mod.sys.perf.typeperf.TypePerf thread group]

                                      Thread[Stdin_ttWmiPerf,5,mod.sys.perf.typeperf.TypePerf thread group]

                                      Thread[Stderr_ttWmiPerf,5,mod.sys.perf.typeperf.TypePerf thread group]

                                  com.tektools.kernel.load.ModuleController$ContextThreadGroup[name=mod.sys.poll.Poller thread group,maxpri=5]

                                  com.tektools.kernel.load.ModuleController$ContextThreadGroup[name=mod.adm.rules.Rules thread group,maxpri=5]

                                      Thread[QuartzScheduler_Worker-0,5,mod.adm.rules.Rules thread group]

                                      Thread[QuartzScheduler_Worker-1,5,mod.adm.rules.Rules thread group]

                                      Thread[QuartzScheduler_Worker-2,5,mod.adm.rules.Rules thread group]

                                      Thread[Rules Publisher,5,mod.adm.rules.Rules thread group]

                                      Thread[Unscheduled Rule Executor,5,mod.adm.rules.Rules thread group]

                                      Thread[Unscheduled Rule Executor,5,mod.adm.rules.Rules thread group]

                                      Thread[Unscheduled Rule Executor,5,mod.adm.rules.Rules thread group]

                                      Thread[Unscheduled Rule Executor,5,mod.adm.rules.Rules thread group]

                                      Thread[Unscheduled Rule Executor,5,mod.adm.rules.Rules thread group]

                                      Thread[Unscheduled Rule Executor,5,mod.adm.rules.Rules thread group]

                                      Thread[Unscheduled Rule Executor,5,mod.adm.rules.Rules thread group]

                                      Thread[Unscheduled Rule Executor,5,mod.adm.rules.Rules thread group]

                                      java.lang.ThreadGroup[name=QuartzScheduler:QuartzScheduler,maxpri=5]

                                          Thread[QuartzScheduler_QuartzSchedulerThread,5,QuartzScheduler:QuartzScheduler]

                                  com.tektools.kernel.load.ModuleController$ContextThreadGroup[name=mod.sys.smis.Smis thread group,maxpri=5]

                                      Thread[CimClient_asset_107,5,mod.sys.smis.Smis thread group]

                                      Thread[CimClient_perf_107,5,mod.sys.smis.Smis thread group]

                                      Thread[CimClient_strg_107,5,mod.sys.smis.Smis thread group]

                                      Thread[CimClient_refsys_107,5,mod.sys.smis.Smis thread group]

                                      Thread[CimClient_asset_108,5,mod.sys.smis.Smis thread group]

                                      Thread[CimClient_perf_108,5,mod.sys.smis.Smis thread group]

                                      Thread[CimClient_strg_108,5,mod.sys.smis.Smis thread group]

                                      Thread[CimClient_refsys_108,5,mod.sys.smis.Smis thread group]

                               

                              Property Settings:

                              -- listing properties --

                              sun.lang.ClassLoader.allowArraySyntax=true

                              java.runtime.name=Java(TM) SE Runtime Environment

                              sun.boot.library.path=D:\Program Files\SolarWinds\Profiler Agent\jre\bin

                              java.vm.version=16.0-b13

                              java.vm.vendor=Sun Microsystems Inc.

                              java.vendor.url=http://java.sun.com/

                              path.separator=;

                              java.vm.name=Java HotSpot(TM) Client VM

                              file.encoding.pkg=sun.io

                              user.country=GB

                              sun.os.patch.level=Service Pack 2

                              java.vm.specification.name=Java Virtual Machine Specification

                              user.dir=D:\Program Files\SolarWinds\Profiler Agent

                              java.runtime.version=1.6.0_18-b07

                              service.inifile=D:\Program Files\SolarWinds\Profiler Agent\ProfilerAgent.ini

                              java.awt.graphicsenv=sun.awt.Win32GraphicsEnvironment

                              java.endorsed.dirs=D:\Program Files\SolarWinds\Profiler Agent\jre\lib\endorsed

                              os.arch=x86

                              java.io.tmpdir=C:\WINDOWS\TEMP\

                              line.separator=

                               

                              service.name=ProfilerAgent

                              java.vm.specification.vendor=Sun Microsystems Inc.

                              user.variant=

                              os.name=Windows 2003

                              service.stop.port=0

                              sun.jnu.encoding=Cp1252

                              java.library.path=D:\Program Files\SolarWinds\Profiler Agent;.;C:\WINDOWS\Sun\Java\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\Program Files\EMC\PowerCommon\;C:\Program Files\EMC\PowerPath\;E:\Program Files\NetApp\DataFabric\DFM\bin;E:\Program Files\NetApp\DataFabric\Sybase\ASA\win32;C:\Program Files\HP\NCU;C:\Program Files\Support Tools\;C:\Program Files\Windows Resource Kits\Tools\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\HP OpenView\Installed Packages\{790c06b4-844e-11d2-972b-080009ef8c2a}\bin;C:\Program Files\HP OpenView\Installed Packages\{790c06b4-844e-11d2-972b-080009ef8c2a}\bin\OpC;C:\Program Files\HP OpenView\bin;C:\Program Files\HP OpenView\bin\;C:\Program Files\HP OpenView\lib\;C:\Program Files\Veritas\Veritas Object Bus\bin;C:\Program Files\Veritas\VRTSobc\pal33\bin;C:\Program Files\Veritas\Veritas Volume Manager 5.1\;D:\Program Files\EMC\SYMCLI\bin;D:/Program Files/SolarWinds/Profiler Agent/jre\bin

                              java.specification.name=Java Platform API Specification

                              java.class.version=50.0

                              java.net.preferIPv4Stack=true

                              sun.management.compiler=HotSpot Client Compiler

                              os.version=5.2

                              user.home=C:\Documents and Settings\a357281.INTL

                              user.timezone=Europe/London

                              sblim.wbem.httpTimeout=600000

                              java.awt.printerjob=sun.awt.windows.WPrinterJob

                              file.encoding=Cp1252

                              java.specification.version=1.6

                              java.class.path=lib\kernel.jar

                              user.name=SYSTEM

                              sun.nio.ch.disableSystemWideOverlappingFileLockCheck=true

                              sblim.wbem.configURL=jar:file:/D:/Program Files/SolarWinds/Profiler Agent/systemic/mod.sys.smis.Smis_1.0/mod.sys.smis.Smis.jar!/sblim-cim-client2.properties

                              java.vm.specification.version=1.0

                              java.home=D:\Program Files\SolarWinds\Profiler Agent\jre

                              sun.arch.data.model=32

                              user.language=en

                              java.specification.vendor=Sun Microsystems Inc.

                              awt.toolkit=sun.awt.windows.WToolkit

                              java.vm.info=mixed mode

                              java.version=1.6.0_18

                              java.ext.dirs=D:\Program Files\SolarWinds\Profiler Agent\jre\lib\ext;C:\WINDOWS\Sun\Java\lib\ext

                              service.path=D:\Program Files\SolarWinds\Profiler Agent\

                              sun.boot.class.path=D:\Program Files\SolarWinds\Profiler Agent\jre\lib\resources.jar;D:\Program Files\SolarWinds\Profiler Agent\jre\lib\rt.jar;D:\Program Files\SolarWinds\Profiler Agent\jre\lib\sunrsasign.jar;D:\Program Files\SolarWinds\Profiler Agent\jre\lib\jsse.jar;D:\Program Files\SolarWinds\Profiler Agent\jre\lib\jce.jar;D:\Program Files\SolarWinds\Profiler Agent\jre\lib\charsets.jar;D:\Program Files\SolarWinds\Profiler Agent\jre\classes

                              java.vendor=Sun Microsystems Inc.

                              file.separator=\

                              java.vendor.url.bug=http://java.sun.com/cgi-bin/bugreport.cgi

                              sun.io.unicode.encoding=UnicodeLittle

                              sun.cpu.endian=little

                              jsnmp.ignoreV1V2PduSizeLimit=true

                              user.region=US

                              sun.desktop=windows

                              sun.cpu.isalist=

                              ---------------------------------------------------------------------------------------

                              Kernel halted at Tue May 25 10:31:42 BST 2010

                                • Re: Data not being collected on DMX arrays
                                  animelov

                                  Well, again, I can't say I'm surprised, DMX arrays are large and slow.  Since you say there are four and the current agent is on a vm, I would recommend getting a second vm to be an agent for collecting from the smi-s box and split the collection between the two (and the smi-s box still be its own physical box).

                                    • Re: Data not being collected on DMX arrays
                                      marc.day@fil.com

                                      Profiler is running on a VM, but the agent is running on a physical.

                                      I am only trying to collect the data for 1 DMX now and even that isnt working.  At the moment am not too impressed!  Sorry!! :-)

                                        • Re: Data not being collected on DMX arrays
                                          ctanner

                                          You could also try increasing the agent memory. 

                                          Open the services menu (Start -> Run -> services.msc) and stop the ProfilerAgent service. 

                                          Open <install dir>\ProfilerAgent.ini (<install dir> = C:\Program Files\SolarWinds\Profiler Agent\ if you choose the default location)

                                          The value we are looking to change is the number after -Xmx. For example, -Xmx512m which signifies the memory is set to 512 MB. 

                                          So, try changing the -Xmx value to something like -Xmx1024m and start the service.