NAME | SYNOPSIS | DESCRIPTION | OPTIONS | ENVIRONMENT VARIABLES | FILES | SEE ALSO
hostint causes a hung domain to panic, dump, then reboot. When used without its -p option, hostint sends an interrupt signal to the boot processor of the domain specified in the SUNW_HOSTNAME environment variable to cause a kernel core dump. If hostint fails to panic the boot processor, it will attempt to interrupt another processor in the domain.
Use hostint only when the domain is hung and the hang is not detected by edd(1M), which would normally do an automatic reboot. You cannot panic an IDN domain unless you use the -f option; however, it can cause a cluster arbstop.
Other steps, with less impact, are available to unhang the domain. Try each of the following procedures, in the order shown, until the hang is fixed:
Attempt a reboot from any functional login on the domain. If this works, the domain was not fully hung. Core is not dumped.
Attempt to break into OpenBoot from the console by sending a break. You can do so via either netcon(1M) or netcontool(1M). Once in OpenBoot, issue the command sync, which causes a panic dump and reboot.
Execute hostint. If this step is successful, the domain panics, dumps, then reboots.
Execute hostreset. If this step is successful, you can then initiate a bringup(1M) if the system does not automatically boot.
If Steps 1 through 4 fail, execute bringup(1M) with its -f option.
The following options are supported:
Send the interrupt signal to the specified processor rather than the boot processor.
Force a panic in an IDN domain.
Verbose Mode. Display information to stdout.
The environment variable SUNW_HOSTNAME must be set to the name of the domain.
The following files are supported:
$SSPETC/snmp/Ultra-Enterprise-10000.mib
NAME | SYNOPSIS | DESCRIPTION | OPTIONS | ENVIRONMENT VARIABLES | FILES | SEE ALSO