Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-5098

/proc/sys/lnet/routes is stupid

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
    • Rank (Obsolete):
      14058

      Description

      Presently /proc/sys/lnet/routers presents information about two more-or-less orthogonal concepts:

      1. Whether this node is has lnet forwarding enabled (is itself acting as a router)
      2. A list of networks that can be reached through peer nodes that are acting as routers

      Examples:

      Routing disabled
      net      hops   state router
      tcp         1      up 10.1.1.75@o2ib9
      tcp1        1      up 10.1.1.75@o2ib9
      tcp2        1    down 10.1.1.161@o2ib9
      tcp3        1    down 10.1.1.162@o2ib9
      tcp4        1      up 10.1.1.75@o2ib9
      o2ib2       1      up 10.1.1.159@o2ib9
      o2ib2       1      up 10.1.1.160@o2ib9
      o2ib6       1      up 10.1.1.52@o2ib9
      o2ib6       1      up 10.1.1.51@o2ib9
      o2ib6       1      up 10.1.1.53@o2ib9
      o2ib6       1      up 10.1.1.54@o2ib9
      o2ib100     1      up 10.1.1.75@o2ib9
      o2ib500     1      up 10.1.1.75@o2ib9
      
      Routing enabled
      net      hops   state router
      

      The first "Routing [enabled|disabled]" line should be not be in the routes file. There should be a separate proc file for that.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                ashehata Amir Shehata
                Reporter:
                morrone Christopher Morrone
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated: