Errors and Error Status Messages

JUNOS-FIPS errors stop all data output from the entire cryptographic module and cause a module panic, except very early in the boot cycle. Errors that occur early in the boot cycle can prevent the system from successfully booting. Keep alternate boot media up-to-date using the request system snapshot command. For more information about this command, see the JUNOS System Basics and Services Command Reference.

JUNOS-FIPS uses only FIPS-approved cryptographic algorithms, and only after a series of self-tests, including Known Answer Tests. A self-test failure results in a JUNOS-FIPS error state.

All but one of the following JUNOS-FIPS error conditions will create a system panic condition:

• Known Answer Test failed
• Random Number is not random
• Signature generation failed
• Signature verification failed
• Certificate verification failed
• Encryption/decryption failed
• Environment error
• Error in pair-wise conditional test
• Memory allocation error

The memory allocation error aborts the process making the call. All other errors result in a system panic condition and stop all data output. All errors except for memory allocation errors have only an extremely small chance of occurring.

For information about AS II FIPS PIC errors, see AS II FIPS PIC Errors.

For more information about JUNOS software errors in general, see the JUNOS System Basics Configuration Guide.

Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice.