1、i 1 MIL-mBK-1351 Dite: 23 Jd93 MILITARY HANDBOOK NETWORK MANAGEMEW FOR DOD COMMUNICATIONS AMSC NIA AREADCPS DISTRIBUTION STATEMEm Approved For Public Rckrse; Distrution iS Unlimited Licensed by Information Handling Services - MIL-HDBK-L35L W 9999970 0399285 273 MIL-HDBK-135 1 23 Jul93 FOREWORD 1. Th
2、is Network Management (NM) militpry hpndbodr is approved for use by di -ts and Agencies of theU.S. Departmwt of Defense (DOD). 2. Beneficial comments (recommendation, additions, deletioas) and any pertineat data which may be of use in improving this documeat should be addred to: Director, Defeame St
3、pndnidizptt * onprogrpmoffice SPO), 5203 kbwg Pike, Suite 1402, Falls Church, VA 22041-3466, by using the self- nddrtssed Stanmon Document hpmvement Proposai D Form 1426) rppePring at the end of this document or by letter. 3. This document is a product of collective efforts of the MILDEPs through th
4、e DoD Daia Communications Protocol Siandards (DCPS) Techaicp1 Managemeat Panel (DTMP) NM Working Group (WG 4) and the National Institute of Standards and Technology 0. ii Licensed by Information Handling ServicesNIL-HDBK-1351 m 9999970 0397286 LOT m MIL-HDBK-135 I 23 Jul93 c0”Ts PAGE PARAGRAPH 1 . S
5、COPE . 1 1.1 scope . 1 1.2 purpose . 1 1.4 Limitations . 2 1.5 ReationsipbtheGNMP 3 1.7 Relotionship to the OMNIPoints 3 1.10 Appendices . 5 1.3 Applicability 2 1.6 3 1.8 4 1.9 SourcesofSpecificati01.1 . 4 1.9.1 Transiti.cOnmderationS . 5 Relationship to the Government 0pa1 Systems IntefCannecGon Fm
6、file (GOSIP) . Relationship to the Simple Network Management Protocol (SNMP) . 2 . APPLICABLE DOCUMENTS 7 2.1 Government documents 7 2.1.1 Specifications. standards. andhandbooks . 7 2.1.1.1 Specifications 7 2.1.1.2 Federal Government and DoD standnrs . 7 2.1.2 other government documents. drawings.
7、and publications . 7 2.1.2.1 Nationai institute of St.ndprds rnd Technology (NIS) 7 2.1.2.2 Defense Infonrrption System Agency (DISA) . 8 2.1.2.3 North Ahtic Treaty 0rk”Pfiaa (NATO) . 8 2.1.2.4 U.S. ArmyInfonuntionSystemsCommnnd(USAISC) . 8 2.2 Nm-gov-t publid= 9 2.2.1 International Organization for
8、 Staneon/intonal Electrotechnid Committee (ISOAEC). International Telegraph and Telephone Consultative Committee (Cm and Mtue of Electrical and ElectronicS Engineers PEE) pubtidons . 9 2.2.2 internet Engineering Task Force publications 11 Industry8tpadards ; 12 2.2.5 osInetpubliatio 12 2.2.3 2.2.4 R
9、egional Workshop coordiripting Commiee (RWS-CC) Technical Reports (TRs) 12 2.3 Orderofpreoedena 12 . 3 . DEFINITIONS 13 3.1 Acmnyms 13 3.2 3.2.1 Definitions andlor expiauntory information 15 Absract Syntax Noation One (ASN.l) 16 3.2.2 AccoUnting management (AM) . 16 3.2.3 AssaciOtion Control Service
10、 Element (ACSE) 16 Cognizant Technical officicil . 16 protocoI (CMS/CMIP) 16 3.2.4 Ab 16 3.2.5 3.2.6 Common mumgemeat idonnation Services and common management information iii Licensed by Information Handling Services3.2.7 3.2.8 3.2.9 3.2.10 3.2.11 3.2.12 3.2.13 3.2.14 3.2.15 3.2.16 3.2.17 3.2.18 3.
11、2.19 3.2.20 3.2.21 3.2.22 3.2.23 3.2.24 3.2.25 3.2.26 3.2.27 3.2.28 3.2.29 3.2.30 3.2.31 3.2.32 3.2.33 3.2.34 3.2.35 MIL-HDBK-1351 23 Jul93 configurptiOnmanigemnt(CM) 16 Element manager system . 17 Event . 17 Humanmgincering 17 Manigsddject . 18 Managcdsysem 18 Managemeatgateways 18 Managemnt inform
12、iton be (MIB) . 18 Mauagersysem 18 Network . 19 Networkadministrator 19 Networkmanagement(“) . 19 19 Networkmaneger . 19 N-layermanager 19 Directory b. to provide guidance for the procurement of interoperable NM products and services for DoD communications systems; c. to direct that Open Systems Int
13、erconnection (OSI)-based management, as represented in the GNMP, is DoDs strategic management solution; d. to indicate that a number of relevant e. to assist in the procurement of standards-based, conformant, commercial off-theshelf (COTS) NM products and services whenever possible in order to avoid
14、 excessive development time and life cycle costs typically associated with proprietary NM products and services; 1 Licensed by Information Handling ServicesMIL-HDBK-1351 23 Jul93 f. to stress DoDs near-term commitment to begin procuring NM produds and services that, at a minimum, conform to GNMP for
15、 basic interoperability among distributed, heterogeneous NM produds and services; g. to identifj high-level requirements crn areas that go beyond the scope of GNMP) hat must be considered by CTs and, as needed, should be translated by specific ms into aquisition-specific, testable requirements; and
16、h. to alert DoD personnel involved with networks, systems and networking that management functions, capabilities and activities associated with such resources should be considered throughout the life cycle of such resources, from early planning stages, throughout daily opedon and growth, to the end
17、of retirement. 1.3 ADD licability. This MIL-HDBK augments the GNMP with DoD-specific requirements. In particular, this h4J.L-HDBK provides guidance for: a. the acquisition of analog and digital networks, communication resources and/or communication services; and b. the acquisition of accompanying ma
18、nagement systems and/or management system components, capabilities or services for such networks, resoutces and services. This MIL-HDBK provides for multiple vendor networWwmmunications capabilities acquired by one procurement to be manageable by other vendors manager systems acquired by another pro
19、airement. The application of this MIL-HDBK to the acquisition of other new systems, such as end systems (e.g., computers) that use network and/or communications products/services, or to the retrofitting of, or interfaces to, existing systems is to be determined on a case-by-case basis by the CO. The
20、 development of standards-based Voice Oriented Telecommunications Network Management Systems (VOT NMSs) is just beginning. Consequently, this MIL-HDBK acknowledges that VOT NMS products that conform to this MIL-HDBK may not be available. As this MIL-HDBK evolves, it will be expanded to cover product
21、s and services of the VOT NMS as they mature. 1.4 -W. By using this MIL-HDBK throughout the DoD, it will be possible to have multiple vendor networWmmmunications capabilities acquired by one procurement be manageable by other vendors manager systems acquired by another procurement. However, it shoul
22、d be noted that not ail aspects of interoperability pertinent to NM have reached the level of maturity and preciseness as those aspects specified in the GNMP. In those areas for which implementation profiles such as those specified in the GNMP do not yet exist, full interoperability across NM elemen
23、ts proaired under different acquisition is at risk. This is especially me for acquisitions based on those references lower in the order of alternative sources of specifications in section 1.9 of this MIL-HDBK. SNMP-based COTS solutions will be much more widely available than CMIS-CMIP solutions and
24、can be used to fulfill requirements that are not yet met by rigorous, stable, industry-accepted implementation profiles. However careful consideration must be given to provide the best present 2 Licensed by Information Handling Services NIL-HDBK-1351 rn 7799970 0399298 921 m MIL-HDBK- 135 1 23 Jul93
25、 solution while at the same time providing a migration path to a fully interoperable open NM system, See section 1.9.1. 1.5 peiationshiD to the G NMP. TIie GNMP, the Federal Information Procasing Standard (FPS 179) for NM, is the standard for all Federal Governmeat agencies to use when acquiring NM
26、products, functions and services for computer and communications systems and networks. The GNMP provides implementation specifications for the Common Management Infodon Services and Proml (CMiS/CMP), specific management functions and services, and the syntax and semantics of the management informati
27、on required to support monitoring and control of logical and physical resources associated with network anci system components. This MIL-HDBK will build upon the GNMP by describing common military architectures and requirements, and manageable computer and communications resources. To address curren
28、t, basic, OShriented, NM interoperability requirements, implementors should consult this MIL-HDBK. In addition, if the DoD identifies general NM interoperability requirements which are not addressed in the GNMP, efforts shall be made to include them in future editions of the GNMP. Additionai managem
29、ent capabilities and managed objects will be included in subsequent releases of the GNMP. To address other requirements, implementors should consult the other sources of specifications identified in Section 1.9. 1.6 Relationshiu to the Go vernment Chen Svstems Inte rconnection Profile GOS E). The GO
30、SIP (FIPS Pub 146-1) defines a common set of data communication protocols that enable systems developed by different vendors to interoperate enabling users of different applications on those systems to exchange information. The GOSIP ais0 specifies services, such as File Transfer, Access and Managem
31、ent TAM), Message Handling Systems (MHS), and Virtuai Terminai 0, that can be used to support NM applications. In accordance with the GNMP, NM systems products and services should meet applicable requirements of the FIPS Pub 146-1. It is expected that future versions of this MIL-HDBK will use other
32、future GOSIP application services, such as Remote Database Access (RDA), Electronic Data Interchange (EDI), and Transaction Processing m), to support future NM applications. It should be noted that it is expected that future versions of the GOSIP FIPS will reference specifications in a new, more-enc
33、ompassing initiative called IGOSS (industry/Govemment Open Systems Specifications). IGOSS, under joint development by the Electric Power industry, the Manufacturing Automation Protocol and Technical Office Protocol (MAPROP) initiatives, and NIST, is scheduled for promulgation in early 1994. 1.7 Rela
34、tionshb to the 0 MWoint. OMNIpoint specifications are profiles of specifications that foster common management functionality and portability, as weil as interoperabidity among heterogeneous management components. OMNLPoints are dened in the Open Management Roadmap, an international partnership of go
35、vernment, industry, vendors, and users. OMWoint 1, a set of intercept points for standards and implementations, is summarized in Appendix D. The Open Management Roadmap, initiated and managed by the Network Management Forum (NMF), is an endeavor to coordinate all the related activities needed to dev
36、elop 3 Licensed by Information Handling Services MIL-HDBK-IIL 9999970 0197299 BbB MIL-HDBK-135 1 23 Jul93 comprehensive, open, turn-key enterprise management solutions. These adivities include developing standards, defining implementation specifications, and defining and conducthg intemperability an
37、d mnformance tests for the many technical aspects of turn-key, enterprise management solutions. These specifications and testing services are bundled into OMNIPoUUs, which are released bi-annually. Such OMNIPoints allow vendors and users to build and to buy distributed, portable, evolvable and inter
38、operable NM products and services, as well as general purpose management platforms, such as those that employ the Distributed Management Environment ME) technology of the Open Software Fouadaion (OSF). Such platforms can host other OMNIPoUir produds and SeMces, such as NM applications software. me G
39、NMP is an integral part of the first OMNIPoUU specification. 1.8 Pelatons i hiotothes im D le Network Mement Protocol SNMP). SNMP is a part of the first OMNIPoUU. It is the current industry de fimo standard for managing a growing set of resources primarily within TCP/IP-based nworks, e.g., routers,
40、as well as a growing set of resources that are interconnected by such networks and the multiple vendor pool of protocol analyzers used to assist NM personnel. SNMP currently plays a major role in the management of military and civilian communications resources. SNMP and SMNP v2 are standards develop
41、ed by the Internet Engineering Task Force (iETF), an organization of vendors/users who implement the JhD TCPm protocol suite. Activities of the IETF are overseen by the internet Advisory Board (IAB) and its parent organization, the internet Society SOC). Each internet standard is documented in a num
42、bered Request for Comment (RFC); for example, SNMP is documented in RFC 1157. Although the intent of this MIL-HDBK is to support the acquisition of NM products and services that conform to OS1 NM standards, it does not preclude the acquisition of specific COTS products and services that are based on
43、 use of industry standards such as SNMP and its potential successors, e.g., the Simple Network Management Protocol v2 (SNMP v2), in situations where OS1 network management products have not yet been developed. SNMP is expected to have utility and be cost-effective for the management of certain wn-OS
44、I resources for the foreseeable future. 1.9 sources o f SDecifications. When CTOs intend to procure NM products and services that incorporate management functions, services, protocols and information that are equivalent to that specified in the GNMP, the GNMP must be used as the source of implementa
45、tion specifications for such procurement. The GNMP does not address all the requirements in this MIL-HDBK. When LTos intend to procure NM products and services that meet those requirements in this MIL-HDBK that are not addressed by the GNMP, then the CTOs (1) should use the other sources of specific
46、ations identified below, and (2) should use them in the order specified below: a. if the specific requirements are addressed by other OMNIPoint 1 specifications, then tiye OMNIPoinr 1 specifications should be used; otherwise, 4 Licensed by Information Handling ServicesMIL-HDBK-1351 I 0 0397300 30T I
47、 MIL-HDBK-1351 23 Jul93 b. if the specific requirements are addressed by current versions of the Open Systems Environment (OSE) Working implementation Agreements, then these Agreements should be used; otherwise, c. if the specific requirements are addressed by current preliminary versions of nationa
48、l/intemationai standards, then these standards should be used; otherwise, d. if the specific requirements are addrd by documents developed by specific consortia, then these documents should be used. 1.9.1 Transition Considerau om. The CO should ensure that future NM systems comply with the GNMP and/
49、or OMNIPoints whenever possible. Throughout the initial period of the application of this handbook, many existing SNMP-based and legacy systems will sul exist. They should not be replaced as long as they are operationally and economically viable. Integrating future NM systems with them should be carefully evaluated to prevent costly software upgrades to proprietary systems. A transition plan should be developed to daennine how these existing systems will be integrated, upgraded, or phased out. Transition to a fully interoperable, ope
