<?xml version="1.0" encoding="UTF-8"?>
<!-- alertStrings.XML V1.1 September 9, 2005 -->
<!-- This XML contains the English language strings for all MSM events -->
<!-- Copyright, 2005 by Avago Technologies
All Rights Reserved, Confidential, Unpublished Property of Avago Technologies

THIS DOCUMENT AND INFORMATION HEREIN IS THE PROPERTY OF Avago Technologies AND ALL UNAUTHORIZED USE AND REPRODUCTION IS PROHIBITED.

Avago Technologies. 
6145-D Northbelt Parkway
NORCROSS, GEORGIA, 30071 
 -->
<!-- REVISION HISTORY -->
<!-- V1.0 	9/8/2005
		First Release
 -->
<!-- V1.1	9/9/2005
		- Added messages 10000 through 10003
		- Substituted ":" for "to" in messages ending with "to" to facilitate language translation
 -->
<!-- V1.2	9/28/2005
		- Added tag alertString to each alert and changed the root tag to alertStringsList
 -->
<alertStringsList>
  <alertString>
    <id>0</id>

    <description> Firmware initialization started:</description>
  </alertString>

  <alertString>
    <id>1</id>

    <description> Image version:</description>
  </alertString>

  <alertString>
    <id>2</id>

    <description> Unable to recover cache data from TBBU</description>
  </alertString>

  <alertString>
    <id>3</id>

    <description> Cache data recovered from TBBU successfully</description>
  </alertString>

  <alertString>
    <id>4</id>

    <description> Configuration cleared</description>
  </alertString>

  <alertString>
    <id>5</id>

    <description> Cluster down; communication with peer lost</description>
  </alertString>

  <alertString>
    <id>6</id>

    <description> Logical drive ownership changed:</description>
  </alertString>

  <alertString>
    <id>7</id>

    <description> Alarm disabled by user</description>
  </alertString>

  <alertString>
    <id>8</id>

    <description> Alarm enabled by user</description>
  </alertString>

  <alertString>
    <id>9</id>

    <description> Background initialization rate changed:</description>
  </alertString>

  <alertString>
    <id>10</id>

    <description> Controller cache discarded due to memory/battery
    problems</description>
  </alertString>

  <alertString>
    <id>11</id>

    <description> Unable to recover cache data due to configuration
    mismatch</description>
  </alertString>

  <alertString>
    <id>12</id>

    <description> Cache data recovered successfully</description>
  </alertString>

  <alertString>
    <id>13</id>

    <description> Controller cache discarded due to firmware version
    incompatibility</description>
  </alertString>

  <alertString>
    <id>14</id>

    <description> Consistency Check rate changed:</description>
  </alertString>

  <alertString>
    <id>15</id>

    <description> Fatal firmware error:</description>
  </alertString>

  <alertString>
    <id>16</id>

    <description> Factory defaults restored</description>
  </alertString>

  <alertString>
    <id>17</id>

    <description> Flash downloaded image corrupt</description>
  </alertString>

  <alertString>
    <id>18</id>

    <description> Flash erase error</description>
  </alertString>

  <alertString>
    <id>19</id>

    <description> Flash timeout during erase</description>
  </alertString>

  <alertString>
    <id>20</id>

    <description> Flash error</description>
  </alertString>

  <alertString>
    <id>21</id>

    <description> Flashing image:</description>
  </alertString>

  <alertString>
    <id>22</id>

    <description> Flash of new firmware image(s) complete</description>
  </alertString>

  <alertString>
    <id>23</id>

    <description> Flash programming error</description>
  </alertString>

  <alertString>
    <id>24</id>

    <description> Flash timeout during programming</description>
  </alertString>

  <alertString>
    <id>25</id>

    <description> Flash chip type unknown</description>
  </alertString>

  <alertString>
    <id>26</id>

    <description> Flash command set unknown</description>
  </alertString>

  <alertString>
    <id>27</id>

    <description> Flash verify failure</description>
  </alertString>

  <alertString>
    <id>28</id>

    <description> Flush rate changed:</description>
  </alertString>

  <alertString>
    <id>29</id>

    <description> Hibernate command received from host</description>
  </alertString>

  <alertString>
    <id>30</id>

    <description> Event log cleared</description>
  </alertString>

  <alertString>
    <id>31</id>

    <description> Event log wrapped</description>
  </alertString>

  <alertString>
    <id>32</id>

    <description> Multi-bit ECC error:</description>
  </alertString>

  <alertString>
    <id>33</id>

    <description> Single-bit ECC error:</description>
  </alertString>

  <alertString>
    <id>34</id>

    <description> Not enough controller memory</description>
  </alertString>

  <alertString>
    <id>35</id>

    <description> Patrol Read complete</description>
  </alertString>

  <alertString>
    <id>36</id>

    <description> Patrol Read paused</description>
  </alertString>

  <alertString>
    <id>37</id>

    <description> Patrol Read Rate changed:</description>
  </alertString>

  <alertString>
    <id>38</id>

    <description> Patrol Read resumed</description>
  </alertString>

  <alertString>
    <id>39</id>

    <description> Patrol Read started</description>
  </alertString>

  <alertString>
    <id>40</id>

    <description> Rebuild rate changed:</description>
  </alertString>

  <alertString>
    <id>41</id>

    <description> Reconstruction rate changed:</description>
  </alertString>

  <alertString>
    <id>42</id>

    <description> Shutdown command received from host</description>
  </alertString>

  <alertString>
    <id>43</id>

    <description> Test event:</description>
  </alertString>

  <alertString>
    <id>44</id>

    <description> Time established since power on:</description>
  </alertString>

  <alertString>
    <id>45</id>

    <description> User entered firmware debugger</description>
  </alertString>

  <alertString>
    <id>46</id>

    <description> Background Initialization aborted on VD:</description>
  </alertString>

  <alertString>
    <id>47</id>
    <description> Background Initialization corrected medium error:</description>
  </alertString>

  <alertString>
    <id>48</id>

    <description> Background Initialization completed on VD:</description>
  </alertString>

  <alertString>
    <id>49</id>

    <description> Background Initialization completed with uncorrectable
    errors on VD:</description>
  </alertString>

  <alertString>
    <id>50</id>

    <description> Background Initialization detected uncorrectable multiple
    medium errors:</description>
  </alertString>

  <alertString>
    <id>51</id>

    <description> Background Initialization failed on VD:</description>
  </alertString>

  <alertString>
    <id>52</id>

    <description> Background Initialization progress:</description>
  </alertString>

  <alertString>
    <id>53</id>

    <description> Background Initialization started on VD:</description>
  </alertString>

  <alertString>
    <id>54</id>

    <description> Policy change on VD:</description>
  </alertString>

  <alertString>
    <id>55</id>

    <description> OBSOLETE</description>
  </alertString>

  <alertString>
    <id>56</id>

    <description> Consistency Check aborted on VD:</description>
  </alertString>

  <alertString>
    <id>57</id>

    <description> Consistency Check corrected medium error:</description>
  </alertString>

  <alertString>
    <id>58</id>

    <description> Consistency Check done on VD:</description>
  </alertString>

  <alertString>
    <id>59</id>

    <description> Consistency Check done with corrections on VD:</description>
  </alertString>

  <alertString>
    <id>60</id>

    <description> Consistency Check detected uncorrectable multiple medium
    errors:</description>
  </alertString>

  <alertString>
    <id>61</id>

    <description> Consistency Check failed on VD:</description>
  </alertString>

  <alertString>
    <id>62</id>
    <description>Consistency Check completed with uncorrectable errors on VD:</description>
  </alertString>

  <alertString>
    <id>63</id>

    <description> Consistency Check found inconsistent parity on VD
    strip:</description>
  </alertString>

  <alertString>
    <id>64</id>

    <description> Consistency Check inconsistency logging disabled, too many
    inconsistencies on VD:</description>
  </alertString>

  <alertString>
    <id>65</id>

    <description> Consistency Check progress:</description>
  </alertString>

  <alertString>
    <id>66</id>

    <description> Consistency Check started on VD:</description>
  </alertString>

  <alertString>
    <id>67</id>

    <description> Initialization aborted on VD:</description>
  </alertString>

  <alertString>
    <id>68</id>

    <description> Initialization failed on VD:</description>
  </alertString>

  <alertString>
    <id>69</id>

    <description> Initialization progress on VD:</description>
  </alertString>

  <alertString>
    <id>70</id>

    <description> Fast initialization started on VD:</description>
  </alertString>

  <alertString>
    <id>71</id>

    <description> Full initialization started on VD:</description>
  </alertString>

  <alertString>
    <id>72</id>

    <description> Initialization complete on VD</description>
  </alertString>

  <alertString>
    <id>73</id>

    <description> Properties updated on VD:</description>
  </alertString>

  <alertString>
    <id>74</id>

    <description> Reconstruction complete:</description>
  </alertString>

  <alertString>
    <id>75</id>

    <description> Reconstruction stopped due to unrecoverable
    errors:</description>
  </alertString>

  <alertString>
    <id>76</id>

    <description> Reconstruct detected uncorrectable multiple medium
    errors:</description>
  </alertString>

  <alertString>
    <id>77</id>

    <description> Reconstruction progress:</description>
  </alertString>

  <alertString>
    <id>78</id>

    <description> Reconstruction resumed:</description>
  </alertString>

  <alertString>
    <id>79</id>

    <description> Reconstruction resume failed due to configuration
    mismatch:</description>
  </alertString>

  <alertString>
    <id>80</id>

    <description> Reconstruction started:</description>
  </alertString>

  <alertString>
    <id>81</id>

    <description> State change on VD:</description>
  </alertString>

  <alertString>
    <id>82</id>

    <description> PD Clear aborted:</description>
  </alertString>

  <alertString>
    <id>83</id>

    <description> PD Clear failed:</description>
  </alertString>

  <alertString>
    <id>84</id>

    <description> PD Clear progress:</description>
  </alertString>

  <alertString>
    <id>85</id>

    <description> PD Clear started:</description>
  </alertString>

  <alertString>
    <id>86</id>

    <description> PD Clear completed:</description>
  </alertString>

  <alertString>
    <id>87</id>

    <description> PD Error:</description>
  </alertString>

  <alertString>
    <id>88</id>

    <description> PD Format complete:</description>
  </alertString>

  <alertString>
    <id>89</id>

    <description> PD Format started:</description>
  </alertString>

  <alertString>
    <id>90</id>

    <description> Hot Spare SMART polling failed on PD:</description>
  </alertString>

  <alertString>
    <id>91</id>

    <description> PD inserted:</description>
  </alertString>

  <alertString>
    <id>92</id>

    <description> PD is not supported:</description>
  </alertString>

  <alertString>
    <id>93</id>
    <description> Patrol Read corrected medium error:</description>
  </alertString>

  <alertString>
    <id>94</id>

    <description> Patrol Read progress:</description>
  </alertString>

  <alertString>
    <id>95</id>

    <description> Patrol Read found an uncorrectable medium
    error:</description>
  </alertString>

  <alertString>
    <id>96</id>

    <description> PD Predictive failure:</description>
  </alertString>

  <alertString>
    <id>97</id>

    <description> Puncturing bad block:</description>
  </alertString>

  <alertString>
    <id>98</id>

    <description> Rebuild aborted by user:</description>
  </alertString>

  <alertString>
    <id>99</id>

    <description> Rebuild complete on VD</description>
  </alertString>

  <alertString>
    <id>100</id>

    <description> Rebuild complete</description>
  </alertString>

  <alertString>
    <id>101</id>

    <description> Rebuild failed due to source drive error:</description>
  </alertString>

  <alertString>
    <id>102</id>

    <description> Rebuild failed due to target drive error:</description>
  </alertString>

  <alertString>
    <id>103</id>

    <description> Rebuild progress:</description>
  </alertString>

  <alertString>
    <id>104</id>

    <description> Rebuild resumed:</description>
  </alertString>

  <alertString>
    <id>105</id>

    <description> Rebuild started:</description>
  </alertString>

  <alertString>
    <id>106</id>

    <description> Rebuild automatically started:</description>
  </alertString>

  <alertString>
    <id>107</id>

    <description> Rebuild stopped due to loss of cluster
    ownership:</description>
  </alertString>

  <alertString>
    <id>108</id>

    <description> Reassign write operation failed:</description>
  </alertString>

  <alertString>
    <id>109</id>

    <description> Unrecoverable medium error during rebuild:</description>
  </alertString>

  <alertString>
    <id>110</id>

    <description> Corrected medium error during recovery:</description>
  </alertString>

  <alertString>
    <id>111</id>

    <description> Unrecoverable medium error during recovery:</description>
  </alertString>

  <alertString>
    <id>112</id>

    <description> PD removed:</description>
  </alertString>

  <alertString>
    <id>113</id>

    <description> Unexpected sense:</description>
  </alertString>

  <alertString>
    <id>114</id>

    <description> State change:</description>
  </alertString>

  <alertString>
    <id>115</id>

    <description> State change by user:</description>
  </alertString>

  <alertString>
    <id>116</id>

    <description> Redundant path broken:</description>
  </alertString>

  <alertString>
    <id>117</id>

    <description> Redundant path restored:</description>
  </alertString>

  <alertString>
    <id>118</id>

    <description> Dedicated Hot Spare no longer useful due to deleted
    array:</description>
  </alertString>

  <alertString>
    <id>119</id>

    <description> SAS topology error: Loop detected</description>
  </alertString>

  <alertString>
    <id>120</id>

    <description> SAS topology error: Device not addressable</description>
  </alertString>

  <alertString>
    <id>121</id>

    <description> SAS topology error: Multiple ports to the same SAS
    address</description>
  </alertString>

  <alertString>
    <id>122</id>

    <description> SAS topology error: Expander error</description>
  </alertString>

  <alertString>
    <id>123</id>

    <description> SAS topology error: SMP timeout</description>
  </alertString>

  <alertString>
    <id>124</id>

    <description> SAS topology error: Out of route entries</description>
  </alertString>

  <alertString>
    <id>125</id>

    <description> SAS topology error: Index not found</description>
  </alertString>

  <alertString>
    <id>126</id>

    <description> SAS topology error: SMP function failed</description>
  </alertString>

  <alertString>
    <id>127</id>

    <description> SAS topology error: SMP CRC error</description>
  </alertString>

  <alertString>
    <id>128</id>

    <description> SAS topology error: Multiple subtractive</description>
  </alertString>

  <alertString>
    <id>129</id>

    <description> SAS topology error: Table to table</description>
  </alertString>

  <alertString>
    <id>130</id>

    <description> SAS topology error: Multiple paths</description>
  </alertString>

  <alertString>
    <id>131</id>

    <description> Unable to access device</description>
  </alertString>

  <alertString>
    <id>132</id>

    <description> Dedicated Hot Spare created:</description>
  </alertString>

  <alertString>
    <id>133</id>

    <description> Dedicated Hot Spare disabled:</description>
  </alertString>

  <alertString>
    <id>134</id>

    <description> Dedicated Hot Spare no longer useful for all
    arrays:</description>
  </alertString>

  <alertString>
    <id>135</id>

    <description> Global Hot Spare created:</description>
  </alertString>

  <alertString>
    <id>136</id>

    <description> Global Hot Spare disabled:</description>
  </alertString>

  <alertString>
    <id>137</id>

    <description> Global Hot Spare does not cover all arrays</description>
  </alertString>

  <alertString>
    <id>138</id>

    <description> Created VD:</description>
  </alertString>

  <alertString>
    <id>139</id>

    <description> Deleted VD:</description>
  </alertString>

  <alertString>
    <id>140</id>

    <description> VD Marked inconsistent due to active writes at
    shutdown:</description>
  </alertString>

  <alertString>
    <id>141</id>

    <description> Battery Present</description>
  </alertString>

  <alertString>
    <id>142</id>

    <description> Battery Not Present</description>
  </alertString>

  <alertString>
    <id>143</id>

    <description> New Battery Detected</description>
  </alertString>

  <alertString>
    <id>144</id>

    <description> Battery has been replaced</description>
  </alertString>

  <alertString>
    <id>145</id>

    <description> Battery temperature is high</description>
  </alertString>

  <alertString>
    <id>146</id>

    <description> Battery voltage low</description>
  </alertString>

  <alertString>
    <id>147</id>

    <description> Battery started charging</description>
  </alertString>

  <alertString>
    <id>148</id>

    <description> Battery is discharging</description>
  </alertString>

  <alertString>
    <id>149</id>

    <description> Battery temperature is normal</description>
  </alertString>

  <alertString>
    <id>150</id>

    <description> Battery has failed and cannot support data retention. Please replace the battery</description>
  </alertString>

  <alertString>
    <id>151</id>

    <description> Battery relearn started</description>
  </alertString>

  <alertString>
    <id>152</id>

    <description> Battery relearn in progress</description>
  </alertString>

  <alertString>
    <id>153</id>

    <description> Battery relearn completed</description>
  </alertString>

  <alertString>
    <id>154</id>

    <description> Battery relearn timed out</description>
  </alertString>

  <alertString>
    <id>155</id>

    <description> Battery relearn pending: Battery is under
    charge</description>
  </alertString>

  <alertString>
    <id>156</id>

    <description> Battery relearn postponed</description>
  </alertString>

  <alertString>
    <id>157</id>

    <description> Battery relearn will start in 4 days</description>
  </alertString>

  <alertString>
    <id>158</id>

    <description> Battery relearn will start in 2 days</description>
  </alertString>

  <alertString>
    <id>159</id>

    <description> Battery relearn will start in 1 day</description>
  </alertString>

  <alertString>
    <id>160</id>

    <description> Battery relearn will start in 5 hours</description>
  </alertString>

  <alertString>
    <id>161</id>

    <description> Battery removed</description>
  </alertString>

  <alertString>
    <id>162</id>

    <description> Current capacity of the battery is below
    threshold</description>
  </alertString>

  <alertString>
    <id>163</id>

    <description> Current capacity of the battery is above
    threshold</description>
  </alertString>

  <alertString>
    <id>164</id>

    <description> SES enclosure discovered:</description>
  </alertString>

  <alertString>
    <id>165</id>

    <description> SAF-TE enclosure discovered:</description>
  </alertString>

  <alertString>
    <id>166</id>

    <description> Communication lost on enclosure:</description>
  </alertString>

  <alertString>
    <id>167</id>

    <description> Communication restored on enclosure:</description>
  </alertString>

  <alertString>
    <id>168</id>

    <description> Fan failed on enclosure:</description>
  </alertString>

  <alertString>
    <id>169</id>

    <description> Fan inserted on enclosure:</description>
  </alertString>

  <alertString>
    <id>170</id>

    <description> Fan removed on enclosure:</description>
  </alertString>

  <alertString>
    <id>171</id>

    <description> Power supply failed on enclosure:</description>
  </alertString>

  <alertString>
    <id>172</id>

    <description> Power supply inserted on enclosure:</description>
  </alertString>

  <alertString>
    <id>173</id>

    <description> Power supply removed on enclosure:</description>
  </alertString>

  <alertString>
    <id>174</id>

    <description> ESM failed on enclosure:</description>
  </alertString>

  <alertString>
    <id>175</id>

    <description> ESM inserted on enclosure:</description>
  </alertString>

  <alertString>
    <id>176</id>

    <description> SIM removed on enclosure:</description>
  </alertString>

  <alertString>
    <id>177</id>

    <description> Temperature sensor below warning threshold on
    enclosure:</description>
  </alertString>

  <alertString>
    <id>178</id>

    <description> Temperature sensor below error threshold on
    enclosure:</description>
  </alertString>

  <alertString>
    <id>179</id>

    <description> Temperature sensor above warning threshold on
    enclosure:</description>
  </alertString>

  <alertString>
    <id>180</id>

    <description> Temperature sensor above error threshold on
    enclosure:</description>
  </alertString>

  <alertString>
    <id>181</id>

    <description> Enclosure shutdown:</description>
  </alertString>

  <alertString>
    <id>182</id>

    <description> Too many enclosures connected to port. Enclosure not
    supported:</description>
  </alertString>

  <alertString>
    <id>183</id>

    <description> Firmware mismatch on enclosure:</description>
  </alertString>

  <alertString>
    <id>184</id>

    <description> Sensor bad on enclosure:</description>
  </alertString>

  <alertString>
    <id>185</id>

    <description> Phy is bad on enclosure:</description>
  </alertString>

  <alertString>
    <id>186</id>

    <description> Unstable Enclosure:</description>
  </alertString>

  <alertString>
    <id>187</id>

    <description> Hardware error on enclosure:</description>
  </alertString>

  <alertString>
    <id>188</id>

    <description> No response from enclosure:</description>
  </alertString>

  <alertString>
    <id>189</id>

    <description> SAS/SATA mixing not supported in enclosure; disabled
    PD:</description>
  </alertString>

  <alertString>
    <id>190</id>

    <description> Unsupported hotplug was detected on SES
    enclosure:</description>
  </alertString>

  <alertString>
    <id>191</id>

    <description> Clustering enabled</description>
  </alertString>

  <alertString>
    <id>192</id>

    <description> Clustering disabled</description>
  </alertString>

  <alertString>
    <id>193</id>

    <description> PD too small to be used for auto-rebuild:</description>
  </alertString>

  <alertString>
    <id>194</id>

    <description> BBU enabled; changing WT logical drives to WB</description>
  </alertString>

  <alertString>
    <id>195</id>

    <description> BBU disabled; changing WB logical drives to WT, Forced WB VDs are not affected</description>
  </alertString>

  <alertString>
    <id>196</id>

    <description> Bad block table is 80% full on PD:</description>
  </alertString>

  <alertString>
    <id>197</id>

    <description> Bad block table is full; unable to log block:</description>
  </alertString>

  <alertString>
    <id>198</id>

    <description> Consistency Check Aborted Due to Ownership Loss on
    VD:</description>
  </alertString>

  <alertString>
    <id>199</id>

    <description> Background Initialization (BGI) aborted due to ownership
    loss on VD:</description>
  </alertString>

  <alertString>
    <id>200</id>

    <description> Battery/charger problems detected; SOH Bad</description>
  </alertString>

  <alertString>
    <id>201</id>

    <description> Single-bit ECC error; warning threshold
    exceeded:</description>
  </alertString>

  <alertString>
    <id>202</id>

    <description> Single-bit ECC error; critical threshold
    exceeded:</description>
  </alertString>

  <alertString>
    <id>203</id>

    <description> Single-bit ECC error; further reporting
    disabled:</description>
  </alertString>

  <alertString>
    <id>204</id>

    <description> Power supply switched off for enclosure:</description>
  </alertString>

  <alertString>
    <id>205</id>

    <description> Power supply switched on for enclosure:</description>
  </alertString>

  <alertString>
    <id>206</id>

    <description> Power supply cable removed on enclosure:</description>
  </alertString>

  <alertString>
    <id>207</id>

    <description> Power supply cable inserted on enclosure:</description>
  </alertString>

  <alertString>
    <id>208</id>

    <description> Fan returned to normal on enclosure:</description>
  </alertString>

  <alertString>
    <id>209</id>

    <description> BBU Retention test was initiated on previous
    boot</description>
  </alertString>

  <alertString>
    <id>210</id>

    <description> BBU Retention test passed</description>
  </alertString>

  <alertString>
    <id>211</id>

    <description> BBU Retention test failed!</description>
  </alertString>

  <alertString>
    <id>212</id>

    <description> NVRAM Retention test was initiated on previous
    boot</description>
  </alertString>

  <alertString>
    <id>213</id>

    <description> NVRAM Retention test passed</description>
  </alertString>

  <alertString>
    <id>214</id>

    <description> NVRAM Retention test failed!</description>
  </alertString>

  <alertString>
    <id>215</id>

    <description> Successfully completed test:</description>
  </alertString>

  <alertString>
    <id>216</id>

    <description> FAILED Test:</description>
  </alertString>

  <alertString>
    <id>217</id>

    <description> Self check diagnostics completed</description>
  </alertString>

  <alertString>
    <id>218</id>

    <description> Foreign Configuration Detected</description>
  </alertString>

  <alertString>
    <id>219</id>

    <description> Foreign Configuration Imported</description>
  </alertString>

  <alertString>
    <id>220</id>

    <description> Foreign Configuration Cleared</description>
  </alertString>

  <alertString>
    <id>221</id>

    <description> NVRAM is corrupt; reinitializing</description>
  </alertString>

  <alertString>
    <id>222</id>

    <description> NVRAM mismatch occurred</description>
  </alertString>

  <alertString>
    <id>223</id>

    <description> Link lost on SAS wide port:</description>
  </alertString>

  <alertString>
    <id>224</id>

    <description> Link restored on SAS wide port:</description>
  </alertString>

  <alertString>
    <id>225</id>

    <description> Allowed error rate exceeded on SAS port:</description>
  </alertString>

  <alertString>
    <id>226</id>

    <description> Bad block reassigned:</description>
  </alertString>

  <alertString>
    <id>227</id>

    <description> Controller Hot Plug detected</description>
  </alertString>

  <alertString>
    <id>228</id>

    <description> Temperature sensor differential detected on
    enclosure:</description>
  </alertString>

  <alertString>
    <id>229</id>

    <description> Disk test cannot start. No qualifying disks
    found</description>
  </alertString>

  <alertString>
    <id>230</id>

    <description> Time duration provided by host is not sufficient for self
    check</description>
  </alertString>

  <alertString>
    <id>231</id>

    <description> Marked Missing on array:</description>
  </alertString>

  <alertString>
    <id>232</id>

    <description> Replaced Missing on array:</description>
  </alertString>

  <alertString>
    <id>233</id>

    <description> Temperature returned to normal on enclosure:</description>
  </alertString>

  <alertString>
    <id>234</id>

    <description> Firmware download in progress on enclosure:</description>
  </alertString>

  <alertString>
    <id>235</id>

    <description> Firmware download failed on enclosure:</description>
  </alertString>

  <alertString>
    <id>236</id>

    <description> Drive is not certified:</description>
  </alertString>

  <alertString>
    <id>237</id>

    <description> Dirty Cache data discarded by user</description>
  </alertString>

  <alertString>
    <id>238</id>

    <description> PDs missing from configuration at boot</description>
  </alertString>

  <alertString>
    <id>239</id>

    <description> VDs missing drives and will go offline at boot</description>
  </alertString>

  <alertString>
    <id>240</id>

    <description> VDs missing at boot</description>
  </alertString>

  <alertString>
    <id>241</id>

    <description> Previous configuration completely missing at
    boot</description>
  </alertString>

  <alertString>
    <id>242</id>

    <description> Battery charge complete</description>
  </alertString>

  <alertString>
    <id>243</id>

    <description> Fan speed changed on enclosure:</description>
  </alertString>

  <alertString>
    <id>244</id>

    <description>Dedicated spare imported as global due to missing
    arrays</description>
  </alertString>

  <alertString>
    <id>245</id>

    <description>PD rebuild not possible as SAS/SATA is not supported in an
    array</description>
  </alertString>

  <alertString>
    <id>246</id>

    <description>SEP has been rebooted as a part of enclosure firmware
    download. SEP will be unavailable until reboot
    completes.</description>
  </alertString>

  <alertString>
    <id>247</id>

    <description>Device inserted</description>
  </alertString>

  <alertString>
    <id>248</id>

    <description>Device removed</description>
  </alertString>

  <alertString>
    <id>249</id>

    <description>VD is now OPTIMAL</description>
  </alertString>

  <alertString>
    <id>250</id>

    <description>VD is now PARTIALLY DEGRADED</description>
  </alertString>

  <alertString>
    <id>251</id>

    <description>VD is now DEGRADED</description>
  </alertString>

  <alertString>
    <id>252</id>

    <description>VD is now OFFLINE</description>
  </alertString>

  <alertString>
    <id>253</id>

    <description>Battery requires reconditioning; please initiate a LEARN
    cycle</description>
  </alertString>

  <alertString>
    <id>254</id>

    <description>VD disabled because RAID-5 is not supported by this RAID
    key</description>
  </alertString>

  <alertString>
    <id>255</id>

    <description>VD disabled because RAID-6 is not supported by this
    controller</description>
  </alertString>

  <alertString>
    <id>256</id>

    <description>VD disabled because SAS drives are not supported by this RAID
    key</description>
  </alertString>

  <alertString>
    <id>257</id>

    <description>PD missing</description>
  </alertString>

  <alertString>
    <id>258</id>

    <description>Puncturing of LBAs enabled</description>
  </alertString>

  <alertString>
    <id>259</id>

    <description>Puncturing of LBAs disabled</description>
  </alertString>

  <alertString>
    <id>260</id>

    <description>Enclosure ESM not installed</description>
  </alertString>

  <alertString>
    <id>261</id>

    <description>Package version</description>
  </alertString>

  <alertString>
    <id>262</id>
    <description>Global affinity Hot Spare commissioned in a different enclosure</description>
  </alertString>

  <alertString>
    <id>263</id>
    <description>Foreign configuration table overflow</description>
  </alertString>

  <alertString>
    <id>264</id>
    <description>Partial foreign configuration imported, PDs not imported:</description>
  </alertString>

  <alertString>
    <id>265</id>
    <description>Connector is active:</description>
  </alertString>

  <alertString>
    <id>266</id>
    <description>Board Revision:</description>
  </alertString>

  <alertString>
    <id>267</id>
    <description>Command timeout on PD:</description>
  </alertString>

  <alertString>
    <id>268</id>
    <description>PD Reset:</description>
  </alertString>

  <alertString>
    <id>269</id>
    <description>VD bad block table is 80% full:</description>
  </alertString>

  <alertString>
    <id>270</id>
    <description>VD bad block table is full - unable to log block:</description>
  </alertString>

  <alertString>
    <id>271</id>
    <description>Uncorrectable medium error logged:</description>
  </alertString>

  <alertString>
    <id>272</id>
    <description>VD medium error corrected:</description>
  </alertString>

  <alertString>
    <id>273</id>
    <description>PD Bad block table is 100% full:</description>
  </alertString>

  <alertString>
    <id>274</id>
    <description>VD Bad block table is 100% full:</description>
  </alertString>

  <alertString>
    <id>275</id>
    <description>Controller needs replacement since IOP is faulty</description>
  </alertString>

  <alertString>
    <id>276</id>
    <description>Replace drive operation started on PD:</description>
  </alertString>

  <alertString>
    <id>277</id>
    <description>Replace drive operation aborted on PD:</description>
  </alertString>

  <alertString>
    <id>278</id>
    <description>Replace drive operation completed on PD:</description>
  </alertString>

  <alertString>
    <id>279</id>
    <description>Replace drive operation progress on PD:</description>
  </alertString>

  <alertString>
    <id>280</id>
    <description>Replace drive operation resumed on PD:</description>
  </alertString>

  <alertString>
    <id>281</id>
    <description>Replace drive operation automatically started on PD:</description>
  </alertString>

  <alertString>
    <id>282</id>
    <description>Replace drive operation failed due to source drive error on PD:</description>
  </alertString>

  <alertString>
    <id>283</id>
    <description>Early power off warning was unsuccessful</description>
  </alertString>

  <alertString>
    <id>284</id>
    <description>BBU FRU is: </description>
  </alertString>

  <alertString>
    <id>285</id>
    <description>PD FRU is: </description>
  </alertString>

  <alertString>
    <id>286</id>
    <description>Controller hardware revision id is: </description>
  </alertString>

  <alertString>
    <id>287</id>
    <description>Foreign import shall result in a backward incompatible upgrade of configuration metadata</description>
  </alertString>

  <alertString>
    <id>288</id>
    <description>Redundant path restored</description>
  </alertString>

  <alertString>
    <id>289</id>
    <description>Redundant path broken</description>
  </alertString>

  <alertString>
    <id>290</id>
    <description>Redundant enclosure module inserted</description>
  </alertString>

  <alertString>
    <id>291</id>
    <description>Redundant enclosure module removed</description>
  </alertString>

  <alertString>
    <id>292</id>
    <description>Patrol Read can't be started, as PDs are either not ONLINE, or are in a VD with an active process, or are in an excluded VD</description>
  </alertString>

  <alertString>
    <id>293</id>
    <description>Replace drive operation aborted by user on PD:</description>
  </alertString>

  <alertString>
    <id>294</id>
    <description>Replace drive operation aborted on the hot spare as hot spare needed for rebuild. Hot Spare PD:</description>
  </alertString>

  <alertString>
    <id>295</id>
    <description>Replace drive operation aborted as rebuild required in the array. PD:</description>
  </alertString>

  <alertString>
    <id>296</id>
    <description>Controller cache discarded for missing or offline VD</description>
  </alertString>

  <alertString>
    <id>297</id>
    <description>Replace drive operation cannot be started as drive is too small. PD:</description>
  </alertString>

  <alertString>
    <id>298</id>
    <description>Replace drive operation cannot be started as SAS/SATA is not supported in an array. PD:</description>
  </alertString>

  <alertString>
    <id>299</id>
    <description>Microcode update started on PD:</description>
  </alertString>

  <alertString>
    <id>300</id>
    <description>Microcode update completed on PD:</description>
  </alertString>

  <alertString>
    <id>301</id>
    <description>Microcode update timeout on PD:</description>
  </alertString>

  <alertString>
    <id>302</id>
    <description>Microcode update failed on PD:</description>
  </alertString>

  <alertString>
    <id>303</id>
    <description>Controller properties changed</description>
  </alertString>

  <alertString>
    <id>304</id>
    <description>Patrol Read properties changed</description>
  </alertString>

  <alertString>
    <id>305</id>
    <description>CC Schedule properties changed</description>
  </alertString>

  <alertString>
    <id>306</id>
    <description>Battery properties changed</description>
  </alertString>

  <alertString>
    <id>307</id>
    <description>Periodic Battery Relearn is pending. Please initiate manual learn cycle as Automatic learn is not enabled</description>
  </alertString>

  <alertString>
    <id>308</id>
    <description>Drive security key created</description>
  </alertString>

  <alertString>
    <id>309</id>
    <description>Drive security key backed up</description>
  </alertString>

  <alertString>
    <id>310</id>
    <description>Drive security key from escrow, verified</description>
  </alertString>

  <alertString>
    <id>311</id>
    <description>Drive security key changed</description>
  </alertString>

  <alertString>
    <id>312</id>
    <description>Drive security key, re-key operation failed</description>
  </alertString>

  <alertString>
    <id>313</id>
    <description>Drive security key is invalid</description>
  </alertString>

  <alertString>
    <id>314</id>
    <description>Drive security key destroyed</description>
  </alertString>

  <alertString>
    <id>315</id>
    <description>Drive security key from escrow is invalid</description>
  </alertString>

  <alertString>
    <id>316</id>
    <description>VD is now secured:</description>
  </alertString>
  
  <alertString>
    <id>317</id>
    <description>VD is partially secured:</description>
  </alertString>
  
  <alertString>
    <id>318</id>
    <description>PD security activated:</description>
  </alertString>
  
  <alertString>
    <id>319</id>
    <description>PD security disabled:</description>
  </alertString>
  
  <alertString>
    <id>320</id>
    <description>PD is reprovisioned:</description>
  </alertString>
  
  <alertString>
    <id>321</id>
    <description>PD security key changed:</description>
  </alertString>
  
  <alertString>
    <id>322</id>
    <description>Security subsystem problems detected for PD:</description>
  </alertString>
  
  <alertString>
    <id>323</id>
    <description>Controller cache pinned for missing or offline VD:</description>
  </alertString>
  
  <alertString>
    <id>324</id>
    <description>Controller cache pinned for missing or offline VDs:</description>
  </alertString>
  
  <alertString>
    <id>325</id>
    <description>Controller cache discarded by user for missing VDs:</description>
  </alertString>
  
  <alertString>
    <id>326</id>
    <description>Controller cache destaged for VD:</description>
  </alertString>
  
  <alertString>
    <id>327</id>
    <description>Consistency Check started on an inconsistent VD:</description>
  </alertString>

  <alertString>
    <id>328</id>
    <description>Drive security key failure, cannot access secured configuration</description>
  </alertString>

  <alertString>
    <id>329</id>
    <description>Drive security pass phrase from user is invalid</description>
  </alertString>

  <alertString>
    <id>330</id>
    <description>Detected error with the remote battery connector cable</description>
  </alertString>

  <alertString>
    <id>331</id>
    <description>Power state change on PD</description>
  </alertString>

  <alertString>
    <id>332</id>
    <description>Enclosure element status changed</description>
  </alertString>

  <alertString>
    <id>333</id>
    <description>Rebuild is not allowed on PD as HDD/SSD mix is not supported in VDs. PD:</description>
  </alertString>

  <alertString>
    <id>334</id>
    <description>Replace drive operation is not allowed on PD as HDD/SSD mix is not supported in VDs. PD:</description>
  </alertString>

  <alertString>
    <id>335</id>
    <description>VD Bad block table is cleared.</description>
  </alertString>

  <alertString>
    <id>336</id>
    <description>SAS topology error:</description>
  </alertString>
  <alertString>
    <id>337</id>
    <description>VD cluster of medium errors corrected:</description>
  </alertString>

  <alertString>
    <id>338</id>
    <description>Controller requests a host bus rescan</description>
  </alertString>

  <alertString>
    <id>339</id>
    <description>Controller repurposed and factory defaults restored</description>
  </alertString>


  <alertString>
    <id>340</id>
    <description>Drive security key binding updated</description>
  </alertString>

  <alertString>
    <id>341</id>
    <description>Drive security is in EKM mode</description>
  </alertString>

  <alertString>
    <id>342</id>
    <description>Drive security failed to communicate with EKMS</description>
  </alertString>

  <alertString>
    <id>343</id>
    <description>PD needs key to be</description>
  </alertString>


  <alertString>
    <id>344</id>
    <description>VD secure failed:</description>
  </alertString>

  <alertString>
    <id>345</id>
    <description>Controller encountered a fatal error and was reset</description>
  </alertString>

  <alertString>
    <id>346</id>
    <description>Snapshot enabled on</description>
  </alertString>

  <alertString>
    <id>347</id>
    <description>Snapshot disabled by the user on</description>
  </alertString>

  <alertString>
    <id>348</id>
    <description>Snapshot disabled on</description>
  </alertString>

  <alertString>
    <id>349</id>
    <description>Snapshot Point In Time created on </description>
  </alertString>

  <alertString>
    <id>350</id>
    <description>Snapshot Point In Time deleted on </description>
  </alertString>

  <alertString>
    <id>351</id>
    <description>Snapshot View created on </description>
  </alertString>

  <alertString>
    <id>352</id>
    <description>Snapshot View deleted on </description>
  </alertString>

  <alertString>
    <id>353</id>
    <description>Snapshot rollback started for Point In Time on </description>
  </alertString>

  <alertString>
    <id>354</id>
    <description>Snapshot rollback internally aborted for Point In Time on </description>
  </alertString>

  <alertString>
    <id>355</id>
    <description>Snapshot rollback completed for Point In Time on </description>
  </alertString>

  <alertString>
    <id>356</id>
    <description>Snapshot rollback progress on Point In Time on </description>
  </alertString>

  <alertString>
    <id>357</id>
    <description>Snapshot repository 80% full on </description>
  </alertString>

  <alertString>
    <id>358</id>
    <description>Snapshot repository full on </description>
  </alertString>

  <alertString>
    <id>359</id>
    <description>Snapshot View 80% full on </description>
  </alertString>

  <alertString>
    <id>360</id>
    <description>Snapshot view full on </description>
  </alertString>

  <alertString>
    <id>361</id> 
    <description>Repository lost for VD </description> 
  </alertString>

  <alertString>
    <id>362</id> 
    <description>Repository restored for VD </description> 
  </alertString>

  <alertString>
    <id>363</id>
    <description>Snapshot encountered an unexpected internal error: </description>
  </alertString>

  <alertString>
    <id>364</id>
    <description>Auto Snapshot enabled on</description>
  </alertString>

  <alertString>
    <id>365</id>
    <description>Auto Snapshot disabled on</description>
  </alertString>

  <alertString>
    <id>366</id>
    <description>Configuration command could not be committed to disk, please retry!</description>
  </alertString>

  <alertString>
    <id>367</id>
    <description>COD on PD updated as it was stale.</description>
  </alertString>

  <alertString>
    <id>368</id>
    <description>Power state change failed on PD</description>
  </alertString>

  <alertString>
    <id>369</id>
    <description>VD is not available.</description>
    </alertString>

  <alertString>
    <id>370</id>
    <description>VD is available.</description>
  </alertString>

  <alertString>
    <id>371</id>
    <description>VD is used for Cachecade(TM).</description>
  </alertString>

  <alertString>
    <id>372</id>
    <description>VD is being cached in Cachecade(TM).</description>
  </alertString>

  <alertString>
    <id>373</id>
    <description>VD is no longer being cached in Cachecade(TM).</description>
  </alertString>

  <alertString>
    <id>374</id>
    <description>Snapshot deleted due to resource constraints on </description>
  </alertString>

  <alertString>
    <id>375</id>
    <description>Auto Snapshot failed for VD</description>
  </alertString>

  <alertString>
    <id>376</id>
    <description>Controller reset on-board expander</description>
  </alertString>

  <alertString>
    <id>377</id>
    <description>Cachecade(TM) VD capacity changed.</description>
  </alertString>

  <alertString>
    <id>378</id>
    <description>Battery life has degraded and cannot initiate transparent learn cycles</description>
  </alertString>

  <alertString>
    <id>379</id>
    <description>Advanced Software Options  Key was applied</description>
  </alertString>

  <alertString>
    <id>380</id>
    <description>Snapshot schedule properties changed on VDs: </description>
  </alertString>

  <alertString>
    <id>381</id>
    <description>Snapshot scheduled action is due - Schedule timer expired on VDs: </description>
  </alertString>

  <alertString>
    <id>382</id>
    <description>Performance Metrics: collection command: </description>
  </alertString>

  <alertString>
    <id>383</id>
    <description>Advanced Software Options  Key was transferred</description>
  </alertString>

  <alertString>
    <id>384</id>
    <description>Advanced Software Options  Serial number: </description>
  </alertString>

  <alertString>
    <id>385</id>
    <description>Advanced Software Options  Serial number mismatched. Key vault Serial number is: </description>
  </alertString>

  <alertString>
    <id>386</id>
    <description>Battery cannot support data retention for more than few hour(s).</description>
  </alertString>

 <alertString>
    <id>387</id>

    <description>Power Policy changed on VD:</description>
  </alertString> 

  <alertString>
    <id>388</id>

    <description>Cannot transition to max power savings on VD:</description>
  </alertString> 

  <alertString>
    <id>389</id>

    <description>Host driver is loaded and operational</description>
  </alertString> 

