LLC, Mapped Ethernet and Station Management (SMT) services. The DNA IEEE 802.5/Token Ring module incorporates the functions and operations defined in the IEEE 802.5 Token Ring Access Method, parts of the ISO 8802-1 (IEEE 802.1) Addressing, Internetworking and Network Management, and parts of the ISO 8802-2 (IEEE 802.2) Logical Link Control (LLC) specifications. To this, the DNA 802.5/Token Ring Data Link adds features often needed by users of the data link. A typical such user is the Network Layer of the Digital Network Architecture (OSI). 3 Subentities The entity hierarchy of the Token Ring module is: Node___Token_Ring____Port | |_Station____Source_Route | |_FA_Map The TOKEN RING entity is the top-level entity in the hierarchy of entities belonging to the Token Ring module. A TOKEN RING PORT entity represents an access point to the service offered by the Token Ring module. A client transmits and receives data through a port. Ports are created and deleted by client use of open and close service interface procedures. The port-name refers to the port managed by this command. A TOKEN RING STATION entity manages a Token Ring controller. Each station corresponds to a particular instance of Logical Link Control (LLC), Medium Access Control (MAC), and physical attachment. The Token Ring data link can be monitored and controlled through DNA network management. The station-name refers to the station managed by this command. A TOKEN RING STATION SOURCE ROUTE entity describes an entry in the Source Routing database. In Transparent Source Routing, the Source Route entities are typically created and enabled by the parent Station entity. The sourceroute-id refers to the source route entity managed by this command. The TOKEN RING STATION FA MAP (Functional Address Mapping) entities describe the default Functional Address-Global Address mapping to be applied to ports that are created with the same protocol identifiers. The famap-id refers to the FA map entity managed by this command. 2 Loopback_Application The Loopback Application module allows a network manager to invoke a loopback test between applications on two nodes, thus testing all the supporting layers of the Digital Network Architecture. The Loopback Application module has two components: o The loop access module, which initiates the loopback test o The loop mirror module, which accepts connections from the remote loop access modules and mirrors any data sent to it back to the sender. The Loopback Application module has only one entity: the loopback application entity. This loopback application entity describes features of the Loopback Application module which allows you to run a loopback test between two nodes or itself. The loopback application entity is created and deleted automatically with the node entity, and is always enabled.