home *** CD-ROM | disk | FTP | other *** search
/ Internet Info 1997 December / Internet_Info_CD-ROM_Walnut_Creek_December_1997.iso / ietf / snanau / snanau-minutes-93nov.txt < prev    next >
Text File  |  1994-02-08  |  8KB  |  225 lines
  1.  
  2. CURRENT_MEETING_REPORT_
  3.  
  4. Reported by Deirdre Kostick/Bellcore
  5.  
  6. Minutes of the SNA NAU Services MIB Working Group (SNANAU)
  7.  
  8.  
  9. The SNANAU Working Group met on November 3, 1993 to review the revised
  10. SNA NAU MIB Draft.
  11.  
  12.  
  13.  
  14. New State Model for SNA Nodes
  15.  
  16. The working group identified a ``state'' model for SNA Nodes to clarify
  17. how objects proposed in the snaNodeAdminTable and snaNodeOperTable would
  18. be used to control SNA nodes.  Dr. SNMP (Jeff Case) gave some greatly
  19. appreciated guidance.  Diagrams 1 and 2 (attached at the end of the
  20. notes) summarize the new model and usage of RowStatus, OperStatus and
  21. AdminStatus.
  22.  
  23. The current draft of the SNA NAU MIB shall be updated to reflect this
  24. model.
  25.  
  26.  
  27.  
  28. Other MIB Revisions
  29.  
  30. The working group agreed to make several changes.
  31.  
  32.  
  33.    o Delete the snaPu20AdminTable since there is only one object
  34.      currently in the table, add maxPiu object to snaNodeAdminTable
  35.  
  36.    o Change the max size of snaNodeAdminName to 17
  37.  
  38.    o Change the enumerated list for snaNodeAdminType as follows:  pu21 -->
  39.      t21len add (5) end node (6) network node don't add pu4, pu5 yet
  40.  
  41.    o Change snaNodeAdminId to snaNodeAdminNum and syntax to
  42.      DISPLAYSTRING with max size=3
  43.  
  44.    o Change snaNodeAdminBlockId to DISPLAYSTRING
  45.  
  46.    o Change snaNodeAdminActivationMethod to EnablingMethod
  47.  
  48.    o Add LuTermMethod to snaLu tables to allow a different method for a
  49.      specific LU
  50.  
  51.    o Clarify snaNodeEnablingMethod and add byMSonly(4) if necessary
  52.  
  53.    o Add snaNodeAdmin(Oper)HostDescription to identify a remote host for
  54.      a PU
  55.  
  56.    o Bill Kwan to investigate whether we have sufficient info for XID
  57.      for t2.1
  58.  
  59.  
  60.  
  61. Follow-up Review
  62.  
  63. The working group still needs to complete the detailed review of the
  64. remaining tables.  Definitions need to be cleaned-up.  During the
  65. meeting, the working group did not have time to review comments on the
  66. Session, Link, LU tables, etc.
  67.  
  68. Working Group members are encouraged to make comments on the mailing
  69. list preferably with detailed additions, wording, changes, etc.
  70.  
  71. A conference call will be scheduled (November 8) to continue the MIB
  72. review.  Results of the call will be posted to the mailing list.
  73.  
  74. The group has a December deadline to complete the MIB work.  There is
  75. still a lot of work to do to make this date.
  76.  
  77.  
  78.  
  79. Conformance/Compliance Statements
  80.  
  81. Zbigniew Kielczewski handed out a proposed first cut at
  82. conformance/compliance statements.  These will be updated and posted to
  83. the list.
  84.  
  85.  
  86.  
  87. Future SNA MIB Work
  88.  
  89. Additional SNA MIB work in 1994 may be approved by the Network
  90. Management Area Director, if and only if, the current SNA NAU MIB is
  91. completed on schedule---by December, 1993.
  92.  
  93. The candidate work item for 1994 is to develop APPC-related management
  94. objects.
  95.  
  96. Work to identify APPN-related management objects could be pursued in
  97. parallel, for example, by the AIW.
  98.  
  99.  
  100.  
  101. Next Version
  102.  
  103. The next version of the MIB will be posted to the mailing list by
  104. November 12.  Zbigniew, Kitty, Robin, and Deirdre volunteered to assist
  105. with editing.
  106.  
  107.  
  108. Diagram 1:  Node State Model
  109.  
  110.                         ----------------
  111.                         |              |
  112.                         | DOES NOT     |
  113.                         | EXIST        |
  114.                         |              |
  115.                         ----------------
  116.                                | ^
  117.                        create  | |delete
  118.                                V |
  119.                         ----------------
  120.                         |              |
  121.                         | INACTIVE     |
  122.                         |              |<---------------|
  123.                         |              |                |
  124.                         ----------------                |
  125.                                 | ^                     |
  126.                     activate    | |                     |
  127.                                 V |                     |
  128.                          ----------------               |
  129.                          |              |               |
  130.                  --------| WAITING      |               |
  131.                 |        |              |               |
  132.                 |        |              |               |
  133.                 |        ---------------                |
  134.                 |               | ^                     |
  135.                 |               | |                     |
  136.                 |               V |                     |
  137.                 |        ----------------               |
  138.                 |        |              |               |
  139.                 |        | ACTIVE       |               |
  140.                 |        |              |               |
  141.                 |        |              |               |
  142.                 |        ---------------                |
  143.                 |               | graceful stop or      |
  144.                 |               | stop force            |
  145.                 |               V                       |
  146.                 |        ----------------               |
  147.                 |        |              |               |
  148.                 -------->| STOPPING     |---------------|
  149.                          |              |
  150.                          |              |
  151.                          ----------------
  152.  
  153. Diagram 2:  Using the Proposed snaNodeAdmin and snaNodeOper Tables
  154.  
  155.  
  156.  
  157.         ___________________________________________________________
  158.         |____________Admin_Table_Objects____Oper_Table_Objects_____|
  159.         |____RowStatus_____|_AdminStatus__|_______OperStatus_______|
  160.         |__(no_row_entry)__|_____N/A______|__________N/A___________|
  161.         | To create a row  | inactive     | agent automatically    |
  162.         |  representing a  |              |creates a corresponding |
  163.         |  node instance,  |              |     entry in the       |
  164.         |  set RowStatus   |              | snaNodeOperTable with  |
  165.         |_____=_active_____|______________|__OperStatus=inactive___|
  166.         |     active       |To activate   |     agent changes      |
  167.         |                  |node, set     |  node's OperStatus=    |
  168.         |                  |AdminStatus   |       waiting          |
  169.         |__________________|_=_active_____|________________________|
  170.         |     active       |   active     |   node changes to      |
  171.         |__________________|______________|______``active''________|
  172.         |     active       |to stop node, |stopping or inactive    |
  173.         |                  |set Shutdown  |depending on Shutdown   |
  174.         |                  |Method to     |        Method          |
  175.         |                  |appropriate   |                        |
  176.         |                  | value &      |                        |
  177.         |                  |AdminStatus   |                        |
  178.         |__________________|=_inactive____|________________________|
  179.         |     invalid      | inactive     |      inactive          |
  180.         |____see_note#1____|______________|________________________|
  181.  
  182.  
  183. Notes:
  184.  
  185.  
  186.   1. To delete a row, OperStatus and AdminStatus must both be =
  187.      inactive.  Row deletion can be NMS or agent initiated:
  188.  
  189.      (a) The NMS sets RowStatus=invalid, or
  190.  
  191.      (b) The agent detects that a row is in the ``under creation'' state
  192.          for greater that some default period, e.g., 5mins
  193.  
  194.      (c) After reboot, the row with RowStatus=inactive will not be
  195.          included in the table
  196.  
  197.  
  198.   2. A new object, shutdownMethod, is needed.  shutdownMethod should be
  199.      a R/W object with the following values:
  200.  
  201.      (a) Graceful
  202.      (b) Forced
  203.      (c) Rol - request on line?
  204.      (d) Other
  205.  
  206.      The value of shutdownMethod is only valid for the instance that the
  207.      ``inactive'' button is pushed.
  208.  
  209.  
  210. Attendees
  211.  
  212. Michael Allen            moallen@ralvm6.vnet.ibm.com
  213. Jeff Case                case@cs.utk.edu
  214. Cleve Graves             cvg@oc.com
  215. Jeff Hilgeman            jeffh@apertus.com
  216. Zbigniew Kielczewski     zbig@eicon.qc.ca
  217. Deirdre Kostick          dck2@mail.bellcore.com
  218. William Kwan             kwan@rabbit.com
  219. Shannon Nix              sdn@netlink.com
  220. David Perkins            dperkins@synoptics.com
  221. Eddie Renoux             elr0262@newsit2.mcdata.com
  222. Kitty Shih               kmshih@novell.com
  223. Mauro Zallocco           mdz@netlink.com
  224.  
  225.