HP 6125XLG R2306-HP 6125XLG Blade Switch Fundamentals Configuration Guide - Page 91

FIPS compliance, Enabling configuration encryption, Saving the running configuration

Page 91 highlights

irf mac-address persistent timer irf auto-update enable irf link-delay 0 irf member 2 priority 1 FIPS compliance The device supports the FIPS mode that complies with NIST FIPS 140-2 requirements. Support for features, commands, and parameters might differ in FIPS mode and non-FIPS mode. For more information about FIPS mode, see Security Configuration Guide. Enabling configuration encryption Configuration encryption enables the device to automatically encrypt a startup configuration file when it saves the running configuration. This function provides the following methods: • Private key method-Only the encrypting device can decrypt the encrypted configuration file. • Public key method-Any device running the same software version as the encrypting device can decrypt the encrypted configuration file. IMPORTANT: Do not move or copy a private-key-encrypted configuration file between IRF member devices. These actions can cause a decryption failure because the member devices use different private keys. To enable configuration encryption: Step 1. Enter system view. 2. Enable configuration encryption. Command system-view configuration encrypt { private-key | public-key } Remarks N/A By default, configuration encryption is disabled. Configuration is saved unencrypted. Saving the running configuration When saving the running configuration to a configuration file, you can specify the file as a next-startup configuration file. If you are specifying the file as a next-startup configuration file, use one of the following methods to save the configuration: • Fast mode-Use the save command without the safely keyword. In this mode, the device directly overwrites the target next-startup configuration file. If a reboot or power failure occurs during this process, the next-startup configuration file is lost. You must specify a new startup configuration file after the device reboots (see "Specifying a next-startup configuration file"). • Safe mode-Use the save command with the safely keyword. Safe mode is slower than fast mode, but more secure. In safe mode, the system saves configuration in a temporary file and starts 84

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155

84
irf mac-address persistent timer
irf auto-update enable
irf link-delay 0
irf member 2 priority 1
FIPS compliance
The device supports the FIPS mode that complies with NIST FIPS 140-2 requirements. Support for features,
commands, and parameters might differ in FIPS mode and non-FIPS mode. For more information about
FIPS mode, see
Security Configuration Guide
.
Enabling configuration encryption
Configuration encryption enables the device to automatically encrypt a startup configuration file when it
saves the running configuration. This function provides the following methods:
Private key method
—Only the encrypting device can decrypt the encrypted configuration file.
Public key method
—Any device running the same software version as the encrypting device can
decrypt the encrypted configuration file.
IMPORTANT:
Do not move or copy a private-key-encrypted configuration file between IRF member devices. These
actions can cause a decryption failure because the member devices use different private keys.
To enable configuration encryption:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enable configuration
encryption.
configuration encrypt
{
private-key
|
public-key
}
By default, configuration
encryption is disabled.
Configuration is saved
unencrypted.
Saving the running configuration
When saving the running configuration to a configuration file, you can specify the file as a next-startup
configuration file.
If you are specifying the file as a next-startup configuration file, use one of the following methods to save
the configuration:
Fast mode
—Use the
save
command without the
safely
keyword. In this mode, the device directly
overwrites the target next-startup configuration file. If a reboot or power failure occurs during this
process, the next-startup configuration file is lost. You must specify a new startup configuration file
after the device reboots (see "
Specifying a next-startup configuration file
").
Safe mode
—Use the
save
command with the
safely
keyword. Safe mode is slower than fast mode,
but more secure. In safe mode, the system saves configuration in a temporary file and starts