yexinru/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
Files
fix_python
doc-exports/docs/mrs/umn/alm_25004.html
Yang, Tong 3b1f73dece MRS UMN 2.0.38.SP20 version 
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
Co-authored-by: Yang, Tong <yangtong2@huawei.com>
Co-committed-by: Yang, Tong <yangtong2@huawei.com>
2022-12-13 12:03:34 +00:00

82 lines
16 KiB
HTML
Raw Permalink Blame History

<a name="alm_25004"></a><a name="alm_25004"></a>
<h1 class="topictitle1">ALM-25004 Abnormal LdapServer Data Synchronization </h1>
<div id="body8662426"><div class="section" id="alm_25004__en-us_topic_0191813874_section47176343"><h4 class="sectiontitle">Description</h4><p id="alm_25004__en-us_topic_0191813874_p62855489">This alarm is generated when LdapServer data on Manager is inconsistent. This alarm is cleared when the data becomes consistent. </p>
<p id="alm_25004__en-us_topic_0191813874_p28828491">This alarm is generated when LdapServer data in the cluster is inconsistent with LdapServer data on Manager. This alarm is cleared when the data becomes consistent. </p>
</div>
<div class="section" id="alm_25004__en-us_topic_0191813874_section21933905"><h4 class="sectiontitle">Attribute</h4>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="alm_25004__en-us_topic_0191813874_table53406450" frame="border" border="1" rules="all"><thead align="left"><tr id="alm_25004__en-us_topic_0191813874_row25792371"><th align="left" class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.3.2.2.1.4.1.1"><p id="alm_25004__en-us_topic_0191813874_p8807292">Alarm ID</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.3.2.2.1.4.1.2"><p id="alm_25004__en-us_topic_0191813874_p42302050">Alarm Severity</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="33.33333333333333%" id="mcps1.3.2.2.1.4.1.3"><p id="alm_25004__en-us_topic_0191813874_p3913996">Auto Clear</p>
</th>
</tr>
</thead>
<tbody><tr id="alm_25004__en-us_topic_0191813874_row48598242"><td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.1.4.1.1 "><p id="alm_25004__en-us_topic_0191813874_p44143566">25004</p>
</td>
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.1.4.1.2 "><p id="alm_25004__en-us_topic_0191813874_p18859061">Critical</p>
</td>
<td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.1.4.1.3 "><p id="alm_25004__en-us_topic_0191813874_p51188993">Yes</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div class="section" id="alm_25004__en-us_topic_0191813874_section63187419"><h4 class="sectiontitle">Parameters</h4>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="alm_25004__en-us_topic_0191813874_table52667802" frame="border" border="1" rules="all"><thead align="left"><tr id="alm_25004__en-us_topic_0191813874_row22098140"><th align="left" class="cellrowborder" valign="top" width="50%" id="mcps1.3.3.2.1.3.1.1"><p id="alm_25004__en-us_topic_0191813874_p45118907">Parameter</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="50%" id="mcps1.3.3.2.1.3.1.2"><p id="alm_25004__en-us_topic_0191813874_p30752875">Description</p>
</th>
</tr>
</thead>
<tbody><tr id="alm_25004__en-us_topic_0191813874_row7954964"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.3.2.1.3.1.1 "><p id="alm_25004__en-us_topic_0191813874_p40372317">ServiceName</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.3.2.1.3.1.2 "><p id="alm_25004__en-us_topic_0191813874_p48932206">Specifies the service for which the alarm is generated.</p>
</td>
</tr>
<tr id="alm_25004__en-us_topic_0191813874_row37736673"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.3.2.1.3.1.1 "><p id="alm_25004__en-us_topic_0191813874_p36771698">RoleName</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.3.2.1.3.1.2 "><p id="alm_25004__en-us_topic_0191813874_p25717600">Specifies the role for which the alarm is generated.</p>
</td>
</tr>
<tr id="alm_25004__en-us_topic_0191813874_row30131813"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.3.2.1.3.1.1 "><p id="alm_25004__en-us_topic_0191813874_p24757801">HostName</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.3.2.1.3.1.2 "><p id="alm_25004__en-us_topic_0191813874_p59224828">Host for which the alarm is generated.</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div class="section" id="alm_25004__en-us_topic_0191813874_section31815862"><h4 class="sectiontitle">Impact on the System</h4><p id="alm_25004__en-us_topic_0191813874_p32481801">LdapServer data inconsistency occurs because LdapServer data on Manager or in the cluster is damaged. The LdapServer process with damaged data cannot provide services externally, and the authentication functions of Manager and the cluster are affected. </p>
</div>
<div class="section" id="alm_25004__en-us_topic_0191813874_section17907308"><h4 class="sectiontitle">Possible Causes</h4><ul id="alm_25004__en-us_topic_0191813874_ul13780214"><li id="alm_25004__en-us_topic_0191813874_li56913064">The network of the node where the LdapServer process locates is faulty. </li><li id="alm_25004__en-us_topic_0191813874_li42455531">The LdapServer process is abnormal. </li><li id="alm_25004__en-us_topic_0191813874_li46555465">The OS restart damages data on LdapServer. </li></ul>
</div>
<div class="section" id="alm_25004__en-us_topic_0191813874_section26948044"><h4 class="sectiontitle">Procedure</h4><ol id="alm_25004__en-us_topic_0191813874_ol821304815123"><li class="tableheading" id="alm_25004__en-us_topic_0191813874_li251864915123"><span>Check whether the network where the LdapServer nodes reside is faulty. </span><p><ol type="a" id="alm_25004__en-us_topic_0191813874_ol48957711"><li id="alm_25004__en-us_topic_0191813874_li1487713813414">Go to the cluster details page and choose <strong id="alm_25004__b2324949143115">Alarms</strong>.</li><li id="alm_25004__en-us_topic_0191813874_li37966223">Record the IP address of <strong id="alm_25004__b21481150173112">HostName</strong> in <strong id="alm_25004__b20148175003112">Location</strong> of the alarm as <strong id="alm_25004__b1114865093115">IP1</strong> (if multiple alarms exist, record the IP addresses as <strong id="alm_25004__b9149750193114">IP1</strong>, <strong id="alm_25004__b214918508313">IP2</strong>, and <strong id="alm_25004__b1614965053113">IP3</strong> respectively). </li><li id="alm_25004__en-us_topic_0191813874_li6151694">Contact O&amp;M personnel and use PuTTY to log in to the node corresponding to <strong id="alm_25004__b760912512314">IP1</strong>. Run the <strong id="alm_25004__b15609105111310">ping</strong> command on the node to check whether the IP address of the management plane of the active OMS node can be pinged. <ul class="subitemlist" id="alm_25004__en-us_topic_0191813874_ul28525238"><li id="alm_25004__en-us_topic_0191813874_li55400552">If yes, go to <a href="#alm_25004__en-us_topic_0191813874_aalm-25004_mmccppss_step3">1.d</a>.</li><li id="alm_25004__en-us_topic_0191813874_li58259743">If no, go to <a href="#alm_25004__en-us_topic_0191813874_li4768141014141">2.a</a>.</li></ul>
</li><li id="alm_25004__en-us_topic_0191813874_aalm-25004_mmccppss_step3"><a name="alm_25004__en-us_topic_0191813874_aalm-25004_mmccppss_step3"></a><a name="en-us_topic_0191813874_aalm-25004_mmccppss_step3"></a>Contact O&amp;M personnel to recover the network and check whether the alarm <strong id="alm_25004__b10720193219">ALM-25004 Abnormal LdapServer Data Synchronization</strong> is cleared. <ul class="subitemlist" id="alm_25004__en-us_topic_0191813874_ul58551215"><li id="alm_25004__en-us_topic_0191813874_li57198891">If yes, no further action is required.</li><li id="alm_25004__en-us_topic_0191813874_li45027976">If no, go to <a href="#alm_25004__en-us_topic_0191813874_li4768141014141">2.a</a>.</li></ul>
</li></ol>
</p></li><li class="tableheading" id="alm_25004__en-us_topic_0191813874_li25337345151310"><span>Check whether the LdapServer process is in normal state.</span><p><ol type="a" id="alm_25004__en-us_topic_0191813874_ol2045923315426"><li id="alm_25004__en-us_topic_0191813874_li4768141014141"><a name="alm_25004__en-us_topic_0191813874_li4768141014141"></a><a name="en-us_topic_0191813874_li4768141014141"></a>Go to the cluster details page and choose <strong id="alm_25004__b4314124553216">Alarms</strong>.</li><li id="alm_25004__en-us_topic_0191813874_aalm-25004_mmccppss_step4">Check whether ALM-12004 OLdap Resource Is Abnormal is generated for LdapServer.<ul class="subitemlist" id="alm_25004__en-us_topic_0191813874_ul15337269"><li id="alm_25004__en-us_topic_0191813874_li3817695">If yes, go to <a href="#alm_25004__en-us_topic_0191813874_aalm-25004_mmccppss_step5">2.c</a>.</li><li id="alm_25004__en-us_topic_0191813874_li40797849">If no, go to <a href="#alm_25004__en-us_topic_0191813874_aalm-25004_mmccppss_step7">2.e</a>.</li></ul>
</li><li id="alm_25004__en-us_topic_0191813874_aalm-25004_mmccppss_step5"><a name="alm_25004__en-us_topic_0191813874_aalm-25004_mmccppss_step5"></a><a name="en-us_topic_0191813874_aalm-25004_mmccppss_step5"></a>Rectify the fault by following steps provided in <strong id="alm_25004__b1968517133512">ALM-12004 OLdap Resource Is Abnormal</strong>. </li><li id="alm_25004__en-us_topic_0191813874_li12405375">Check whether the alarm ALM-25004 Abnormal LdapServer Data Synchronization is cleared. <ul class="subitemlist" id="alm_25004__en-us_topic_0191813874_ul44539515"><li id="alm_25004__en-us_topic_0191813874_li65311315">If yes, no further action is required.</li><li id="alm_25004__en-us_topic_0191813874_li50930930">If no, go to <a href="#alm_25004__en-us_topic_0191813874_aalm-25004_mmccppss_step7">2.e</a>.</li></ul>
</li><li id="alm_25004__en-us_topic_0191813874_aalm-25004_mmccppss_step7"><a name="alm_25004__en-us_topic_0191813874_aalm-25004_mmccppss_step7"></a><a name="en-us_topic_0191813874_aalm-25004_mmccppss_step7"></a>On the <strong id="alm_25004__b992652293517">Alarms</strong> page of MRS Manager, check whether the alarm ALM-12007 Process Fault of LdapServer is generated. <ul class="subitemlist" id="alm_25004__en-us_topic_0191813874_ul17446726"><li id="alm_25004__en-us_topic_0191813874_li22802807">If yes, go to <a href="#alm_25004__en-us_topic_0191813874_step8">2.f</a>.</li><li id="alm_25004__en-us_topic_0191813874_li35088084">If no, go to <a href="#alm_25004__en-us_topic_0191813874_li1816316468144">3.a</a>.</li></ul>
</li><li id="alm_25004__en-us_topic_0191813874_step8"><a name="alm_25004__en-us_topic_0191813874_step8"></a><a name="en-us_topic_0191813874_step8"></a>Rectify the fault by following steps provided in ALM-12007 Process Fault.</li><li id="alm_25004__en-us_topic_0191813874_li10736577">Check whether the alarm ALM-25004 Abnormal LdapServer Data Synchronization is cleared. <ul class="subitemlist" id="alm_25004__en-us_topic_0191813874_ul29520332"><li id="alm_25004__en-us_topic_0191813874_li64356400">If yes, no further action is required.</li><li id="alm_25004__en-us_topic_0191813874_li42336695">If no, go to <a href="#alm_25004__en-us_topic_0191813874_li1816316468144">3.a</a>.</li></ul>
</li></ol>
</p></li><li class="tableheading" id="alm_25004__en-us_topic_0191813874_li16555502151317"><span>Check whether the OS restart damages data on LdapServer.</span><p><ol type="a" id="alm_25004__en-us_topic_0191813874_ol3451375315426"><li id="alm_25004__en-us_topic_0191813874_li1816316468144"><a name="alm_25004__en-us_topic_0191813874_li1816316468144"></a><a name="en-us_topic_0191813874_li1816316468144"></a>Go to the cluster details page and choose <strong id="alm_25004__b1886524311365">Alarms</strong>.</li><li id="alm_25004__en-us_topic_0191813874_step10">Record the IP address of <strong id="alm_25004__b12715462367">HostName</strong> in <strong id="alm_25004__b1072114643620">Location</strong> of the alarm as <strong id="alm_25004__b1472114611364">IP1</strong> (if multiple alarms exist, record the IP addresses as <strong id="alm_25004__b472746143617">IP1</strong>, <strong id="alm_25004__b273646153610">IP2</strong>, and <strong id="alm_25004__b1573194643611">IP3</strong> respectively). Choose <strong id="alm_25004__b1858414505366">Services</strong> &gt; <strong id="alm_25004__b658995003615">LdapServer</strong> &gt; <strong id="alm_25004__b185891650183616">Service Configuration</strong> and record the LdapServer port number as <strong id="alm_25004__b12589165016367">PORT</strong>. (If the IP address in the alarm location information is the IP address of the standby OMS node, the default port number is 21750.)</li><li id="alm_25004__en-us_topic_0191813874_li7469042">Log in to node <strong id="alm_25004__b1276205218362">IP1</strong> as user <strong id="alm_25004__b1176285243611">omm</strong> and run the <strong id="alm_25004__b67639524363">ldapsearch -H ldaps://IP1:PORT -x -LLL -b dc=hadoop,dc=com</strong> command (if the IP address is the IP address of the standby OMS node, run the <strong id="alm_25004__b4763155293610">ldapsearch -H ldaps://IP1:PORT -x -LLL -b dc=hadoop,dc=com</strong> command before running this command). Check whether error information is displayed in the command output.<ul class="subitemlist" id="alm_25004__en-us_topic_0191813874_ul9113635"><li id="alm_25004__en-us_topic_0191813874_li14913854">If yes, go to <a href="#alm_25004__en-us_topic_0191813874_aalm-25004_mmccppss_step12">3.d</a>.</li><li id="alm_25004__en-us_topic_0191813874_li62687">If no, go to <a href="#alm_25004__en-us_topic_0191813874_li572522141314">4</a>.</li></ul>
</li><li id="alm_25004__en-us_topic_0191813874_aalm-25004_mmccppss_step12"><a name="alm_25004__en-us_topic_0191813874_aalm-25004_mmccppss_step12"></a><a name="en-us_topic_0191813874_aalm-25004_mmccppss_step12"></a>Recover the LdapServer and OMS nodes using backup data before the alarm is generated. For details, see section "Recovering Manager Data" in the <em id="alm_25004__i161579379">Administrator Guide</em>. <div class="note" id="alm_25004__en-us_topic_0191813874_note45699530"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p class="text" id="alm_25004__en-us_topic_0191813874_p8642591">Use the OMS data and LdapServer data backed up at the same time to restore data. Otherwise, the service and operation may fail. To recover data when services run properly, you are advised to manually back up the latest management data and then recover the data. Otherwise, Manager data produced between the backup point in time and the recovery point in time will be lost. </p>
</div></div>
</li><li id="alm_25004__en-us_topic_0191813874_li10674462">Check whether the alarm ALM-25004 Abnormal LdapServer Data Synchronization is cleared. <ul class="subitemlist" id="alm_25004__en-us_topic_0191813874_ul28961294"><li id="alm_25004__en-us_topic_0191813874_li59325057">If yes, no further action is required.</li><li id="alm_25004__en-us_topic_0191813874_li64163473">If no, go to <a href="#alm_25004__en-us_topic_0191813874_li572522141314">4</a>.</li></ul>
</li></ol>
</p></li><li id="alm_25004__en-us_topic_0191813874_li572522141314"><a name="alm_25004__en-us_topic_0191813874_li572522141314"></a><a name="en-us_topic_0191813874_li572522141314"></a><span>Collect fault information.</span><p><ol type="a" id="alm_25004__en-us_topic_0191813874_en-us_topic_0191813935_ol6089206913036"><li id="alm_25004__en-us_topic_0191813874_en-us_topic_0191813935_li4478836213036">On MRS Manager, choose <span class="menucascade" id="alm_25004__menucascade362074557"><b><span class="uicontrol" id="alm_25004__uicontrol15575775513">System</span></b> &gt; <b><span class="uicontrol" id="alm_25004__uicontrol9621719551">Export Log</span></b></span>.</li><li id="alm_25004__li18574327401">Contact technical support engineers for help. For details, see <a href="https://docs.otc.t-systems.com/en-us/public/learnmore.html" target="_blank" rel="noopener noreferrer">technical support</a>.</li></ol>
</p></li></ol>
</div>
<div class="section" id="alm_25004__en-us_topic_0191813874_section41205809"><h4 class="sectiontitle">Reference</h4><p id="alm_25004__en-us_topic_0191813874_p48873995">None</p>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="mrs_01_0241.html">Alarm Reference (Applicable to Versions Earlier Than MRS 3.x)</a></div>
</div>
</div>
View Git Blame Copy Permalink