<alertString>
    <id>390</id>

    <description>Mirror broken on VD:</description>
  </alertString> 

<alertString>
    <id>391</id>

    <description>Mirror joined on VD:</description>
  </alertString> 

<alertString>
    <id>392</id>

    <description>Link failed on Wide Port</description>
  </alertString> 

<alertString>
    <id>393</id>

    <description>Link restored on Wide Port</description>
  </alertString> 
<alertString>
    <id>394</id>

    <description>Memory module FRU is:</description>
  </alertString> 
<alertString>
    <id>395</id>

    <description>Cache-vault power pack is sub-optimal. Please replace the pack.</description>
  </alertString> 
<alertString>
    <id>396</id>

    <description>Foreign configuration auto-import did not import any drives</description>
  </alertString> 
<alertString>
    <id>397</id>

    <description>Cache-vault microcode update required</description>
  </alertString> 
<alertString>
    <id>398</id>

    <description>capacity exceeds maximum allowed size, extra capacity is not used</description>
  </alertString> 
<alertString>
    <id>399</id>

    <description>protection information lost on VD:</description>
  </alertString> 
<alertString>
    <id>400</id>

    <description>Diagnostics passed on PD: </description>
  </alertString> 

 <alertString>
    <id>401</id>

    <description>Diagnostics failed on PD:</description>
  </alertString> 

 <alertString>
    <id>402</id>

    <description>Server Power capability Diagnostic Test Started</description>
  </alertString> 

 <alertString>
    <id>403</id>

    <description>Drive Cache settings enabled during rebuild on PD:</description>
  </alertString> 

 <alertString>
    <id>404</id>

    <description>Drive Cache settings restored after rebuild on PD:</description>
  </alertString> 

 <alertString>
    <id>405</id>

    <description>PD commissioned as Emergency spare</description>
  </alertString> 

 <alertString>
    <id>406</id>

    <description>Reminder: Potential non-optimal configuration due, PD commissioned as Emergency Spare</description>
  </alertString> 

 <alertString>
    <id>407</id>

    <description>Consistency Check suspended on VD:</description>
  </alertString> 


 <alertString>
    <id>408</id>

    <description>Consistency Check resumed on VD:</description>
  </alertString> 
 <alertString>
    <id>409</id>

    <description>Background Initialization suspended on VD:</description>
  </alertString> 
 <alertString>
    <id>410</id>

    <description>Background Initialization resumed on VD:</description>
  </alertString> 
 <alertString>
    <id>411</id>

    <description>Reconstruction suspended on VD:</description>
  </alertString> 
 <alertString>
    <id>412</id>

    <description>Rebuild suspended on PD:</description>
  </alertString> 
 <alertString>
    <id>413</id>

    <description>Replace drive suspended on PD:</description>
  </alertString> 

 <alertString>
    <id>414</id>

    <description>Reminder: Consistency Check suspended on VD:</description>
  </alertString> 

 <alertString>
    <id>415</id>

    <description>Reminder: Background Initialization suspended on VD:</description>
  </alertString>

 <alertString>
    <id>416</id>

    <description>Reminder: Reconstruction suspended on VD: </description>
  </alertString>
 

 <alertString>
    <id>417</id>

    <description>Reminder: Rebuild suspended on PD:</description>
  </alertString>


 <alertString>
    <id>418</id>

    <description>Reminder: Replace drive suspended on PD:</description>
  </alertString>


 <alertString>
    <id>419</id>

    <description>Reminder: Patrol Read suspended</description>
  </alertString>

 <alertString>
    <id>420</id>

    <description>Erase aborted on PD:</description>
  </alertString>

 <alertString>
    <id>421</id>

    <description>Erase failed on PD:</description>
  </alertString> 

 <alertString>
    <id>422</id>

    <description>Erase progress on PD:</description>
  </alertString> 

 <alertString>
    <id>423</id>

    <description>Erase started on PD:</description>
  </alertString> 

 <alertString>
    <id>424</id>

    <description>Erase completed on PD:</description>
  </alertString> 

 <alertString>
    <id>425</id>

    <description>Erase aborted on VD:</description>
  </alertString> 

 <alertString>
    <id>426</id>

    <description>Erase failed on VD:</description>
  </alertString> 

 <alertString>
    <id>427</id>

    <description>Erase progress on VD:</description>
  </alertString> 

 <alertString>
    <id>428</id>


    <description>Erase started on VD:</description>
  </alertString> 

 <alertString>
    <id>429</id>

    <description> Erase completed on VD:</description>
  </alertString> 

 <alertString>
    <id>430</id>

    <description> Potential leakage during erase on VD:</description>
  </alertString> 

 <alertString>
    <id>431</id>

    <description> Battery charging was suspended due to high battery temperature</description>
  </alertString>
     
 <alertString>
    <id>432</id>

    <description> NVCache firmware update was successful </description>
  </alertString> 
 
  <alertString>
    <id>433</id>

    <description> NVCache firmware update failed </description>
  </alertString>
     
 <alertString>
    <id>434</id>

    <description>access blocked as cached data in Cachecade(TM) is unavailable </description>
  </alertString>
  
 <alertString>
    <id>435</id>

    <description>Cachecade(TM) disassociate started on VD: </description>
  </alertString>
     
 <alertString>
    <id>436</id>

    <description> Cachecade(TM) disassociate completed on VD: </description>
  </alertString>

 <alertString>
    <id>437</id>

    <description> Cachecade(TM) disassociate failed on VD:</description>
  </alertString>
   
 <alertString>
    <id>438</id>

    <description> Cachecade(TM) disassociate progress on VD:</description>
  </alertString>
    
 <alertString>
    <id>439</id>

    <description> Cachecade(TM) disassociate aborted by user on VD:</description>
  </alertString>
   
 <alertString>
    <id>440</id>

    <description> Link speed changed on SAS port </description>
  </alertString>
    
 <alertString>
    <id>441</id>

    <description> Advanced Software Options was deactivated for:</description>
  </alertString>
   
 <alertString>
    <id>442</id>

    <description> VD is now accessible</description>
  </alertString>
  
 <alertString>
    <id>443</id>

    <description> VD is using Cachecade(TM)</description>
  </alertString>
  
 <alertString>
    <id>444</id>

    <description> VD is no longer using Cachecade(TM)</description>
  </alertString>	
  
 <alertString>
    <id>445</id>

    <description>Patrol Read aborted on PD:</description>
  </alertString>

 <alertString>
    <id>446</id>

    <description>Transient error detected while communicating with PD:</description>
  </alertString>

 <alertString>
    <id>447</id>

    <description>PI error in cache for LD:</description>
  </alertString>

 <alertString>
    <id>448</id>

    <description>Flash downloaded image is not supported</description>
  </alertString>

 <alertString>
    <id>449</id>

    <description>BBU mode selected - </description>
 </alertString>
 
 <alertString>
    <id>450</id>

    <description>Periodic Battery Relearn was missed and Rescheduled</description>
  </alertString>
 
    
  <alertString>
    <id>451</id>

    <description> Controller reset requested by host : </description>
  </alertString>    

  <alertString>
    <id>452</id>

    <description> Controller reset requested by host, completed </description>
  </alertString>

  <alertString>
    <id>453</id>
	
	<description> L3 cache error has been detected : </description>
  </alertString>
  
  <alertString>
    <id>454</id>

    <description> L2 cache error has been detected </description>
  </alertString>

  <alertString>
    <id>455</id>

    <description> Controller booted in headless mode with errors : </description>
  </alertString>

  <alertString>
    <id>456</id>

    <description> Controller booted to safe mode due to critical errors : </description>
  </alertString>

  <alertString>
    <id>457</id>

    <description> Warning Error during boot : </description>
  </alertString>

   <alertString>
    <id>458</id>

    <description> Critical Error during boot : </description>
  </alertString>

