Looks like this bug;
*libpiclsnmp:snmp_init()* Blocks Indefinitely in *open()* on
primary Domain
*Bug ID 6736962:* Power Management sometimes fails to retrieve policy
from the service processor on LDoms startup after the control domain
boots. If CPU power management could not retrieve the power management
policy from the service processor, it allows LDoms to start up as
expected, but logs the error Unable to get the initial PM Policy -
timeout to the LDoms log and remains in performance mode.
Add forceload: drv/ds_snmp to /etc/system, then reboot the control domain.
There was a ton of messages in the the ldmd log about pmi timeouts.
While the customer tried the add forceload it was still having issues.
Verified that the ds_snmp was loaded via modinfo but still having issues.
They made a couple of changes via the BUI on the SP and magically it
started to work and we are not sure why.
One was to make sure the DNS entry was set correctly on the SP as it was
never reset after a static address was used for the SP.
The other was a change to the syslog ip which was blank and they set it
to 0.0.0.0, both of these settings were copied from another
5440 that was working ok.
Not sure if there was any other changes.
Regards
Gary
On 4/13/2010 8:28 AM, Gary Andresen wrote:
Thanks.
So 4 Gig is still recommended for zfs then. I thought 2Gig was
adequate now days.
I give it a tweak.
Regards
Gary
On 4/12/2010 9:59 PM, Octave Orgeron wrote:
Hi,
If you are using ZFS as the file system in the control domain, I
would allocate atleast 4GB of memory to allow enough space for the
ZFS ARC. There is also a tunable to control the size of the ARC, take
a look at the ZFS guide on solarisinternals.com. Another possible
area is the network settings in the link aggregation on the server or
switch side.
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Octave J. Orgeron
Solaris Virtualization Architect and Consultant
Web: http://unixconsole.blogspot.com
E-Mail: [email protected]
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
----- Original Message ----
From: Gary Andresen<[email protected]>
To: [email protected]
Sent: Mon, April 12, 2010 9:32:41 PM
Subject: [ldoms-discuss] ldm list -l primary takes ~30 secs to return
Still trying to track down whats happening at a customer site, but
right now on a T5440 box with 2 CPUs 32 gig of memory and setting the
control domain
to 1 core (8 threads) and 2g of memory, 1 MAU with Solaris 10 U8 with
latest patch cluster,Latest Firmware 139446-10, boot disk is a zfs
pool mirrored.
Network is a aggregate of nxge0 and 4 I believe and vsw0 was created by
ldm add-vsw net-dev=arrg1 primary-vsw0 primary
unplumbed aggr1
plumbed vsw0 in it's place.
All seemed to be going well but;
Running 'ldm list -l primary' takes up to 20-30 secs to printout
data. No errors that they can see (dmesg, /var/adm/messages).
Missing patch? Ideas?
Gary
_______________________________________________
ldoms-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
_______________________________________________
ldoms-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
_______________________________________________
ldoms-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
