Errors generated from Solaris "awk" utility during DiscoveryIssue <!-- div.margin{ padding: 10px 40px 40px 30px; } table.tocTable{ border: 1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); padding-top: .6em; padding-bottom: .6em; padding-left: .9em; padding-right: .6em; } table.noteTable{ border:1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); width: 100%; border-spacing:2; } table.internalTable{ border:1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); width: 85%; border-spacing:0; } .sp td{ border-bottom: 1px solid; border-right: 1px solid; border-color:#E0E0E0; background-color: #ffffff; height: 20px; padding-top: .5em; padding-bottom: .5em; padding-left: .5em; padding-right: .5em; } .sphr td{ border-right: 1px solid; border-bottom: 1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); padding-top: .5em; padding-bottom: .5em; padding-left: .5em; padding-right: .5em; height: 20px; } .title { color: #D1232B; font-weight:; font-size:25px; } .hd1{ color: #D1232B; font-weight:; font-size:18px; } .hd2{ color: #646464; font-weight:bold; font-size:16px; text-decoration: underline; } .hd3{ color: #7a7a7a; font-weight:; font-size:16px; text-decoration:; } .hd4{ color: #000000; font-weight:bold; font-size:14px; text-decoration:; } --> Errors Generated from Solaris "awk" Utility During Discovery Error During Discovery of a Solaris 10 system, the following error was received: System Configuration: Sun Microsystems sun4uawk: syntax error at source line 437context ismodelname=10*sprintf >>> "%d\n" <<< , ((cpuclock/10)+0.5)awk: illegal statement at source line 437awk: syntax error at source line 444 Workaround The error was generated from the Solaris awk utility. It appeared that the awk binary generating the error was corrupt. For a quick workaround, copy the awk binary from another Solaris 10 host server where the awk utility is working correctly, and replace the awk binary on the host server where it is not working correctly. Replacing the awk binary fixed the issue so Discovery could run normally.