<alertString>
    <id>459</id>

    <description> Fatal Error during boot :  </description>
  </alertString>

  <alertString>
    <id>460</id>
	<description>Peer Controller entered HA</description>
  </alertString>
  
  <alertString>
    <id>461</id>
	<description>Peer Controller exited HA</description>
  </alertString>
  
  <alertString>
    <id>462</id>
	<description>Peer Controller now manages PD</description>
  </alertString>
  
  <alertString>
    <id>463</id>
	<description>Local Controller now manages PD</description>
  </alertString>
  
  <alertString>
    <id>464</id>
	<description>Peer Controller now manages VD</description>
  </alertString>
  
  <alertString>
    <id>465</id>
	<description>Local Controller now manages VD</description>
  </alertString>
  
  <alertString>
    <id>466</id>
	<description>Target ID conflict detected on VD</description>
  </alertString>
  
  <alertString>
    <id>467</id>
	<description>Shared access policy set for VD</description>
  </alertString>  
  
  <alertString>
    <id>468</id>
	<description>Exclusive access policy set for VD</description>
  </alertString>
  
  <alertString>
    <id>469</id>
	<description>VD is incompatible in the HA Domain.</description>
  </alertString>
  
  <alertString>
    <id>470</id>
	<description>Peer controller settings are incompatible with HA</description>
  </alertString>
  
  <alertString>
    <id>471</id>
	<description>Peer Controller hardware is incompatible with HA</description>
  </alertString>
  
  <alertString>
    <id>472</id>
	<description>Controller property mismatch detected with Peer controller.</description>
  </alertString>
  
  <alertString>
    <id>473</id>
	<description>FW version does not match Peer controller.</description>
  </alertString>
  
  <alertString>
    <id>474</id>
	<description>Advanced Software Option mismatch detected with Peer controller.</description>
  </alertString>
  
  <alertString>
    <id>475</id>
	<description>Cache mirroring is Online.</description>
  </alertString>  

  <alertString>
    <id>476</id>
	<description>Cache mirroring is Offline.</description>
  </alertString>

  <alertString>
    <id>477</id>
	<description>Cached data from Peer controller is unavailable for VD</description>
  </alertString>

  <alertString>
    <id>478</id>
	<description>Cache-vault power pack is not supported. Please replace the pack.</description>
  </alertString>
  
  <alertString>
    <id>479</id>
    <description>Temperature is above warning threshold on PD</description>
  </alertString>
    
  <alertString>
    <id>480</id>
    <description>Temperature is above critical threshold on PD</description>
  </alertString>
    
  <alertString>
    <id>481</id>
    <description>Temperature is normal on PD</description>
  </alertString>
    
  <alertString>
    <id>482</id>
    <description>IOs are being throttled on PD</description>
  </alertString>
    
  <alertString>
    <id>483</id>
    <description>IOs are normal on PD</description>
  </alertString>
    
  <alertString>
    <id>484</id>
    <description>Life left on PD</description>
  </alertString>
    
  <alertString>
    <id>485</id>
    <description>Life is below optimal on PD</description>
  </alertString>
        
  <alertString>
    <id>486</id>
    <description>Life is critical on PD</description>
  </alertString>     
    
  <alertString>
    <id>487</id>
    <description>PD failure, device locked-up.</description>
  </alertString>

  <alertString>
    <id>488</id>
    <description>Host driver needs to be upgraded</description>
  </alertString>

  <alertString>
    <id>489</id>
    <description>Direct communication with peer controller(s) was not established. Please check proper cable connections.</description>
  </alertString>

  <alertString>
    <id>490</id>
    <description>Firmware image does not contain signed component.</description>
  </alertString>

  <alertString>
    <id>491</id>
    <description>Authentication failure of the signed firmware image.</description>
  </alertString>

  <alertString>
    <id>492</id>
    <description>Setting VD as boot device.</description>
  </alertString>

  <alertString>
    <id>493</id>
    <description>Setting PD as boot device.</description>
  </alertString>

  <alertString>
    <id>494</id>
    <description>The BBU temperature is changed</description>
  </alertString>

  <alertString>
    <id>495</id>
    <description>The Controller temperature is changed</description>
  </alertString>  
  
   <alertString>
    <id>496</id>
    <description>NVCache capacity is too less to support data backup. Write-back VDs will be converted to write-through.</description>
  </alertString>

  <alertString>
    <id>497</id>
    <description>NVCache data backup capacity has decreased, consider replacement.</description>
  </alertString>

  <alertString>
    <id>498</id>
    <description>NVCache device failed, cannot support data retention.</description>
  </alertString>

  <alertString>
    <id>499</id>
    <description>Boot Device reset, setting target ID as invalid</description>
  </alertString>

  <alertString>
    <id>500</id>
    <description>Write back Nytro cache size mismatch between the servers. The Nytro cache size was adjusted to GB.</description>
  </alertString>  
  
  <alertString>
    <id>501</id>
    <description>VD is not shared between servers but assigned for caching. Write back Nytro cache content of the VD will be mirrored</description>
  </alertString>

  <alertString>
    <id>502</id>
    <description>Power watts usage base IOs throttle started.</description>
  </alertString>

  <alertString>
    <id>503</id>
    <description>Power base IOs throttle stopped.</description>
  </alertString>

  <alertString>
    <id>504</id>
    <description>Controller tunable parameter(s) changed</description>
  </alertString>

  <alertString>
    <id>505</id>
    <description>Controller operating temperature within normal range, full operation restored.</description>
  </alertString>  
  
  <alertString>
    <id>506</id>
    <description>Controller temperature threshold exceeded. This may indicate inadequate system cooling. Switching to low performance mode.</description>
  </alertString>

  <alertString>
    <id>507</id>
    <description>Controller supports HA mode, currently functioning with HA feature set.</description>
  </alertString>

  <alertString>
    <id>508</id>
    <description>Controller supports HA mode, currently functioning with single controller feature set.</description>
  </alertString>

  <alertString>
    <id>509</id>
    <description>Cache-vault components mismatch. Write-back VDs will be converted write-through.</description>
  </alertString>

  <alertString>
    <id>510</id>
    <description>Controller has entered into maintenance mode.</description>
  </alertString>  
  
  <alertString>
    <id>511</id>
    <description>Controller has returned to normal mode.</description>
  </alertString>

  <alertString>
    <id>512</id>
    <description>Topology is in mode:</description>
  </alertString>

  <alertString>
    <id>513</id>
    <description>Cannot enter expected mode because LD would not be supported.</description>
  </alertString>

  <alertString>
    <id>514</id>
    <description>Cannot enter expected mode because PD would not be supported.</description>
  </alertString>

  <alertString>
    <id>515</id>
    <description>Cache Flush started.</description>
  </alertString>  
  
  <alertString>
    <id>516</id>
    <description>Cache Flush finished.</description>
  </alertString>

  <alertString>
    <id>517</id>
    <description>Cache Flush aborted by user.</description>
  </alertString>

  <!-- <alertString>
	<id>518</id>
    <description>Controller personality changed to </description>
  </alertString> -->
  
   <alertString>
	<id>519</id>
    <description>Configuration automatically created.</description>
  </alertString>
  
   <alertString>
	<id>522</id>
    <description>Initialization aborted on VD due to controller reset.</description>
  </alertString>
  
  <alertString>
	<id>523</id>
    <description>Peer controller security key mismatch.</description>
  </alertString>
  
  <alertString>
	<id>524</id>
    <description>Peer controller security key match.</description>
  </alertString>
  
  <alertString>
	<id>525</id>
    <description>Compatible in the HA domain.</description>
  </alertString>

  <alertString>
	<id>530</id>
    <description>MegaRAID Solution will shut down due to maximum temperature threshold exception. This may indicate inadequate system cooling.</description>
  </alertString>
  
  <alertString>
	<id>531</id>
    <description>Shutdown chassis command received from host.</description>
  </alertString>
  
  <alertString>
	<id>532</id>
    <description>Restart chassis command received from host.</description>
  </alertString>
  
  <alertString>
	<id>533</id>
    <description>Controller Information changed.</description>
  </alertString>

