V20z service processor

Before I call Sun, I thought I'd ask here:
I have a brand new SunFire v20z that I am trying to manage remotely. I had no problem getting the service processor set up and connecting to it, and I was able to access it for several days. It worked fine.
Then I went away for a few days, and when I returned, the SP had very slow response, and randomly started hanging up on me and killing the running command. I thinbk
bash-2.03$ ssh -l spuser 10.0.0.7
spuser@10.0.0.7's password:
Sun Microsystems
IPMI v1.5 Service Processor
Version: V2.0.0.48
localhost $ help
help: not found
localhost $ platform help<br />Killed<br />localhost $ sp help
Connection to 10.0.0.7 closed.
What made the SP so sick? Any ideas? TIA
Jeremiah

I had this on a V20z. It seemed to start intermittently a few days ago but this evening it was doing it consistently. It was doing it when trying to use SP commands 'platform console' and 'sp get events', though 'sp reboot' did work and thankfully seems to have cleared the problem.
The SP reboot was necessary as a last resort because I had some planned work to do in an agreed outage and needed to boot the server a few times, so needed proper console access, i.e. I needed to sort out the SP problem to allow console access which we reach via the SP.

Similar Messages

  • Service Processor Issues v20z

    Apologies if this question is in the wrong forum, although I believe it is a hardware related issue.
    My issue relates to the Service Processor on a v20z. Basically, it seems to reset itself every few minutes and will not retain any information at all, which intern has caused the fans to stay on at 100%, all the time now, which is concerning. Once on it says "Main power off". The SP will then reset itself not long after.
    This started when I decided to rebuild one of our V20z servers, as Solaris 10 did not like the raid card when in it's early versions. Anyway, I have successfully installed the latest Solaris 10 build, 1/06 X86 (of course seeing the Athlon cpu's). After this I felt the need to get console working properly, as it was not before. I changed the eeprom as documented with the input and output pointing to the console.
    At this point I decided I should get the Service Processor working, as I had not read anything about it previously. I managed to manually assign it an ip address, which it kept. I then had to reboot the server for other reasons, and the SP would not keep its IP details. It will not even obtain one via dhcp, comes up with "Service Error on set IP DHCP".
    I have tried updating the bios etc, by manually entering in the information on the lcd screen, however have had to such luck either. I have a funny feeling I have broken something as there does not appear to be anyone with the same type of issues. From everything I have read everyone else seems to have no issues at all. Some advice would be greatly appreciated, as I've been tearing my hair out for a few days now over it.
    Many Thanks
    Simon

    It's ok I figured it out. Embarasingly simple really
    eeprom output-device=ttya
    eeprom input-device=ttya
    This is awesome, just look at this. I'm twenty miles from the server booted in single user mode.
    Yes, more sleep time for me less late nights at the office. Sorry if this is old hat to you guys, It's the first time I've seen it on any servers I've owned.
    Select (b)oot or (i)nterpreter: b -s
    SunOS Release 5.9 Version Generic_117172-17 32-bit
    Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    configuring IPv4 interfaces: bge0.
    Hostname: v20z1
    INIT: SINGLE USER MODE
    Type control-d to proceed with normal startup,
    (or give root password for system maintenance):
    single-user privilege assigned to /dev/console.
    Entering System Maintenance Mode
    Jun 22 22:52:10 su: 'su root' succeeded for root on /dev/console
    Sun Microsystems Inc. SunOS 5.9 Generic January 2003
    # ifconfig -a
    lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
    inet 127.0.0.1 netmask ff000000
    bge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
    inet 192.9.200.10 netmask ffffff00 broadcast 192.9.200.255
    ether 0:9:3d:11:c7:c0
    Nice one SUN...
    Pity I couldn't Install solaris 9 on the v20z's from the CDs in the first place though (I needed to install from an install server).

  • Service Processor on X4100 and 4200

    How can I send order from inside solaris 10 to the Service Processor on the X4100 and 4200 ?
    We use the serial consol to log messages from the system (helpful for crash or panic), but with the X4100 or 4200 the service processor manage the serial link and we have to do 'login' and start /SP/console to get solaris 10 console.
    I would like to automatically start the console from inside solaris if it's not started or to configure the SP in console automatically after a power-on.
    Thanks

    Thanks, I granted the user with permission sysadmin, but still I am facing the problem.
    Let me download SP3 and SP4, if that could solve my problem.
    Hello,
    Please refer to below blog,See workaround mentioned in below blog.I am quite sure this would be fixed in SP3 or SP4 but first please apply this workaround and then install SP4.
    Unable to start SQL server agent
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • SMC agent on M9000 service processor

    Hi, I'm trying to monitor an M9000 Platform
    at this time domain agents are up and running but the service processor agent's is stopped and I can't find how to start it.
    this is the output from setsunmc and showsunmc
    XSCF> setsunmc -s 140.126.65.82 -z segob -c public -p 1161 -t 162 -e 163 -a 161 -d 1161
    setsunmc: Updating Sun MC config file
    XSCF> showsunmc
    Agent Status: Disabled, stopped
    Setup Status: Set up
    SunMC Server: 140.126.65.82
    Security Seed: segob
    SNMPv1 Community String: public
    Agent Port: 1161
    Host Trap Port: 162
    Host Event Port: 163
    SNMP Agent Port: 161
    Domain Agent Port: 1161
    XSCF> setsunmc enable
    setsunmc: Agent enabled.
    setsunmc: Note that this command will return before SunMC is completely enabled.
    XSCF> showsunmc
    Agent Status: Enabled, stopped
    Setup Status: Set up
    SunMC Server: 140.126.65.82
    Security Seed: segob
    SNMPv1 Community String: public
    Agent Port: 1161
    Host Trap Port: 162
    Host Event Port: 163
    SNMP Agent Port: 161
    Domain Agent Port: 1161
    Do you have any clue why Agent won't start?
    Thanks for any comment

    Dear Sir,
    I also have this problem on our M9000. And I have set and enabled the SNMP then set and enable SunMC, but the Agent status is still "Enabled,Stopped". Please refer to below information and check what's wrong for me, thanks a lot.
    XSCF> setsunmc disable
    setsunmc: Agent disabled.
    setsunmc: Note that this command will return before SunMC is completely disabled.
    XSCF> setsnmp disable
    setsnmp: Agent disabled.
    XSCF> setsnmp enable
    setsnmp: Agent enabled.
    XSCF> setsunmc enable
    setsunmc: Agent enabled.
    setsunmc: Note that this command will return before SunMC is completely enabled.
    XSCF> showsnmp
    Agent Status: Enabled
    Agent Port: 161
    System Location:
    System Contact:
    System Description: SMP HPC of SPARC Enterprise M9000-64
    Trap Hosts:
    Hostname Port Type Community String Username Auth Protocol
    192.168.1.100 162 v2 public n/a n/a
    SNMP V1/V2c:
    Status: Enabled
    Community String: public
    Enabled MIB Modules:
    SP MIB
    FM MIB
    XSCF> showsunmc
    Agent Status: Enabled, stopped
    Setup Status: Set up
    SunMC Server: 192.168.1.100
    Security Seed: 1211
    SNMPv1 Community String: public
    Agent Port: 1161
    Host Trap Port: 162
    Host Event Port: 163
    SNMP Agent Port: 161
    Domain Agent Port: 8161
    Edited by: Yu-Hung on Apr 1, 2008 12:31 AM
    Edited by: Yu-Hung on Apr 1, 2008 12:35 AM

  • HELP! SUNFIRE x2100 M2 server service processor problem,,,,,

    i got a problem with my x2100m2 server,
    the service processor doesn't seem to start
    at all, even if at standy power.
    the OK led in the front panel doesn't seem
    to flash.
    wats the possible problems with my server??

    try to remove power cables wait around 3 minutes plug it again you should have output if no try to power on the server
    are you connecting to serial mgt make sure u r having the right config for serial conx . 9600 8 N 1
    Edited by: yishak on Mar 2, 2009 2:28 AM

  • SSH from service processor to host os (Solaris 10) on V20z?

    Hi all,
    when I try to ssh from the service console to the host os, which is Solaris 10, I get the error message:
    /etc/ssh/ssh_config line 19: garbage at end of line; "1".
    Any ideas?
    Thanks

    Seems like there is something wrong in the ssh_config file, most likely on line 19, you should have a look on that line and see what it says..

  • Using SOL from Service Processor on SunFire 20

    I'm trying to get a remote console on a server gone bad; Using SOL I can see bios boot, and grub loading. And I can use Grub to change kernel parameters, where I add "console=ttyS0,9600 console=tty0" as per the manual.
    Problem is, that everything freezes after that. nothing gets to my screen and the server still doesn't boot.
    I need a few pointers to where the problem could be?? I've tried booting to recovery mode, text mode etc. and nothing helps. I don't even see the kernel loading. Even worse, the recovery CD simply gives me a blank screen on the console too.
    I'm a bit desperate. Any ideas?

    Hello FSCHU,
    The path to maintain the subject is as follows.
    CRM --> Basic Functions --> Catalogs,Codes&Profiles.
    The subject profile SLFN0001contains Catalog, and the catalogue contains code groups. This code groups is linked to subject entries of the fast entry screens..
    Let me know if this answer has solved your issue.
    Rgds,
    Sri

  • NWSnps for solaris 10 on V20z ?

    Is there a NWSnps package (V20z AMD 64 bit ) for Solaris 10 or should I just use
    the Solaris 9 one?
    More info on NWSnps can be found at:
    http://sunportal.sunmanagers.org/pipermail/summaries/2005-February/006173.html

    By the way: before installing the NWSnps package (which is the Solaris driver for the service processor, everything worked with DHCP.

  • Solaris 10 on V20z - Help!!!

    Hi all,
    I installed S10 (06/2005) on a V20z with bge0 using DHCP.
    I also installed the necessary BIOS and service processor as well as the 64-bit NWSnps package.
    After rebooting I het the message:
    Failed to configure IPv4 DHCP on interface(s) bge0
    I cant get rid of this problem.
    Any ideas, what's going on?
    Thanks

    By the way: before installing the NWSnps package (which is the Solaris driver for the service processor, everything worked with DHCP.

  • Windows Deployment Service corrupts \systemroot\system32\config\software in images.

    Hello,
    Recently we have upgraded to Server 2012 R2 to handle our WDS services but some images are not deploying correctly. 
    When checking the event log on the machines that do not deploy correctly, the following error message is discovered: "\systemroot\system32\config\software was corrupted and it has been recovered'
    We can restore the SOFTWARE registry backup from the regback folder and this corrects the problem, but this has to be done after the image is deployed and takes a lot of time.
    The WIM files all deploy fine in all instances of deployment on Server 2008 R2, using DISM directly and ImageX.
    For one image, this only occurs on certain machines.  It has been tested on 3 Z200 with the same hardware setup and the error occurs on 2 consistently and does not occur on the 3rd.
    On another one of the images, this error occurs every time it is deployed using Server 2012 R2 but never when deployed using WDS on Server 2008 R2, DISM or ImageX.
    This occurs whether the deployment is set attended or unattended. The majority of deployments have been tested without using an unattended file to eleminate variables.
    Does anyone have any suggestions? Any ideas would be appreciated.
    Edit:
    We have also exported the WIM file of the image that always "breaks" from WDS 2012 R2 and successfully deployed it every time using 2008R2 WDS DISM and ImageX. 
    We have created separate folders for these problem WIM files so that the RES file only contains the information from the specific WIM that is having problems; this does not fix the problem. 
    Edit 2:
    There is an error in setupact.log but it onlys says that the mentioned registry setting is malformed or corrupt. I tried a web search on this and had results but the majority of the answers were related to errors sysprepping. 
    Starting WDS GUI
    2014-02-12 16:47:07, Warning    [0x0a0180] UI     Failed to change the UI language to en-US.
    2014-02-12 16:47:22, Error      [0x0a0052] UI     Failed to read image data from blackboard[gle=0x00000002]
    2014-02-12 16:47:29, Warning    [0x07008d] DIAG   Win32_Processor : CoInitializeEx returned RPC_E_CHANGED_MODE. Continue. Error code = 0x80010106
    2014-02-12 16:47:31, Warning    [0x070026] DIAG   Win32_Processor : Unable to retrieve Stepping, vtType = 8. Error code = 0x0
    Setting up disk
    2014-02-12 16:47:51, Warning    [0x0606cc] IBS    DeleteFileEx: Unable to clear out attributes on [D:\$WINDOWS.~BT\Sources\Rollback\bootsec.dat]; GLE = 0x2
    2014-02-12 16:47:51, Warning               WDS    CallBack_WdsClient_MulticastCopyFiles: Error transferring files. Falling back to unicast. Error [0x80070002]
    2014-02-12 16:47:51, Warning    [0x0b0095] WDS    CallBack_WdsClient_MulticastCopyFiles: Multicast transfer failed. Error code [0x80070002].
    Active Dir Setup
    2014-02-12 17:11:21, Info       [0x0b0083] WDS    MgLibpOpenLdapConnectionFromDN: DN=
    2014-02-12 17:11:21, Error      [0x0b00c2] WDS    [
    2014-02-12 17:11:21, Info       [0x0b00c2] WDS    <
    2014-02-12 17:11:21, Error      [0x0b00c2] WDS    [
    2014-02-12 17:11:21, Info       [0x0b00c2] WDS    <
    2014-02-12 17:11:21, Error      [0x0b00c2] WDS    [
    2014-02-12 17:11:21, Info       [0x0b007e] WDS    ProcessDomainJoinInformation: MachineName = [(null)], MachineDomain = [(null)]
    2014-02-12 17:11:21, Warning    [0x0b0093] WDS    ProcessDomainJoinInformation: Error resetting machine account. Error [0x80070057].
    2014-02-12 17:11:21, Error      [0x0b00c2] WDS    [
    Set up IBSLIB
    2014-02-12 17:12:39, Info                  IBSLIB Copying files from D:\Windows\Boot\PCAT\en-US to \\?\GLOBALROOT\Device\HarddiskVolume3\Boot\en-US...
    2014-02-12 17:12:39, Info                  IBSLIB SetNamedSecurityInfo failed! Error code = 0x2
    2014-02-12 17:12:39, Info                  IBSLIB Unable to open file \\?\GLOBALROOT\Device\HarddiskVolume3\Boot\en-US\bootmgr.exe.mui for read because the file or path does
    not exist
    2014-02-12 17:12:39, Info                  IBSLIB SetNamedSecurityInfo failed! Error code = 0x2
    2014-02-12 17:12:39, Info                  IBSLIB Unable to open file \\?\GLOBALROOT\Device\HarddiskVolume3\Boot\en-US\memtest.exe.mui for read because the file or
    2014-02-12 17:12:39, Warning               IBSLIB Resource files missing from D:\Windows\Boot\Resources. These files are required for some editions of Windows. If you are servicing older
    versions of Windows, you can ignore this message.
    Sysprep Plug N Play
    2014-02-12 17:14:54, Info                  SYSPRP SPPNP: Removing the devices that are using service mpio ...
    2014-02-12 17:14:54, Info                  SYSPRP SPPNP: The device Root\LEGACY_MPIO\0000 is using the service mpio.
    2014-02-12 17:14:54, Warning               SYSPRP SPPNP: Error 0xE000020B occurred while adding device Root\LEGACY_MPIO\0000 to the device info set.
    2014-02-12 17:14:54, Info                  SYSPRP SPPNP: Finished removing the devices that are using service mpio.
    Sysprep specalize
    2014-02-12 17:18:11, Info       [0x0f008a] SYSPRP RunRegistryDlls:Retrieved section name for this phase as Specialize
    2014-02-12 17:18:11, Warning    [0x0f008f] SYSPRP RunRegistryDlls:Registry key is either empty or malformed: SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\SysPrepExternal\Specialize
    2014-02-12 17:18:11, Info                  IBS    Callback_Specialize: External Providers Specialized Succeeded
    Modify boot entries (Non UFI)
    2014-02-12 17:18:15, Info       [0x0606cc] IBS    Flushing registry to disk...
    2014-02-12 17:18:17, Info       [0x0606cc] IBS    Flush took 1201 ms.
    2014-02-12 17:18:17, Info       [0x06036b] IBS    Callback_SystemRestore: Successfully set System Restore state.
    2014-02-12 17:18:17, Info       [0x0606cc] IBS    GetSystemPartitionNTPath: Found system partition at [\Device\HarddiskVolume1].
    2014-02-12 17:18:17, Warning    [0x0606cc] IBS    GetSystemPartitionPath: Unable to find DOS drive path for system partition [\Device\HarddiskVolume1].
    2014-02-12 17:18:17, Info       [0x0606cc] IBS    GetSystemPartitionNTPath: Found system partition at [\Device\HarddiskVolume1].
    2014-02-12 17:18:17, Warning    [0x0606cc] IBS    GetSystemPartitionPath: Unable to find DOS drive path for system partition [\Device\HarddiskVolume1].
    2014-02-12 17:18:17, Warning               IBSLIB ModifyBootEntriesLegacy: There was an error getting the path to the boot.ini or ntldr. dwRetCode=[0x1F]
    2014-02-12 17:18:17, Warning               IBSLIB ModifyBootEntriesLegacy: We did not successfully complete ModifyBootEntriesLegacy.  This is non-fatal, continuing setup. dwRetCode[0x1F]
    Error in system log:
    Log Name:      System
    Source:        Microsoft-Windows-Kernel-General
    Date:          2/12/2014 5:14:28 PM
    Event ID:      5
    Task Category: None
    Level:         Error
    Keywords:     
    User:          SYSTEM
    Computer:     
    Description:
    {Registry Hive Recovered} Registry hive (file): '\SystemRoot\System32\Config\SOFTWARE' was corrupted and it has been recovered. Some data might have been lost.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Microsoft-Windows-Kernel-General" Guid="{}" />
        <EventID>5</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x8000000000000000</Keywords>
        <TimeCreated SystemTime="2014-02-13T01:14:28.620907400Z" />
        <EventRecordID>12326</EventRecordID>
        <Correlation />
        <Execution ProcessID="4" ThreadID="364" />
        <Channel>System</Channel>
        <Computer>COMPUTERNAME</Computer>
        <Security UserID="S-1-5-18" />
      </System>
      <EventData>
        <Data Name="FinalStatus">0x8000002a</Data>
        <Data Name="ExtraStringLength">36</Data>
        <Data Name="ExtraString">\SystemRoot\System32\Config\SOFTWARE</Data>
      </EventData>
    </Event>
    Sysprep Panther Log:
    2014-02-12 14:39:58, Warning    [0x0f008f] SYSPRP RunRegistryDlls:Registry key is either empty or malformed: SOFTWARE
    \Microsoft\Windows\CurrentVersion\Setup\SysPrepExternal\Cleanup
    2014-02-12 14:39:58, Warning    [0x0f008f] SYSPRP RunRegistryDlls:Registry key is either empty or malformed: SOFTWARE
    \Microsoft\Windows\CurrentVersion\Setup\SysPrepExternal\Generalize
    2014-02-12 14:40:10, Warning                      TapiSysPrep.dll:RetainTapiLocations:RegQueryValueEx() returned 2
    2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service vhdmp was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service VMBusHID was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service Brserid was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service usbcir was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service usbccgp was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service usbhub was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service USBSTOR was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service sffdisk was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service vpcbus was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service umbus was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service swenum was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service rdpbus was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:15, Warning               SYSPRP SPPNP: The original start type of service iScsiPrt was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:15, Warning               SYSPRP SPPNP: The original start type of service CompositeBus was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:15, Warning               SYSPRP SPPNP: The original start type of service circlass was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:15, Warning               SYSPRP SPPNP: The original start type of service ebdrv was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:15, Warning               SYSPRP SPPNP: The original start type of service b06bdrv was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:15, Warning               SYSPRP SPPNP: The original start type of service s3cap was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:15, Warning               SYSPRP SPPNP: The original start type of service 1394ohci was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service usbehci was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service usbohci was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service usbuhci was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service ohci1394 was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service HDAudBus was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service BrUsbMdm was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service BrSerWdm was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service HidBatt was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service MTConfig was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service mouhid was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service kbdhid was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service sfloppy was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service usbprint was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service HidUsb was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service UmPass was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service HidIr was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service HidBth was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service BTHMODEM was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service hcw85cir was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service WacomPen was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service Processor was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service IPMIDRV was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service intelppm was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service AmdK8 was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service AmdPPM was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service AcpiPmi was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service CmBatt was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service sermouse was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service ErrDev was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service WmiAcpi was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service flpydisk was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service fdc was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service Parport was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service pcmcia was not found in its expected back-up location. Hence we will not be re-enabling this service.
    This is not necessarily an error.
    2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service i8042prt was not found in its expected back-up location. Hence we will not be re-enabling this
    service. This is not necessarily an error.

    We have discovered that this is only happening to target computers with installed
    RAM greater than 4gb. If the machine has greater than 4gb of RAM, the mentioned corruption occurs. If the machine has
    4gb or less, the corruption does not occur. We still have not found a fix for this, (besides removing the excess RAM during imaging and reinstalling after.)  Any ideas/thoughts would be helpful! Thank you in advance.

  • Trying to create an abstract service that supports both DataService(LCDS) and RemoteObject

    I am trying to create a generic service processor in ActionScript that would be able to use a DataService(from LCDS) or a RemoteObject, depending on a property setting. The intent is to be able to change a setting during installation to control whether DataServices would be used, or RemoteObjects. I understand that the server side logic would need to be written differently for each of the implementations.
    The challenge is that accessing a DataService is synchronous, but a RemoteObject access is asynchronous.
    For the synchronous access, I can just call a service and return the result directly to an object which can be passed back to the client.
    For the asynchronous support, extra code must be written on the client side to listen for the return of a requested result (for example, the results of a database quesy). This code must be placed outside of the service itself, thus making the generic service non-generic.
    Are there any examples available that accomplish what I am trying to do?

    Hi. As far as I know both DataService and RemoteObject are asynchronous APIs. If you call a DataService method such as fill() or call a method on your RemoteObject, code in your Flex application will continue to execute and the result from the RemoteObject or DataService request will be received asynchrounously. I don't believe there is any way currently to make synchronous or blocking calls in Flex because of the Flash Player's execution model.
    How are you planning on using the DataService and RemoteObject in your application? Is it to do something like populate a DataGrid? Do you plan on updating the data retrieved from the DataService or RemoteObject such as adding, updating or deleting records?
    The DataService API is much more powerful than the RemoteObject API, in that if you bind an ArrayCollection that is populated from a DataService to your DataGrid, when you update data in the DataGrid, the data on the server is updated and all other clients that have the same view of the data will also get the updates. You don't currently get this functionality with RemoteObjects.
    My point here is that if you wanted to write an abstract service that supports both DataService and RemoteObject and you need to be able to add, update or delete records you are going to need to write a lot of custom code to listen for collection change events when data on the client is modified and translate these change events into RemoteObject requests. Even if you did do that, other clients would not get these updates.
    If all you want to do is something simple like populate a DataGrid with data from the DataService or RemoteObject, then sure, writing an abstraction layer on the client that supports both of these wouldn't be hard.  
    -Alex

  • Luactivate 'succeeds' but then new BE does not show up in GRUB menu

    Hi,
    I'm trying to do a live upgrade from S10 u6 to u7.
    The machine is a Sun v20z (which is an x64 box).
    The only file system is ZFS, which consists of two drives that forming one pool, "rpool".
    I use the Service Processor/LOM over SSH to monitor the status of the console and GRUB menu.
    I did everything as directed and everything seemed to check out OK, but no matter what, the new BE never shows up on the GRUB menu! It's driving me nuts! PLEASE HELP!
    lola@sol10box:~$ sudo lucreate -n s10_u7        
    lola@sol10box:~$ sudo pkgadd -d /mnt/Solaris_10/Product SUNWluu SUNWlur
    lola@sol10box:~$ sudo lustatus
    Boot Environment           Is       Active Active    Can    Copy     
    Name                       Complete Now    On Reboot Delete Status   
    s10x_u6wos_07b             yes      yes    yes       no     -        
    s10_u7                     yes      no     no        yes    -        
    lola@sol10box:~$ sudo luupgrade -u -n s10_u7 -s /mnt
    System has findroot enabled GRUB
    No entry for BE <s10_u7> in GRUB menu
    Copying failsafe kernel from media.
    Uncompressing miniroot
    Creating miniroot device
    miniroot filesystem is <ufs>
    Mounting miniroot at </mnt/Solaris_10/Tools/Boot>
    Validating the contents of the media </mnt>.
    The media is a standard Solaris media.
    The media contains an operating system upgrade image.
    The media contains <Solaris> version <10>.
    Constructing upgrade profile to use.
    Locating the operating system upgrade program.
    Checking for existence of previously scheduled Live Upgrade requests.
    Creating upgrade profile for BE <s10_u7>.
    Checking for GRUB menu on ABE <s10_u7>.
    Saving GRUB menu on ABE <s10_u7>.
    Checking for x86 boot partition on ABE.
    Determining packages to install or upgrade for BE <s10_u7>.
    Performing the operating system upgrade of the BE <s10_u7>.
    CAUTION: Interrupting this process may leave the boot environment unstable
    or unbootable.
    Upgrading Solaris: 100% completed
    Installation of the packages from this media is complete.
    Restoring GRUB menu on ABE <s10_u7>.
    Updating package information on boot environment <s10_u7>.
    Package information successfully updated on boot environment <s10_u7>.
    Adding operating system patches to the BE <s10_u7>.
    The operating system patch installation is complete.
    ABE boot partition backing deleted.
    PBE GRUB has no capability information.
    PBE GRUB has no versioning information.
    ABE GRUB is newer than PBE GRUB. Updating GRUB.
    GRUB update was successfull.
    Configuring failsafe for system.
    Failsafe configuration is complete.
    INFORMATION: The file </var/sadm/system/logs/upgrade_log> on boot
    environment <s10_u7> contains a log of the upgrade operation.
    INFORMATION: The file </var/sadm/system/data/upgrade_cleanup> on boot
    environment <s10_u7> contains a log of cleanup operations required.
    INFORMATION: Review the files listed above. Remember that all of the files
    are located on boot environment <s10_u7>. Before you activate boot
    environment <s10_u7>, determine if any additional system maintenance is
    required or if additional media of the software distribution must be
    installed.
    The Solaris upgrade of the boot environment <s10_u7> is complete.
    Installing failsafe
    Failsafe install is complete.
    lola@sol10box:~$
    root@sol10box:/# luactivate s10_u7
    System has findroot enabled GRUB
    Generating boot-sign, partition and slice information for PBE <s10x_u6wos_07b>
    Saving existing file </etc/bootsign> in top level dataset for BE <s10x_u6wos_07b> as <mount-point>//etc/bootsign.prev.
    A Live Upgrade Sync operation will be performed on startup of boot environment <s10_u7>.
    Setting failsafe console to <ttya>.
    Generating boot-sign for ABE <s10_u7>
    Saving existing file </etc/bootsign> in top level dataset for BE <s10_u7> as <mount-point>//etc/bootsign.prev.
    Generating partition and slice information for ABE <s10_u7>
    Copied boot menu from top level dataset.
    Generating multiboot menu entries for PBE.
    Generating multiboot menu entries for ABE.
    Disabling splashimage
    No more bootadm entries. Deletion of bootadm entries is complete.
    GRUB menu default setting is unaffected
    Done eliding bootadm entries.
    The target boot environment has been activated. It will be used when you
    reboot. NOTE: You MUST NOT USE the reboot, halt, or uadmin commands. You
    MUST USE either the init or the shutdown command when you reboot. If you
    do not use either init or shutdown, the system will not boot using the
    target BE.
    In case of a failure while booting to the target BE, the following process
    needs to be followed to fallback to the currently working boot environment:
    1. Boot from Solaris failsafe or boot in single user mode from the Solaris
    Install CD or Network.
    2. Mount the Parent boot environment root slice to some directory (like
    /mnt). You can use the following command to mount:
         mount -Fzfs /dev/dsk/c1t0d0s0 /mnt
    3. Run <luactivate> utility with out any arguments from the Parent boot
    environment root slice, as shown below:
         /mnt/sbin/luactivate
    4. luactivate, activates the previous working boot environment and
    indicates the result.
    5. Exit Single User mode and reboot the machine.
    Modifying boot archive service
    Propagating findroot GRUB for menu conversion.
    File </etc/lu/installgrub.findroot> propagation successful
    File </etc/lu/stage1.findroot> propagation successful
    File </etc/lu/stage2.findroot> propagation successful
    File </etc/lu/GRUB_capability> propagation successful
    Deleting stale GRUB loader from all BEs.
    File </etc/lu/installgrub.latest> deletion successful
    File </etc/lu/stage1.latest> deletion successful
    File </etc/lu/stage2.latest> deletion successful
    Activation of boot environment <s10_u7> successful.
    root@sol10box:/#
    lola@sol10box:~$ sudo lustatus
    Password:
    Boot Environment           Is       Active Active    Can    Copy     
    Name                       Complete Now    On Reboot Delete Status   
    s10x_u6wos_07b             yes      yes    yes       no     -        
    s10_u7                     yes      no     no        yes    -        
    lola@sol10box:~$
    lola@sol10box:~$ sudo init 0
        GNU GRUB  version 0.95  (616K lower / 4127168K upper memory)               
    +-------------------------------------------------------------------------+   
    | Solaris 10 10/08 s10x_u6wos_07b X86                                     |   
    | Solaris failsafe                                                        |   
    |                                                                         |   

    What happens when you create a new BE using the current BE without any changes (just making a bootable copy of the current BE)? What is the results of cat /rpool/boot/grub/menu.lst? If you do a lufslist bootenvname, do all of the indicated filesystems actually exist?

  • Error.  Cannot install public key for specified user

    I'm getting "Error. Cannot install public key for specified user" when trying to add a public ssh key for a service processor user on a V20z. I've tried it for different users and still get the error. The same operation works fine on a V40z. Any help would be appreciated.

    That would be great if the resolution was that simple.  I am using a public key I generated using the putty key generator.  Below is the key I would use if I got that far.  However I get an error on the "ssh authentication publickey" attribute so I never get the chance to enter a public key.  What code version and hardware version are you running that this worked on?
    AAAAB3NzaC1yc2EAAAABJQAAAIEA2h00RCKBbpbrTWSe/3TYAvRpkJz7tLwQDCf9
    4fDJUWUGrmxXHeomuBhNGZh7tyfFjRL2CKY6nWmFyKN/eDm0PF4IWhhCArzOPVDu
    q7Nu2y/pD8wWH8dH4a3zRpkLSekNJtH6lzuqmY0zqz9TnZlpS6g4LI1a+lOGSmhU
    /HySw9s=
    ciscoasa(config)#username test nopassword privilege 15
    ciscoasa(config)#username test attributes
    ciscoasa(config-username)#ssh ?
    configure mode commands/options:
      Hostname or A.B.C.D  The IP address of the host and/or network authorized to
                           login to the system
      X:X:X:X::X/<0-128>   IPv6 address/prefix authorized to login to the system
      scopy                Secure Copy mode
      timeout              Configure ssh idle timeout
      version              Specify protocol version to be supported
    exec mode commands/options:
      disconnect  Specify SSH session id to be disconnected after this keyword
    ciscoasa(config-username)# ssh
    ciscoasa(config-username)# sh ver | in Ver
    Cisco Adaptive Security Appliance Software Version 9.1(1)
    Device Manager Version 7.1(1)52
    ciscoasa(config-username)#

  • Can Anyone Tell Us What CPU This Blade Log Has? (SPARC T3-1B) - PLEASE

    Primary Bootstrap.
    U-Boot 1.1.4
    Custom AST2100 U-Boot 3.0 (Feb  4 2011 - 00:21:51) r62572
    DRAM:  119 MB
    Flash bank 0 at 10000000 has 32MB in 256 sectors (chipSize 1<<25, ratio 1, bufSz 64).
    Flash: 32 MB
    VUART1 at port 0x03f8, SerIRQ[4] disabled
    VUART2 at port 0x02f8, SerIRQ[3] disabled
    Protecting U-Boot flash sectors; monitor_base=100a0000.
    board_findGpioNum(): ERROR, 'BIOS_TOP_BLOCK_LOCK' does not match any pin.
    board_findGpioNum(): ERROR, 'SP_PECI_ENABLE' does not match any pin.
    H/W:   Virgoplus Service Processor; SOC: AST2100 Rev. 02 ('A3')
      PWC_SP_Broken_OD = 0;  ARM restart caused by: power-on
      The host is OFF(held) (hostWantsPwr=1, powerGood=0,
            allowPwrOn=0|0, outOfReset=0, fatalError=0).
      Reset straps=0x8c819180, def. H-PLL=264 MHz, CPU/AHB=2:1, boot CS0# normal speed
      PCI w/VGA noVBIOS;  NOR 38ns/byte;  DRAM clock is M-PLL: 264 MHz (DDR2-528)
      DRAM: 128MB data - 8MB VGA, 32-bit noECC, 2 BA 10 CA, CL=4 BL=4 ap=1, 61440 us refr, DQSipv=0x2020202
    Board Revision - 8d
    Date: 2013-11-05 (Tuesday)    Time: 16:15:08
    Reading FRUID...Valid CRC.
    ethaddr=00:21:28:BB:FD:76
    eth1addr=00:21:28:BB:FD:77
    Platform (virgo): Configuring HPC FPGA (data=0x100ed800, len=45844)
    ## Extracting HPC microcode...done
    Now programming 225844 bytes...
    HPC programming done, rc = 0
    HPC_FPGA_DONE = 1
    Net:   faradaynic#0, faradaynic#1
    Enter Diagnostics Mode ['q'uick/'n'ormal(default)/e'x'tended(manufacturing mode)] .....   0
    Diagnostics Mode - NORMAL
    <DIAGS> Memory Data Bus Test ... PASSED
    <DIAGS> Memory Address Bus Test ... PASSED
    I2C Probe Test - Motherboard
            Bus     Device                          Address Result
            ===     ============================    ======= ======
             1               PCA9548 MUX (U3004)    0xE2    PASSED
             2                 Sys FRUID (U3003)    0xA0    PASSED
             2                Power CPLD (U3301)    0x4E    PASSED
             2          CPU0 Fault LED's (U3001)    0x40    PASSED
             2          CPU1 Fault LED's (U3002)    0x42    PASSED
             2            PCA9555 (Misc) (U3005)    0x44    PASSED
             2        Temp. Sensor(LM75) (U3006)    0x90    PASSED
             2                   LTC4215 (U5102)    0x96    PASSED
             2                 DIMM IMAX (U3102)    0x12    PASSED
             6          Bank Panel Led's (U3406)    0xC6    PASSED
             6               DS1338(RTC) ( U803)    0xD0    PASSED
    <DIAGS>Testing 4eyes access .... PASSED
    <DIAGS> PHY #0 R/W Test ... PASSED
    <DIAGS> PHY #0 Link Status ... PASSED
    <DIAGS> ETHERNET PHY #0, Internal Loopback Test ... PASSED                                                           <DIAGS> USB 1.1 Test ... PASSED
    <DIAGS>Access to BIOS Flash ... PASSED
    <DIAGS> Testing PowerCPLD version ... PASSED
    checking for abnormal reboots: 0:0.
    abnormal reboot found -- too long, ignore
    Booting linux in 3 seconds...
    Un-Protect Flash Bank # 1
    flctrl: Recovery U-Boot (r56177) at 0x10040000 is valid (min. r51654).
    Trying primary image...
    Trying to boot package at 10100000
    Found kernel image at 10102000
    Found root image at 1025f9f4
    copying 0x00a8d040 bytes from 0x1025f9f4 to 0x00800000
    bootargs= root=/dev/ram  ramdisk_size=10804  console=ttyS0,9600 bigphysarea=6144 ractrends.mtdblocks=env,0x20000,0x20000,coredump,0x1500000,0x800000,persist,0x1d00000,0x200000,params,0x1f00000,0x100000,
    ## Booting image at 10102000 ...
       Image Name:   Linux-2.6.27.43
       Created:      2011-02-04   5:18:45 UTC
       Image Type:   ARM Linux Kernel Image (uncompressed)
       Data Size:    1431988 Bytes =  1.4 MB
       Load Address: 00008000
       Entry Point:  00008000
       Verifying Checksum ... OK
    OK
    do_bootm_linux() armlinux.c:104
      bootm
      0x10102000
      0x00800000
    theKernel=00008000
    do_bootm_linux() armlinux.c:121 - 9
    ## Loading Ramdisk Image at 00800000 ...
    do_bootm_linux() armlinux.c:155 - 10
       Image Name:
       Created:      2011-02-04   6:07:05 UTC
       Image Type:   ARM Linux RAMDisk Image (uncompressed)
       Data Size:    11063296 Bytes = 10.6 MB
       Load Address: 00000000
       Entry Point:  00000000
       Verifying Checksum ... OK
    do_bootm_linux() armlinux.c:182 - 11
    do_bootm_linux() armlinux.c:245 - 15
    arch_number = 0x00000386
    env_t       = 0x01ED0008
    boot_params = 0x40000100
    DRAM bank   = 0x00000000
    -> start    = 0x00000000
    -> size     = 0x07700000
    ethaddr     = 00:21:28:BB:FD:76
    eth1addr    = 00:21:28:BB:FD:77
    ip_addr     = 0.0.0.0
    baudrate    = 9600 bps
    Sun extensions:
      bi_UBootEnvAddr     = 0x10020000
      bi_UBootEnvSize     = 0x00020000
      bi_flashstart       = 0x10000000
      bi_flashsize        = 0x02000000
      bi_flashbanksize    = 0x02000000
      bi_flashbanks       = 0x01
      bi_flashbankwidth   = 0x01
      bi_flashsectorsize  = 0x00020000
      bi_flashsectorcount = 0x00000100
      bi_boottype         = 0x02
      bi_primarytype      = 0x02
      bi_secondarytype    = 0x00
      bi_booted           = 0x10100000
      bi_primary          = 0x100a0000
      bi_secondary        = 0xffffffff
      bi_primaryhdr       = 0x10100000
      bi_secondaryhdr     = 0xffffffff
      bi_imagearea0       = 0x100a0000
      bi_imagearea1       = 0xffffffff
      bi_maximagesize     = 0x01f60000
      bi_min_firmware_rev = 0
      bi_sptrace_base     = 0x00000000
      bi_sptrace_len      = 0x00000000
      bi_apbclockhz       = 0x03ef1480
    H/W:   Virgoplus Service Processor; SOC: AST2100 Rev. 02 ('A3')
      The host is OFF(held) (hostWantsPwr=1, powerGood=0,
            allowPwrOn=0|0, outOfReset=0, fatalError=0).
      ARM Control reg: RR=0 HV=0 IC=1 BPd=0 RomP=0 SysP=0 BE=0 WB=1 DC=0 AlinFlt=1 MMU=0
      Cache Type reg: CType=0xe WB, sep.; I: 16KB of 32B lines 4-way; D: 16KB of 32B lines 4-way
            IC locked ways(3:0): 0000b, DC locked ways: 0000b
      Reset straps=0x8c819180, def. H-PLL=264 MHz, CPU/AHB=2:1, boot CS0# normal speed
      H-PLL (params=0x04291) 264.000 MHz, M-PLL params=0x04120-->264.000 MHz
      CPUCLK: H-PLL/1=264 MHz, AHB HCLK: CPUCLK/2=132 MHz, APB PCLK: H-PLL/4= 66 MHz
      PCI w/VGA noVBIOS;  NOR 38ns/byte;  DRAM clock is M-PLL: 264 MHz (DDR2-528)
      Bus-master-mode clocks: PCI BHCLK= 33 MHz, LPC LHCLK= 33 MHz
      Stopped clocks: vidCap-1, SP-Display, HACE, PCI-host
      DRAM: 128MB data - 8MB VGA, 32-bit noECC, 2 BA 10 CA, CL=4 BL=4 ap=1, 61440 us refr, DQSipv=0x2020202
      Reset controls: HACE, PwmFt, displays, MDMA, PCI-host
      Register protect: SCU prot, DMC prot, AHBC prot, VIC U-prot
      Ethernet MAC-PHY interface mode=6 (RMII + RMII), no MII2DC+DIO pins
    do_bootm_linux() armlinux.c:260
    do_bootm_linux() armlinux.c:263
    do_bootm_linux() armlinux.c:267
    do_bootm_linux() armlinux.c:279
    do_bootm_linux() armlinux.c:283
    do_bootm_linux() armlinux.c:287
    do_bootm_linux() armlinux.c:295
    Galactic register 1: 400509c0
    Starting watchdog timer.
    Starting kernel at 0x00008000...
    do_bootm_linux() armlinux.c:320
    do_bootm_linux() armlinux.c:324 (0x00000386,0x40000100)
    Uncompressing Linux............................................................................................... done, booting the kernel.
    Linux version 2.6.27.43 (buildbot@build-slave-sh-8) (gcc version 3.3.6) #1 Fri Feb 4 00:18:12 EST 2011
    CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
    Machine: ASPEED-AST2100
    Memory policy: ECC disabled, Data cache writeback
    CPU0: D VIVT write-back cache
    CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
    CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128 sets
    Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 30226
    Kernel command line: root=/dev/ram  ramdisk_size=10804  console=ttyS0,9600 bigphysarea=6144 ractrends.mtdblocks=env,0x20000,0x20000,coredump,0x1500000,0x800000,persist,0x1d00000,0x200000,params,0x1f00000,0x100000,
    PID hash table entries: 512 (order: 9, 2048 bytes)
    console [ttyS0] enabled
    mach/timer.c: Just lost 80 clock interrupts.
    Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
    Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
    Memory: 119MB = 119MB total
    Memory: 82144KB available (2708K code, 246K data, 124K init)
    Calibrating delay loop... 131.48 BogoMIPS (lpj=657408)
    Mount-cache hash table entries: 512
    Initializing cgroup subsys ns
    Initializing cgroup subsys cpuacct
    CPU: Testing write buffer coherency: ok
    net_namespace: 804 bytes
    NET: Registered protocol family 16
    NET: Registered protocol family 2
    IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
    TCP established hash table entries: 4096 (order: 3, 32768 bytes)
    TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
    TCP: Hash tables configured (established 4096 bind 4096)
    TCP reno registered
    NET: Registered protocol family 1
    checking if image is initramfs...it isn't (bad gzip magic numbers); looks like an initrd
    Freeing initrd memory: 10804K
    NetWinder Floating Point Emulator V0.97 (double precision)
    bigphysarea: Allocated 6144 pages at 0xc128e000.
    squashfs: version 3.4 (2008/08/26) Phillip Lougher
    squashfs: LZMA suppport for slax.org by jro
    JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
    msgmni has been set to 181
    Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
    io scheduler noop registered (default)
    ttyS0 at MMIO 0x1e783000 (irq = 9) is a GUC-ASPEED UART
    ttyS1 at MMIO 0x1e784000 (irq = 10) is a GUC-ASPEED UART
    brd: module loaded
    loop: module loaded
    FTGMAC100: ASPEED FTGMAC Driver, (Linux Kernel 2.6.15.7) 11/17/2008 - by ASPEED
    FTGMAC100: eth0: at 0xfe660000 IRQ:2 noWait:0, MAC 00:21:28:bb:fd:76
    FTGMAC100: eth0:ftgmac100_reset, phyAddr=0x0, miiPhyId=0x0040_61e4
    FTGMAC100: lp->rx_descs = ffc00000, lp->rx_rx_descs_dma = 67ac000
    FTGMAC100: lp->rx_buf = 00000000, lp->rx_buf_dma = 0
    FTGMAC100: lp->tx_descs = ffc01000, lp->tx_rx_descs_dma = 67bd000
    FTGMAC100: lp->tx_buf = 00000000, lp->tx_buf_dma = 0
    FTGMAC100: eth1: at 0xfe680000 IRQ:3 noWait:0, MAC 00:21:28:bb:fd:77
    FTGMAC100: eth1:ftgmac100_reset, phyAddr=0xff, miiPhyId=0x0000_0002
    FTGMAC100: lp->rx_descs = ffc02000, lp->rx_rx_descs_dma = 67c1000
    FTGMAC100: lp->rx_buf = 00000000, lp->rx_buf_dma = 0
    FTGMAC100: lp->tx_descs = ffc03000, lp->tx_rx_descs_dma = 67d4000
    FTGMAC100: lp->tx_buf = 00000000, lp->tx_buf_dma = 0
    Ractrends Flash mapping: 0x2000000 at 0x10000000
    Bank #0: Found 1 x16 devices at 0x0 in 8-bit bank
    Amd/Fujitsu Extended Query Table at 0x0040
    Bank #0: CFI does not contain boot bank location. Assuming top.
    number of CFI chips: 1
    Number of banks found = 1
    GetMTDPartitions() says string is "env,0x20000,0x20000,coredump,0x1500000,0x800000,persist,0x1d00000,0x200000,params,0x1f00000,0x100000,"
    MTD Partition 0 : fullpart @ 0x0 of Size 0x2000000
    MTD Partition 1 : env @ 0x20000 of Size 0x20000
    MTD Partition 2 : coredump @ 0x1500000 of Size 0x800000
    MTD Partition 3 : persist @ 0x1d00000 of Size 0x200000
    MTD Partition 4 : params @ 0x1f00000 of Size 0x100000
    Creating 5 MTD partitions on "Bank #0":
    0x00000000-0x02000000 : "fullpart"
    0x00020000-0x00040000 : "env"
    0x01500000-0x01d00000 : "coredump"
    0x01d00000-0x01f00000 : "persist"
    0x01f00000-0x02000000 : "params"
    wdt: AST2100 WDT is installed.
    wdt: AST2100 WDT nowayout = 1, heartbeat = 30 secs
    wdt: AST2100 WDT guardstartupshutdown = 1
    wdt: AST2100 WDT startuptimeout = 600, shutdowntimeout = 60
    wdt: AST2100 WDT was enabled at driver start, time remaining 53 secs.
    wdt: Guarding startup, setting watchdog for 600 seconds.
    nf_conntrack version 0.5.0 (2048 buckets, 8192 max)
    CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Plase use
    nf_conntrack.acct=1 kernel paramater, acct=1 nf_conntrack module option or
    sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
    ip_tables: (C) 2000-2006 Netfilter Core Team
    TCP cubic registered
    NET: Registered protocol family 10
    ip6_tables: (C) 2000-2006 Netfilter Core Team
    NET: Registered protocol family 17
    RPC: Registered udp transport module.
    RPC: Registered tcp transport module.
    802.1Q VLAN Support v1.8 Ben Greear <[email protected]>
    All bugs added by David S. Miller <[email protected]>
    drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
    RAMDISK: squashfs filesystem found at block 0
    RAMDISK: Loading 10801KiB [1 disk] into ram disk... done.
    VFS: Mounted root (squashfs filesystem) readonly.
    Freeing init memory: 124K
    INIT: version 2.86 booting
    Creating /var tmpfs
    Creating directories in /var...done.
    Creating /var/log tmpfs...done.
    Calculating module dependencies... done.
    Loading modules...
        flashinfo
        helper
    Helper Module Driver Version 1.1
    mach/timer.c: Just lost 2 clock interrupts.
    Copyright (c) 2006 American Megatrends Inc.
        dbgpersist
    Persistent Driver Debugger version 1.1
    Copyright (c) 2008 Sun Microsystems Inc.
            Loading debug: usbhub [success]
            1 debug modules loaded
        gpiomgr
        gpioint
        peci
    PECI Driver: peci_initialize_device(696) Setup device peci0.
        i2c-core
    i2c_boardinfo: module license 'unspecified' taints kernel.
        i2c-dev
    i2c /dev entries driver
        i2c-algo-as
        i2c-aspeed
    i2c-adapter i2c-0: Hardware routines registered
    Registered bus id: i2c-0
    i2c-adapter i2c-1: Hardware routines registered
    Registered bus id: i2c-1
    i2c-adapter i2c-2: Hardware routines registered
    Registered bus id: i2c-2
    i2c-adapter i2c-3: Hardware routines registered
    Registered bus id: i2c-3
    i2c-adapter i2c-4: Hardware routines registered
    Registered bus id: i2c-4
    i2c-adapter i2c-5: Hardware routines registered
    Registered bus id: i2c-5
    i2c-adapter i2c-6: Hardware routines registered
    Registered bus id: i2c-6
        i2c-boardinfo
        videocap
    AST Video Capture Driver Version 1.0
    Copyright (c) 2005-2006 American Megatrends Inc.
        usb
    Initializing USB Devices -
    USB Device Endpoint Driver
    Copyright 2006 American Megatrends Inc.
    usb_init(): --USB INITIALIZING-- version MOD-VER:2011-02-04,00:09:46 with UsbEth and EndPoint-Remapping: 1
    USB GlobalDisconnect(): Called
    (E)ethBot_ConvertMacStr: converting '002128574716'
    Init AST11 Success
    USB GlobalReconnect(): Called
    mach/timer.c: Just lost 2 clock interrupts.
    USB Driver is Successfully Initialized
        btkcs
    All modules loaded.
    ... done.
    Checking device file systems
    Finished check of device file systems
    Checking configuration files state ...
    Image date:  Fri Feb  4 01:06:21 EST 2011       Image revision: 62572
    Conf date:   Fri Feb  4 01:06:21 EST 2011       Conf revision:  62572
    Configuration files state good after upgrade.
    Starting Platform Initialization: platinit.
    Running ldconfig...done
    Starting Platform Initialization: c10init.
    Starting FRU update program, platform id phase: frutool.
    Starting spdiag Platform Init: /usr/local/bin/spdiag  Done (0)
    Setting up networking...done.
    Hostname: SUNSP-1113FMN04D.
    Setting up IP spoofing protection: rp_filter.
    Configuring IPv6...done
    Configuring network interfaces...FTGMAC100: eth0:ftgmac100_open
    mach/timer.c: Just lost 3 clock interrupts.
    FTGMAC100: eth0:ftgmac100_reset, phyAddr=0x0, miiPhyId=0x0040_61e4
    FTGMAC100: eth1:ftgmac100_open
    FTGMAC100: eth1:ftgmac100_reset, phyAddr=0xff, miiPhyId=0x0000_0002
    SIOCSIFNETMASK: Cannot assign requested address
    SIOCSIFBRDADDR: Cannot assign requested address
    Failed to bring up eth1.
    done.
    Starting Constellation Blade Daemon: c10bd.
    Running ldconfig...done
    Starting portmap daemon: portmap.
    Starting ILOM Watchdog daemon.
    wdt: WDT device opened.  Watchdog starting with heartbeat = 30 secs
    mach/timer.c: Just lost 6 clock interrupts.
    wdt: AST2100 WDT was enabled at driver open, time remaining 556 secs.
    Done
    populating memstore vars from disk
    Running plat...plat: platform=b10, chassis=c01
    Done running plat
    Identifying Product Data...done.
    Starting FRU info cache program: frucache.
    INIT: Entering runlevel: 3
    Preparsing sensor.xml...
    Starting Shared Sensor Broadcast Daemon: ssbcastd  Done
    Starting system log daemon: syslogd and klogd.
    Starting capidirect daemon: capidirectd . Done
    Starting Event Manager: eventmgr  . Done
    Starting ipmi log manager daemon: logmgr . Done
    Starting System Avoidance Daemon: sad  Done
    Starting user mgmt upgrade program: usrmgt_upgrade.
    Starting the Health Monitor Daemon...
    Starting portmap daemon: portmap.
    Starting Host console Daemon: consd . Done
    Starting capidirectd: Done.
    Starting Error Telemetry Collection Daemon: etcd . Done
    Starting Fault Diagnosis Daemon: fdd . Done
    Starting IPMI Stack: . Done
    SSH RSA Host Key Files already exist. Skipping key creation ...
    SSH DSA Host Key Files already exist. Skipping key creation ...
    Starting sshd.
    Starting OpenBSD Secure Shell server: sshd-man.
    Starting SP fishwrap cache daemon: fishwrapd . Done
    Starting Network Controller Sideband Interface Daemon: ncsid . Done
    Starting Platform Obfuscation Daemon: pod . Done
    Starting lu main daemon: lumain . Done
    Starting HT sign on daemon: htsignond . Done
    Starting webgo Web Server: webgo . Done
    Starting Detection/Diagnosis After System Boot: dasboot  Done
    Starting Shared Sensor Poller: sspoller  Done
    Starting Servicetags discoverer: stdiscoverer.
    Starting Servicetags listener: stlistener.
    Starting Dynamic FRUID Daemon: dynafrud  Done
    Starting FRU info cache program: frucache.
    SUNSP-1113FMN04D login:

    For which reason do you want to known the SP processor model ?

  • Error while updating the firmware

    I have X4500 running solaris 10 OS with software version 5.10. The ILOM version is 1.1.1. I tried to update the firmware but I cannot do that because I am getting an error. This is how I setup everything and I get the error mentioned below.
    C H A P T E R 1 - Flash Upgrading Your Server to Software Release 1.2
    I referred to the above link to do so. But, I do not understand what is the tftpserver that I need to mention here. I get an error message saying gethostbyname() failed. I also setup tftp server on my solaris machine using the following link.
    A P P E N D I X C - Updating the Firmware
    Please, help me.

    ILOM <1.1.8 was pretty flaky. 1.0 was described to me by a Sun CSE as the worst piece of software they ever released. I beg to differ, having been forced to use YP and rpc.lockd in the past but I digress ...
    o) Are you sure that you're getting the right firmware image? You want the x4500-specific images here: http://www.sun.com/servers/x64/x4500/downloads.jsp Be careful not to mix up x4100/x4200, x4100m2/x4200m2, x4600, x4500, etc. files as they are different
    o) Do a "show /SYS/MB" before updating your firmware and stash the output. Updates from 1.x versions of ILOM have a way of wiping the system serial and part numbers. If you record that info first you can repair after the fact.
    o) Do a "reset /SP" to reset the service processor before attempting the update. 1.x versions of ILOM, especially <=1.1.1, seem to upgrade more reliably when they're freshly booted
    o) Be sure that /SYS is stopped before you update ILOM
    o) You don't specify what command you're using to try to update, but I suspect that you're trying something like
    load -source tftp://some.host.domain/file.ima
    given the gethostbyname error. Give it the ip address of the tftp server not the FQDN.

Maybe you are looking for