 










              DECelms - Managing Digital's FDDI and Ethernet Extended Local
              Area Networks


              By Bruce E. Sweet



          Abstract                               as a part of Digital's FDDI
              The DECelms software               program.

             product provides extended
             local area network               DECelms Development
             management for Digital's             The DECelms product,
             Ethernet/IEEE 802.3                 Digital's extended
             and fiber distributed               local area network (LAN)
             data interface (FDDI)               management software,
             bridges and for its FDDI            provides remote network
             wiring concentrator.                management for Digital's
             Product development                 LAN Bridge 100, LAN
             entailed keeping pace               Bridge 150, LAN Bridge
             with a changing set                 200, DECbridge 500,
             of requirements. These              and DECconcentrator 500
             included the evolving               products. The remote
             ANSI FDDI standard, the             networks are included in
             proposed Digital Network            the extended LAN by means
             Architecture FDDI data              of transparent bridges.
             link specification, the             DECelms functionality
             Enterprise Management               includes basic SET and
             Architecture, the                   SHOW capabilities, fault
             ability to extend the               management, performance
             serviceability of the               monitoring, FDDI ring
             products, and the                   mapping, automatic device
             aggressive schedules of             discovery, and user alarms.
             the hardware and firmware           The DECelms software runs
             development teams. DECelms          as an application on a VAX
             development resulted in an          processor running under the
             improved network management         VMS operating system.
             functionality including
             fault, performance, and              When Digital embraced the
             topology management. These          new fiber distributed
             advanced features required          data interface (FDDI)
             corresponding enhancements          LAN technology, the role
             to the user interface and           that network management
             dependable documentation.           would play in the first
             The development team                product set was unclear.
             met these challenges and            As our understanding of
             successfully delivered the          the technology grew, and we
             DECelms product to market           recognized the differences


                          Digital Technical Journal Vol. 3 No. 2 Spring 1991  1

 


           DECelms - Managing Digital's FDDI and Ethernet Extended Local Area Networks



             between the token ring              not only a good network
             architecture and the                management solution but
             carrier sense multiple              a key development tool as
             access with collision               well.
             detection (CSMA/CD)                 Key FDDI Differences
             protocol, the challenge
             became obvious. Both                 Several key differences
             technical and business              between the FDDI and
             reasons made network                Ethernet technologies
             management a priority.              determined the specific
              On Ethernet/802.3 LANs,            requirements of the
             network management tools            DECelms product. First,
             provide the ability to              the physical topology and
             monitor the networks and            the location of stations
             troubleshoot problems as            attached to an FDDI ring
             they arise. The failure             play a significant role
             mechanisms of Ethernet              in how the ring operates.
             /802.3 LANs, such as                Each station is active
             faulty transceiver                  and must participate in
             taps, continuously                  connection management to
             transmitting stations, and          form a working LAN.[1] On
             broadcast storms, are well          Ethernet/802.3 LANs, each
             understood. In addition to          station is passive until it
             network management tools,           wishes to use the network.
             powerful datascopes aid             Thus, an Ethernet/802.3 LAN
             the network manager in              can operate with stations
             recognizing and correcting          that do not strictly
             these problems. Moving              observe the protocol, since
             into the 100-megabit                less stringent protocol
             (Mb) world of the FDDI              requirements between
             token ring brought a new            stations are necessary
             set of problems, some               to make the LAN work. This
             of which were understood            difference places a high
             and others not even                 priority on the ability
             imagined. We realized the           to manage topology, a
             need to offer a network             functionality that is less
             management solution that            significant on Ethernet
             was capable of performing           /802.3 LANs. Requirements
             the same functions as our           to build FDDI ring maps and
             Ethernet/802.3 products             examine third-party station
             and had the additional              management (SMT) frame data
             functionality necessary             grew from this priority.

             to meet the new challenges           A second difference is the
             of the FDDI technology.             need to manage the FDDI
             Further, no FDDI datascopes         physical layer. This need
             were available to aid               arose mainly because the
             in the development of               DECconcentrator 500 product
             the FDDI product set. To            is a physical layer device
             correct this deficiency,            and the primary building
             requirements for DECelms            block of FDDI rings. To
             functionality called                manage the FDDI physical
             for the software to be              layer, a network manager


          2  Digital Technical Journal Vol. 3 No. 2 Spring 1991

 


    DECelms - Managing Digital's FDDI and Ethernet Extended Local Area Networks



             must be able to add or              view of the FDDI data link
             remove FDDI stations from           behavior.
             the rings via manipulation          Extended Management
             of the physical layer ports         Capabilities
             (PHY ports) of the wiring
             concentrator. In addition,           Beyond the technical
             greater visibility was              requirements to provide
             given into the quality of           FDDI network management,
             the physical medium, using          DECelms requirements were
             the link error monitor, for         driven by the need for
             example.[1]                         better network management
              Another difference between         capabilities in general.
             the two technologies is             Providing an integrated
             the order of magnitude              product was a key project
             increase in performance             goal. Since managing FDDI
             of the FDDI ring over               products included managing
             Ethernet/802.3. The                 bridges, the program team
             ability to transparently            decided that the DECelms
             connect 100-Mb FDDI token           product would supersede the
             rings to 10-Mb Ethernet             current bridge management
             /802.3 LANs using the               product, remote bridge
             DECbridge 500 product               management software
             greatly influenced network          (RBMS), and incorporate
             management requirements.            RBMS functionality as
             Using these plug-and-play           a subset of the DECelms
             bridges makes it easier to          operating features. Thus,
             create network topologies           DECelms software needed
             that can funnel high                to provide basic SET
             throughput FDDI traffic             and SHOW capabilities
             onto the lower bandwidth            for the LAN Bridge 100,
             Ethernet/802.1 segments.            LAN Bridge 150, and LAN
             A good management tool is           Bridge 200 products, as
             required to monitor and             well as for the new FDDI
             control these topologies.           products, the DECbridge
                                                 500 and DECconcentrator 500
              A final key difference             devices.
             is simply the need to                In addition to the ability
             manage the FDDI data                to set and to show system
             link. The performance of            parameters, DECelms
             the ring operation must             software had requirements
             be tuned, and having the            to provide automatic fault
             capability to modify FDDI           detection, automatic device
             media access control (MAC)          discovery, performance
             characteristics such as             monitoring, and FDDI
             the valid transmission time         ring mapping. Automatic
             or target token rotation            fault detection would
             time can provide the means          be provided by a built-
             to accomplish this tuning.          in polling mechanism and
             Coupled with the modify             user alarms. Automatic
             operations is a rich set            device discovery would be
             of SHOW capabilities,               accomplished by listening
             which gives a detailed              to system identification



                          Digital Technical Journal Vol. 3 No. 2 Spring 1991  3

 


           DECelms - Managing Digital's FDDI and Ethernet Extended Local Area Networks



             announcements broadcast             months off the original 18-
             by the devices and                  month schedule. The DECelms
             registering these devices           team was expected to meet
             in the DECelms registry.            these challenging time
             Performance statistics              constraints.
             could be calculated from             Reducing the time spent
             counters kept by the LAN            on development required
             Bridge 200 and DECbridge            the DECelms team to make
             500 products and presented          many trade-offs. The first
             to the user in tabular              trade-off concerned whether
             format. FDDI ring mapping           the product platform would
             would be accomplished by            comply with the Enterprise
             interpreting the data               Management Architecture
             found in the SMT status             (EMA). The FDDI project
             information frame (SIF)             was concurrent with DECmcc
             configuration messages.             development (Digital's EMA-
             These functions and                 compliant director), but
             their implementations are           the FDDI program was three
             described in more detail            to six months ahead. Given
             later in this paper.                the time constraints, the

             Development under Time-to-          team decided that the FDDI
             market Constraints                  program could not wait for
              The requirements of the            the DECmcc program to catch
             DECelms capabilities                up. A point product was the
             were stablizing. Program            only solution that could
             decisions were now                  be achieved in the short
             influenced by the time-             time frame. A second trade-
             to-market constraints.              off involved optimizing
             Advanced development                the development effort.
             work on the DECbridge 500           Having no EMA experience,
             and DECconcentrator 500             the team used the expertise
             products was progressing,           it had recently gained
             and this work was converted         from working on the RBMS
             into a full-fledged                 version 2.0 development
             product development                 effort. They made the
             effort. When the network            pragmatic decision to port
             management discussions              the available RBMS code
             began, this effort was well         in order to meet the time-
             underway. Marketing and             to-market constraints. The
             engineering management              team planned to start with
             clearly communicated                the RBMS code, delete code
             to the developers the               that was not applicable,
             expectation that Digital            and add code to provide the
             would be the first vendor           desired new functionality.

             with a complete FDDI                 But at the same time the
             solution. This pressure             RBMS code was being refined
             prompted the developers             and expanded, the DECelms
             to be very creative in              team had to keep the
             choosing methodologies.             basic RBMS management code
             As a result, the DECbridge          operational. The firmware
             500 and DECconcentrator             teams needed to use DECelms
             500 teams shaved seven              code to debug their new

          4  Digital Technical Journal Vol. 3 No. 2 Spring 1991

 


    DECelms - Managing Digital's FDDI and Ethernet Extended Local Area Networks



             code, so the DECelms code           solely for implementing
             had to evolve in such a way         management agents in server
             that new code would replace         products. This option was
             old and supersede its               the most pure architectural
             functionality in a short            solution and fit in well
             period of time. This method         with Digital's long-
             of code development led to          term network strategy.
             a series of operations akin         But the effort was just
             to "brain transplants,"             beginning as an advanced
             where an interface was              development project,
             drawn in the existing code          and the Phase V protocol
             and new code containing             specifications were still
             additional functionality            in the review process.
             was added while the product         The memory constraints
             was kept running. The               imposed by the DECbridge
             timing of adding functions          500 and DECconcentrator 500
             had to coincide with the            devices coupled with the
             development of the peer             risk that the product might
             functionality in the                not meet the time-to-market
             firmware.                           constraints caused this
                                                 option to be ruled out as a
          Network Management                     solution.

          Architecture                            The second option was
              With the product strategy          to use the CMIP protocol
             taking shape, some                  layered over a subset
             difficult technical                 of the DNA Phase IV
             decisions concerning the            protocols. This subset is a
             management architecture             streamlined implementation
             had to be made. Choosing a          of the network services
             network management protocol         protocol (NSP) over an
             as well as supporting               802.3 data link. The
             transport and network               network layer is null, so
             layer protocols was a major         the protocol is limited
             challenge.                          to the extended LAN.
                                                 This solution was small
             Choosing a Protocol                 in size as dictated by
              The team identified three          the hardware, offered
             options for the management          guaranteed end-to-end
             protocol implementation.            delivery service, and
             The first option was using          would take less time to
             the common management               implement than the DNA
             information protocol                Phase V option; but there
             (CMIP) layered on top of            were several drawbacks.
             a pared-down implementation         The bridge and wiring
             of the Digital Network              concentrator management
             Architecture (DNA)                  entities were not defined
             Phase V protocols. This             in terms of the EMA entity
             implementation would                model, as was necessary to
             include a subset of the             define the CMIP protocol
             DECnet Phase V session,             structure. Using the Phase
             transport, routing, and             IV transport protocol
             data link protocols used            option did not bring the


                          Digital Technical Journal Vol. 3 No. 2 Spring 1991  5

 


           DECelms - Managing Digital's FDDI and Ethernet Extended Local Area Networks



             management architecture             protocol was clearly the
             closer to the open systems          best possible choice.
             interconnect (OSI) model            SMT as Compared to
             defined by DECnet/OSI               Management over the
             Phase V, and, in fact,              Protocol Stack
             would result in "throwaway"
             transport and network layer          Another approach to network
             code. Thus, this option was         management was via the
             not suitable.                       FDDI station management
              The third option was               frames defined in the
             to extend the bridge                American National Standards
             management architecture             Institute (ANSI) X3T9.5
             and the RBMS protocol to            FDDI working group draft
             include support for the             standard version 5.1. To
             FDDI products. In terms of          provide this alternative
             pure architecture, this was         meant adding complexity
             the poorest solution, since         to SMT that belonged in
             it would merely result              a more robust management
             in the extension of an              protocol such as CMIP.
             already limited protocol            Further, the SMT standard
             architecture. RBMS is               was unstable in this area;
             layered over the Ethernet           many vendors participating
             /802.3 data link, has a             in the standards work were
             null network layer, and is          advocating differing FDDI
             therefore constrained to            functionalities for SMT,
             the extended LAN. The RBMS          thus trying to extend
             transport is connectionless         SMT beyond its originally
             and, thus, does not offer           intended scope. Digital's
             guaranteed end-to-end               position was that network
             delivery service. In                management should be
             addition, no asynchronous           performed using an OSI
             message support exists, so          model where management is
             the delivery of events or           an application that runs on
             traps is unsupported. But           top of the protocol stack
             RBMS is simple, being based         and is widely available.
             on the IEEE 802.1 standard          SMT frames are below the
             for network management,             MAC level and, therefore,
             and easy to extend.                 do not traverse a LAN
             Also, the LAN Bridge 200            beyond a local FDDI ring.
             development effort produced         Thus, management using SMT
             a new implementation of             frames must come from a
             the management agent                local station on the FDDI
             that could be ported                ring. The data provided
             into the DECbridge 500              by the SMT frames, such
             and DECconcentrator 500             as the SIF, is valuable
             products. Further, there            to the network manager.
             was the opportunity to              The appropriate mechanism
             port code from the RBMS             to communicate this data
             version 2.0 product. Given          is a management protocol
             the time constraints under          using an agent that can
             which the DECelms team              communicate across extended
             had to operate, the RBMS            LANs. Once again, RBMS
                                                 could perform this task.


          6  Digital Technical Journal Vol. 3 No. 2 Spring 1991

 


    DECelms - Managing Digital's FDDI and Ethernet Extended Local Area Networks



             Management Model Definition         available. One source
              After the protocol issue           was the existing bridge
             was settled, the next step          management architecture,
             was to define the FDDI              which defined how to
             manageable entities and             manage an Ethernet/802.3
             attributes. The DECelms             bridge such as the LAN
             program team had decided            Bridge 200 device. Another
             to use RBMS, but the chosen         information source was
             long-term strategy was              the emerging ANSI X3T9.5
             to use CMIP with the                FDDI working group draft
             EMA guidelines. The RBMS            standard, specifically
             decision affected only the          the chapter concerning
             server products and not             FDDI station management.
             the FDDI adapters that were         Additional information was
             also under development. The         found in an early draft
             adapters would be managed           of the DNA FDDI data link
             via DECnet/OSI Phase V on           specification as well as
             both the VMS and the ULTRIX         in the approved version of
             operating systems. The RBMS         the DNA CSMA/CD data link
             effort could not derail             specification. The final
             the long-term management            set of inputs came from
             strategy of EMA and the             the product requirements
             migration to OSI. Thus,             of the DECbridge 500
             there needed to be two              and DECconcentrator 500
             management structures that          devices. These requirements
             offered similar management          called attention to
             capabilities but used               management capabilities
             different mechanisms.               that went beyond bridging,
             Later, a third management           wiring concentrators, FDDI
             structure driven by the             data links, and Ethernet
             internet community would            data links including
             become important, namely,           management of the down-
             the management information          line-load upgrade feature
             base (MIB) supported by the         and availability of field-
             simple network management           replaceable unit (FRU)
             protocol (SNMP).                    status.[2,3]

              A series of FDDI network
             management meetings                  All of the above data
             took place involving                sources had to be
             the FDDI implementors,              assimilated expeditiously
             the DNA architects, and             because the chip designs
             members of the ANSI FDDI            were nearing final form.
             standards working group.            If the infrastructure
             The goal was to converge            necessary to allow for the
             on a set of manageable              extension of management
             entities and attributes             functionality was not
             for the DECbridge 500               identified, either proposed
             and DECconcentrator 500             features would be dropped
             products, while keeping             from the products, or the
             an eye to the future of             chips would have to be
             EMA. Several key sources            respun. Keep in mind that
             of information were                 the strategy was to have


                          Digital Technical Journal Vol. 3 No. 2 Spring 1991  7

 


           DECelms - Managing Digital's FDDI and Ethernet Extended Local Area Networks



             two management structures           formal DNA architecture,
             in place: the first, based          pending the results of the
             on the bridge management            continuing ANSI standards
             architecture to be used             meetings.
             for the DECbridge 500
             and DECconcentrator 500
             products and managed using
             the DECelms product; and,
             the second, incorporating
             the DNA FDDI data link
             architecture and a future
             bridge and concentrator
             management architecture
             based on the EMA. Design
             decisions regarding network
             management entities and
             attributes were made
             accordingly and are
             described below.

              The following discussion
             presents the manner in
             which the combined model
             for the DECbridge 500
             and DECconcentrator 500
             products was developed.
             The proposed management
             model for the concentrator
             was flattened out and
             inserted into the current
             bridge architecture. The
             bridge architecture was
             extended to include the
             FDDI data link in addition
             to the Ethernet/802.3
             data link. Additionally,
             the PHY port entity was
             added, but instead of
             being subordinate to
             the data link as in the
             management model for the
             bridge alone, the PHY
             port entity was at a peer
             level, as shown in Figure
             1. Additional management
             attributes were defined to
             bring the visibility into
             the box as required for
             each product. This phase
             of designing a network
             management architecture
             resulted in a delay in
             the development of the


          8  Digital Technical Journal Vol. 3 No. 2 Spring 1991

 


    DECelms - Managing Digital's FDDI and Ethernet Extended Local Area Networks



             Station Management Gateway          by datagram loss on the
                                                 Ethernet. With the SMT
              As mentioned earlier in            gateway architecture in
             this paper, SMT frames do           place, a DECelms management
             not travel beyond a local           station located anywhere
             FDDI ring. The DECelms              on the extended LAN can
             product was expected to             gather SMT frame data from
             manage Digital and third-           any FDDI SMT version 5.1-
             party FDDI stations on the          compliant station on the
             FDDI ring using SMT frames.         same ring as a Digital SMT
             This management had to be           gateway station.
             initiated from the Ethernet
             /802.3 segment on which the      Management Beyond Set and Show
             DECelms host was located.
             The concept of the SMT               Several management
             gateway emerged from this           functions beyond basic
             situation.                          SET and SHOW capabilities
              An SMT gateway is                  were introduced in an
             firmware residing on the            earlier section, namely
             DECconcentrator 500 device          automatic fault detection,
             (and subsequently on the            automatic device discovery,
             DECbridge 500 product)              performance monitoring,
             that encapsulates SMT               and FDDI ring mapping.
             frames into RBMS protocol           These features add value
             data units (PDUs) and               to the network manager.
             forwards these frames               They present network fault
             across the extended LAN.            and topology data in a
             The architecture that               timely and concise manner
             evolved to implement the            which frees the network
             SMT gateway was another             manager from interpreting
             extension of the RBMS               the microlevel details of
             protocol. A new entity type         the network. A primary goal
             called the SMT gateway was          of the DECelms team was
             added. Gateway requests and         to develop a set of tools
             responses relating to SIFs,         that the network manager
             neighborhood information            could use to detect and
             frames (NIFs), and echo             correct a network problem
             frames were defined, for            before it was reported by a
             example, GET SIF, GET               distressed user.

             NIF, and DO ECHO. A set             Automatic Device Discovery
             of timers was defined to             The addition of a station
             allow the RBMS host, the            to an Ethernet/802.3 LAN is
             SMT gateway, and the target         now a common and simple
             station to be synchronized          procedure. Using the
             and to avoid an ambiguous           plug-and-play nature of
             response. For example, if           Digital's bridge products,
             a response is missing, it           the connection of Ethernet
             is important to know if the         /802.3 or FDDI LANs is
             lack of response is caused          also straightforward.
             by gateway congestion,              The addition of stations
             by no response from the             to an FDDI ring is easy
             target station, or simply           with the use of wiring


                          Digital Technical Journal Vol. 3 No. 2 Spring 1991  9

 


           DECelms - Managing Digital's FDDI and Ethernet Extended Local Area Networks



             concentrators. In campus             The ability to quickly
             environments, network               recognize changes in the
             managers can typically,             state or counters of a
             but not always, control             network device can help
             physical access to the              a network manager avoid
             network backbone but have           a degradation of service.
             less control once a segment         The DECelms background
             enters an individual                poller provides this type
             department. Consequently,           of fault recognition by
             there is a need to                  keeping information about
             automatically discover              the state of each device
             the "renegade" devices              in the DECelms registry
             that can be added to such           and reporting changes in
             networks. The DECelms               that state to the network
             product solves this problem         manager through user
             by providing a device               alarms and a log file. The
             listener that listens to            information includes the
             the maintenance operation           designated bridge on a LAN,
             protocol (MOP) system               the number of FDDI ring
             identification messages             initializations, the number
             periodically broadcast by           of cyclic redundancy check
             all of Digital's bridges            (CRC) errors on a given
             and wiring concentrators.           data link, and, perhaps
             When a new station is               most importantly, the fact
             heard, the DECelms software         that a station has become
             queries the station via             unreachable.
             the RBMS protocol to obtain         Network Interface
             more detailed information           Multiplexer Process
             about the station and
             automatically adds the               Both the device listener
             station to the DECelms              and the background poller
             registry. The software              are integral parts of the
             also produces a user alarm          DECelms process known as
             that notifies the network           the network interface
             manager of the existence            multiplexer (NIMUX).
             of this device and allows           As implied by its name,
             the manager to evaluate             NIMUX also provides the
             its impact on the topology          basic multiplexing of
             and performance of the              user protocol messages
             LAN. For instance, every            as they are sent and
             bridge added between two            received by the data link
             stations adds latency to            driver. Designing NIMUX
             the protocol communications         to incorporate these three
             between the devices. Too            distinct functions was a
             much latency may negatively         considerable challenge. The
             impact LAN performance by           design includes a mailbox
             causing certain protocols           interface to the variable
             to fail.                            number of user interface
             Background Poller                   tasks. This interface
                                                 provides for both the
                                                 sending and receiving of
                                                 user data and alarms. The
                                                 NIMUX design also provides


          10  Digital Technical Journal Vol. 3 No. 2 Spring 1991

 


    DECelms - Managing Digital's FDDI and Ethernet Extended Local Area Networks



             the control interface for           itself. Several event flags
             the background poller and           are required to identify
             the device listener and a           when a query is pending and
             service interface for the           then to identify whether
             DECelms registry, which is          the query is a success or
             only written by NIMUX for           a failure. When a single
             synchronization purposes.           query is completed, the
              Within NIMUX is a kernel           next step is dependent
             that synchronizes these             upon the device type and
             three basic functions.              the status of the previous
             Synchronization is                  query.

             performed using VMS                  The automatic addition of
             asynchronous system                 a device to the DECelms
             traps (ASTs) and event              registry is performed
             flags. When the NIMUX               in the polling cycle.
             has no tasks, the process           Once a device MOP system
             hibernates to conserve              identification message
             the CPU utilization. But,           is heard and the device
             the NIMUX process may be            is recognized as new to
             woken up, for example, by           DECelms, the responsibility
             the delivery of a mailbox           of performing the RBMS
             message from a user process         protocol queries belongs to
             or by the completion of a           the poller. Three protocol
             network I/O operation.              messages are necessary
              The implementation of              to determine the device
             the background poller is            type and MAC addresses.
             complex. The background             The recognition that these
             poller gathers state                two functions have this
             information for each device         common thread helped to
             in the DECelms registry             simplify the NIMUX design
             and continually circulates          and limited the amount of
             through the registry. This          internal state information
             initial query is necessary          that it was necessary to
             to determine whether the            keep.

             device is currently active           In parallel to the
             or inactive. To obtain the          background device queries
             complete state of a device,         and the automatic device
             the DECelms software                registration taking place,
             must issue multiple                 NIMUX also has to process
             protocol requests to that           user requests. These
             device. In the case of a            requests are given
             DECconcentrator 500 device,         priority over those of the
             twelve requests must be             background poller, since
             issued to accumulate                an interactive user cannot
             all the device data. The            be made to wait until all
             synchronization of these            the background polling
             requests is a challenge,            queries are completed. This
             since it is possible for            processing is accomplished
             any of these requests to            in the outermost loop of
             fail because of a datagram          NIMUX. If a user request
             loss or the failure of              is delivered via a mailbox,
             the network or the device           an event flag indicates

                         Digital Technical Journal Vol. 3 No. 2 Spring 1991  11

 


           DECelms - Managing Digital's FDDI and Ethernet Extended Local Area Networks



             its arrival. This request           to allow user registration,
             is given preference over            modification, and deletion
             moving on to the next step          of devices in the DECelms
             in the polling process.             database using NIMUX as the
              An important part of the           server.

             interface between NIMUX             FDDI Ring Mapping
             and the user processes               The ability to map the
             is the ability to deliver           FDDI ring is a key feature
             alarm messages. Each user           of the DECelms product.
             process has the option of           The SMT gateway provides
             enabling or disabling alarm         the mechanism to obtain
             messages for its process.           the raw SMT frame data
             The fact that multiple              necessary to build ring
             alarms can be generated             maps. Two types of ring
             by a single device query            maps were identified as
             from the background poller,         possible functionalities:
             and multiple users need             a simple logical ring
             to receive these alarms,            map and a physical ring
             means the interface has to          map. The logical ring map
             contain queues to buffer            could be built using the
             the alarms and state                upstream neighbor address
             variables to control the            (UNA) contained in the
             sending of the data. This           NIFs. This functionality
             problem was solved, as were         would provide a list of
             most of the NIMUX interface         the MAC addresses in the
             problems, by the addition           FDDI ring to which the
             of these data structures to         token was passed, but would
             the bridge control process          not provide information
             (BCP) tables. A BCP table           regarding the number of PHY
             is a robust data structure          ports in a concentrator or
             that keeps the NIMUX state          the details of the physical
             information for a single            topology of the network.
             user process. One table
             is created and destroyed             The preferred functionality
             for each user process that          was the physical ring map
             exists.                             which can provide detail
              The last job NIMUX can             into the actual physical
             perform is giving write             topology of the FDDI ring.
             access to the DECelms               Using the theory of wiring
             registry. Since both                concentrators to build
             the automatic device                FDDI rings, the resulting
             registration function in            topology is a ring of
             NIMUX and a user process            trees. Typically, this
             can add devices into the            configuration includes dual
             registry, synchronization           attachment concentrators
             is necessary. The simplest          (DACs) located on the
             solution is to eliminate            dual FDDI ring, with
             the need to synchronize by          other concentrators and
             having only NIMUX do the            single attachment stations
             registry write operations.          (SASs) connected to the
             The mailbox interface               concentrator on the
             commands were extended              dual ring in a tree-like


          12  Digital Technical Journal Vol. 3 No. 2 Spring 1991

 


    DECelms - Managing Digital's FDDI and Ethernet Extended Local Area Networks



             fashion.[3] The physical            increased testing the ring
             ring map is required to             map could interpret data
             represent this topology             from many vendors and thus
             showing the PHY port                became a very useful and
             attachments in addition             popular tool.
             to the MAC attachments.              Another feature was added

              This representation is             to the ring map which
             accomplished using the              made it possible to build
             data contained in the SIF           partial ring maps. The
             configuration messages.             capability of specifying
             The physical ring mapping           the ring map starting
             starts when the user                address allows a user
             supplies the address of an          to pass a station that
             SMT gateway on the target           cannot be mapped otherwise
             FDDI ring. The DECelms host         (i.e., the station does
             then issues GET SIF gateway         not correctly respond to a
             requests to the gateway.            SIF request) and manually
             The algorithm calls for             continue the map with the
             the ring map to start               next station on the ring.
             with the gateway's SIF
             information. Then, the UNA
             of the gateway contained
             in the SIF configuration
             message indicates which
             station in the ring to
             query next. Using the
             station descriptor, station
             state, and path descriptor
             fields of the SIF response,
             the DECelms host can derive
             the detailed physical map.

              The basic mechanism to
             provide the physical ring
             map was understood, but
             the implementation and
             the actual application
             mandated additional
             requirements. With the
             SMT standard still in a
             state of flux, testing the
             ring map with third-party
             vendors disclosed that it
             was possible to interpret
             the standard in different
             ways. Consequently, the
             ring map code had to be
             more flexible to interpret
             the same data fields
             which often had slight
             variations in format due
             to loose interpretations
             of the specification. With

                         Digital Technical Journal Vol. 3 No. 2 Spring 1991  13

 


           DECelms - Managing Digital's FDDI and Ethernet Extended Local Area Networks



              The display of the
             map was a noteworthy                the way in which logic
             task. Concepts for this             statements appear in a
             implementation ranged from          compiler listing. Figure
             a simple tabular format             2 is an example of a ring
             to color graphics. The              map display. This icon
             time constraints greatly            implementation was achieved
             influenced our decision.            in far less time than a
             A simple and concise set            graphics display solution
             of icons was developed to           would have taken and offers
             represent the stations on           the user a picture of the
             the ring. These icons are           FDDI ring map, which is
             actually depicted as stick          an advantage over simply
             figures displayed using             presenting a table. In
             ASCII terminal art. Each            actual use, the map is easy
             icon is paired with the             to understand and provides
             level at which it exists            an intuitive picture of the
             in a tree, similar to               network topology.





































          14  Digital Technical Journal Vol. 3 No. 2 Spring 1991

 


    DECelms - Managing Digital's FDDI and Ethernet Extended Local Area Networks



          User Interface                         keypad and options to move
              As described earlier,              the output data into files.
             the DECelms code has                The integration of ESM
             its roots in the RBMS               into the DECelms software
             software. However, the              was accomplished through
             RBMS user interface is              a well-defined interface
             a simple command line               that could take the output
             which lacks a number of             of the original RBMS output
             features necessary to make          and convert it into the
             the product more useful             required format for ESM.
             to network managers. To             One by one, the old screens
             remedy this deficiency,             were replaced by ESM, and
             the DECelms team set                at any given time during
             the following goals for             development there was a
             the user interface. The             working user interface that
             software needed to provide          provided debug support for
             intuitive commands to a             the firmware developers.

             previous RBMS user, shorter
             commands than RBMS, the          Summary
             ability to scroll through            This paper presents
             long output displays, the           two important themes.
             ability to input data from          The first concerns the
             command files, and the              technical challenges and
             ability to redirect output          accomplishments of the
             into files. During the              DECelms product. Among the
             process of reaching these           challenges were defining
             goals, the product had to           the network management
             be continuously available           architecture, including the
             as a development tool.              protocol, the manageable

              A screen-based, user               entities and attributes,
             interface solution,                 and the SMT gateway.
             known as the DECelms                Technical accomplishments
             screen manager (ESM), was           included the design of
             designed. ESM uses VMS              NIMUX and its multifaceted
             screen management (SMG)             functionality. The
             to provide the basic                second theme was how the
             screen manipulation.                development team proceeded
             Two screen modes were               to build the product. The
             developed: an input mode            time to market became the
             and an output mode. In              controlling factor in many
             the input screen mode,              product decisions. Trade-
             commands are echoed and             offs were made in favor of
             error messages displayed.           product functionality and
             This mode provides command          meeting users' expectations
             line recall, command line           rather than to promote and
             editing, and support for            preserve architectural and
             command files. The output           design purity. Above all,
             screen mode is used to              product quality remained
             display the data from               the top priority and the
             command requests. This              motivation for the DECelms
             mode provides the user with         development team to strive
             scrolling driven by the             for excellence.

                         Digital Technical Journal Vol. 3 No. 2 Spring 1991  15

 


           DECelms - Managing Digital's FDDI and Ethernet Extended Local Area Networks



                                                 DECelms product a success
          Acknowledgments                        story.

              The DECelms product was a
             significant accomplishment,      References
             completed in a short period
             of time. It was the result          o  P. Ciarfella, D. Benson,
             of a great team effort and             and D. Sawyer, "An
             personal sacrifice by the              Overview of the Common
             DECelms development team.              Node Software," Digital
             I want to recognize the                Technical Journal, vol.
             following individuals for              3, no. 2 (Spring 1991,
             their efforts as members               this issue): 42-52.
             of the engineering team:            o  R. Kochem, J. Hiscock,
             Barry Colella, Mary Ellen              and B. Mayo, "The
             Monette, Phil Morano, Ken              Development of the
             Pruyn, and Herman Levenson.            DECbridge Product,"
             In addition, I want to                 Digital Technical
             thank Andrew Shores for his            Journal, vol. 3, no.
             diligence and endurance in             2 (Spring 1991, this
             producing the DECelms user             issue): 53-63.
             documentation. Lastly, I            o  W. Tiffany, P. Koning,
             want to thank members of               and J. Kuenzel, "The
             the FDDI program team,                 DECconcentrator 500
             the DECbridge 500 and                  Product," Digital
             DECconcentrator 500 teams,             Technical Journal, vol.
             and the NAC architecture               3, no. 2 (Spring 1991,
             group for their support and            this issue): 64-75.
             contributions that made the


























          16  Digital Technical Journal Vol. 3 No. 2 Spring 1991
=============================================================================
Copyright 1991 Digital Equipment Corporation.  Forwarding and copying of this 
article is permitted for personal and educational purposes without fee 
provided that Digital Equipment Corporation's copyright is retained with the 
article and that the content is not modified. This article is not to be 
distributed for commercial advantage. Abstracting with credit of Digital 
Equipment Corporation's authorship is permitted.  All rights reserved.
=============================================================================
