1# 2# Copyright 2006 Sun Microsystems, Inc. All rights reserved. 3# Use is subject to license terms. 4# 5# CDDL HEADER START 6# 7# The contents of this file are subject to the terms of the 8# Common Development and Distribution License (the "License"). 9# You may not use this file except in compliance with the License. 10# 11# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE 12# or http://www.opensolaris.org/os/licensing. 13# See the License for the specific language governing permissions 14# and limitations under the License. 15# 16# When distributing Covered Code, include this CDDL HEADER in each 17# file and include the License file at usr/src/OPENSOLARIS.LICENSE. 18# If applicable, add the following below this CDDL HEADER, with the 19# fields enclosed by brackets "[]" replaced with your own identifying 20# information: Portions Copyright [yyyy] [name of copyright owner] 21# 22# CDDL HEADER END 23# 24#ident "%Z%%M% %I% %E% SMI" 25# 26# DO NOT EDIT -- this file is generated by the Event Registry. 27# 28# 29# code: SCA1000-8000-0V 30# keys: fault.io.sca1000.hw 31# 32msgid "SCA1000-8000-0V.type" 33msgstr "Fault" 34msgid "SCA1000-8000-0V.severity" 35msgstr "Major" 36msgid "SCA1000-8000-0V.description" 37msgstr "The Solaris Fault Manager has detected a hardware failure on the Sun Crypto Accelerator 1000 card. Refer to %s for more information." 38msgid "SCA1000-8000-0V.response" 39msgstr "The module has been disabled and un-registered as a hardware provider to the Solaris Cryptographic Framework." 40msgid "SCA1000-8000-0V.impact" 41msgstr "The card will no longer function as a cryptographic accelerator." 42msgid "SCA1000-8000-0V.action" 43msgstr "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" 44