+++ /dev/null
-module mef-topology {\r
- namespace "http://metroethernetforum.org/ns/yang/mef-topology";\r
- prefix mef-topology;\r
- import mef-types {\r
- prefix mef-types;\r
- revision-date 2015-05-26;\r
- }\r
- organization "Metro Ethernet Forum";\r
- contact\r
- "Web URL: http://metroethernetforum.org/ \\ E-mail: mibs@metroethernetforum.org\r
- \\ Postal: Metro Ethernet Forum \\ 6033 W. Century Boulevard,\r
- Suite 1107 \\ Los Angeles, CA 90045 \\ U.S.A. \\ Phone: +1 310-642-2800\r
- \\ Fax: +1 310-642-2808";\r
- description\r
- "This module models the NMS level view of the network devices,\r
- their physical interfaces, and the network topology. When the\r
- NMS discovers a network device,it is to pull the device configuration\r
- and operational status as expected for an NMS. Once the NMS has\r
- a network device's configuration, it creates the /mef-topology/devices/device{}\r
- entry and populates the list of physical interfaces. The Peers\r
- entries are populated as configuration to reflect physical cabling\r
- interconnections.Hints could be detected from LLDP Neighbor information[802.1AB].\r
- Reference Overview: A number of base documents have been used\r
- to create the MEF Topology YANG Module. The following are the\r
- abbreviations for the baseline documents: [RFC 6991] refers to\r
- IETF RFC 6991 'Common YANG Data Types', 2013-07-15 [RFC 6643]\r
- refers to IETF RFC 6643 'Translation of Structure of Management\r
- Information Version 2 (SMIv2) MIB Modules to YANG Modules', 2011-11-25\r
- [802.1AB] refers to 'Station and Media Access Control Connectivity\r
- Discovery', IEEE 802.1AB-2009, September 2009 [802.1q] refers\r
- to IEEE 802.1Q-2011 'IEEE Standard for Local and metropolitan\r
- area networks --Media Access Control (MAC) Bridges and Virtual\r
- Bridged Local Area Networks, August 2011 [802-2001] refers to\r
- 'IEEE Standard for Local and Metropolitan Area Networks: Overview\r
- and Architecture', IEEE 802-2001, February 2002 [MEF10.3] refers\r
- to MEF 10.3 'Ethernet Services Attributes Phase 3', October 2013\r
- [MEF6.2] refers to MEF 6.2 'EVC Ethernet Services Defintions Phase\r
- 3', August 2014 [MEF40] refers to MEF 40 'UNI and EVC Definition\r
- of Managed Objects', April 2013 [MEF45] refers to MEF 45 'Multi-CEN\r
- L2CP', August 2014 [MEF7.2] refers to MEF 7.2 'Carrier Ethernet\r
- Management Information Model', April 2013 [MEF7.3] refers to MEF\r
- 7.3 'Carrier Ethernet Management Information Model', Working Draft\r
- #1 2015 [RFC 2737] refers to IETF RFC 2737 'Entity MIB (Version\r
- 2)', December 1999 [RFC 2863] refers to IETF RFC 2863 'The Interfaces\r
- Group MIB', June 2000 [RFC 3419] refers to IETF RFC 3419 'Textual\r
- Conventions for Transport Addresses', December 2002 [Y.1731] refers\r
- to ITU-T Y.1731 'OAM functions and mechanisms for Ethernet based\r
- networks', July 2011 [Q.840.1] refers to ITU-T Q.840.1 'Requirements\r
- and analysis for NMS-EMS management interface of Ethernet over\r
- Transport and Metro Ethernet Network(EoT/MEN)' March 2007";\r
- revision 2015-05-26 {\r
- description\r
- "Formal Project Review Draft 1.";\r
- reference "EVC Ethernet Services Definitions YANG Modules " +\r
- "(MEF XX), TBD";\r
- }\r
-\r
- container mef-topology {\r
- description\r
- "MEF Topology";\r
- container devices {\r
- description\r
- "Network Devices in the CEN.";\r
- list device {\r
- key "dev-id";\r
- description\r
- "Network Device List.";\r
- container interfaces {\r
- description\r
- "Physical Ports/Interfaces associated with this " +\r
- "Network Device.";\r
- list interface {\r
- key "phy";\r
- description\r
- "External Interface for the Network Device.";\r
- leaf phy {\r
- type mef-types:identifier45;\r
- description\r
- "The Phy Name for the Physical Port.";\r
- }\r
- leaf ieee8023-phy {\r
- type identityref {\r
- base mef-types:ieee-8023-interface-type;\r
- }\r
- description\r
- "The Physical Layer for each physical link " +\r
- "implementing the UNI MUST be one of the PHYs " +\r
- "listed in IEEE Std 802.3–2012 but excluding " +\r
- "1000BASE-PX-D and 1000BASE-PX-U.";\r
- reference "[MEF10.3] Section 9.2 [R60].";\r
- }\r
- }\r
- }\r
- leaf role {\r
- type mef-types:device-role;\r
- default "ce";\r
- description\r
- "The role of this device in the network.";\r
- }\r
- leaf dev-id {\r
- type mef-types:identifier45;\r
- description\r
- "Device Identifier.";\r
- }\r
- leaf device-name {\r
- type string;\r
- }\r
- }\r
- }\r
- container connections {\r
- description\r
- "Physical Network Connections";\r
- list connection {\r
- key "name";\r
- leaf name {\r
- type mef-types:identifier45;\r
- }\r
- container endpoint-1 {\r
- description\r
- "End Point 1";\r
- leaf device {\r
- type leafref {\r
- path "../../../../devices/device/dev-id";\r
- }\r
- description\r
- "Hostname or IP Address for the End Point's Device.";\r
- }\r
- leaf interface {\r
- type leafref {\r
- path "../../../../devices/device[dev-id = current()/../device]/interfaces/interface/phy";\r
- }\r
- description\r
- "The Phy Name for the End Point's Physical Port.";\r
- }\r
- }\r
- container endpoint-2 {\r
- description\r
- "End Point 2";\r
- leaf device {\r
- type leafref {\r
- path "../../../../devices/device/dev-id";\r
- }\r
- description\r
- "Hostname or IP Address for the End Point's Device.";\r
- }\r
- leaf interface {\r
- type leafref {\r
- path "../../../../devices/device[dev-id = current()/../device]/interfaces/interface/phy";\r
- }\r
- description\r
- "The Phy Name for the End Point's Physical Port.";\r
- }\r
- }\r
- }\r
- }\r
- }\r
-}\r
Code Review / unimgr.git / blobdiff