Unable to Resolve NTP Server's IP Address
The causes and resolutions refer to the Dell Modular Disk Storage Manager recovery guru. Launch Dell Modular Disk Storage Manager to diagnose and fix the recovery failure as follows:
Open Start >> Programs >> Dell >> MD Storage Manager >> Modular Disk Storage Manager Client.
If the MD Storage Array is already being managed by MDSM, you can proceed with the Causes and Resolution sections.
From Edit -> Add Storage Array, provide the IP address of the MD Storage Array and Add it to the discovered devices configuration in order to manage it.
Select the MD Storage Array and follow the steps specified in this recovery guru.
The RAID controller module is unable to resolve the IP address of one of its configured NTP servers.
Important Notes
If at least one of the RAID controller module's management ports are configured via DHCP, the RAID controller module may be able to automatically detect NTP and DNS servers from your DHCP server.
If neither of the management ports are configured via DHCP, or you do not wish the RAID controller module to use the NTP or DNS servers from your DHCP server's configuration, you may provide static addresses for the RAID controller module to use instead.
If a static NTP server's domain name is provided, a DNS server must also be configured on the RAID controller module to resolve the servers IP address. You may configure a DNS server for the RAID controller module in the Configure Domain Name System Server dialog by selecting the Hardware > RAID Controller Module > Configure > DNS Server menu option.
Confirm that the NTP server domain name list in the Details area is correct.
Open the Configure Network Time Protocol Server dialog by selecting the RAID controller module maml:listed in the Details area, and then the Hardware > RAID Controller Module > Configure > NTP Server menu option.
If... | Then... |
there is a typo in the Server's domain name | correct the domain name and go to step 3. |
the Server's domain name is correct | go to step 2. |
Confirm that the RAID controller module has at least one valid DNS Server configured.
Open the Configure Domain Name System Server dialog by selecting the RAID controller module that is listed in the recovery guru Details area, and then the Hardware > RAID Controller Module > Configure > DNS Server menu option.
If... | Then... |
the RAID controller module is set to obtain DNS server addresses automatically | go to step b. |
static DNS server addresses have been specified | check the following:
If the answer to any of the above questions is no, correct the problem and go to step 3. If the answer to all of the above is yes, contact your Technical Support Representative. |
Check if the RAID controller module can detect any DNS servers from your DHCP server.
If... | Then... |
DNS servers are being detected | check the following:
If the answer to any of the above questions is no, correct the problem and go to step 3. If the answer to all of the above is yes, contact your Technical Support Representative. |
no DNS servers were detected and at least one of the RAID controller module's management ports are configured via DHCP | add at least one DNS server to your DHCP server's configuration or specify at least one static DNS server address and go to step 3. |
no DNS servers were detected and neither of the RAID controller module's management ports are configured via DHCP | specify at least one static DNS server address and go to step 3. |
Wait one hour for the RAID controller module to re-query the specified NTP servers. If the failure does not disappear after one hour, recheck the RAID controller module's NTP and DNS configuration and then contact your Technical Support Representative.
Target | Microsoft.SystemCenter.ManagementServer | ||
Category | Alert | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | Warning | ||
Alert Priority | Normal | ||
Remotable | True | ||
Alert Message |
|
ID | Module Type | TypeId | RunAs |
---|---|---|---|
DS | DataSource | Microsoft.Windows.ScriptGenerated.EventProvider | Default |
Alert | WriteAction | System.Health.GenerateAlert | Default |
WriteToDW | WriteAction | Microsoft.SystemCenter.DataWarehouse.PublishEventData | Default |
<Rule ID="Dell.MDStorageArray.ABBXMLEvent465" Enabled="onEssentialMonitoring" Target="SystemCenter!Microsoft.SystemCenter.ManagementServer" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">
<Category>Alert</Category>
<DataSources>
<DataSource ID="DS" TypeID="Windows!Microsoft.Windows.ScriptGenerated.EventProvider">
<ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<ScriptName>RBODEventGenerator</ScriptName>
<EventNumber>465</EventNumber>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="Alert" TypeID="SystemHealth!System.Health.GenerateAlert">
<Priority>1</Priority>
<Severity>1</Severity>
<AlertMessageId>$MPElement[Name="Dell.MDStorageArray.ABBXMLEvent465.StringResource"]$</AlertMessageId>
<AlertParameters>
<AlertParameter1>$Data/EventDescription$</AlertParameter1>
</AlertParameters>
<Suppression>
<SuppressionValue>$Data/EventDisplayNumber$</SuppressionValue>
<SuppressionValue>$Data/Channel$</SuppressionValue>
<SuppressionValue>$Data/PublisherName$</SuppressionValue>
<SuppressionValue>$Data/LoggingComputer$</SuppressionValue>
<SuppressionValue>$Data/EventCategory$</SuppressionValue>
<SuppressionValue>$Data/EventLevel$</SuppressionValue>
<SuppressionValue>$Data/UserName$</SuppressionValue>
<SuppressionValue>$Data/EventNumber$</SuppressionValue>
<SuppressionValue>$Data/EventDescription$</SuppressionValue>
</Suppression>
<Custom1/>
<Custom2/>
<Custom3/>
<Custom4/>
<Custom5/>
<Custom6/>
<Custom7/>
<Custom8/>
<Custom9/>
<Custom10/>
</WriteAction>
<WriteAction ID="WriteToDW" TypeID="SCDW!Microsoft.SystemCenter.DataWarehouse.PublishEventData"/>
</WriteActions>
</Rule>