System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

stopped the cim service on all servers

 
aamir4u
Regular Advisor

stopped the cim service on all servers

Hi,

 

I stopped the cim service on all servers .Is any disadvantages of cim on the servers.

 

Thanks

Thanks
aamir uddin
6 REPLIES
Ajin_1
Valued Contributor

Re: stopped the cim service on all servers

Hi

 

Then you are not able to use HP WBEM Services.

 

 

Regards


Ajin.S

Thanks & Regards
Ajin.S
Proverbs 3:5,6 Trust in the Lord with all your heart and lean not on your own understanding; in all your ways acknowledge him, and he will make all your paths straight.
Nighwish
Frequent Advisor

Re: stopped the cim service on all servers

aamir4u
Regular Advisor

Re: stopped the cim service on all servers

Hi,

 

My syslog contains following error messages.

 

Jan 14 02:11:42 prodata1 cimserver[1528]: PGS17200: Authentication failed for user root.
Jan 14 02:12:23 prodata1 cimserver[1528]: PGS17200: Authentication failed for user root.
Jan 14 02:12:27 prodata1 cimserver[1528]: PGS17200: Authentication failed for user root.

 

 

what it is mean.how to resolved.

 

Is any thing critical.

 

Thanks

 

Thanks
aamir uddin
Henry Fauni
Valued Contributor

Re: stopped the cim service on all servers

Do you have an "HP Systems Insight Manager" Server configured on your environment? It's possible that the HP SIM Server is trying to connect to this host, but Systems credentials are not setup correctly.

aamir4u
Regular Advisor

Re: stopped the cim service on all servers

Hello,

 

My cim services are currently running.

for example:--

 

 

uatdata1 /#ps -ef |grep cim
    root  1520  1513  0  Jan  6  ?         0:05 /opt/wbem/lbin/cimprovagt 0 5 10 root HPUXFCIndicationProviderModule
    root  1516  1513  0  Jan  6  ?        38:09 /opt/wbem/lbin/cimprovagt 0 5 10 root SFMProviderModule
    root  1515  1513  0  Jan  6  ?         0:02 /opt/wbem/lbin/cimprovagt 0 5 10 root EMSHAProviderModule
 cimsrvr  1514  1513  0  Jan  6  ?         7:15 cimservermain --executor-socket 5
    root  1513     1  0  Jan  6  ?         0:32 /opt/wbem/lbin/cimserver
    root  1521  1513  0  Jan  6  ?        162:56 /opt/wbem/lbin/cimprovagt 0 5 10 root HPUXIOTreeIndicationProviderModule
    root  1522  1513  0  Jan  6  ?         0:26 /opt/wbem/lbin/cimprovagt 0 5 10 root HPUXLANIndicationProviderModule
    root  1875     1  0  Jan  6  ?         0:05 /opt/wbem/lbin/cimserverd
    root 19871  1513  0 11:02:50 ?         0:00 /opt/wbem/lbin/cimprovagt 0 5 9 root HPUXSASCSProviderModule
    root 19966  1513  0 11:02:57 ?         0:00 /opt/wbem/lbin/cimprovagt 0 5 9 root IOTreeModule
    root 19875  1513  0 11:02:50 ?         0:00 /opt/wbem/lbin/cimprovagt 0 5 9 root ComputerSystemModule
    root 19869  1513  0 11:02:50 ?         0:00 /opt/wbem/lbin/cimprovagt 0 5 9 root HPUXLANCSProviderModule
    root 19956  1513  0 11:02:57 ?         0:00 /opt/wbem/lbin/cimprovagt 0 5 9 root HPUXFCProviderModule
    root 19873  1513  0 11:02:50 ?         0:00 /opt/wbem/lbin/cimprovagt 0 5 9 root HPUXIOTreeCSProviderModule
    root 19883  1513  0 11:02:51 ?         0:00 /opt/wbem/lbin/cimprovagt 0 5 9 root HPUXRAIDSAProviderModule
    root 19872  1513  0 11:02:50 ?         0:00 /opt/wbem/lbin/cimprovagt 0 5 9 root HPUXFCCSProviderModule
    root 19870  1513  0 11:02:50 ?         0:00 /opt/wbem/lbin/cimprovagt 0 5 9 root HPUXRAIDSACSProviderModule
    root 19955  1513  0 11:02:57 ?         0:00 /opt/wbem/lbin/cimprovagt 0 5 9 root HPUXLANProviderModule
    root 19948  1513  0 11:02:56 ?         0:00 /opt/wbem/lbin/cimprovagt 0 5 9 root HPUXSASProviderModule
    root 19897  1513  0 11:02:51 ?         0:00 /opt/wbem/lbin/cimprovagt 0 5 9 root HPUXSCSIProviderModule
    root 19874  1513  0 11:02:50 ?         0:00 /opt/wbem/lbin/cimprovagt 0 5 9 root HPUXSCSICSProviderModule
    root 26729 26097  1 11:15:50 pts/1     0:00 grep cim

 

