Spc-3007; Spc-3008; Spc-3009 - Brocade Communications Systems SN3000B Reference

Recommended For status code 14, complete primary KEK generation; otherwise, contact your switch service
Action provider.
Severity ERROR

SPC-3007

Message
<timestamp>, [SPC-3007], <sequence-number>,, ERROR, <system-name>, S<slot number
containing Encryption Engine>, <module name>: DEK create error: <SP status code>,
info: <other info>.
Probable Cause Indicates the cause depends on the SP status code:
•
•
•
•
•
•
Recommended For status code 14, complete primary KEK generation; otherwise, contact your switch service
Action provider.
Severity ERROR

SPC-3008

Message
<timestamp>, [SPC-3008], <sequence-number>,, INFO, <system-name>, S<slot number
containing Encryption Engine>, <module name>: SP crypto got READY notification.
Probable Cause Indicates the key application (KPD) within the Crypto Module of the EE has been started.
Recommended No action is required.
Action
Severity INFO

SPC-3009

Message
<timestamp>, [SPC-3009], <sequence-number>,, ERROR, <system-name>, S<slot number
containing Encryption Engine>, <module name>: FIPS certificate mismatch,
certificate: <FIPS certificate is CO-0 or User-1>.
Probable Cause Indicates the FIPS certificate within the Crypto Module does not match that of the node.
Recommended Zeroize the EE (after backing up any needed primary or secondary KEK), then execute the cryptocfg
Action initEE and cryptocfg
--
Severity ERROR
Fabric OS Message Reference
53-1002448-01
2 - Invalid input DEK specification
21 - No primary KEK exists with which to wrap the DEK
14 - Creation not allowed: primary KEK generation is in progress
31 - DEK could not be wrapped
73 - Invalid KEK format
other - Internal error
regEE commands.
--
97
SPC-3007
657