Uploaded image for project: 'lacp'
  1. lacp
  2. LACP-10

RPC Exception messages are thrown while trying to scale the number of LAG's to 32 entries.

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Resolution: Done
    • unspecified
    • None
    • General
    • None
    • Operating System: All
      Platform: All

    • 3539

    Description

      Mininet Topology: 32 Host & Switches and 2 links connecting each host and switch. Configure the Hosts on LACP mode and check if the LAG groups are formed on the switch side.
      Openvswitch version: 2.3.1
      Build no: Integration build 2133

      Steps to recreate:
      1. Bring up the controller and feature install the LACP module.
      2. Once the controller is setup, create a mininet topology script as specified above and check if the group entries are formed on all the switches. <<<Entries are formed as expected
      3. Also, check the Karaf logs to see if there are any LACP specific errors being generated while scaling up to this number. <<<<RPC Exception issue seen now.

      Error message generated on Karaf log:

      2015-06-02 11:24:24,838 | ERROR | Thread-80 | LacpGroupTbl | 203 - org.opendaylight.lacp.main.lacp.main.impl - 1.0.0.SNAPSHOT | received interrupt {}java.util.concurrent.ExecutionException: org.opendaylight.controller.md.sal.dom.api.DOMRpcImplementationNotAvailableException: No implementation of RPC AbsoluteSchemaPath

      {path=[(urn:opendaylight:group:service?revision=2013-09-18)update-group]}

      available <<<<<<On looking at the message, the exception problem looks to be because of some issue with the LcpGroupTbl impl.

      Sometimes, the same message is slightly modified and displayed as below when you scale up the LAG numbers first and create the topology, then follow it up by starting the controller.
      64 LAG's in the below case
      2015-06-01 14:44:15,591 | ERROR | Thread-1073 | LacpFlow | 203 - org.opendaylight.lacp.main.lacp.main.impl - 1.0.0.SNAPSHOT | received

      interrupt in lacp flow removal java.util.concurrent.ExecutionException: org.opendaylight.controller.md.sal.dom.api.DOMRpcImplementationNotAvailableException:

      SchemaPath AbsoluteSchemaPath

      {path=[(urn:opendaylight:flow:service?revision=2013-08-19)remove-flow]}

      is not resolved to an RPC <<<<On looking at the message, the exception problem looks to be because of some issue with the LacpFlow impl.

      Please find the Karaf.log files attached along with this bug.

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          People

            kalaiselvi_k@dell.com Kalaiselvi
            mahesh_manivasagam@dell.com Mahesh Manivasagam
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: