Dell PowerEdge VRTX Chassis Management Controller Version 1.0 for Dell PowerEd - Page 75

Creating a CMC Configuration File, Chassis Management Controller

Get Dell PowerEdge VRTX PDF manuals and user guides View all Dell PowerEdge VRTX manuals
Add to My Manuals
Save this manual to your list of manuals

Page 75 highlights

NOTE: Some configuration files contain unique CMC information (such as the static IP address) that must be modified before you export the file to other CMCs. 1. Use RACADM to query the target CMC that contains the desired configuration. NOTE: The generated configuration file is myfile.cfg. You can rename the file. The .cfg file does not contain user passwords. When the .cfg file is uploaded to the new CMC, you must re-add all passwords. 2. Open a Telnet/SSH text console to the CMC, log in, and type: racadm getconfig -f myfile.cfg NOTE: Redirecting the CMC configuration to a file using getconfig -f is only supported with the remote RACADM interface. 3. Modify the configuration file using a plain-text editor (optional). Any special formatting characters in the configuration file may corrupt the RACADM database. 4. Use the newly created configuration file to modify a target CMC. At the command prompt, type: racadm config -f myfile.cfg 5. Reset the target CMC that was configured. At the command prompt, type: racadm reset The getconfig -f myfile.cfg subcommand requests the CMC configuration for the active CMC and generates the myfile.cfg file. If required, you can rename the file or save it to a different location. You can run the getconfig command to perform the following actions: - Display all configuration properties in a group (specified by group name and index). - Display all configuration properties for a user by user name. The config subcommand loads the information into other CMCs. The Server Administrator uses the config command to synchronize the user and password database. Creating a CMC Configuration File The CMC configuration file, .cfg, is used with the racadm config -f .cfg command to create a simple text file. The command allows you to build a configuration file (similar to a .ini file) and configure the CMC from this file. You may use any file name, and the file does not require a .cfg extension (although it is referred to by that designation in this subsection). NOTE: For more information about the getconfig subcommand, see the Chassis Management Controller for PowerEdge VRTX RACADM Command Line Reference Guide. RACADM parses the .cfg file when it is first loaded on to the CMC to verify that a valid group and object names are present, and that simple syntax rules are being followed. Errors are flagged with the line number that detected the error, and a message explains the problem. The entire file is parsed for correctness, and all errors display. If an error is found in the .cfg file, write commands are not transmitted to the CMC. You must correct all errors before any configuration can take place. To check for errors before you create the configuration file, use the -c option with the config subcommand. With the -c option, config only verifies syntax and does not write to the CMC. Follow these guidelines when you create a .cfg file: • If the parser encounters an indexed group, it is the value of the anchored object that differentiates the various indexes. 75

  • 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
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
NOTE:
Some configuration files contain unique CMC information (such as the static IP address) that must be
modified before you export the file to other CMCs.
1.
Use RACADM to query the target CMC that contains the desired configuration.
NOTE:
The generated configuration file is
myfile.cfg
. You can rename the file. The
.cfg
file does not contain
user passwords. When the
.cfg
file is uploaded to the new CMC, you must re-add all passwords.
2.
Open a Telnet/SSH text console to the CMC, log in, and type:
racadm getconfig -f myfile.cfg
NOTE:
Redirecting the CMC configuration to a file using
getconfig -f
is only supported with the remote
RACADM interface.
3.
Modify the configuration file using a plain-text editor (optional). Any special formatting characters in the
configuration file may corrupt the RACADM database.
4.
Use the newly created configuration file to modify a target CMC. At the command prompt, type:
racadm config -f myfile.cfg
5.
Reset the target CMC that was configured. At the command prompt, type:
racadm reset
The
getconfig -f myfile.cfg
subcommand requests the CMC configuration for the active CMC and
generates the
myfile.cfg
file. If required, you can rename the file or save it to a different location.
You can run the
getconfig
command to perform the following actions:
–
Display all configuration properties in a group (specified by group name and index).
–
Display all configuration properties for a user by user name.
The
config
subcommand loads the information into other CMCs. The Server Administrator uses the
config
command to synchronize the user and password database.
Creating a CMC Configuration File
The CMC configuration file,
<filename>.cfg
, is used with the
racadm config -f <filename>.cfg
command to
create a simple text file. The command allows you to build a configuration file (similar to a
.ini
file) and configure the
CMC from this file.
You may use any file name, and the file does not require a
.cfg
extension (although it is referred to by that designation in
this subsection).
NOTE:
For more information about the
getconfig
subcommand, see the
Chassis Management Controller for
PowerEdge VRTX RACADM Command Line Reference Guide
.
RACADM parses the
.cfg
file when it is first loaded on to the CMC to verify that a valid group and object names are
present, and that simple syntax rules are being followed. Errors are flagged with the line number that detected the error,
and a message explains the problem. The entire file is parsed for correctness, and all errors display. If an error is found
in the
.cfg
file, write commands are not transmitted to the CMC. You must correct all errors before any configuration can
take place.
To check for errors before you create the configuration file, use the
-c
option with the
config
subcommand. With the
-c
option,
config
only verifies syntax and does not write to the CMC.
Follow these guidelines when you create a
.cfg
file:
•
If the parser encounters an indexed group, it is the value of the anchored object that differentiates the various
indexes.
75