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

Parsing Rules, Chassis Management, Controller for PowerEdge VRTX RACADM Command Line Reference Guide

Page 76 highlights

The parser reads in all of the indexes from the CMC for that group. Any objects within that group are modifications when the CMC is configured. If a modified object represents a new index, the index is created on the CMC during configuration. • You cannot specify a desired index in a .cfg file. Indexes may be created and deleted. Over time, the group may become fragmented with used and unused indexes. If an index is present, it is modified. If an index is not present, the first available index is used. This method allows flexibility when adding indexed entries where you do not need to make exact index matches between all the CMCs being managed. New users are added to the first available index. A .cfg file that parses and runs correctly on one CMC may not run correctly on another, if all indexes are full and you must add a new user. • Use the racresetcfg subcommand to configure both the CMCs with identical properties. Use the racresetcfg subcommand to reset the CMC to original defaults, and then run the racadm config -f .cfg command. Make sure that the .cfg file includes all desired objects, users, indexes, and other parameters. For a complete list of objects and groups, see the Chassis Management Controller for PowerEdge VRTX RACADM Command Line Reference Guide. CAUTION: Use the racresetcfg subcommand to reset the database and the CMC Network Interface settings to the original default settings and remove all users and user configurations. While the root user is available, other users' settings are also reset to the default settings. • If you type racadm getconfig -f .cfg, the command builds a .cfg file for the current CMC configuration. This configuration file can be used as an example and as a starting point for your unique .cfg file. Parsing Rules • Lines that start with a hash character (#) are treated as comments. A comment line must start in column one. A "#" character in any other column is treated as a # character. Some modem parameters may include # characters in their strings. An escape character is not required. You may want to generate a .cfg from a racadm getconfig -f .cfg command, and then perform a racadm config -f .cfg command to a different CMC, without adding escape characters. For example: # # This is a comment [cfgUserAdmin] cfgUserAdminPageModemInitString= • All group entries must be surrounded by open- and close-brackets ([ and ]). The starting [ character that denotes a group name must be in column one. This group name must be specified before any of the objects in that group. Objects that do not include an associated group name generate an error. The configuration data is organized into groups as defined in the database property chapter of the RACADM Command Line Reference Guide for iDRAC6 and CMC. The following example displays a group name, object, and the object's property value: [cfgLanNetworking] -{group name} cfgNicIpAddress=143.154.133.121 {object name} {object value} • All parameters are specified as "object=value" pairs with no white space between the object, =, or value. White spaces that are included after the value are ignored. A white space inside a value string remains unmodified. 76

  • 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

The parser reads in all of the indexes from the CMC for that group. Any objects within that group are
modifications when the CMC is configured. If a modified object represents a new index, the index is created on
the CMC during configuration.
You cannot specify a desired index in a
.cfg
file.
Indexes may be created and deleted. Over time, the group may become fragmented with used and unused
indexes. If an index is present, it is modified. If an index is not present, the first available index is used.
This method allows flexibility when adding indexed entries where you do not need to make exact index matches
between all the CMCs being managed. New users are added to the first available index. A
.cfg
file that parses
and runs correctly on one CMC may not run correctly on another, if all indexes are full and you must add a new
user.
Use the
racresetcfg
subcommand to configure both the CMCs with identical properties.
Use the
racresetcfg
subcommand to reset the CMC to original defaults, and then run the
racadm
config -f <filename>.cfg
command. Make sure that the
.cfg
file includes all desired objects, users,
indexes, and other parameters. For a complete list of objects and groups, see the
Chassis Management
Controller for PowerEdge VRTX RACADM Command Line Reference Guide
.
CAUTION: Use the
racresetcfg
subcommand to reset the database and the CMC Network Interface
settings to the original default settings and remove all users and user configurations. While the root user is
available, other users’ settings are also reset to the default settings.
If you type
racadm getconfig -f <filename> .cfg
, the command builds a
.cfg
file for the current
CMC configuration. This configuration file can be used as an example and as a starting point for your unique
.cfg
file.
Parsing Rules
Lines that start with a hash character (#) are treated as comments.
A comment line must start in column one. A "#" character in any other column is treated as a # character.
Some modem parameters may include # characters in their strings. An escape character is not required. You
may want to generate a
.cfg
from a
racadm getconfig -f <filename> .cfg
command, and then
perform a
racadm config -f <filename> .cfg
command to a different CMC, without adding
escape characters.
For example:
#
# This is a comment
[cfgUserAdmin]
cfgUserAdminPageModemInitString= <Modem init # not
a comment>
All group entries must be surrounded by open- and close-brackets ([ and ]).
The starting [ character that denotes a group name must be in column one. This group name must be specified
before any of the objects in that group. Objects that do not include an associated group name generate an error.
The configuration data is organized into groups as defined in the database property chapter of the
RACADM
Command Line Reference Guide for iDRAC6 and CMC
. The following example displays a group name, object, and
the object’s property value:
[cfgLanNetworking] -{group name}
cfgNicIpAddress=143.154.133.121 {object name}
{object value}
All parameters are specified as "object=value" pairs with no white space between the object, =, or value. White
spaces that are included after the value are ignored. A white space inside a value string remains unmodified.
76