HP的OVPM性能分析工具问题

johnsen168

在OVPM管理端抓取一台server的性能数据时，提示连接不到，
Problem in getting Coda information Problem in getting Coda information No data source was specified. Please select a system or other data source (err203)
查看管理端的配置文件没有问题，网络通讯良好。
client端的这台server状态为：
serdb</>#mwa status
Perf Agent status:
    Running scopeux               (Perf Agent data collector) pid 6258
    Running midaemon              (Measurement Interface daemon) pid 6278
    Running ttd                   (ARM registration daemon) pid 25783 6277

Perf Agent Server status:

    Running ovcd                  (OV control component) pid 5822
    Running ovbbccb               (BBC5 communication broker) pid 5823
    Running coda                  (perf component) pid(s) 5824
最后一条状态显示不出来，一直停在这里，然后使用top查看发现coda进程占cpu好高，

CPU TTY  PID USERNAME PRI NI   SIZE    RES STATE    TIME %WCPU  %CPU COMMAND
2   ?  5824 root     152 20 90064K  9392K run    709:17 100.44 100.27 coda
3   ? 11335 root     232 20 24616K  2708K run      2:26 100.22 100.04 perfalarm

不知问题出在哪里，望高手指点，谢谢啊！
有时候抓出来mwa状态为：
serdb</>#mwa status
Perf Agent status:
    Running scopeux               (Perf Agent data collector) pid 11895
    Running midaemon              (Measurement Interface daemon) pid 11919
    Running ttd                   (ARM registration daemon) pid 25783 6277

Perf Agent Server status:

    Running ovcd                  (OV control component) pid 5822
    Running ovbbccb               (BBC5 communication broker) pid 5823
    Running coda                  (perf component) pid(s) 13433
                  EPC(CODA) Configured
    Running perfalarm             (alarm generator) pid(s) 11920

[ 本帖最后由 johnsen168 于 2009-7-16 11:37 编辑 ]

cjhvslhb

#mwa stop
#mwa start重起下OVPM的进程看看呢?
还有你配置的CONFIG文件里有没乱码或者错误?

johnsen168

stop和start很多次，不能解决问题，在6月初还正常使用过，config文件没变动过的。

cjhvslhb

http://forums11.itrc.hp.com/serv ... do?threadId=1106312
Following some tips in order to help you:

OVPM Server collects information from OVPA 4.x managed nodes through https/http.
Tips:
1) Port 383 should be open between OVPM Server and OVPA managed nodes.

2) OVPA by default uses BBC communication broker (port 383) and coda uses a dynamically allocated port. BBC uses HTTP.

3) If you are using a RPC/DCE communication on OVPA managed node you need to open port 382 and port 135 between OVPM Server and OVPA managed nodes.

4) There is a exclusive tip for OVPM 5.0, when a user is unable to draw graphs in OVPM:
-> it is necessary to select the data source as CODA in OVPM since OVPA 4.7 uses the CODA datacomm by default.

看看这个对你有没帮助.