vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
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

94 lines
15 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="body60024434"><div class="section" id="ALM-25004__s4f25443ec3e949a3841a41ce8c408857"><h4 class="sectiontitle">Description</h4><p id="ALM-25004__p104028482361">The system checks the LdapServer data every 30 seconds. This alarm is generated when the data on the active and standby LdapServers of Manager is inconsistent for 12 consecutive times. This alarm is cleared when the data on the active and standby LdapServers is consistent.</p>
<p id="ALM-25004__p240294853616">The system checks the LdapServer data every 30 seconds. This alarm is generated when the LdapServer data in the cluster is inconsistent with that on Manager for 12 consecutive times. This alarm is cleared when the data is consistent.</p>
</div>
<div class="section" id="ALM-25004__s26612750fa3143ad881187a65ddf9c5e"><h4 class="sectiontitle">Attribute</h4>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="ALM-25004__en-us_topic_0070543545_table40305966" frame="border" border="1" rules="all"><thead align="left"><tr id="ALM-25004__en-us_topic_0070543545_row33362098"><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_0070543545_p17975388">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_0070543545_p46720306">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_0070543545_p26248478">Auto Clear</p>
</th>
</tr>
</thead>
<tbody><tr id="ALM-25004__en-us_topic_0070543545_row45751941"><td class="cellrowborder" valign="top" width="33.33333333333333%" headers="mcps1.3.2.2.1.4.1.1 "><p id="ALM-25004__en-us_topic_0070543545_p14919761">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_0070543545_p541162">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_0070543545_p43834167">Yes</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div class="section" id="ALM-25004__s65f8656d47c34b8caf433cb92b2eb650"><h4 class="sectiontitle">Parameters</h4>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="ALM-25004__en-us_topic_0070543545_table60906657" frame="border" border="1" rules="all"><thead align="left"><tr id="ALM-25004__en-us_topic_0070543545_row46080827"><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_0070543545_p41559524">Name</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_0070543545_p10878253">Meaning</p>
</th>
</tr>
</thead>
<tbody><tr id="ALM-25004__row695010168"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.3.2.1.3.1.1 "><p id="ALM-25004__p192431315431">Source</p>
</td>
<td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.3.2.1.3.1.2 "><p id="ALM-25004__p692551319435">Specifies the cluster for which the alarm is generated.</p>
</td>
</tr>
<tr id="ALM-25004__en-us_topic_0070543545_row8723262"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.3.2.1.3.1.1 "><p id="ALM-25004__en-us_topic_0070543545_p35495616">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_0070543545_p56572634">Specifies the service for which the alarm is generated.</p>
</td>
</tr>
<tr id="ALM-25004__en-us_topic_0070543545_row39391664"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.3.2.1.3.1.1 "><p id="ALM-25004__en-us_topic_0070543545_p36608226">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_0070543545_p12476353">Specifies the role for which the alarm is generated.</p>
</td>
</tr>
<tr id="ALM-25004__en-us_topic_0070543545_row45178316"><td class="cellrowborder" valign="top" width="50%" headers="mcps1.3.3.2.1.3.1.1 "><p id="ALM-25004__en-us_topic_0070543545_p35565017">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_0070543545_p62194118">Specifies the host for which the alarm is generated.</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div class="section" id="ALM-25004__s5287b6d4f1fd43c1805aa4cdbfcb725c"><h4 class="sectiontitle">Impact on the System</h4><p id="ALM-25004__en-us_topic_0070543545_p4558779">LdapServer data inconsistency occurs because the LdapServer data in Manager is damaged or the LdapServer data 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__sc725e93619b3477188476e5af927d67c"><h4 class="sectiontitle">Possible Causes</h4><ul id="ALM-25004__en-us_topic_0070543545_ul33716833"><li id="ALM-25004__en-us_topic_0070543545_li35016046">The network of the node where the LdapServer process locates is faulty.</li><li id="ALM-25004__en-us_topic_0070543545_li46708959">The LdapServer process is abnormal.</li><li id="ALM-25004__en-us_topic_0070543545_li17727455">The OS restart damages data on LdapServer.</li></ul>
</div>
<div class="section" id="ALM-25004__s90fcd9d24b3a48fdb245a066699db392"><h4 class="sectiontitle">Procedure</h4><p class="tableheading" id="ALM-25004__en-us_topic_0070543545_p26637782"><strong id="ALM-25004__b64336301957">Check whether the network where the LdapServer nodes reside is faulty.</strong></p>
<ol id="ALM-25004__ol292774919519"><li id="ALM-25004__li28876797952"><span>On the FusionInsight Manager portal, choose <strong id="ALM-25004__b96821413151918">O&amp;M &gt; Alarm<strong id="ALM-25004__b27872374104950"> &gt; Alarms</strong></strong>. Record the IP address of HostName in the alarm locating information as IP1 (if multiple alarms exist, record the IP addresses as IP1, IP2, and IP3 respectively).</span></li><li id="ALM-25004__li60356966952"><span>Contact <span id="ALM-25004__text4614151421417">O&amp;M personnel</span> and log in to the nodes corresponding to IP 1. Run the ping command to check whether the IP address of the management plane of the active OMS node can be pinged.</span><p><ul class="subitemlist" id="ALM-25004__ul43989031952"><li id="ALM-25004__li57319207952">If yes, go to <a href="#ALM-25004__li16739739952">4</a>.</li><li id="ALM-25004__li12344210952">If no, go to <a href="#ALM-25004__li8942461952">3</a>.</li></ul>
</p></li><li id="ALM-25004__li8942461952"><a name="ALM-25004__li8942461952"></a><a name="li8942461952"></a><span>Contact the network administrator to recover the network and check whether <strong id="ALM-25004__b6543151792454">Abnormal LdapServer Data Synchronization</strong> is cleared.</span><p><ul class="subitemlist" id="ALM-25004__ul938905952"><li id="ALM-25004__li57076041952">If yes, no further action is required.</li><li id="ALM-25004__li59756646952">If no, go to <a href="#ALM-25004__li16739739952">4</a>.</li></ul>
</p></li></ol>
<p class="tableheading" id="ALM-25004__p573993619521"><strong id="ALM-25004__b468322049521">Check whether the LdapServer processes are normal.</strong></p>
<ol start="4" id="ALM-25004__ol166046269547"><li id="ALM-25004__li16739739952"><a name="ALM-25004__li16739739952"></a><a name="li16739739952"></a><span>On the <strong id="ALM-25004__b13373288952">Alarm</strong> page of FusionInsight Manager, check whether the <strong id="ALM-25004__b197414019278">OLdap Resource Abnormal </strong>exists.</span><p><ul class="subitemlist" id="ALM-25004__ul16773051952"><li id="ALM-25004__li18342163952">If yes, go to <a href="#ALM-25004__li13741581952">5</a>.</li><li id="ALM-25004__li9320212952">If no, go to <a href="#ALM-25004__li40748590952">7</a>.</li></ul>
</p></li><li id="ALM-25004__li13741581952"><a name="ALM-25004__li13741581952"></a><a name="li13741581952"></a><span>Clear the alarm by following the steps provided in "ALM-12004 OLdap Resource Abnormal".</span></li><li id="ALM-25004__li53334144952"><span>Check whether <strong id="ALM-25004__b6328319192743">Abnormal LdapServer Data Synchronization</strong> is cleared in the alarm list.</span><p><ul class="subitemlist" id="ALM-25004__ul13382556952"><li id="ALM-25004__li39326292952">If yes, no further action is required.</li><li id="ALM-25004__li31313112952">If no, go to <a href="#ALM-25004__li40748590952">7</a>.</li></ul>
</p></li><li id="ALM-25004__li40748590952"><a name="ALM-25004__li40748590952"></a><a name="li40748590952"></a><span>On the <strong id="ALM-25004__b10245253952">Alarm</strong> page of FusionInsight Manager, check whether <strong id="ALM-25004__b6474052492822">Process Faul</strong>t is generated for the LdapServer service.</span><p><ul class="subitemlist" id="ALM-25004__ul4527621952"><li id="ALM-25004__li19706206952">If yes, go to <a href="#ALM-25004__li12301476952">8</a>.</li><li id="ALM-25004__li52698852952">If no, go to <a href="#ALM-25004__li36315373952">10</a>.</li></ul>
</p></li><li id="ALM-25004__li12301476952"><a name="ALM-25004__li12301476952"></a><a name="li12301476952"></a><span>Handle the alarm according to "ALM-12007 Process Fault".</span></li><li id="ALM-25004__li20561347952"><span>Check whether <strong id="ALM-25004__b1276899392542">Abnormal LdapServer Data Synchronization</strong> is cleared.</span><p><ul class="subitemlist" id="ALM-25004__ul3567861952"><li id="ALM-25004__li56895536952">If yes, no further action is required.</li><li id="ALM-25004__li45135671952">If no, go to <a href="#ALM-25004__li36315373952">10</a>.</li></ul>
</p></li></ol>
<p class="tableheading" id="ALM-25004__p8450147952"><strong id="ALM-25004__b403277009512">Check whether the LdapServer processes are normal.</strong></p>
<ol start="10" id="ALM-25004__ol517031729612"><li id="ALM-25004__li36315373952"><a name="ALM-25004__li36315373952"></a><a name="li36315373952"></a><span>On FusionInsight Manager, choose <strong id="ALM-25004__b12681135720587">O&amp;M</strong> &gt; <strong id="ALM-25004__b1681145711584">Alarm</strong> &gt; <strong id="ALM-25004__b96811657175818">Alarms</strong>. Record the IP address of HostName in the alarm locating information as "IP1" (if multiple alarms exist, record the IP addresses as "IP1", "IP2", and "IP3" respectively). Choose <strong id="ALM-25004__b2681125725814">Cluster</strong> &gt; <em id="ALM-25004__i6681155713587">Name of the desired cluster </em>&gt; <strong id="ALM-25004__b136811557145815">Services</strong> &gt; <strong id="ALM-25004__b868185795816">LdapServer</strong> &gt; <strong id="ALM-25004__b106816570583">Configurations</strong>. Record the port number of LdapServer as "PORT". (If the IP address in the alarm locating information is the IP address of the standby management node, choose <strong id="ALM-25004__b13681155716581">System</strong> &gt; <strong id="ALM-25004__b6681757185816">OMS</strong> &gt; <strong id="ALM-25004__b1568119575585">oldap</strong> &gt; <strong id="ALM-25004__b46821857115813">Modify Configuration</strong> and record the listening port number of LdapServer.)</span></li><li id="ALM-25004__li15636124010141"><span>Log in to the nodes corresponding to IP1 as user <strong id="ALM-25004__b46371040101419">omm</strong>.</span></li><li id="ALM-25004__li10392898952"><span>Run the following command to check whether errors are displayed in the queried information.</span><p><p id="ALM-25004__p159769252119"><strong id="ALM-25004__b134469372114">ldapsearch -H ldaps://</strong><em id="ALM-25004__i54467376117">I</em><em id="ALM-25004__i222513418116">P1</em>:<em id="ALM-25004__i10225163491112">PORT</em><strong id="ALM-25004__b16224183415118"> -LLL -x -D cn=root,dc=hadoop,dc=com -W -b ou=Peoples,dc=hadoop,dc=com</strong></p>
<p id="ALM-25004__p174711517417">After running the command, enter the <strong id="ALM-25004__b18471543134111">LDAP</strong> administrator password. Contact the system administrator to obtain the password.</p>
<ul class="subitemlist" id="ALM-25004__ul5218207201511"><li id="ALM-25004__li4218974155">If yes, go to <a href="#ALM-25004__li5200119952">13</a>.</li><li id="ALM-25004__li02181977159">If no, go to <a href="#ALM-25004__li40582301952">15</a>.</li></ul>
</p></li><li id="ALM-25004__li5200119952"><a name="ALM-25004__li5200119952"></a><a name="li5200119952"></a><span>Recover the LdapServer and OMS nodes using data backed up before the alarm is generated.</span><p><div class="note" id="ALM-25004__note68240502466"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p class="text" id="ALM-25004__p108241650204620">Use the OMS data and LdapServer data backed up at the same point in time to recover the 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>
</p></li><li id="ALM-25004__li56762198952"><span>Check whether alarm <strong id="ALM-25004__b485610149261">Abnormal LdapServer Data Synchronization</strong> is cleared.</span><p><ul class="subitemlist" id="ALM-25004__ul38811974952"><li id="ALM-25004__li18556507952">If yes, no further action is required.</li><li id="ALM-25004__li26682062952">If no, go to <a href="#ALM-25004__li40582301952">15</a>.</li></ul>
</p></li></ol>
<p class="tableheading" id="ALM-25004__p13763451952"><strong id="ALM-25004__b47613011964">Collect fault information.</strong></p>
<ol start="15" id="ALM-25004__ol230459379618"><li id="ALM-25004__li40582301952"><a name="ALM-25004__li40582301952"></a><a name="li40582301952"></a><span>On the FusionInsight Manager portal, choose <strong id="ALM-25004__b16767199102311">O&amp;M</strong> &gt; <strong id="ALM-25004__b34335306952">Log &gt; Download</strong>.</span></li><li id="ALM-25004__li21015825952"><span>Select <strong id="ALM-25004__b29696395952">LdapServer</strong> in the required cluster and <strong id="ALM-25004__b65940963952">OmsLdapServer</strong> from the <strong id="ALM-25004__b56597760952">Service</strong>.</span></li><li id="ALM-25004__li1145664103113"><span>Click <span><img id="ALM-25004__image1945644173117" src="en-us_image_0269417456.png"></span> in the upper right corner, and set <strong id="ALM-25004__b6456941173117">Start Date</strong> and <strong id="ALM-25004__b11456154113318">End Date</strong> for log collection to 1 hour ahead of and after the alarm generation time, respectively. Then, click <strong id="ALM-25004__b13456164113319">Download</strong>.</span></li><li id="ALM-25004__li11719809952"><span>Contact the <span id="ALM-25004__text20771180202413">O&amp;M personnel</span> and send the collected logs.</span></li></ol>
</div>
<div class="section" id="ALM-25004__section1529716184534"><h4 class="sectiontitle">Alarm Clearing</h4><p id="ALM-25004__p4677152685316">After the fault is rectified, the system automatically clears this alarm.</p>
</div>
<div class="section" id="ALM-25004__saefc4351f41d4ce9a21bc7b0fe10bb8e"><h4 class="sectiontitle">Related Information</h4><p id="ALM-25004__p8246748245">None</p>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="mrs_01_1298.html">Alarm Reference (Applicable to MRS 3.x)</a></div>
</div>
</div>
View Git Blame Copy Permalink