http://jira.mobinets.com/jira This file is an XML representation of an issue en-us 6.1.4 6159 19-11-2013 http://jira.mobinets.com/jira/browse/LS-566 L3 Support <p>It is found that, there are few naming Convention rules which are not working for SDH nodes. Please find below details.</p> <p>In below details, I have shared the naming rule for the Models with sample NEs for which the error occured.</p> <p>WDM Ciena Ciena6500 s(D)&lt;&gt;siteID&lt;&gt;counter&lt;&gt;s<img class="emoticon" src="http://jira.mobinets.com/jira/images/icons/emoticons/forbidden.gif" height="16" width="16" align="absmiddle" alt="" border="0"/>&lt;&gt;s(6500)&lt;&gt;s<img class="emoticon" src="http://jira.mobinets.com/jira/images/icons/emoticons/forbidden.gif" height="16" width="16" align="absmiddle" alt="" border="0"/>&lt;&gt;alphaCounter<br/> DB000101-6500-SOHAR<br/> DB000200-6500-SAH2<br/> DB000300-6500-SUWAIQ</p> <p>ADM Huawei 155/622 s(S)&lt;&gt;siteID&lt;&gt;counter&lt;&gt;s<img class="emoticon" src="http://jira.mobinets.com/jira/images/icons/emoticons/forbidden.gif" height="16" width="16" align="absmiddle" alt="" border="0"/>&lt;&gt;s(Metro2050)&lt;&gt;s<img class="emoticon" src="http://jira.mobinets.com/jira/images/icons/emoticons/forbidden.gif" height="16" width="16" align="absmiddle" alt="" border="0"/>&lt;&gt;alphaCounter<br/> SB000113-Metro2050-SOH<br/> SB029000-Metro2050<br/> SD000105-Metro2050-SAL<br/> SD000106-Metro2050-SAL2</p> <p>ADM Huawei M3100 s(S)&lt;&gt;siteID&lt;&gt;counter&lt;&gt;s<img class="emoticon" src="http://jira.mobinets.com/jira/images/icons/emoticons/forbidden.gif" height="16" width="16" align="absmiddle" alt="" border="0"/>&lt;&gt;s(Metro3100)&lt;&gt;s<img class="emoticon" src="http://jira.mobinets.com/jira/images/icons/emoticons/forbidden.gif" height="16" width="16" align="absmiddle" alt="" border="0"/>&lt;&gt;counter<br/> SB000201-Metro3100<br/> SB000303-Metro3100-SUW<br/> SB000401-Metro3100-Khab<br/> SD000103-Metro3100-SAL2<br/> SD000104-Metro3100-SAL2</p> <p>WDM Huawei M6040V2 s(D)&lt;&gt;siteID&lt;&gt;counter&lt;&gt;s<img class="emoticon" src="http://jira.mobinets.com/jira/images/icons/emoticons/forbidden.gif" height="16" width="16" align="absmiddle" alt="" border="0"/>&lt;&gt;s(Metro6040V2)&lt;&gt;s<img class="emoticon" src="http://jira.mobinets.com/jira/images/icons/emoticons/forbidden.gif" height="16" width="16" align="absmiddle" alt="" border="0"/>&lt;&gt;counter<br/> DB000110-Metro6040V2-SOH<br/> DB000204-Metro6040V2-SAHAM<br/> DB000304-Metro6040V2-SUW<br/> DB000306-Metro6040V2-SUW</p> LS-566

OT | Naming Convention issue for SDH Nodes

Bug Normal QA In Progress Unresolved Aurobinda Panda Aurobinda Panda Tue, 12 Aug 2025 06:59:18 +0300 Fri, 5 Dec 2025 05:30:59 +0200 NEP Fri, 22 Aug 2025 00:00:00 +0300 0 4 0 minutes 1 day, 7 hours, 10 minutes <p> please provide more details about the issue as it's not clear the scenario and what you are expecting?</p> <p>Dear Hassan,<br/> i have added the SS from naming convnetion and attchament from KQI. We have tried to change the naming rule from counter to alphacounter. but still same nodes are reporting.</p> <p>Please check.</p> <p>as discussed with marwan , we need to check if we can add more options in preferences to cover our cases</p> <p>tx</p> <p>dear @aurobinda kindly share a sample xml for the nodes above for test purpose </p> <p>Asked Integration to generate an XML</p> <p>Dear @Aurobinda Panda,</p> <p>note that I checked the rules locally and, after testing, the issue is within the rule itself, as the nodes are ending with zone names.</p> <p>Therefore, I suggest applying the following rule:<br/> s(D)&lt;&gt;siteID&lt;&gt;counter&lt;&gt;s<img class="emoticon" src="http://jira.mobinets.com/jira/images/icons/emoticons/forbidden.gif" height="16" width="16" align="absmiddle" alt="" border="0"/>&lt;&gt;s(Metro6040V2)&lt;&gt;s<img class="emoticon" src="http://jira.mobinets.com/jira/images/icons/emoticons/forbidden.gif" height="16" width="16" align="absmiddle" alt="" border="0"/>&lt;&gt;zone</p> <p>Additionally, for the rest of the rules, please add zone instead of counter or AlphaCounter and verify the rule afterward.</p> <p>Best Regards,<br/> Marwan Kanaan I Software Developer</p> <p>Naming convention changed as suggested. Will check the result.</p> <p>@Marwan, As checked, still same issue occurred. Please check again.</p> <p>Dear @Aurobinda Panda,</p> <p>The names and zone names don’t match. Either the zone names should be in uppercase for Sohar, Saham, and Suwaiq, or you can choose to ignore the mismatched ones as this is a normal case due to naming convention variations for these nodes.</p> <p>Also, how do you expect SUW to match SUWAIQ_3G?</p> <p>Best Regards,<br/> Marwan Kanaan I Software Developer</p> <p>Dear @marwan,<br/> As per your suggestions naming convention rules changed. But if still issue is not resolved, so the suggestions are not relevant. atleast one of the NEs should have updated with the suggested rule. but it didn't happen.</p> <p>So instead of Zone, can't we use counter as a static value.</p> <p>Kindly confirm.</p> <p>dear @aurobinda </p> <p>kindly know that you can set counter as a static value but non of the above names going to be working.</p> <p>regards,</p> Actual Start Fri, 10 Oct 2025 00:00:00 +0300 Baseline End Fri, 22 Aug 2025 00:00:00 +0300 Baseline Start Fri, 22 Aug 2025 00:00:00 +0300 Complexity Customer Date of Baselining Thu, 14 Aug 2025 15:43:31 +0300 Dev. Actual Duration Gantt Options Last Comment <p style="display:inline"><b>Evaluation License Error:</b> EXPIRED</p> Original Estimate PDM Actual Duration Planned End Fri, 22 Aug 2025 00:00:00 +0300 Planned Start Fri, 22 Aug 2025 00:00:00 +0300 REQUESTER Rank 0|xtip61: Rank (Obsolete) 9223372036854775807 VTDirections