1、 MIL-HDBK-818-1 31 October 1992 MILITARY HANDBOOK SRVIVABLE ADAPTABLE FIBER OPTIC EMBEDDED NETWORK (SAFENET) NETWORK DEVELOPMENT GUIDANCE AMSC N/A AREA MCCR PIS BA. Approved for public release; distribution is * unlimited. Provided by IHSNot for ResaleNo reproduction or networking permitted without
2、license from IHS-,-,-MIL-HDBK-818 -1 9999970 0100L39 093 MIL-HDBK-818-1 FOREWORD 1. Departments and Agencies of the Department of Defense. 2. Beneficial comments (recommendations, additions, deletions) and any pertinent data which may be of use in improving this document should be addressed to: Spac
3、e and Naval Warfare Systems Command, Code 233-2B2, Washington, D.C., 20363- 5100, by using the self-addressed Standardization Document Improvement Proposal (DD Form 1426) appearing at the end of this document or by letter. This military handbook is approved for use by all 3. This document provides g
4、uidance for the development of fiber optic local area networks which are intended for use in support of mission critical computer resources. companion document to MIL-STD-2204, the SAFENET standard. It is a ii Provided by IHSNot for ResaleNo reproduction or networking permitted without license from
5、IHS-,-,-NIL-HDBK-818 -1 W 9999970 010OLllO 805 MIL-HDBK-818-1 CONTENTS PAGE PARAGRAPH 1 . SAFENET OVERVIEW 1 1.1 Background 1 1.2 Network features . 1 1.3 SAFENET profile 2 1.4 Profile selection . 2 2 . SAFENET USER SERVICES 5 2.1 Introduction . 5 2.2 User services overview 5 2.3 Components of user
6、services 11 3 . NETWORK MANAGEMENT . 15 3.1 Introduction . 15 3.2 Network management overview 15 3.3 Limitations 19 4 . SAFENET LIGHTWEIGHT APPLICATION SERVICE DEFINITION . 21 4.1 Introduction . 21 4.2 Service definitions 21 4.3 Lightweight application services . 22 5 . NATO NETWORK INDEPENDENT INTE
7、RFACE . 37 5.1 Introduction . 37 5.2 NIIF services . 38 5.3 NIIF specifications 43 6 . XTP Implementation Notes 47 6.1 Introduction . 47 6.2 Context Identification 47 6.3 Retry Frenzy . 47 6.4 Context Termination 47 6.5 Multicast Reliability . 48 7 . SAFENET TRANSFER SERVICES 49 7.1 Introduction . 4
8、9 7.2 Transport layer services . 49 7.3 Network layer services 52 7.4 Logical link control services . 54 8 . SAFENET CONFIGURATION OPTIONS 55 8.1 Introduction . 55 8.2 Criteria for Selection 55 8.3 Fiber . 55 8.4 Cable topology 59 iii Provided by IHSNot for ResaleNo reproduction or networking permit
9、ted without license from IHS-,-,-9. 10 o 11. 12. MIL-HDBK-818-1 8.5 Network devices and connection options SAFENET OPTICAL POWER BUD and network security. This structure is defined in ISO/IEC 7498-4 Management Framework and ISO/IEC 10040 System Management Overview. network management as defined by I
10、S0 standards are still evolving, enough is stable to provide a sound and useful basis for managing complex networks. The following subsections provide an overview and general requirements derived from the current NIST OIW Stable Implementation Agreements and from the underlying IS0 standards (IS0 74
11、98, ISO/IEC 7498-4, ISO/IEC 10040, ISO/IEC 10165-1). While aspects of 3.2.1 StruC ture. Network management can be viewed as the set of operational and administrative mechanisms necessary to: a. bring up, enroll, and/or alter network resources, b. keep network resources operational, c. fine tune thes
12、e resources and/or plan for their d. manage the accounting of their use, and e. expansion, manage their protection from unauthorized useltampering. The structure provided in the current IS0 standards and in the NIST OIW Implementation Agreements is designed to support all the above functions. The me
13、chanisms included in the SAFENET profile will primarily support a subset of the capabilities in the first three areas. A complete set of management capabilities in a network system will require IS0 system management functions, IS0 layer management functions, and local or system node management funct
14、ions. This last is outside the scope of the IS0 standards. System management in the IS0 standards is based on the following concepts: f . managed objects, g. layer management, h. managing applications, i. management agent applications, 15 Provided by IHSNot for ResaleNo reproduction or networking pe
15、rmitted without license from IHS-,-,-MIL-HDBK-18 -1 D 9999970 OItOOL59 981 MIL-HDBK-818-1 j. k. 1. 3.2.1.1 pianaaed obiects. A managed resource is any resource such as a layer entity, a connection, or an item of physical communication equipment within the managed system that is subject to management
16、. view of such a resource that represents its properties as seen by, and for the purposes of, management. The IS0 standards include a subset (ISO/IEC 10165-1, 2, 4) which describe how objects are to be defined. It is the responsibi-lity of the group defining a communication service or device to prov
17、ide the definition of the managed object classes required by that entity. The definition of a managed object class includes its attributes (for example the parameters which can be read or set), control actions which can be taken on the real entity it represents, and notifications of important events
18、 which can be transmitted to a managing application. Thus the definition of the managed object classes relevant to an entity define the management operations which can be used with respect to that entity and the notifications which the entity will make available to a managing process . The set of ma
19、naged object class definitions representing the managed resources in a real open system is referred to as its Management Information Base (MIB). This is a conceptual grouping of all the infomation, actions, and notifications. It is not intended to imply any particular way of storing information. par
20、ticular it does not imply a central storage of all information. capability in each instantiation of a communication protocols for communication between managing interfaces between the agent application and layer service (or equipment) to carry out management actions or provide management information
21、, applications and agent applications, management entities in the same system node. A managed object is the abstracted In The NIST OIW includes in its implementation agreements a non-normative appendix which provides the definitions of certain managed object classes. Management Information Library (
22、MIL). Object definitions to be used in SAFENET are provided in MIL-STD-2204. that some management functions will need to be carried out primarily within specific layers of a profile. The specification of such functions is included in the standards for the layer in question. Any managed object defini
23、tions required should be in accordance with the rules for defining managed objects as defined in MIL-STD-2204. In SAFENET, LAN station management (SMT) is an This listing is referred to as the 3.2.1.2 Lav er manacrement . The IS0 architecture recognizes 16 Provided by IHSNot for ResaleNo reproductio
24、n or networking permitted without license from IHS-,-,-NIL-HDBK-ALA -1, 9999970 OLOOLb0 bT3 MIL-HDBK-818-1 important example of this. other things SMT controls the initialization and reconfiguration processes for the LAN. controlled by system management much is carried out without direct reliance on
25、 system management. 3.2.1.3 Managina am1 kation. System network management will be carried out by some combination of people and software implementing system policy. The software implementing or assisting people in implementing management policy may be centralized, federated, or distributed. The IS0
26、 standards allow for all cases. software, and the definition of policies to be implemented by such software, are outside the scope of IS0 communication standards. to carry out policy and provide the communication protocols needed. managing application processes. Each one may, for example, be concern
27、ed with a different aspect of system management (e.g., security, fault recovery) or be concerned with managing a subset of the nodes in the system. This is defined in FDDI SMT. Among While some aspects of this can be The managing applications which make up this The IS0 standards define the capabilit
28、ies available There may be a number of system nodes which contain 3.2.1.4 Manaaement aaent Drocess. An agent application is an application making use of system management services, which for a particular exchange of systems management information performs management operations on managed objects and
29、 emits notifications of events on behalf of managed objects. This definition and the standards allow for the case in which an application acts as both manager and agent. The same application process may take on the managing role and agent role in different instances of management communication. In t
30、he OS1 profile each SAFENET LAN node should have a management agent process. all supported management interactions with the managed objects in the LAN node of which it is a part. (services) supported are defined in MIL-STD-2204. Figure 2 shows the relationships between a process acting in the manage
31、r role and one acting in the agent role. management functions is not shown in this figure. This agent process should carry out The management interactions Layer management or local 3.2.1.5 Laver man aaement entities. Any instantiation of a communication service should provide the capability to carry
32、 out management actions and provide the management information specified in the definition of the managed object classes relevant to it. referred to as the layer management entity. an example of a layer management entity. The layer management entity does not have to be a separately defined and ident
33、ified The instantiation of these capabilities is The SMT of FDDI is 17 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-HDBK-818 -1 m 9999970 OLOOLbL 53T m I l , part of an implementation. MIL-HDBK-818-1 I I MANAGING OPEN SYSTEM COMMUNICATIONS MAN
34、AGED OPEN SYSTEM Figure 2. Systems Management Interactions The managed object class definition provides the semantics The specification of and syntax of the information, and describes actions which the communication object may be required to carry out and the events for which it will generate notifi
35、cations. the layer management entity interface to the local management agent application is a local matter. entities, then the interface may be the subject of other standards. standards provide the communication protocols and service definitions for interchanges between applications acting in the ma
36、naging and agent roles. process which implements these standards and is logically a part of the application layer is called the System Management Application Entity (SMAE). services that are included in the SMAE. The SMAE includes the management services and protocols defined by the IS0 standards wh
37、ich are used by an application process acting in the manager If both are software 3.2.1.6 *E SVSta ato O . The IS0 That portion of the application Figure 3 shows application layer 18 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-MIL-HDBK-BIB -1 = 9
38、999970 O100162 ri76 9 MIL-HDBK-818-1 role, agent role, or both. application interface between the SMAE or its components and the remaining functions of the management application process. SMAE is logically comprised of Common Management Information Service Element (CMISE), System Management Applicat
39、ion Service Element (SMASE), Remote Operation Service Element (ROSE), and Association Control Service Element (ACSE). These last two application service elements are also intended to be used by other application layer capabilities (for example FTAM and directory services). SMAE a system management a
40、pplication process may make use of other services such as FTAM. An instantiation of the SMAE may also contain locally defined capabilities such as the mechanism for gaining access to local managed objects. The IS0 standards do not specify whether or how managing processes in different system nodes w
41、ill communicate with each other when multiple managers exist in a system. the Private Cornunications application interface could be used for this purpose. layer standards such as Transaction Processing (ISO/IEC 10026 parts 1-4) could also be used but are outside the scope of SAFENET. The IS0 standar
42、ds do not define the The In addition to the services included in the Within the scope of SAFENET, FTAM or Capabilities defined in other IS0 application The components of the SMAE are defined in MIL-STD-2204. 3.2.1.7 hocal interfaces. The means by which an application acting in either the managing ro
43、le or the agent role carries out management operations or receives notifications within the system node in which it is resident is a local matter. The exception to this is when the Network Independent Interface (NIIF) is required, in which case management information should be passed betweep lower l
44、ayer entities and the application by means of the NIIF management operations. 3.3 Limitat ions. A conforming implementation of SAFENET should provide mechanisms for carrying out network management. Some capabilities, such as providing selected fault detection and recovery functions, are inherent in
45、the layer standards themselves and are available whenever the layer standard is implemented. For example, a conforming FDDI implementation automatically reconfigures to recover from certain breaks in the cable plant. As outlined in the following paragraph, the complete provision of network managemen
46、t in a system requires much additional capability beyond that supplied if only the functions and mechanisms specified in the SAFENET profile are implemented. System designers and implementors using components based on SAFENET need to establish their requirements for the way in which network componen
47、ts are interconnected, and for capabilities such as system initialization, dynamic configuration control, fault 19 Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-NIL-HDBK-818 -1 9999970 OLOOLb3 302 = MIL-HDBK-818-1 MANAGIEMENT APPLICATION PROCESSES
48、(MANAGERIAGENT) IMPLEMENTOR SPECIFIED APPLICATION INTERFACES SMAE LIGHTWEIGHT APPLICATION SERVICE. S SERVICES S IMPLEMENTOR DEFINE0 MANAQEMENT CAPABIUTY -AM I I Figure 3. Management and the Application Layer detection and recovery, sunrivability, safety, security, and time of day distribution which
49、are supported by network management. The selection of the components to be connected to the network, the network topology, and the management policies to be implemented in managing processes will determine the extent to which system requirements can be achieved by a LAN based on the SAFENET profile. The selection process, management policies, and the functions implemented in managing processes are outside the scope of
