This procedure captures in a syslog file all failed login attempts.
1.Set up the /etc/default/login file with the desired values for SYSLOG and SYSLOG_FAILED_LOGINS Edit the /etc/default/login file to change the entry. Make sure that SYSLOG=YES is uncommented.
2.Create a file with the correct permissions to hold the logging information. Create the authlog file in the /var/adm directory.
3.Edit the syslog.conf file to log failed password attempts. Send the failures to the authlog file.

Different UNIX-like operating systems store information about their release versions differently. If you know what OS you have, but not sure about the version, then here's how you can find out: bash-2.03$ cat /etc/release Solaris 8 2/04 s28s_hw4wos_05a SPARC Copyright 2004 Sun Microsystems, Inc. All Rights Reserved. Assembled 08 January 2004
Reference:How To: Find Out the Release Version of Your UNIX

Explanation/Reference:
Explanation:
The command dladm is used to configure data-link interfaces in Sun Solaris. A configured data-link is represented in the system as interface that can be used for TCP/IP. Each data-link relies on either a single network device or an link aggregation device to send & recieve packets.
Network interfaces provide the connection between the system and the network. These interfaces are configured over data links, which in turn correspond to instances of hardware devices in the system.
In the current model of the network stack, interfaces and links on the software layer build on the devices in the hardware layer. More specifically, a hardware device instance in the hardware layer has a corresponding link on the data-link layer and a configured interface on the interface layer. This one-to-one relationship among the network device, its data link, and the IP interface is illustrated in the figure that follows.
Network Stack Showing Network Devices, Links, and Interfaces:

SVC.CONFIGD is the repository daemon responsible for maintaining /etc/svc/repository.db.
The repository.db must come clean during this integrity check otherwise it is a "no go" for usual boot sequence to run level 3. The repository may get corrupted due to various hardware issues, software bugs, disk write failures, etc.
Note: When svc.configd(1M), the Solaris Repository Daemon, is started, it does an integrity check of the smf(5) repository, stored in /etc/svc/repository.db. This integrity check can fail due to a disk failure, the database file being corrupted either due to a hardware bug, a software bug, or an accidental overwrite. If the integrity check fails, svc.configd will write a message to the console.

First line (rm file1) deletes/removes file1.
Second line captures the text into file2.
The first part of line 3 (cat file1) fails as the file1 does not exist.
The && (AND) operator will ensure that the third line fails. The result of line 3 will be the result of first part of line 3 (cat file1).
Note: cat - concatenate files and print on the standard output
Note #1: A list is a sequence of one or more pipelines separated by one of the operators ';',
'&', '&&', or '||', and optionally terminated by one of ';', '&', or a newline.
Of these list operators, '&&' and '||' have equal precedence, followed by ';' and '&', which have equal precedence.
AND and OR lists are sequences of one or more pipelines separated by the control operators '&&' and '||', respectively. AND and OR lists are executed with left associativity.
An AND list has the form
command1 && command2
command2 is executed if, and only if, command1 returns an exit status of zero.
An OR list has the form
command1 || command2
command2 is executed if, and only if, command1 returns a non-zero exit status.
The return status of AND and OR lists is the exit status of the last command executed in the list.
Note #2 (on exit status): Zero means command executed successfully, if exit status returns non-zero value then your command failed to execute.