How to on common solaris openboot commands?



  • Booting & Testing

    Did you know that most new systems run in a new standard default for openboot, that runs diagnostic tests and enables full automatic system recovery (ASR) during power on and error reset.

    Two parameters affect extended boot time:

    diag-level (max): default is max
    extensive memory testing, which extends boot time.

    verbosity (normal): default is normal
    affects the amount output message from the diagnostics.

    Openboot Parameters that control Diagnostics and Recovery

    auto-boot?: default is true
    This one determines if the systems should boot up into the operating systems or not, settings are true or false.

    auto-boot-on-error?: default is true
    Determines if the systems should boot after a non-fatal error, settings are true or false.

    boot-device:
    This is the name of the default boot device.

    boot-file:
    This is the default boot arguments.

    diag-device:
    The name of the boot device when diag-switch? is set to true, normally same as boot device

    diag-file:
    Specifies the boot arguments to use when diag-switch? is set to true.

    diag-level:
    The level of diagnostics you want, setting are off, min, or max

    diag-out-console:
    Only if you have a system controller, on your system. Will direct messages to it.

    diag-passes: default is 1
    Determines how many times do you want to run diagnotics via obdiag

    diag-script: default is normal
    Determines which devices to test, settings are none, normal (all devices which are expected to be present), and all (every device which has the capability of running a self-test).

    diag-switch?:
    Determines the diagnostic execution in normal mode. Settings are true and false; true will run diagnostics on power on reset, what is tested and the amount of output is controlled via user settings, false will run diagnostics on the next system reset, but only for those class of reset events specified by diag-trigger, the level and amount of output is still user controlled.

    diag-trigger: default is power-on-reset error-reset
    This setting determines the class of reset events that causes diagnostics to run automatically. Settings are none, error-reset, power-on-reset, user-reset, and all-resets. None, does nothing, power-on-reset, is a reset caused by power cycling the system, user-reset, is a reset initiated by the operating system panic, or user commands like, reset-all, boot, via the OS, reboot, shutdown, and init. The final setting, all-resets, mean any type of reset. Reset mean the POST and Openboot diags are run, unless diag-script is set to none, then only POST runs.

    error-reset-recovery: default is sync
    The recovery action when an error reset occurs, settings are none, boot, or sync.

    service-mode?: default is false
    Controls service mode, settings are true or false, true diagnostics are executed at sun specified diag levels but, user specified levels are preserved, false is normal mode unless the keyswitch is set to diag. Software diags depend on diag-switch? setting.

    test-args:
    A string of reserved test words, determins which tests openboot diagnostics should use.

    verbosity:
    Controls the amount of output produced of Openboot, POST, and Openboot Diags, settings are none, min, normal, or max.

    Service Mode.
    Service mode allow you to run full/max diags, without changing normal user defined settings. This is useful is you only want to run full diags in check problems on a non-functional system. To invoke service mode, set service-mode? to true

    Normal Mode.
    To set normal mode set key panel switch to normal or service-mode? to false, set diag-level = min, and set verbosity = min

    Post Command.
    post command overrides the system controller command, bootmode diag, bootmode skip_diag and service mode? It is useful for one off execution of POST diags, the format is post [level [verbosity]] level is min or max and verbosity is min, normal or max.

    The Device Tree

    Inside the host computer there are series of communication pathways called buses, these buses have devices attached to them. Openboot see these buses and devices as a device tree.

    A Full Device Path Name:
    /pci@1e,600000/lpfc@3/sd@1,4

    Each node (the bit between the slashes) has the format:

    device-name@unit-address:device-arguments

    The device-name:

    An identifier of the device, e.g. SUNW,sd, pci, lpfc, etc...

    The @:

    Precedes the address.

    The unit-address:

    A text string physical address of the device.

    The :

    Precedes any arguments.

    The device arguments:

    A text string, used to pass additional information to the devices software


Log in to reply
 

© Lightnetics 2024