<alertString>
	<id>534</id>
    <description>Hidden policy not set for all LDs in the array.</description>
  </alertString>
  
  <alertString>
	<id>535</id>
    <description>PD is not enterprise class self encrypting drive. Encryption capability of the drive will be disabled</description>
  </alertString>
  
  <alertString>
	<id>536</id>
    <description>Controller firmware was updated with force option</description>
  </alertString>
  
  <alertString>
	<id>537</id>
    <description>Default access policy is set to read/write mode.</description>
  </alertString> 

  <alertString>
	<id>538</id>
    <description>Disabling writes to flash due to a critical error. Reboot the system to enable writes to flash again</description>
  </alertString>
  
  <alertString>
	<id>539</id>
    <description>Disabling writes to flash as the part has gone bad</description>
  </alertString>
 
<alertString>
	<id>540</id>
    <description>Locate LED started on PD</description>
  </alertString>  
  
   <alertString>
	<id>541</id>
    <description>Locate LED stopped on PD</description>
  </alertString>  
  
  <alertString>
	<id>542</id>
    <description>Patrol read aborted due to conflict with other background operations on PD</description>
  </alertString>

  <alertString>
	<id>543</id>
    <description>Bad Media Events on PD</description>
  </alertString>
  
  <alertString>
	<id>544</id>
    <description>PD has bad Performance</description>
  </alertString>
  
 <!-- Added for  SCGCQ00819877-->

 <alertString>
	<id>545</id>
    <description>SuperCap Health After Learn Cycles Capacitance</description>
  </alertString>
  
   <!-- <alertString>
	<id>546</id>
    <description>Controller personality will change PCI ID to:</description>
  </alertString> -->
  
   <alertString>
	<id>548</id>
    <description>VD is marked as Transport Ready</description>
  </alertString>
  
    <alertString>
	<id>549</id>
    <description>VD is cleared from Transport Ready state</description>
  </alertString>

  <alertString>
	<id>550</id>
    <description>System reset required</description>
  </alertString>
  
  <alertString>
	<id>551</id>
    <description>Block recovery is skipped for Cache-vault. Reboot the system to recover the blocks</description>
  </alertString>

 <!-- Monitor related events -->

  <alertString>
    <id>10000</id>

    <description>Successful log on to the server</description>
  </alertString><alertString>
    <id>10001</id>

    <description>Successful log out from the server</description>
  </alertString>

  <alertString>
    <id>10002</id>

    <description>Full access denied on the server</description>
  </alertString>

  <alertString>
    <id>10003</id>

    <description>Server log cleared</description>
  </alertString>

