ITU-T G.874.1
(Pre-Published) Optical transport network (OTN): Protocol-neutral management information model for the network element view
Year: 2012
Abstract: This Recommendation provides a management-protocol-neutral information model for managing network elements in the optical transport network (OTN) [1]-[3]. It identifies the telecommunications management network (TMN) managed entities required for the management of OTN network elements. These entities are relevant to information exchanged across standardized interfaces defined in the M.3010 TMN architecture [6]. The management-protocol-neutral information model should be used as the base for defining management-protocol-specific information models, for examples, XML (Web Service or Netconf/Yang) information model, CORBA IDL model, and SNMP MIB.
The specific mapping of the management-protocol-neutral entities into management-protocolspecific managed object classes is the decision of the management-protocol-specific solution design. For example, an object class defined in this Recommendation may be mapped into multiple tables in a SNMP MIB. On the other hand, all the monitoring entities may be mapped into a single class in a protocol-specific model. Protocol-specific solution and their mapping from the protocolneutral model will be described in other Recommendations and is outside the scope of this Recommendation.
This Recommendation applies to OTN network elements and those systems in the TMN that manage OTN network elements. Functional capabilities of OTN equipment are defined in ITU-T Rec. G.798 [3], and requirements of the management of OTN equipment are provided in ITU-T Recs. G.7710/Y.1701 [4] and G.874 [5]. The information model specified in this Recommendation applies to the EMS-NE interface, as shown in Figure 1-1, specifically for managing the OTN functional capabilities of the NE.
The specific mapping of the management-protocol-neutral entities into management-protocolspecific managed object classes is the decision of the management-protocol-specific solution design. For example, an object class defined in this Recommendation may be mapped into multiple tables in a SNMP MIB. On the other hand, all the monitoring entities may be mapped into a single class in a protocol-specific model. Protocol-specific solution and their mapping from the protocolneutral model will be described in other Recommendations and is outside the scope of this Recommendation.
This Recommendation applies to OTN network elements and those systems in the TMN that manage OTN network elements. Functional capabilities of OTN equipment are defined in ITU-T Rec. G.798 [3], and requirements of the management of OTN equipment are provided in ITU-T Recs. G.7710/Y.1701 [4] and G.874 [5]. The information model specified in this Recommendation applies to the EMS-NE interface, as shown in Figure 1-1, specifically for managing the OTN functional capabilities of the NE.
Show full item record
| contributor author | ITU-T - International Telecommunication Union/ITU Telcommunication Sector | |
| date accessioned | 2017-09-04T18:43:17Z | |
| date available | 2017-09-04T18:43:17Z | |
| date copyright | 2012.10.01 | |
| date issued | 2012 | |
| identifier other | KBQRBFAAAAAAAAAA.pdf | |
| identifier uri | http://yse.yabesh.ir/std;query=autho4703659/handle/yse/224733 | |
| description abstract | This Recommendation provides a management-protocol-neutral information model for managing network elements in the optical transport network (OTN) [1]-[3]. It identifies the telecommunications management network (TMN) managed entities required for the management of OTN network elements. These entities are relevant to information exchanged across standardized interfaces defined in the M.3010 TMN architecture [6]. The management-protocol-neutral information model should be used as the base for defining management-protocol-specific information models, for examples, XML (Web Service or Netconf/Yang) information model, CORBA IDL model, and SNMP MIB. The specific mapping of the management-protocol-neutral entities into management-protocolspecific managed object classes is the decision of the management-protocol-specific solution design. For example, an object class defined in this Recommendation may be mapped into multiple tables in a SNMP MIB. On the other hand, all the monitoring entities may be mapped into a single class in a protocol-specific model. Protocol-specific solution and their mapping from the protocolneutral model will be described in other Recommendations and is outside the scope of this Recommendation. This Recommendation applies to OTN network elements and those systems in the TMN that manage OTN network elements. Functional capabilities of OTN equipment are defined in ITU-T Rec. G.798 [3], and requirements of the management of OTN equipment are provided in ITU-T Recs. G.7710/Y.1701 [4] and G.874 [5]. The information model specified in this Recommendation applies to the EMS-NE interface, as shown in Figure 1-1, specifically for managing the OTN functional capabilities of the NE. | |
| language | English | |
| title | ITU-T G.874.1 | num |
| title | (Pre-Published) Optical transport network (OTN): Protocol-neutral management information model for the network element view | en |
| type | standard | |
| page | 251 | |
| status | Active | |
| tree | ITU-T - International Telecommunication Union/ITU Telcommunication Sector:;2012 | |
| contenttype | fulltext |

درباره ما