Skip to main content
NetApp Knowledge Base

What is the impact of enabling FIPS on Brocade Switch

  1. Last updated
  2. Save as PDF
Views:
57
Visibility:
Public
Votes:
0
Category:
fabric-interconnect-and-management-switches
Specialty:
brocade
Last Updated:

Applies to

  • Brocade Switch

Answer

Additional Information

******************************************************
It is strongly recommended to block certain services and functions, such as FTP, HTTP, remote procedure calls (RPC), root account, etc., before the systems enter FIPS Inside mode.
Refer to the
Brocade Fabric OS FIPS Cryptographic Module 8.2 User Guide for information on configuring your system for FIPS 140-2 level-1 compliance.
 
1. Selftests will not be run if enabled in Fabric OS v9.0.0 as this has not been supported in FOS post upgrade to the latest openSSL.
2. FIPS mode cannot be modified through  configDownload
 
1. FIPS is not supported on all platforms. For FIPS-compliant hardware, refer to the  Brocade Fabric OS Administration Guide
 
2. In Fabric OS v9.0.0 or later, FIPS-inside mode runs only integrity test and selftests are not run.
3. In a Virtual Fabric environment, FIPS is treated as chassis-wide configuration and applies to all logical switches in the chassis. Chassis permissions are required to configure FIPS.
4. This command is subject to Virtual Fabric restrictions that may be in place. See "Using Fabric OS Commands" and "Command Availability" for details.
******************************************************

  • There will be no impact in case there are a number of SAN switch joining to the same Fabric without FIPS enabled in production environment and If the new SAN switch enables FIPS and join to the existing fabric,  since FIPS enabled is chassis-wide.

  • Neither it will cause other SAN physical switches in the same Fabric to enable FIPS automatically.

  • Once the services and unctions, such as FTP, HTTP, remote procedure calls (RPC), root account, etc are blocked before the system enters FIPS Inside mode, we cannot enable those services back after FIPS is enabled.

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.