<!-- Warhawk related events -->

  <alertString>
    <id>65522</id>
    <description>SSD is in unlocked state.</description>
  </alertString>

  <alertString>
    <id>65523</id>
    <description>SSD is in locked state.</description>
  </alertString>

  <alertString>
    <id>65525</id>
    <description>Temperature has exceeded critical temperature threshold</description>
  </alertString>

  <alertString>
    <id>65526</id>
    <description>Temperature has exceeded warning temperature threshold</description>
  </alertString>

  <alertString>
    <id>65527</id>
    <description>Power throttling is now removed Percent Power Throttled</description>
  </alertString>

  <alertString>
    <id>65528</id>
    <description>Percent Power Throttled</description>
  </alertString>

  <alertString>
    <id>65529</id>
    <description>Temperature has exceeded Critical level on Sensor</description>
  </alertString>

  <alertString>
    <id>65530</id>
    <description>Temperature has exceeded Warning level on Sensor</description>
  </alertString>

  <alertString>
    <id>65531</id>
    <description>The Backup Rail Monitor has failed</description>
  </alertString>

  <alertString>
    <id>65532</id>

    <description>SSD Life is exhausted on Slot</description>
  </alertString>

  <alertString>
    <id>65533</id>

    <description>SSD Life is at warning level on Slot</description>
  </alertString>

  <alertString>
    <id>65534</id>

    <description>SSD throttling is now removed on Slot</description>
  </alertString>

  <alertString>
    <id>65535</id>

    <description>SSD is being throttled on Slot</description>
  </alertString>

  <!-- CCOH related events -->
  
  <alertString>
    <id>49152</id>

    <description>Added Cache Device</description>
  </alertString>
  
  <alertString>
    <id>49153</id>

    <description>Removed Cache Device</description>
  </alertString>
  
  <alertString>
    <id>49154</id>

    <description>Added VD</description>
  </alertString>
  
  <alertString>
    <id>49155</id>

    <description>Removed VD</description>
  </alertString>
  
  <alertString>
    <id>49156</id>

    <description>VD went Offline</description>
  </alertString>
  
  <alertString>
    <id>49157</id>

    <description>VD is Ready for Online</description>
  </alertString>
  
  <alertString>
    <id>49158</id>

    <description>VD is Online</description>
  </alertString>
  
</alertStringsList>