C: To change the default behavior of the Fast Reboot feature on the SPARC platform, so that a fast reboot is automatically performed when the system reboots, see below.
The following example shows how to set the property's value to true on the SPARC platform, so that a fast reboot is initiated by default:
# svccfg -s "system/boot-config:default" setprop config/fastreboot_default=true
# svcadm refresh svc:/system/boot-config:default
D: Fast Reboot implements an in-kernel boot loader that loads the kernel into memory and then switches to that kernel.
The firmware and boot loader processes are bypassed, which enables the system to reboot within seconds.
The Fast Reboot feature is managed by SMF and implemented through a boot configuration service, svc:/system/boot-config. The boot-config service provides a means for setting or changing the default boot configuration parameters. When the config/fastreboot_default property is set to true, the system performs a fast reboot automatically, without the need to use the reboot -f command. This property's value is set to true on the x86 platform. For task-related information, including how to change the default behavior of Fast Reboot on the SPARC platform, see Accelerating the Reboot Process on an x86 Based System.
Note: One new feature, called Fast Reboot, will allow the system to boot up without doing the routine set of hardware checks, a move that can make system boot times up to two- and-a-half times faster, Oracle claimed. This feature can be handy in that an administrator applying a patch or software update across thousands of Solaris deployments can reboot them all the more quickly.

The Internet Control Message Protocol (ICMP) is one of the core protocols of the Internet Protocol Suite.
ICMP differs from transport protocols such as TCP and UDP in that it is not typically used to exchange data between systems, nor is it regularly employed by end-user network applications (with the exception of some diagnostic tools like ping and traceroute).

Explanation/Reference:
Explanation:
zonep2vchk
- check a global zone's configuration for physical to virtual migration into non-global zone The zonep2vchk utility is used to evaluate a global zone's configuration before the process of physical-to- virtual (p2v) migration into a non-global zone.
The p2v process involves archiving a global zone (source), and then installing a non-global zone (target) using that archive
Zonep2vchk serves two functions. First, it can be used to report issues on the source which might prevent a successful p2v migration. Second, it can output a template zonecfg, which can be used to assist in configuring the non-global zone target.
Zonep2vchk can be executed on a Solaris 10 or later global zone. To execute on Solaris 10, copy the zonep2vchkutility to the Solaris 10 source global zone.
When run on Solaris 10, a target release of S11 can be specified, which will check for p2v into a Solaris 10 Branded zone.

Here we should use SIGTERM to terminate the process.
Note:
When no signal is included in the kill command-line syntax, the default signal that is used is -15
(SIGKILL). Using the -9 signal (SIGTERM) with the kill command ensures that the process
terminates promptly. However, the -9 signal should not be used to kill certain processes, such as
a database process, or an LDAP server process. The result is that data might be lost.
Tip - When using the kill command to stop a process, first try using the command by itself, without
including a signal option. Wait a few minutes to see if the process terminates before using the kill
command with the -9 signal.
Reference: Terminate the process

Here we should use SIGTERM to terminate the process.
Note:
When no signal is included in the kill command-line syntax, the default signal that is used is -15
(SIGKILL). Using the -9 signal (SIGTERM) with the kill command ensures that the process
terminates promptly. However, the -9 signal should not be used to kill certain processes, such as
a database process, or an LDAP server process. The result is that data might be lost.
Tip - When using the kill command to stop a process, first try using the command by itself, without
including a signal option. Wait a few minutes to see if the process terminates before using the kill
command with the -9 signal.
Reference: Terminate the process