There is a known bug in solaris 10. Try restarting picld. The fix is combo of firmware upgrade to 7.31b (obp 4.30 IIRC - I will verify) and update solaris to current. Your obp/ilom doesn' have ldom 2.0
________________________________ From: Manek, Joe A (SAIC) <[email protected]> To: Hudes, Dana; [email protected] <[email protected]> Sent: Thu Apr 28 13:41:18 2011 Subject: RE: [ldoms-discuss] Non-responsive ldm interface 'prtdiag -v' hangs just like 'ldm' commands do. The best I have is from a console history on our Servial Console Server from (auspicisously) 9/11/2010, but I believe it to still be current. 7, "2010-09-11 14:22:59", "> ", " hypervisor_version = Hypervisor 1.7.9 2010/07/19 15:51" 7, "2010-09-11 14:22:59", "> ", " obp_version = OBP 4.30.9 2010/07/16 09:06" 7, "2010-09-11 14:22:59", "> ", " post_version = POST 4.30.9 2010/07/16 09:40ersion = POST 4.30.9 2010/07/16 09:40 ________________________________ From: Hudes, Dana [mailto:[email protected]] Sent: Thursday, April 28, 2011 8:59 AM To: Manek, Joe A (SAIC); '[email protected]' Subject: Re: [ldoms-discuss] Non-responsive ldm interface Which OBP? Prtdiag -v from control ldom. ________________________________ From: [email protected] <[email protected]> To: [email protected] <[email protected]> Sent: Thu Apr 28 12:45:59 2011 Subject: [ldoms-discuss] Non-responsive ldm interface Hello all, I have one of my T5240's which decided to not talk via it's serial or network mgmt interfaces. This seemed to occur suspiciously during a recycle of our Cisco/Lantronix Terminal Server. Don't know if something nasty was inadvertenly sent along the serial connection causing problems in the Serial Mgmt interface, but now I'm no longer able to do a 'prtdiag -v' on the Control-LDOM or do any 'ldm' which appears to need to access the Hypervisor. For instance, trival commands such as 'ldm ls' or 'ldm -V' work fine, but an 'ldm -l' hangs. I'm also now unable to ssh or http to the Service Processor. Debugging the ssh connection attempts show it does connect but doesn't actually complete the connection conversation. The Global-Zone on Control-LDOM functions w/o issue as do all the Guest-LDOMs and virtualized resources. Essentially I'm now flying blind with no console access to Service Processor and no way to interrogate/modify any LDOM configuration via 'ldm'. Short of a hard-power cycle, this is a production box, anybody know of any tricks/techniques to kick the Service Processor in the butt and restart it w/o the aforementioned power cycle? Thanks, Joe.
_______________________________________________ ldoms-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
