A subnetwork, or subnet, is a logically visible subdivision of an IP network. The practice of dividing a network into two or more networks is called subnetting. The routing prefix of an address is written in a form identical to that of the address itself. This is called the network mask, or netmask, of the address. For example, a specification of the most-significant 18 bits of an IPv4 address, 11111111.11111111.11000000.00000000, is written as 255.255.192.0.

Explanation/Reference:
Explanation:
There is no data-link named vswitch192.168.
We need to create an etherstub first.
See Note and example below for details.
Note: Create a VNIC in the system's global zone.
# dladm create-vnic -l data-link vnic-name
data-link is the name of the interface where the VNIC is to be configured.
-l link, --link=link
link can be a physical link or an etherstub.
vnic-name is the name that you want to give the VNIC.
For example, to create a VNIC named vnic0 on interface e1000g0, you would type the following:
# dladm create-vnic -l e1000g0 vnic0
Example: Creating a Virtual Network Without a Physical NIC
First, create an etherstub with name stub1:
# dladm create-etherstub stub1
Create two VNICs with names hello0 and test1 on the etherstub. This operation implicitly creates a virtual switch connecting hello0 and test1.
# dladm create-vnic -l stub1 hello0
# dladm create-vnic -l stub1 test1

The ipadm delete-addr subcommand removes addresses from interfaces.
To remove an address from the IPMP group, type the following command:
# ipadm delete-addr addrobj
The addrobj uses the naming convention inder-interface/user-string.
Reference: Oracle Solaris Administration: Network Interfaces and Network Virtualization

OpenBoot firmware is executed immediately after you turn on your system. The primary tasks of OpenBoot firmware are to:
* Test and initialize the system hardware (B)
* Determine the hardware configuration
*Boot the operating system from either a mass storage device or from a network (C)
*Provide interactive debugging facilities for testing hardware and software

Note 1: State Transition Sets are defined as:
to<state>
Set of all transitions that have <state> as the final state of the transition.
form-<state>
Set of all transitions that have <state> as the initial state of the transition.
<state>
Set of all transitions that have <state> as the initial state of the transition.
all
Set of all transitions. (A)
Valid values of state are maintenance, offline(G), disabled (E), online and degraded. An example
of a transitions set definition: maintenance, from-online, to-degraded.
F: In this context, events is a comma separated list of SMF state transition sets or a comma separated list of FMA (Fault Management Architecture) event classes. events cannot have a mix of SMF state transition sets and FMA event classes. For convenience, the tags problem{diagnosed,updated,repaired,resolved} describe the lifecycle of a problem diagnosed by the FMA subsystem - from initial diagnosis to interim updates and finally problem closure.
Note2: SMF allows notification by using SNMP or SMTP of state transitions. It publishes Information Events for state transitions which are consumed by notification daemons like snmp-notify(1M) and smtp-notify(1M). SMF state transitions of disabled services do not generate notifications unless the final state for the transition is disabled and there exist notification parameters for that transition. Notification is not be generated for transitions that have the same initial and final state.
Reference: man svccfg setnotify