#

# Copyright 2006 Sun Microsystems, Inc. All rights reserved.

# Use is subject to license terms.

#

# CDDL HEADER START

#

# The contents of this file are subject to the terms of the

# Common Development and Distribution License (the "License").

# You may not use this file except in compliance with the License.

#

# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE

# or http://www.opensolaris.org/os/licensing.

# See the License for the specific language governing permissions

# and limitations under the License.

#

# When distributing Covered Code, include this CDDL HEADER in each

# file and include the License file at usr/src/OPENSOLARIS.LICENSE.

# If applicable, add the following below this CDDL HEADER, with the

# fields enclosed by brackets "[]" replaced with your own identifying

# information: Portions Copyright [yyyy] [name of copyright owner]

#

# CDDL HEADER END

#

#ident "%Z%%M% %I% %E% SMI"

#

# DO NOT EDIT -- this file is generated by the Event Registry.

#

#

# code: SCA1000-8000-0V

# keys: fault.io.sca1000.hw

#

msgid "SCA1000-8000-0V.type"

msgstr "Fault"

msgid "SCA1000-8000-0V.severity"

msgstr "Major"

msgid "SCA1000-8000-0V.description"

msgstr "The Solaris Fault Manager has detected a hardware failure on the Sun Crypto Accelerator 1000 card. Refer to %s for more information."

msgid "SCA1000-8000-0V.response"

msgstr "The module has been disabled and un-registered as a hardware provider to the Solaris Cryptographic Framework."

msgid "SCA1000-8000-0V.impact"

msgstr "The card will no longer function as a cryptographic accelerator."

msgid "SCA1000-8000-0V.action"

msgstr "Ensure that the board is securely installed on the system.\n\nUse the cryptoadm(1M) command\n\ncryptoadm list -p\n\n\nto check whether 'dca/x' (where x is a number) is listed under 'kernel hardware\nproviders'. If so, run diagnostics on the hardware provider using SUNVTS\nfollowing the procedures described in the Sun Crypto Accelerator 1000 Board\nUser's Guide.\n\nUse the fmdump(1M) command\n\nfmdump -vu event-id\n\n\nto view the results of diagnosis and the specific Field Replaceable\nUnit (FRU) identified for replacement.\n\nThe event-id can be found in the EVENT-ID field of the message.\nFor example:\n\n\nEVENT-ID: 39b30371-f009-c76c-90ee-b245784d2277\n"