Details

    • Type: Bug Bug
    • Status: QA In Progress QA In Progress (View Workflow)
    • Priority: Normal Normal
    • Resolution: Unresolved
    • Component/s: NEP
    • Labels:
      None Labels
    • Customer:
      OMAN-Tel
    • Complexity:
      High
    • REQUESTER:
      INTERNAL

      Description

      It is found that, there are few naming Convention rules which are not working for SDH nodes. Please find below details.

      In below details, I have shared the naming rule for the Models with sample NEs for which the error occured.

      WDM Ciena Ciena6500 s(D)<>siteID<>counter<>s<>s(6500)<>s<>alphaCounter
      DB000101-6500-SOHAR
      DB000200-6500-SAH2
      DB000300-6500-SUWAIQ

      ADM Huawei 155/622 s(S)<>siteID<>counter<>s<>s(Metro2050)<>s<>alphaCounter
      SB000113-Metro2050-SOH
      SB029000-Metro2050
      SD000105-Metro2050-SAL
      SD000106-Metro2050-SAL2

      ADM Huawei M3100 s(S)<>siteID<>counter<>s<>s(Metro3100)<>s<>counter
      SB000201-Metro3100
      SB000303-Metro3100-SUW
      SB000401-Metro3100-Khab
      SD000103-Metro3100-SAL2
      SD000104-Metro3100-SAL2

      WDM Huawei M6040V2 s(D)<>siteID<>counter<>s<>s(Metro6040V2)<>s<>counter
      DB000110-Metro6040V2-SOH
      DB000204-Metro6040V2-SAHAM
      DB000304-Metro6040V2-SUW
      DB000306-Metro6040V2-SUW

        Activity

        Hide
        Aurobinda Panda added a comment -

        Naming convention changed as suggested. Will check the result.

        Show
        Aurobinda Panda added a comment - Naming convention changed as suggested. Will check the result.
        Hide
        Aurobinda Panda added a comment -

        @Marwan, As checked, still same issue occurred. Please check again.

        Show
        Aurobinda Panda added a comment - @Marwan, As checked, still same issue occurred. Please check again.
        Hide
        Marwan Kanaan added a comment - - edited

        Dear @Aurobinda Panda,

        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.

        Also, how do you expect SUW to match SUWAIQ_3G?

        Best Regards,
        Marwan Kanaan I Software Developer

        Show
        Marwan Kanaan added a comment - - edited Dear @Aurobinda Panda, 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. Also, how do you expect SUW to match SUWAIQ_3G? Best Regards, Marwan Kanaan I Software Developer
        Hide
        Aurobinda Panda added a comment -

        Dear @marwan,
        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.

        So instead of Zone, can't we use counter as a static value.

        Kindly confirm.

        Show
        Aurobinda Panda added a comment - Dear @marwan, 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. So instead of Zone, can't we use counter as a static value. Kindly confirm.
        Hide
        Marwan Kanaan added a comment -

        dear @aurobinda

        kindly know that you can set counter as a static value but non of the above names going to be working.

        regards,

        Show
        Marwan Kanaan added a comment - dear @aurobinda kindly know that you can set counter as a static value but non of the above names going to be working. regards,

          People

          • Assignee:
            Aurobinda Panda
            Reporter:
            Aurobinda Panda
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Due:
              Created:
              Updated:
              Planned Start:
              Planned End:
              Actual Start:
              Date of Baselining:

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 1 day, 7 hours, 10 minutes
              1d 7h 10m

                Drag and Drop