Show address information, either for the given addrobj or all the address objects configured on the specified interface, including the address objects that are only in the persistent configuration.
State can be:disabled, down, duplicate, inaccessible, ok, tentative
Example: # ipadm show-addr ADDROBJ TYPE STATE ADDR lo0/v4 static ok 127.0.0.1/8 lo0/v6 static ok ::1/128

Explanation/Reference:
Explanation:
You can use the pkg set-publisher command to change a publisher URI.
Changing a Publisher Origin URI
To change the origin URI for a publisher, add the new URI and remove the old URI. Use the -g option to add a new origin URI. Use the -G option to remove the old origin URI.
# pkg set-publisher -g http://pkg.example.com/support \
-G http://pkg.example.com/release example.com
Note: You can use either the install or update subcommand to update a package.
The install subcommand installs the package if the package is not already installed in the image. If you want to be sure to update only packages that are already installed, and not install any new packages, then use the update subcommand.

zfs snapshot [-r] [-o property=value] ... filesystem@snapname|volume@snapname
Creates a snapshot with the given name. All previous modifications by successful system calls to
the file system are part of the snapshot
zfs clone [-p] [-o property=value] ... snapshot filesystem|volume
Creates a clone of the given snapshot.
Note:
Because snapshots are fast and low overhead, they can be used extensively without great
concern for system performance or disk use .
With ZFS you can not only create snapshot but create a clone of a snapshot.
A clone is a writable volume or file system whose initial contents are the same as the dataset from
which it was created. As with snapshots, creating a clone is nearly instantaneous, and initially
consumes no additional disk space. In addition, you can snapshot a clone.
A clone is a writable volume or file system whose initial contents are the same as the original
dataset. As with snapshots, creating a clone is nearly instantaneous, and initially consumes no
additional space.
Clones can only be created from a snapshot. When a snapshot is cloned, it creates an implicit
dependency between the parent and child.
Reference: man zfs

How to Recreate a ZFS Root Pool and Restore Root Pool Snapshots In this scenario, assume the following conditions:
*ZFS root pool cannot be recovered
*ZFS root pool snapshots are stored on a remote system and are shared over NFS
*The system is booted from an equivalent Solaris release to the root pool version so that the Solaris release and the pool version match. Otherwise, you will need to add the -o version=version-number property option and value when you recreate the root pool in step 4 below.
All steps below are performed on the local system.
1.Boot from CD/DVD or the network.
On a SPARC based system, select one of the following boot methods:
ok boot net -s ok boot cdrom -s If you don't use -s option, you'll need to exit the installation program.
2.Mount the remote snapshot dataset.
For example:
3.Recreate the root pool.
For example:
# zpool create -f -o failmode=continue -R /a -m legacy -o cachefile=/etc/zfs/zpool.cache rpool c1t0d0s0
4.Restore the root pool snapshots.
This step might take some time. For example:
# cat /mnt/rpool.0311 | zfs receive -Fdu rpool Using the -u option means that the restored archive is not mounted when the zfs receive operation completes.
5.Set the bootfs property on the root pool BE.
For example:
# zpool set bootfs=rpool/ROOT/osolBE rpool
6.Install the boot blocks on the new disk.
On a SPARC based system:
# mount -F nfs remote-system:/rpool/snaps /mnt # installboot -F zfs /usr/platform/`uname -i`/lib/fs/zfs/bootblk /dev/rdsk/c1t0d0s0
Reference: How to Recreate a ZFS Root Pool and Restore Root Pool Snapshots, Oracle Solaris ZFS Administration Guide