L3 Support
  1. L3 Support
  2. LS-1013

Clarification of attributes implementation for Huawei lambdas in NEP

        Details

        • Type: CR CR
        • Status: Ready for QA Ready for QA (View Workflow)
        • Priority: Normal Normal
        • Resolution: Unresolved
        • Component/s: NEP
        • Labels:
          None Labels
        • Customer:
          OMAN-Tel
        • Complexity:
          Medium
        • Severity:
          Major
        • Product:
          NEP
        • REQUESTER:
          EXTERNAL

          Description

          Dear Khaled khalil,
          Kindly assign a resource for below requirements.

          There are few attribute which are parsing in lambda reports for Huawei Nodes. As checked, these attributes are not coming from XML. So need to know about these details from NEP.

          Lambda in Lambda Service Report
          This attribute gives the lambda route assigned for each Lambda service. But not able to find the lambda assigned to this services in NEP for Huawei lambda Services.

          Capacity Details
          There are multiple Capacity Attributes available in NEP which are not present in XML. So unable to find the values for these services.

          So need assistance to identify these attributes in NEP and the data parsing rules.

            Activity

            Hide
            Permalink
            Marwan Kanaan added a comment -

            Dear @Aurobinda Panda

            Regarding your question about Lambda, Port Max Capacity, Used Capacity, and Free Capacity, please find the clarification below:

            Lambda:
            The Lambda value in the Lambda service is deduced from the Lambda routes. The system uses the Lambda attribute available in the Lambda model, which is populated by checking the main hops of the route, identifying the related interface, and verifying whether its type supports carrying Lambda.

            Port Max Capacity:
            The system deduces the final capacity based on the interface type:
            OTU → capacity × 1000 (converted to Mbps)
            Port Type Client (non-ODU) → capacity taken from the related OduType
            Otherwise → use the Node Interface Type own capacity

            Used Capacity:
            This is calculated from the Transmission Link by checking all operational Traffic Units.
            The value depends on the traffic type and applies special handling for microwave Ethernet/E1 mode.

            Free Capacity:
            Free Capacity =  Max Capacity − Used Capacity

            Best Regards,
            Marwan Kanaan I Software Developer

            Show
            Marwan Kanaan added a comment - Dear @Aurobinda Panda Regarding your question about Lambda, Port Max Capacity, Used Capacity, and Free Capacity, please find the clarification below: Lambda: The Lambda value in the Lambda service is deduced from the Lambda routes. The system uses the Lambda attribute available in the Lambda model, which is populated by checking the main hops of the route, identifying the related interface, and verifying whether its type supports carrying Lambda. Port Max Capacity: The system deduces the final capacity based on the interface type: OTU → capacity × 1000 (converted to Mbps) Port Type Client (non-ODU) → capacity taken from the related OduType Otherwise → use the Node Interface Type own capacity Used Capacity: This is calculated from the Transmission Link by checking all operational Traffic Units. The value depends on the traffic type and applies special handling for microwave Ethernet/E1 mode. Free Capacity: Free Capacity =  Max Capacity − Used Capacity Best Regards, Marwan Kanaan I Software Developer
            Cancel

              People

              • Assignee:
                Aurobinda Panda
                Reporter:
                Aurobinda Panda
              • Votes:
                0 Vote for this issue
                Watchers:
                2 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 - 5 hours
                  5h

                    Drag and Drop