uatdata1 /#ps -ef |grep -i cimserver|grep -v grep
 cimsrvr  1514  1513  0  Jan  6  ?         7:15 cimservermain --executor-socket 5
    root  1513     1  0  Jan  6  ?         0:32 /opt/wbem/lbin/cimserver
    root  1875     1  0  Jan  6  ?         0:05 /opt/wbem/lbin/cimserverd

 

uatdata1 /#uatdata1 /#cimprovider -l -s
MODULE                                  STATUS
OperatingSystemModule                   OK
ComputerSystemModule                    OK
ProcessModule                           OK
IPProviderModule                        OK
DNSProviderModule                       OK
NTPProviderModule                       OK
NISProviderModule                       OK
SDProviderModule                        OK
IOTreeModule                            OK
HPUXLVMProviderModule                   OK
AmgrAgentProviderModule                 OK
EMSHAProviderModule                     OK
HPUX_ProviderModule                     OK
HP_NParProviderModule                   OK
HP_ResParProviderModule                 OK
HPUXRAIDSAProviderModule                OK
HPUXRAIDSACSProviderModule              OK
HPUXSASProviderModule                   OK
HPUXSASCSProviderModule                 OK
HPUXSCSIProviderModule                  OK
HPUXSCSICSProviderModule                OK
HP_VParProviderModule                   OK
HPUXFCProviderModule                    OK
HPUXFCCSProviderModule                  OK
HPUXFCIndicationProviderModule          OK
FSProviderModule                        OK
HPUXIOTreeCSProviderModule              OK
HPUXLANProviderModule                   OK
HPUXLANCSProviderModule                 OK
HPUXLANIndicationProviderModule         OK
HP_iCODProviderModule                   OK
HP_iCAPProviderModule                   OK
HP_GiCAPProviderModule                  OK
HP_OLOSProviderModule                   OK
HP_UtilizationProviderModule            OK
HPVMProviderModule                      OK
SFMProviderModule                       OK
HPUXIOTreeIndicationProviderModule      OK
SGProvidersModule                       OK

 

uatdata1 /#uatdata1 /#cimserver -v
A.02.07.02
uatdata1 /#

 

grep cimserver /var/adm/syslog/syslog.log
Jan  6 14:24:03 uatdata1 cimserver[1511]: starting
Jan  6 14:24:24 uatdata1 cimserver[1514]: PGS10026:  The CIM server is listening on HTTPS port 5,989.
Jan  6 14:24:24 uatdata1 cimserver[1514]: PGS10028: The CIM server is listening on the local connection socket.
Jan  6 14:24:24 uatdata1 cimserver[1514]: PGS10030:  Started HP-UX WBEM Services version A.02.07.02.
Jan  7 02:10:38 uatdata1 cimserver[1514]: PGS17200: Authentication failed for user root.
Jan 12 10:31:18 uatdata1 cimserver[1514]: PGS17200: Authentication failed for user root.
Jan 12 10:31:26 uatdata1 cimserver[1514]: PGS17200: Authentication failed for user root.
Jan 12 14:17:37 uatdata1 cimserver[1514]: PGS17200: Authentication failed for user root.
Jan 12 14:17:45 uatdata1 cimserver[1514]: PGS17200: Authentication failed for user root.
Jan 12 14:25:40 uatdata1 cimserver[1514]: PGS17200: Authentication failed for user root.
Jan 12 14:25:48 uatdata1 cimserver[1514]: PGS17200: Authentication failed for user root.
Jan 13 11:28:46 uatdata1 cimserver[1514]: PGS17200: Authentication failed for user root.
Jan 13 11:28:54 uatdata1 cimserver[1514]: PGS17200: Authentication failed for user root.
Jan 14 02:11:37 uatdata1 cimserver[1514]: PGS17200: Authentication failed for user root.
Jan 14 02:12:05 uatdata1 cimserver[1514]: PGS17200: Authentication failed for user root.

 

So,

Why  this message come again and again.

 

How can resolved the problem or stop the error message.

Thanks

 

Thanks
aamir uddin
Henry Fauni
Valued Contributor

Re: stopped the cim service on all servers

You may not be aware of it, but you may have an external HP SIM Server configured in your environment (not uatdata1!). In our environment we have a Windows HP SIM Server, and our Windows system administrator set it up to auto-discover other nodes. This in turn tried to add all our HP-UX hosts in the HP SIM Server database. Depending on how often the host polling was set up in the HP SIM Server (not uatdata1, but an external HP SIM Server), it will attempt to login to the HP-UX host using webem/snmp/ssh or whatever authentication was configured. If the root password was not entered correctly, then you will see thoses messages on your syslog.log.