Hi Naveen, With your sample configuration, if second enclosure is not discovered, then. Could you please let us know the OpenHPI version and OS details.
Thanks& Regards, Hemantha Reddy ________________________________________ From: Shivegowda, Naveen (NSN - IN/Bangalore) [[email protected]] Sent: Monday, July 23, 2012 2:53 PM To: Beecherla, Hemantha Cc: [email protected] Subject: RE: [Openhpi-devel] Reg. openhpi daemon in case of HP Blade servers Hi, The below shown is an sample configuration that I have in which the entity no is diff. for both the enclosures: handler liboa_soap { entity_root = "{SYSTEM_CHASSIS,1}" OA_User_Name = "Administrator" # OA user name with admin privileges (required) OA_Password = "yt_xk39b" # OA password for above user (required) ACTIVE_OA = "10.255.14.50" # Active OA hostname or IP address (required) # STANDBY_OA = "hostname" # Standby OA hostname or IP address (optional) } handler liboa_soap { entity_root = "{SYSTEM_CHASSIS,2}" OA_User_Name = "user" # OA user name with admin privileges (required) OA_Password = "password" # OA password for above user (required) ACTIVE_OA = "10.255.14.70" # Active OA hostname or IP address (required) # STANDBY_OA = "hostname" # Standby OA hostname or IP address (optional) } Regards Naveen S -----Original Message----- From: ext Beecherla, Hemantha [mailto:[email protected]] Sent: Monday, July 23, 2012 6:43 PM To: [email protected] Subject: Re: [Openhpi-devel] Reg. openhpi daemon in case of HP Blade servers Hi Naveen, In the configuration file, while configuring with multiple enclosures make sure that the entity number is unique as in example below. ex:- handler liboa_soap { entity_root = "{SYSTEM_CHASSIS,1}" OA_User_Name = "User" # OA user name with admin privileges (required) OA_Password = "Password" # OA password for above user (required) ACTIVE_OA = "X.X.X.X" # Active OA hostname or IP address (required) STANDBY_OA = "X.X.X.X" # Standby OA hostname or IP address (optional) } handler liboa_soap { entity_root = "{SYSTEM_CHASSIS,2}" OA_User_Name = "User" # OA user name with admin privileges (required) OA_Password = "Password" # OA password for above user (required) ACTIVE_OA = "X.X.X.X" # Active OA hostname or IP address (required) STANDBY_OA = "X.X.X.X" # Standby OA hostname or IP address (optional) } Thanks& Regards, Hemantha Reddy ________________________________ From: Shivegowda, Naveen (NSN - IN/Bangalore) [[email protected]] Sent: Monday, July 23, 2012 1:15 PM To: [email protected] Subject: [Openhpi-devel] Reg. openhpi daemon in case of HP Blade servers Hi, I had configured 2 OA's(from diff. enclosure's) and tried the hpiinv command, the command is failing to retrieve the information form 2nd OA always. In the first attempt, OpenHpi daemon exited with the following errors: Jul 19 20:20:52 blr04 openhpid: transport: strmsock.cpp:514: accept failed. Jul 19 20:21:01 blr04 openhpid: oa_soap: oa_soap_hotswap.c:400: oa_soap_set_autoinsert_timeout is not supported Jul 19 20:21:01 blr04 openhpid: oa_soap: oa_soap_hotswap.c:401: Default auto insert timeout is IMMEDIATE and read only Jul 19 20:21:01 blr04 openhpid: openhpid: plugin.c:593: Cannot propagate auto-insert timeout to handler. Jul 19 20:21:09 blr04 openhpid: oa_soap: oa_soap_hotswap.c:400: oa_soap_set_autoinsert_timeout is not supported Jul 19 20:21:09 blr04 openhpid: oa_soap: oa_soap_hotswap.c:401: Default auto insert timeout is IMMEDIATE and read only Jul 19 20:21:09 blr04 openhpid: openhpid: plugin.c:593: Cannot propagate auto-insert timeout to handler. Jul 19 20:22:34 blr04 openhpid: oa_soap: oa_soap_event.c:164: oa->server is NULL. Exiting the thread Jul 19 20:24:13 blr04 openhpid: openhpid: server.cpp:227: 0x1145940 Error or Timeout while reading socket. Jul 19 20:24:13 blr04 openhpid: openhpid: server.cpp:227: 0x11458f0 Error or Timeout while reading socket. And from the next attempt onwards, daemon is not exiting but it is not able to retrieve the information the 2nd OA. Errors: Jul 20 10:09:26 blr04 openhpid: ssl: oh_ssl.c:466: BIO_new_ssl_connect() failed Jul 20 10:09:26 blr04 openhpid: oa_soap: oa_soap_callsupport.c:644: oh_ssl_connect() failed Jul 20 10:09:26 blr04 openhpid: oa_soap: oa_soap_callsupport.c:1087: failed to communicate with OA during soap_call() Jul 20 10:09:26 blr04 openhpid: oa_soap: oa_soap_utils.c:657: Get OA status call failed Jul 20 10:09:26 blr04 openhpid: oa_soap: oa_soap_utils.c:856: check oa_status has failed for - 10.255.14.70 Jul 20 10:09:26 blr04 openhpid: oa_soap: oa_soap_discover.c:246: Discovery failed for OA 10.255.14.70:443 Both the OA's were in pingable state. Regards Naveen S ------------------------------------------------------------------------ ------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Openhpi-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openhpi-devel ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Openhpi-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openhpi-devel
