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

Interpreting LED Colors and Blinking Patterns, Using Diagnostic Console

Page 175 highlights

You can also check the ntpd status by typing the following racadm command: racadm getractime -n If the '*' is not displayed for one of the configured servers, the settings may not be configured correctly. The output of this command contains detailed NTP statistics that may be useful in debugging the problem. If you attempt to configure a Windows-based NTP server, it may help to increase the MaxDist parameter for ntpd. Before changing this parameter, understand all the implications, since the default setting must be large enough to work with most NTP servers. To modify the parameter, type the following command: racadm config -g cfgRemoteHosts -o cfgRhostsNtpMaxDist 32 After making the change, disable NTP, wait for 5-10 seconds, then enable NTP again: NOTE: NTP may take an additional three minutes to synchronize again. To disable NTP, type: racadm config -g cfgRemoteHosts -o cfgRhostsNtpEnable 0 To enable NTP, type: racadm config -g cfgRemoteHosts -o cfgRhostsNtpEnable 1 If the NTP servers are configured correctly and this entry is present in the trace log, then this confirms that CMC is not able to synchronize with any of the configured NTP servers. If the NTP server IP address is not configured, you may see a trace log entry similar to the following: Jan 8 19:59:24 cmc ntpd[1423]: Cannot find existing interface for address 1.2.3.4 Jan 8 19:59:24 cmc ntpd[1423]: configuration of 1.2.3.4 failed If an NTP server setting was configured with an invalid host name, you may see a trace log entry as follows: Aug 21 14:34:27 cmc ntpd_initres[1298]: host name not found: blabla Aug 21 14:34:27 cmc ntpd_initres[1298]: couldn't resolve `blabla', giving up on it For information on how to enter the gettracelog command to review the trace log using the CMC Web interface, see Using Diagnostic Console. Interpreting LED Colors and Blinking Patterns The LEDs on the chassis provide the following status of a component: • Steadily glowing green LEDs indicate that the component is turned on. If the green LED is blinking, it indicates a critical but routine event, such as a firmware upload, during which the unit is not operational. It does not indicate a fault. • A blinking amber LED on a module indicates a fault on that module. • Blue, blinking LEDs are configurable by the user and used for identification. For more information about configuration, see Downloading SNMP Management Information Base MIB File. Table 32. LED Color and Blinking Patterns Component CMC LED Color, Blinking Pattern Green, glowing steadily Green, blinking Green, dark Status Turned on Firmware is being uploaded Turned off 175

  • 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

You can also check the ntpd status by typing the following racadm command:
racadm getractime –n
If the ‘*’ is not displayed for one of the configured servers, the settings may not be configured correctly. The output of
this command contains detailed NTP statistics that may be useful in debugging the problem.
If you attempt to configure a Windows-based NTP server, it may help to increase the
MaxDist
parameter for
ntpd
.
Before changing this parameter, understand all the implications, since the default setting must be large enough to work
with most NTP servers.
To modify the parameter, type the following command:
racadm config –g cfgRemoteHosts –o cfgRhostsNtpMaxDist 32
After making the change, disable NTP, wait for 5-10 seconds, then enable NTP again:
NOTE:
NTP may take an additional three minutes to synchronize again.
To disable NTP, type:
racadm config –g cfgRemoteHosts –o cfgRhostsNtpEnable 0
To enable NTP, type:
racadm config –g cfgRemoteHosts –o cfgRhostsNtpEnable 1
If the NTP servers are configured correctly and this entry is present in the trace log, then this confirms that CMC is not
able to synchronize with any of the configured NTP servers.
If the NTP server IP address is not configured, you may see a trace log entry similar to the following:
Jan 8 19:59:24 cmc ntpd[1423]: Cannot find existing interface for address
1.2.3.4 Jan 8 19:59:24 cmc ntpd[1423]: configuration of 1.2.3.4 failed
If an NTP server setting was configured with an invalid host name, you may see a trace log entry as follows:
Aug 21 14:34:27 cmc ntpd_initres[1298]: host name not found: blabla Aug 21
14:34:27 cmc ntpd_initres[1298]: couldn't resolve `blabla', giving up on it
For information on how to enter the
gettracelog
command to review the trace log using the CMC Web interface,
see
Using Diagnostic Console
.
Interpreting LED Colors and Blinking Patterns
The LEDs on the chassis provide the following status of a component:
Steadily glowing green LEDs indicate that the component is turned on. If the green LED is blinking, it indicates a
critical but routine event, such as a firmware upload, during which the unit is not operational. It does not
indicate a fault.
A blinking amber LED on a module indicates a fault on that module.
Blue, blinking LEDs are configurable by the user and used for identification. For more information about
configuration, see
Downloading SNMP Management Information Base MIB File
.
Table 32. LED Color and Blinking Patterns
Component
LED Color, Blinking Pattern
Status
CMC
Green, glowing steadily
Turned on
Green, blinking
Firmware is being uploaded
Green, dark
Turned off
175