• Generated on 29/04/2025 by the YANG Catalog. Fujitsu https://github.com/FujitsuNetworkCommunications/FSS2-Yang/tree/master/FSS2-API-Yang/T600/1.1/yang

YANG Model	Compilation	Compilation Results (pyang --lint). 2.6.1	Compilation Results (pyang). Note: also generates errors for imported files. 2.6.1	Compilation Results (confdc). Note: also generates errors for imported files. confd-8.0	Compilation Results (yangdump-pro). Note: also generates errors for imported files. yangdump-sdk 21.10-12	Compilation Results (yanglint -i). Note: also generates errors for imported files. yanglint 2.1.111
dhcp-client-dev@2015-09-11.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" dhcp-client-dev@2015-09-11.yang --lint 2>&1": dhcp-client-dev@2015-09-11.yang:28: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement		Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/dhcp-client-dev@2015-09-11.yang 2>&1": Error: 'dhcp-client-dev@2015-09-11.yang' import of module 'dhcp-client' failed dhcp-client-dev@2015-09-11.yang:5.5: error(236): module not found Error: object 'clientv4' not found in module dhcp-client-dev in Xpath target /dhcp:clientv4/dhcp:client-if dhcp-client-dev@2015-09-11.yang:42.2: error(250): definition not found Error: object 'serverv4' not found in module dhcp-client-dev in Xpath target /dhcp:serverv4 dhcp-client-dev@2015-09-11.yang:42.2: error(250): definition not found Error: object 'relayv4' not found in module dhcp-client-dev in Xpath target /dhcp:relayv4 dhcp-client-dev@2015-09-11.yang:42.2: error(250): definition not found
dhcp-client@2014-12-18.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" dhcp-client.yang --lint 2>&1": dhcp-client.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement dhcp-client.yang:1: error: RFC 8407: 4.8: statement "module" must have a "organization" substatement dhcp-client.yang:12: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement dhcp-client.yang:14: error: RFC 8407: 4.14: statement "container" must have a "description" substatement dhcp-client.yang:15: error: RFC 8407: 4.14: statement "container" must have a "description" substatement dhcp-client.yang:16: error: RFC 8407: 4.14: statement "list" must have a "description" substatement dhcp-client.yang:20: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:21: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:22: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:26: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:27: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:28: error: keyword "default" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:29: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:33: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:34: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:35: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:39: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:40: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:41: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:45: error: RFC 8407: 4.14: statement "container" must have a "description" substatement dhcp-client.yang:52: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:53: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:54: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:58: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:59: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:60: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:64: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:65: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:66: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:70: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:71: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:72: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:74: error: RFC 8407: 4.14: statement "container" must have a "description" substatement dhcp-client.yang:78: error: keyword "key" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:79: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client.yang:82: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client.yang:86: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client.yang:90: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client.yang:94: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client.yang:98: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client.yang:102: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client.yang:106: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client.yang:110: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client.yang:114: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client.yang:118: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client.yang:122: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client.yang:126: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client.yang:130: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client.yang:134: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client.yang:142: error: RFC 8407: 4.14: statement "container" must have a "description" substatement dhcp-client.yang:143: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client.yang:147: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client.yang:151: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client.yang:155: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client.yang:159: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client.yang:163: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client.yang:167: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client.yang:171: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client.yang:175: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client.yang:179: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client.yang:183: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client.yang:187: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client.yang:191: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client.yang:195: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client.yang:199: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client.yang:203: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client.yang:207: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement dhcp-client.yang:213: error: RFC 8407: 4.14: statement "container" must have a "description" substatement dhcp-client.yang:214: error: RFC 8407: 4.14: statement "container" must have a "description" substatement dhcp-client.yang:217: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:218: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:221: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:222: error: keyword "default" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:226: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:227: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:230: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:231: error: keyword "default" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:234: error: RFC 8407: 4.14: statement "container" must have a "description" substatement dhcp-client.yang:235: error: RFC 8407: 4.14: statement "list" must have a "description" substatement dhcp-client.yang:239: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:240: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:243: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:247: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:248: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:251: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:253: error: RFC 8407: 4.14: statement "container" must have a "description" substatement dhcp-client.yang:256: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:257: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:258: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:262: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:263: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:264: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:267: error: RFC 8407: 4.14: statement "container" must have a "description" substatement dhcp-client.yang:268: error: RFC 8407: 4.14: statement "list" must have a "description" substatement dhcp-client.yang:272: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:273: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:276: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:280: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:281: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:282: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:283: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:287: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:288: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:289: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:290: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:292: error: RFC 8407: 4.14: statement "container" must have a "description" substatement dhcp-client.yang:295: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:296: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:297: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:301: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:302: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:303: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:307: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:308: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:309: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:313: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:314: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:315: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:325: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:326: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:329: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:330: error: keyword "default" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:334: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:335: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:338: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:339: error: keyword "default" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:343: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:344: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:347: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:348: error: keyword "default" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:353: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:354: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:355: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:359: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:360: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:363: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:367: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:368: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:369: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:373: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:374: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:388: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:390: error: RFC 8407: 4.14: statement "container" must have a "description" substatement dhcp-client.yang:394: error: keyword "key" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:397: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:398: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:401: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:405: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:406: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:407: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:411: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:412: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:415: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:419: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:420: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:423: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:427: error: RFC 8407: 4.14: statement "container" must have a "description" substatement dhcp-client.yang:430: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:431: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:432: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:436: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:437: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:438: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:442: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:443: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:444: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:448: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:449: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:450: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:455: error: RFC 8407: 4.14: statement "container" must have a "description" substatement dhcp-client.yang:458: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:459: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:460: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:464: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:465: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:466: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:470: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:471: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:472: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:476: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:477: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:478: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:482: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:483: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:484: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:488: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:489: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:490: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:494: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:495: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:496: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:500: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:501: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:502: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:506: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:507: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:508: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:512: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:513: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:514: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:521: error: RFC 8407: 4.14: statement "list" must have a "description" substatement dhcp-client.yang:525: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:526: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:527: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:531: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:532: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:533: error: keyword "default" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:534: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:541: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:542: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:549: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:553: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:554: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:555: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:559: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:560: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:561: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:569: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:570: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:571: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:575: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:576: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:577: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:581: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:582: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:583: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:587: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:588: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:589: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:593: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:594: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:595: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:599: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:600: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:601: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:605: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:606: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:607: error: keyword "config" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:611: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) dhcp-client.yang:612: error: keyword "type" not in canonical order (see RFC 6020, Section 12) dhcp-client.yang:613: error: keyword "config" not in canonical order (see RFC 6020, Section 12)
dhcpv6-client-dev@2016-03-10.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" dhcpv6-client-dev@2016-03-10.yang --lint 2>&1": dhcpv6-client-dev@2016-03-10.yang:27: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement		Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/dhcpv6-client-dev@2016-03-10.yang 2>&1": Error: 'dhcpv6-client-dev@2016-03-10.yang' import of module 'dhcpv6-client' failed dhcpv6-client-dev@2016-03-10.yang:5.3: error(236): module not found Error: object 'serverv6' not found in module dhcpv6-client-dev in Xpath target /dhcpv6:serverv6 dhcpv6-client-dev@2016-03-10.yang:43.2: error(250): definition not found Error: object 'relayv6' not found in module dhcpv6-client-dev in Xpath target /dhcpv6:relayv6 dhcpv6-client-dev@2016-03-10.yang:43.2: error(250): definition not found Error: object 'clientv6' not found in module dhcpv6-client-dev in Xpath target /dhcpv6:clientv6/dhcpv6:client-if dhcpv6-client-dev@2016-03-10.yang:43.2: error(250): definition not found
dhcpv6-client@2015-10-16.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" dhcpv6-client.yang --lint 2>&1": dhcpv6-client.yang:136: error: RFC 8407: 4.10: top-level node serverv6 must not be mandatory dhcpv6-client.yang:1677: error: RFC 8407: 4.10: top-level node relayv6 must not be mandatory		Warning: top-level NP container 'serverv6' is mandatory dhcpv6-client.yang:136.3: warning(1048): top-level object is mandatory Warning: top-level NP container 'relayv6' is mandatory dhcpv6-client.yang:1677.3: warning(1048): top-level object is mandatory
fujitsu-access-control-list@2018-06-26.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-access-control-list.yang 2>&1": fujitsu-access-control-list.yang:9: error: module 'ietf-access-control-list' not found fujitsu-access-control-list.yang:15: error: module 'iana-if-type' not found fujitsu-access-control-list.yang:66: error: the node 'access-lists' from module 'ietf-access-control-list' is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-protocols.yang:28: warning: the revision statements are not given in reverse chronological order	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-access-control-list.yang 2>&1": fujitsu-access-control-list.yang:12: warning: imported module "ietf-yang-types" not used fujitsu-access-control-list.yang:66: error: "ietf-access-control-list:access-lists" in the path for acl-name at fujitsu-access-control-list.yang:62 is not found fujitsu-access-control-list.yang:148: error: node ietf-access-control-list::access-lists is not found fujitsu-access-control-list.yang:150: warning: node "ietf-access-control-list::protocol" is not found in "fujitsu-access-control-list::/acl:access-lists/acl:acl/acl:access-list-entries/acl:ace/acl:matches/acl:ace-type/acl:ace-ip" fujitsu-access-control-list.yang:156: warning: node "ietf-access-control-list::protocol" is not found in "fujitsu-access-control-list::/acl:access-lists/acl:acl/acl:access-list-entries/acl:ace/acl:matches/acl:ace-type/acl:ace-ip" fujitsu-access-control-list.yang:162: warning: node "ietf-access-control-list::protocol" is not found in "fujitsu-access-control-list::/acl:access-lists/acl:acl/acl:access-list-entries/acl:ace/acl:matches/acl:ace-type/acl:ace-ip" fujitsu-access-control-list.yang:168: error: node ietf-access-control-list::access-lists is not found fujitsu-protocols.yang:28: warning: the revision statements are not given in reverse chronological order	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-access-control-list.yang --lint 2>&1": fujitsu-access-control-list.yang:12: warning: imported module "ietf-yang-types" not used fujitsu-access-control-list.yang:43: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-access-control-list.yang:47: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-access-control-list.yang:52: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-access-control-list.yang:57: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-access-control-list.yang:64: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-access-control-list.yang:65: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-access-control-list.yang:148: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-access-control-list.yang:148: error: node ietf-access-control-list::access-lists is not found fujitsu-access-control-list.yang:150: warning: node "ietf-access-control-list::protocol" is not found in "fujitsu-access-control-list::/acl:access-lists/acl:acl/acl:access-list-entries/acl:ace/acl:matches/acl:ace-type/acl:ace-ip" fujitsu-access-control-list.yang:156: warning: node "ietf-access-control-list::protocol" is not found in "fujitsu-access-control-list::/acl:access-lists/acl:acl/acl:access-list-entries/acl:ace/acl:matches/acl:ace-type/acl:ace-ip" fujitsu-access-control-list.yang:162: warning: node "ietf-access-control-list::protocol" is not found in "fujitsu-access-control-list::/acl:access-lists/acl:acl/acl:access-list-entries/acl:ace/acl:matches/acl:ace-type/acl:ace-ip" fujitsu-access-control-list.yang:168: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-access-control-list.yang:168: error: node ietf-access-control-list::access-lists is not found		Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-access-control-list.yang 2>&1": Error: 'fujitsu-access-control-list.yang' import of module 'ietf-access-control-list' failed fujitsu-access-control-list.yang:9.3: error(236): module not found Warning: revision dates not in descending order fujitsu-protocols.yang:28.3: warning(1035): bad revision-stmt order Error: Module for prefix 'acl' not found fujitsu-access-control-list.yang:150.15: error(236): module not found Error: Module for prefix 'acl' not found fujitsu-access-control-list.yang:156.15: error(236): module not found Error: Module for prefix 'acl' not found fujitsu-access-control-list.yang:162.15: error(236): module not found Error: object 'access-lists' not found in module fujitsu-access-control-list in Xpath target /acl:access-lists fujitsu-access-control-list.yang:168.3: error(250): definition not found Error: object 'access-lists' not found in module fujitsu-access-control-list in Xpath target /acl:access-lists/acl:acl/acl:access-list-entries/acl:ace/acl:matches/acl:ace-type/acl:ace-ip fujitsu-access-control-list.yang:148.3: error(250): definition not found Error: path failed (module not found): '/acl:access-lists/acl:acl/acl:acl-name' Error: Module for prefix 'acl' not found fujitsu-access-control-list.yang:66.17: error(236): module not found Warning: Module 'ietf-yang-types' not used fujitsu-access-control-list.yang:12.3: warning(1015): import not used
fujitsu-ains-keywords@2018-05-17.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-ains-keywords.yang --lint 2>&1": fujitsu-ains-keywords.yang:22: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ains-keywords.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ains-keywords.yang:58: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-ains-keywords.yang:59: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-ains-keywords.yang:61: warning: RFC 8407: 4.4: statement "mandatory" is given with its default value "false" fujitsu-ains-keywords.yang:62: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-ains-keywords.yang:64: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-ains-keywords.yang:68: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
fujitsu-alarm-types@2018-08-02.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-alarm-types.yang 2>&1": fujitsu-alarm-types.yang:5: error: module 'ietf-alarms' not found fujitsu-alarm-types.yang:159: warning: the revision statements are not given in reverse chronological order fujitsu-alarm-types.yang:163: warning: the revision statements are not given in reverse chronological order fujitsu-alarm-types.yang:167: warning: the revision statements are not given in reverse chronological order	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-alarm-types.yang 2>&1": fujitsu-alarm-types.yang:159: warning: the revision statements are not given in reverse chronological order fujitsu-alarm-types.yang:163: warning: the revision statements are not given in reverse chronological order fujitsu-alarm-types.yang:167: warning: the revision statements are not given in reverse chronological order fujitsu-alarm-types.yang:173: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:177: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:181: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:185: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:189: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:193: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:197: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:201: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:205: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:209: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:213: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:217: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:221: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:225: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:229: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:233: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:237: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:241: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:245: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:249: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:253: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:257: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:261: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:265: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:269: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:273: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:277: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:281: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:285: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:289: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:293: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:297: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:301: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:305: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:309: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:313: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:317: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:321: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:325: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:329: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:333: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:337: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:341: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:345: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:349: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:353: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:357: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:361: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:365: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:369: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:373: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:377: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:381: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:385: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:389: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:393: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:397: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:401: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:405: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:409: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:413: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:417: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:421: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:425: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:429: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:433: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:437: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:441: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:445: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:449: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:453: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:457: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:461: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:465: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:469: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:473: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:477: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:481: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:485: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:489: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:493: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:497: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:501: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:505: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:509: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:513: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:517: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:521: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:525: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:529: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:533: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:537: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:541: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:545: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:549: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:553: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:557: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:561: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:565: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:569: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:573: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:577: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:581: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:585: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:589: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:593: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:597: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:601: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:605: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:609: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:613: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:617: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:621: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:625: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:629: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:633: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:637: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:641: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:645: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:649: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:653: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:657: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:661: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:665: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:669: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:673: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:677: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:681: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:685: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:689: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:693: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:697: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:701: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:705: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:709: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:713: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:717: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:721: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:725: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:729: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:733: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:737: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:741: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:745: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:749: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:753: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:757: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:761: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:765: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:769: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:773: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:777: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:781: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:785: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:789: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:793: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:797: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:801: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:805: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:809: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:813: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:817: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:821: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:825: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:829: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:833: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:837: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:841: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:845: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:849: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:853: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:857: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:861: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:865: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:869: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:873: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:877: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:881: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:885: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:889: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:893: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:897: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:901: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:905: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:909: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:913: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:917: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:921: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:925: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:929: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:933: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:937: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:941: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:945: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:949: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:953: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:957: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:961: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:965: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:969: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:973: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:977: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:981: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:985: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:989: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:993: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:997: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1001: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1005: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1009: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1013: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1017: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1021: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1025: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1029: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1033: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1037: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1041: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1045: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1049: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1053: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1057: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1061: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1065: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1069: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1073: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1077: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1081: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1085: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1089: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1093: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1097: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1101: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1105: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1109: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1113: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1117: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1121: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1125: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1129: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1133: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1137: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1141: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1145: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1149: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1153: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1157: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1161: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1165: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1169: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1173: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1177: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1181: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1185: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1189: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1193: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1197: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1201: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1205: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1209: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1213: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1217: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1221: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1225: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1229: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1233: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1237: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1241: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1245: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1249: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1253: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1257: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1261: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1265: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1269: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1273: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1277: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1281: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1285: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1289: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1293: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1297: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1301: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1305: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1309: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1313: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1317: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1321: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1325: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1329: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1333: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1337: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1341: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1345: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1349: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1353: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1357: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1361: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1365: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1369: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1373: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1377: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1381: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1385: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1389: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1393: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1397: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1401: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1405: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1409: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1413: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1417: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1421: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1425: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1429: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1433: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1437: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1441: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1445: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1449: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1453: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1457: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1461: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1465: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1469: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1473: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1477: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1481: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1485: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1489: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1493: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1497: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1501: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1505: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1509: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1513: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1517: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1521: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1525: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1529: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1533: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1537: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1541: error: identity "alarm-identity" not found in module "ietf-alarms"	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-alarm-types.yang --lint 2>&1": fujitsu-alarm-types.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:34: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:42: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:46: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:50: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:54: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:58: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:62: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:66: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:70: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:74: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:78: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:82: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:86: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:90: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:94: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:98: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:102: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:106: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:110: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:114: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:119: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:125: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:129: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:134: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:139: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:143: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:147: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:151: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:155: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:159: warning: the revision statements are not given in reverse chronological order fujitsu-alarm-types.yang:159: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:163: warning: the revision statements are not given in reverse chronological order fujitsu-alarm-types.yang:163: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:167: warning: the revision statements are not given in reverse chronological order fujitsu-alarm-types.yang:167: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarm-types.yang:172: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:173: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:176: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:177: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:180: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:181: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:184: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:185: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:188: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:189: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:192: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:193: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:196: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:197: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:200: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:201: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:204: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:205: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:208: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:209: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:212: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:213: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:216: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:217: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:220: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:221: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:224: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:225: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:228: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:229: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:232: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:233: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:236: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:237: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:240: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:241: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:244: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:245: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:248: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:249: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:252: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:253: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:256: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:257: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:260: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:261: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:264: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:265: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:268: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:269: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:272: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:273: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:276: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:277: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:280: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:281: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:284: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:285: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:288: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:289: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:292: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:293: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:296: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:297: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:300: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:301: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:304: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:305: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:308: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:309: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:312: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:313: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:316: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:317: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:320: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:321: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:324: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:325: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:328: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:329: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:332: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:333: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:336: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:337: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:340: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:341: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:344: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:345: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:348: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:349: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:352: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:353: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:356: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:357: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:360: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:361: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:364: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:365: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:368: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:369: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:372: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:373: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:376: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:377: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:380: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:381: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:384: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:385: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:388: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:389: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:392: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:393: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:396: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:397: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:400: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:401: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:404: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:405: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:408: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:409: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:412: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:413: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:416: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:417: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:420: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:421: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:424: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:425: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:428: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:429: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:432: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:433: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:436: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:437: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:440: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:441: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:444: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:445: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:448: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:449: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:452: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:453: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:456: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:457: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:460: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:461: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:464: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:465: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:468: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:469: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:472: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:473: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:476: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:477: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:480: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:481: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:484: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:485: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:488: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:489: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:492: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:493: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:496: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:497: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:500: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:501: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:504: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:505: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:508: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:509: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:512: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:513: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:516: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:517: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:520: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:521: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:524: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:525: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:528: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:529: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:532: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:533: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:536: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:537: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:540: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:541: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:544: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:545: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:548: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:549: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:552: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:553: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:556: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:557: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:560: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:561: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:564: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:565: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:568: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:569: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:572: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:573: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:576: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:577: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:580: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:581: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:584: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:585: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:588: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:589: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:592: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:593: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:596: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:597: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:600: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:601: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:604: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:605: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:608: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:609: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:612: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:613: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:616: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:617: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:620: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:621: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:624: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:625: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:628: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:629: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:632: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:633: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:636: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:637: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:640: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:641: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:644: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:645: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:648: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:649: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:652: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:653: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:656: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:657: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:660: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:661: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:664: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:665: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:668: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:669: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:672: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:673: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:676: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:677: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:680: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:681: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:684: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:685: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:688: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:689: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:692: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:693: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:696: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:697: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:700: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:701: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:704: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:705: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:708: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:709: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:712: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:713: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:716: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:717: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:720: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:721: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:724: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:725: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:728: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:729: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:732: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:733: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:736: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:737: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:740: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:741: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:744: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:745: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:748: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:749: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:752: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:753: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:756: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:757: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:760: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:761: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:764: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:765: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:768: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:769: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:772: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:773: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:776: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:777: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:780: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:781: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:784: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:785: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:788: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:789: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:792: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:793: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:796: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:797: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:800: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:801: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:804: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:805: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:808: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:809: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:812: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:813: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:816: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:817: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:820: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:821: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:824: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:825: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:828: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:829: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:832: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:833: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:836: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:837: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:840: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:841: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:844: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:845: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:848: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:849: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:852: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:853: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:856: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:857: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:860: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:861: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:864: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:865: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:868: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:869: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:872: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:873: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:876: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:877: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:880: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:881: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:884: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:885: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:888: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:889: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:892: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:893: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:896: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:897: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:900: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:901: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:904: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:905: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:908: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:909: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:912: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:913: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:916: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:917: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:920: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:921: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:924: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:925: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:928: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:929: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:932: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:933: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:936: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:937: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:940: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:941: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:944: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:945: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:948: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:949: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:952: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:953: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:956: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:957: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:960: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:961: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:964: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:965: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:968: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:969: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:972: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:973: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:976: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:977: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:980: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:981: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:984: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:985: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:988: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:989: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:992: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:993: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:996: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:997: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1000: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1001: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1004: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1005: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1008: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1009: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1012: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1013: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1016: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1017: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1020: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1021: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1024: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1025: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1028: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1029: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1032: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1033: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1036: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1037: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1040: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1041: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1044: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1045: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1048: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1049: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1052: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1053: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1056: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1057: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1060: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1061: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1064: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1065: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1068: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1069: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1072: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1073: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1076: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1077: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1080: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1081: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1084: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1085: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1088: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1089: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1092: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1093: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1096: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1097: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1100: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1101: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1104: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1105: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1108: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1109: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1112: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1113: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1116: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1117: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1120: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1121: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1124: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1125: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1128: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1129: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1132: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1133: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1136: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1137: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1140: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1141: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1144: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1145: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1148: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1149: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1152: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1153: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1156: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1157: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1160: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1161: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1164: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1165: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1168: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1169: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1172: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1173: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1176: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1177: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1180: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1181: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1184: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1185: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1188: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1189: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1192: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1193: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1196: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1197: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1200: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1201: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1204: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1205: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1208: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1209: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1212: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1213: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1216: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1217: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1220: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1221: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1224: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1225: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1228: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1229: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1232: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1233: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1236: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1237: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1240: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1241: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1244: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1245: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1248: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1249: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1252: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1253: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1256: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1257: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1260: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1261: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1264: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1265: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1268: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1269: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1272: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1273: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1276: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1277: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1280: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1281: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1284: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1285: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1288: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1289: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1292: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1293: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1296: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1297: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1300: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1301: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1304: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1305: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1308: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1309: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1312: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1313: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1316: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1317: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1320: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1321: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1324: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1325: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1328: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1329: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1332: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1333: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1336: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1337: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1340: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1341: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1344: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1345: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1348: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1349: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1352: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1353: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1356: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1357: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1360: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1361: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1364: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1365: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1368: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1369: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1372: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1373: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1376: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1377: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1380: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1381: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1384: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1385: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1388: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1389: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1392: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1393: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1396: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1397: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1400: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1401: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1404: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1405: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1408: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1409: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1412: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1413: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1416: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1417: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1420: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1421: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1424: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1425: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1428: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1429: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1432: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1433: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1436: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1437: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1440: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1441: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1444: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1445: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1448: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1449: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1452: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1453: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1456: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1457: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1460: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1461: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1464: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1465: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1468: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1469: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1472: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1473: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1476: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1477: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1480: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1481: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1484: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1485: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1488: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1489: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1492: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1493: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1496: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1497: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1500: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1501: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1504: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1505: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1508: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1509: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1512: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1513: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1516: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1517: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1520: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1521: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1524: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1525: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1528: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1529: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1532: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1533: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1536: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1537: error: identity "alarm-identity" not found in module "ietf-alarms" fujitsu-alarm-types.yang:1540: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-alarm-types.yang:1541: error: identity "alarm-identity" not found in module "ietf-alarms"		Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-alarm-types.yang 2>&1": Error: 'fujitsu-alarm-types.yang' import of module 'ietf-alarms' failed fujitsu-alarm-types.yang:5.3: error(236): module not found Warning: revision with same date on line 58 fujitsu-alarm-types.yang:62.3: warning(1054): Revision date has already been used Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:172.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:176.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:180.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:184.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:188.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:192.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:196.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:200.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:204.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:208.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:212.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:216.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:220.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:224.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:228.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:232.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:236.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:240.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:244.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:248.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:252.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:256.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:260.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:264.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:268.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:272.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:276.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:280.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:284.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:288.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:292.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:296.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:300.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:304.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:308.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:312.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:316.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:320.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:324.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:328.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:332.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:336.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:340.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:344.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:348.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:352.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:356.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:360.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:364.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:368.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:372.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:376.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:380.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:384.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:388.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:392.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:396.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:400.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:404.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:408.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:412.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:416.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:420.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:424.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:428.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:432.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:436.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:440.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:444.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:448.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:452.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:456.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:460.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:464.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:468.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:472.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:476.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:480.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:484.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:488.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:492.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:496.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:500.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:504.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:508.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:512.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:516.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:520.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:524.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:528.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:532.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:536.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:540.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:544.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:548.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:552.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:556.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:560.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:564.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:568.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:572.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:576.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:580.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:584.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:588.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:592.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:596.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:600.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:604.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:608.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:612.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:616.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:620.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:624.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:628.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:632.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:636.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:640.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:644.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:648.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:652.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:656.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:660.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:664.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:668.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:672.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:676.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:680.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:684.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:688.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:692.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:696.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:700.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:704.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:708.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:712.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:716.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:720.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:724.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:728.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:732.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:736.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:740.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:744.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:748.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:752.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:756.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:760.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:764.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:768.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:772.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:776.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:780.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:784.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:788.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:792.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:796.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:800.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:804.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:808.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:812.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:816.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:820.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:824.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:828.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:832.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:836.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:840.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:844.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:848.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:852.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:856.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:860.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:864.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:868.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:872.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:876.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:880.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:884.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:888.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:892.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:896.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:900.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:904.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:908.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:912.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:916.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:920.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:924.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:928.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:932.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:936.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:940.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:944.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:948.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:952.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:956.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:960.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:964.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:968.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:972.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:976.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:980.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:984.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:988.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:992.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:996.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1000.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1004.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1008.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1012.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1016.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1020.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1024.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1028.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1032.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1036.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1040.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1044.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1048.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1052.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1056.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1060.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1064.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1068.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1072.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1076.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1080.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1084.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1088.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1092.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1096.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1100.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1104.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1108.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1112.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1116.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1120.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1124.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1128.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1132.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1136.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1140.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1144.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1148.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1152.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1156.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1160.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1164.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1168.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1172.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1176.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1180.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1184.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1188.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1192.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1196.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1200.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1204.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1208.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1212.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1216.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1220.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1224.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1228.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1232.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1236.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1240.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1244.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1248.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1252.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1256.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1260.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1264.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1268.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1272.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1276.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1280.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1284.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1288.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1292.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1296.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1300.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1304.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1308.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1312.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1316.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1320.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1324.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1328.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1332.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1336.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1340.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1344.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1348.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1352.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1356.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1360.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1364.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1368.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1372.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1376.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1380.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1384.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1388.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1392.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1396.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1400.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1404.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1408.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1412.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1416.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1420.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1424.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1428.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1432.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1436.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1440.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1444.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1448.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1452.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1456.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1460.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1464.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1468.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1472.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1476.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1480.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1484.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1488.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1492.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1496.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1500.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1504.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1508.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1512.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1516.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1520.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1524.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1528.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1532.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1536.3: error(236): module not found Load module 'ietf-alarms' failed (module not found) Error: failure importing module 'ietf-alarms' fujitsu-alarm-types.yang:1540.3: error(236): module not found
fujitsu-alarms-ext@2017-04-21.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-alarms-ext.yang 2>&1": fujitsu-alarms-ext.yang:5: error: module 'ietf-alarms' not found		Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-alarms-ext.yang --lint 2>&1": fujitsu-alarms-ext.yang:38: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-alarms-ext.yang:45: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-alarms-ext.yang:48: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-alarms-ext.yang:51: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-alarms-ext.yang:54: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-alarms-ext.yang:57: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-alarms-ext.yang:66: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-alarms-ext.yang:103: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-alarms-ext.yang:116: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-alarms-ext.yang:120: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-alarms-ext.yang:142: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-alarms-ext.yang:191: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-alarms-ext.yang:204: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-alarms-ext.yang:263: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement		Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-alarms-ext.yang 2>&1": Error: 'fujitsu-alarms-ext.yang' import of module 'ietf-alarms' failed fujitsu-alarms-ext.yang:5.3: error(236): module not found Error: typedef definition for 'al:alarm-type-id' not found in module ietf-alarms fujitsu-alarms-ext.yang:73.12: error(250): definition not found Error: typedef definition for 'al:alarm-type-id' not found in module ietf-alarms fujitsu-alarms-ext.yang:161.14: error(250): definition not found Error: typedef definition for 'al:alarm-type-id' not found in module ietf-alarms fujitsu-alarms-ext.yang:218.14: error(250): definition not found Error: object 'alarms' not found in module fujitsu-alarms-ext in Xpath target /al:alarms fujitsu-alarms-ext.yang:142.3: error(250): definition not found Error: object 'alarm-notification' not found in module fujitsu-alarms-ext in Xpath target /al:alarm-notification fujitsu-alarms-ext.yang:263.3: error(250): definition not found Error: object 'alarms' not found in module fujitsu-alarms-ext in Xpath target /al:alarms/al:alarm-list/al:alarm fujitsu-alarms-ext.yang:120.3: error(250): definition not found Error: object 'alarm-type-id' not found in module fujitsu-alarms-ext in Xpath target alarm-type-id fujitsu-alarms-ext.yang:144.7: error(250): definition not found Error: invalid identifier in key for list 'alarm-severity-assignment' (alarm-type-id) fujitsu-alarms-ext.yang:144.7: error(250): definition not found Error: object 'alarm-type-id' not found in module fujitsu-alarms-ext in Xpath target alarm-type-id fujitsu-alarms-ext.yang:151.7: error(250): definition not found Error: invalid identifier in key for list 'alarm-severity-status' (alarm-type-id) fujitsu-alarms-ext.yang:151.7: error(250): definition not found Error: object 'alarm-type-id' not found in module fujitsu-alarms-ext in Xpath target alarm-type-id fujitsu-alarms-ext.yang:208.7: error(250): definition not found Error: invalid identifier in key for list 'severity-defaults' (alarm-type-id) fujitsu-alarms-ext.yang:208.7: error(250): definition not found
fujitsu-data-encryption@2017-09-19.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-data-encryption.yang 2>&1": /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-user-security.yang:9: error: module 'tailf-aaa' not found	fujitsu-user-security.yang:9: warning: imported module "tailf-aaa" not used	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-data-encryption.yang --lint 2>&1": fujitsu-data-encryption.yang:32: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-data-encryption.yang:36: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-data-encryption.yang:40: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-data-encryption.yang:44: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-data-encryption.yang:48: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-data-encryption.yang:53: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-data-encryption.yang:57: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-data-encryption.yang:61: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-data-encryption.yang:65: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-data-encryption.yang:70: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-data-encryption.yang:74: error: keyword "presence" not in canonical order (see RFC 6020, Section 12) fujitsu-data-encryption.yang:80: error: keyword "value" not in canonical order (see RFC 6020, Section 12) fujitsu-data-encryption.yang:85: error: keyword "value" not in canonical order (see RFC 6020, Section 12) fujitsu-data-encryption.yang:94: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-data-encryption.yang:95: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-data-encryption.yang:98: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-data-encryption.yang:103: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-data-encryption.yang:114: error: keyword "length" not in canonical order (see RFC 6020, Section 12) fujitsu-data-encryption.yang:118: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) fujitsu-data-encryption.yang:120: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement fujitsu-data-encryption.yang:137: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) fujitsu-data-encryption.yang:185: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-data-encryption.yang:188: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-data-encryption.yang:191: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-data-encryption.yang:194: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-data-encryption.yang:197: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-data-encryption.yang:214: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-data-encryption.yang:217: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement		Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-data-encryption.yang 2>&1": Error: 'fujitsu-user-security.yang' import of module 'tailf-aaa' failed fujitsu-user-security.yang:9.3: error(236): module not found Warning: top-level NP container 'security' is mandatory fujitsu-user-security.yang:91.3: warning(1048): top-level object is mandatory Warning: Module 'tailf-aaa' not used fujitsu-user-security.yang:9.3: warning(1015): import not used Error: 'fujitsu-data-encryption.yang' import of module 'fujitsu-user-security' failed fujitsu-data-encryption.yang:5.3: error(332): imported module has errors Error: object 'security' not found in module fujitsu-data-encryption in Xpath target /secu:security fujitsu-data-encryption.yang:70.3: error(250): definition not found
fujitsu-database@2018-11-26.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-database.yang --lint 2>&1": fujitsu-database.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-database.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-database.yang:36: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-database.yang:63: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-database.yang:279: error: keyword "default" not in canonical order (see RFC 6020, Section 12)
fujitsu-dcnutils@2016-10-08.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-dcnutils.yang --lint 2>&1": fujitsu-dcnutils.yang:23: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-dcnutils.yang:29: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-dcnutils.yang:33: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-dcnutils.yang:36: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-dcnutils.yang:41: error: RFC 8407: 4.14: statement "leaf-list" must have a "description" substatement fujitsu-dcnutils.yang:50: error: RFC 8407: 4.14: statement "leaf-list" must have a "description" substatement
fujitsu-dhcp-client@2018-10-09.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-dhcp-client.yang 2>&1": fujitsu-dhcp-client.yang:9: error: module 'dhcp-client' not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-license.yang:32: warning: the revision statements are not given in reverse chronological order /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-user-security.yang:9: error: module 'tailf-aaa' not found	fujitsu-dhcp-client.yang:18: warning: imported module "fujitsu-system" not used fujitsu-equipment.yang:11: warning: imported module "fujitsu-notification-types" not used fujitsu-license.yang:32: warning: the revision statements are not given in reverse chronological order fujitsu-system.yang:6: warning: imported module "fujitsu-entity-states" not used fujitsu-system.yang:15: warning: imported module "ietf-yang-types" not used fujitsu-system.yang:18: warning: imported module "ietf-netconf-acm" not used fujitsu-system.yang:33: warning: imported module "fujitsu-license" not used fujitsu-user-security.yang:9: warning: imported module "tailf-aaa" not used	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-dhcp-client.yang --lint 2>&1": fujitsu-dhcp-client.yang:6: warning: imported module "ietf-inet-types" not used fujitsu-dhcp-client.yang:12: warning: imported module "ietf-interfaces" not used fujitsu-dhcp-client.yang:15: warning: imported module "ietf-ip" not used fujitsu-dhcp-client.yang:18: warning: imported module "fujitsu-system" not used fujitsu-dhcp-client.yang:42: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-dhcp-client.yang:46: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-dhcp-client.yang:50: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-dhcp-client.yang:54: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-dhcp-client.yang:58: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-dhcp-client.yang:60: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-dhcp-client.yang:61: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-dhcp-client.yang:62: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-dhcp-client.yang:67: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-dhcp-client.yang:68: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-dhcp-client.yang:72: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-dhcp-client.yang:73: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-dhcp-client.yang:77: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-dhcp-client.yang:78: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-dhcp-client.yang:88: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-dhcp-client.yang:90: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-dhcp-client.yang:91: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) fujitsu-dhcp-client.yang:96: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-dhcp-client.yang:110: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-dhcp-client.yang:111: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-dhcp-client.yang:117: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-dhcp-client.yang:118: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-dhcp-client.yang:119: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-dhcp-client.yang:120: error: keyword "must" not in canonical order (see RFC 6020, Section 12)		Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-dhcp-client.yang 2>&1": Error: 'fujitsu-dhcp-client.yang' import of module 'dhcp-client' failed fujitsu-dhcp-client.yang:9.3: error(236): module not found Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: revision with same date on line 34 fujitsu-port.yang:39.3: warning(1054): Revision date has already been used Warning: Module 'fujitsu-notification-types' not used fujitsu-equipment.yang:11.3: warning(1015): import not used Error: 'fujitsu-user-security.yang' import of module 'tailf-aaa' failed fujitsu-user-security.yang:9.3: error(236): module not found Warning: top-level NP container 'security' is mandatory fujitsu-user-security.yang:91.3: warning(1048): top-level object is mandatory Warning: Module 'tailf-aaa' not used fujitsu-user-security.yang:9.3: warning(1015): import not used Error: 'fujitsu-security-certificates.yang' import of module 'fujitsu-user-security' failed fujitsu-security-certificates.yang:5.3: error(332): imported module has errors Error: object 'security' not found in module fujitsu-security-certificates in Xpath target /secu:security fujitsu-security-certificates.yang:79.3: error(250): definition not found Error: Module for prefix 'secu' not found fujitsu-security-certificates.yang:145.17: error(236): module not found Error: Module for prefix 'secu' not found fujitsu-security-certificates.yang:164.17: error(236): module not found Error: 'fujitsu-system.yang' import of module 'fujitsu-security-certificates' failed fujitsu-system.yang:21.3: error(236): module not found Error: 'fujitsu-system.yang' import of module 'fujitsu-user-security' failed fujitsu-system.yang:24.3: error(332): imported module has errors Error: 'fujitsu-system.yang' import of module 'tailf-xsd-types' failed fujitsu-system.yang:27.3: error(236): module not found Warning: revision dates not in descending order fujitsu-license.yang:32.3: warning(1035): bad revision-stmt order Warning: revision with same date on line 92 fujitsu-system.yang:96.3: warning(1054): Revision date has already been used Error: typedef definition for 'xs:duration' not found in module tailf-xsd-types fujitsu-system.yang:1712.16: error(250): definition not found Error: typedef definition for 'xs:duration' not found in module tailf-xsd-types fujitsu-system.yang:1851.16: error(250): definition not found Error: Module for prefix 'secu' not found fujitsu-system.yang:1750.23: error(236): module not found Warning: Module 'fujitsu-entity-states' not used fujitsu-system.yang:6.3: warning(1015): import not used Warning: Module 'ietf-yang-types' not used fujitsu-system.yang:15.3: warning(1015): import not used Warning: Module 'ietf-netconf-acm' not used fujitsu-system.yang:18.3: warning(1015): import not used Warning: Module 'fujitsu-license' not used fujitsu-system.yang:33.3: warning(1015): import not used Error: 'fujitsu-dhcp-client.yang' import of module 'fujitsu-system' failed fujitsu-dhcp-client.yang:18.3: error(236): module not found Error: object 'clientv4' not found in module fujitsu-dhcp-client in Xpath target /dhcp:clientv4 fujitsu-dhcp-client.yang:60.3: error(250): definition not found Error: object 'clientv4' not found in module fujitsu-dhcp-client in Xpath target /dhcp:clientv4 fujitsu-dhcp-client.yang:96.3: error(250): definition not found Warning: Module 'fujitsu-system' not used fujitsu-dhcp-client.yang:18.3: warning(1015): import not used
fujitsu-dhcpv6-client@2018-10-09.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-dhcpv6-client.yang 2>&1": fujitsu-dhcpv6-client.yang:9: error: module 'dhcpv6-client' not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-license.yang:32: warning: the revision statements are not given in reverse chronological order /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-user-security.yang:9: error: module 'tailf-aaa' not found	fujitsu-dhcpv6-client.yang:18: warning: imported module "fujitsu-system" not used fujitsu-equipment.yang:11: warning: imported module "fujitsu-notification-types" not used fujitsu-license.yang:32: warning: the revision statements are not given in reverse chronological order fujitsu-system.yang:6: warning: imported module "fujitsu-entity-states" not used fujitsu-system.yang:15: warning: imported module "ietf-yang-types" not used fujitsu-system.yang:18: warning: imported module "ietf-netconf-acm" not used fujitsu-system.yang:33: warning: imported module "fujitsu-license" not used fujitsu-user-security.yang:9: warning: imported module "tailf-aaa" not used	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-dhcpv6-client.yang --lint 2>&1": fujitsu-dhcpv6-client.yang:12: warning: imported module "ietf-interfaces" not used fujitsu-dhcpv6-client.yang:15: warning: imported module "ietf-ip" not used fujitsu-dhcpv6-client.yang:18: warning: imported module "fujitsu-system" not used fujitsu-dhcpv6-client.yang:42: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-dhcpv6-client.yang:46: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-dhcpv6-client.yang:50: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-dhcpv6-client.yang:54: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-dhcpv6-client.yang:58: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-dhcpv6-client.yang:62: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-dhcpv6-client.yang:64: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-dhcpv6-client.yang:65: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-dhcpv6-client.yang:66: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-dhcpv6-client.yang:130: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-dhcpv6-client.yang:132: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-dhcpv6-client.yang:133: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) fujitsu-dhcpv6-client.yang:140: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-dhcpv6-client.yang:165: error: keyword "must" not in canonical order (see RFC 6020, Section 12)		Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-dhcpv6-client.yang 2>&1": Error: 'fujitsu-dhcpv6-client.yang' import of module 'dhcpv6-client' failed fujitsu-dhcpv6-client.yang:9.3: error(236): module not found Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: revision with same date on line 34 fujitsu-port.yang:39.3: warning(1054): Revision date has already been used Warning: Module 'fujitsu-notification-types' not used fujitsu-equipment.yang:11.3: warning(1015): import not used Error: 'fujitsu-user-security.yang' import of module 'tailf-aaa' failed fujitsu-user-security.yang:9.3: error(236): module not found Warning: top-level NP container 'security' is mandatory fujitsu-user-security.yang:91.3: warning(1048): top-level object is mandatory Warning: Module 'tailf-aaa' not used fujitsu-user-security.yang:9.3: warning(1015): import not used Error: 'fujitsu-security-certificates.yang' import of module 'fujitsu-user-security' failed fujitsu-security-certificates.yang:5.3: error(332): imported module has errors Error: object 'security' not found in module fujitsu-security-certificates in Xpath target /secu:security fujitsu-security-certificates.yang:79.3: error(250): definition not found Error: Module for prefix 'secu' not found fujitsu-security-certificates.yang:145.17: error(236): module not found Error: Module for prefix 'secu' not found fujitsu-security-certificates.yang:164.17: error(236): module not found Error: 'fujitsu-system.yang' import of module 'fujitsu-security-certificates' failed fujitsu-system.yang:21.3: error(236): module not found Error: 'fujitsu-system.yang' import of module 'fujitsu-user-security' failed fujitsu-system.yang:24.3: error(332): imported module has errors Error: 'fujitsu-system.yang' import of module 'tailf-xsd-types' failed fujitsu-system.yang:27.3: error(236): module not found Warning: revision dates not in descending order fujitsu-license.yang:32.3: warning(1035): bad revision-stmt order Warning: revision with same date on line 92 fujitsu-system.yang:96.3: warning(1054): Revision date has already been used Error: typedef definition for 'xs:duration' not found in module tailf-xsd-types fujitsu-system.yang:1712.16: error(250): definition not found Error: typedef definition for 'xs:duration' not found in module tailf-xsd-types fujitsu-system.yang:1851.16: error(250): definition not found Error: Module for prefix 'secu' not found fujitsu-system.yang:1750.23: error(236): module not found Warning: Module 'fujitsu-entity-states' not used fujitsu-system.yang:6.3: warning(1015): import not used Warning: Module 'ietf-yang-types' not used fujitsu-system.yang:15.3: warning(1015): import not used Warning: Module 'ietf-netconf-acm' not used fujitsu-system.yang:18.3: warning(1015): import not used Warning: Module 'fujitsu-license' not used fujitsu-system.yang:33.3: warning(1015): import not used Error: 'fujitsu-dhcpv6-client.yang' import of module 'fujitsu-system' failed fujitsu-dhcpv6-client.yang:18.3: error(236): module not found Error: object 'clientv6' not found in module fujitsu-dhcpv6-client in Xpath target /dhcpv6:clientv6 fujitsu-dhcpv6-client.yang:64.3: error(250): definition not found Error: object 'clientv6' not found in module fujitsu-dhcpv6-client in Xpath target /dhcpv6:clientv6 fujitsu-dhcpv6-client.yang:140.3: error(250): definition not found Warning: Module 'fujitsu-system' not used fujitsu-dhcpv6-client.yang:18.3: warning(1015): import not used
fujitsu-dns-resolver@2015-08-26.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-dns-resolver.yang --lint 2>&1": fujitsu-dns-resolver.yang:45: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-dns-resolver.yang:61: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12)
fujitsu-encryption-user@2017-07-05.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-encryption-user.yang 2>&1": /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-user-security.yang:9: error: module 'tailf-aaa' not found	fujitsu-encryption-user.yang:5: warning: imported module "fujitsu-user-security" not used fujitsu-user-security.yang:9: warning: imported module "tailf-aaa" not used	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-encryption-user.yang --lint 2>&1": fujitsu-encryption-user.yang:5: warning: imported module "fujitsu-user-security" not used fujitsu-encryption-user.yang:29: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-encryption-user.yang:33: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-encryption-user.yang:41: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-encryption-user.yang:42: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-encryption-user.yang:48: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-encryption-user.yang:49: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-encryption-user.yang:54: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-encryption-user.yang:55: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-encryption-user.yang:64: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) fujitsu-encryption-user.yang:65: error: keyword "must" not in canonical order (see RFC 6020, Section 12) fujitsu-encryption-user.yang:71: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-encryption-user.yang:72: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-encryption-user.yang:73: error: keyword "default" not in canonical order (see RFC 6020, Section 12)		Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-encryption-user.yang 2>&1": Error: 'fujitsu-user-security.yang' import of module 'tailf-aaa' failed fujitsu-user-security.yang:9.3: error(236): module not found Warning: top-level NP container 'security' is mandatory fujitsu-user-security.yang:91.3: warning(1048): top-level object is mandatory Warning: Module 'tailf-aaa' not used fujitsu-user-security.yang:9.3: warning(1015): import not used Error: 'fujitsu-encryption-user.yang' import of module 'fujitsu-user-security' failed fujitsu-encryption-user.yang:5.3: error(332): imported module has errors Warning: Module 'fujitsu-user-security' not used fujitsu-encryption-user.yang:5.3: warning(1015): import not used
fujitsu-entity-maintenance-loopback@2015-09-10.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-entity-maintenance-loopback@2015-09-10.yang --lint 2>&1": fujitsu-entity-maintenance-loopback@2015-09-10.yang:22: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-entity-maintenance-loopback@2015-09-10.yang:27: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
fujitsu-entity-maintenance-testsignal@2018-08-22.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-entity-maintenance-testsignal.yang --lint 2>&1": fujitsu-entity-maintenance-testsignal.yang:22: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-entity-maintenance-testsignal.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-entity-maintenance-testsignal.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-entity-maintenance-testsignal.yang:34: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-entity-maintenance-testsignal.yang:39: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
fujitsu-entity-states@2017-03-02.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-entity-states.yang --lint 2>&1": fujitsu-entity-states.yang:29: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-entity-states.yang:33: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-entity-states.yang:38: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-entity-states.yang:80: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-entity-states.yang:101: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-entity-states.yang:111: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-entity-states.yang:121: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-entity-states.yang:128: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-entity-states.yang:131: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement		Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used
fujitsu-eqpt-operations-dev@2017-02-28.yang	FAILED		fujitsu-equipment.yang:11: warning: imported module "fujitsu-notification-types" not used	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-eqpt-operations-dev.prod.yang --lint 2>&1": fujitsu-eqpt-operations-dev.prod.yang:25: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-eqpt-operations-dev.prod.yang:29: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-eqpt-operations-dev.prod.yang:33: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-eqpt-operations-dev.prod.yang:37: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-eqpt-operations-dev.prod.yang:41: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement		Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: revision with same date on line 34 fujitsu-port.yang:39.3: warning(1054): Revision date has already been used Warning: Module 'fujitsu-notification-types' not used fujitsu-equipment.yang:11.3: warning(1015): import not used
fujitsu-eqpt-operations@2018-10-12.yang	FAILED		fujitsu-equipment.yang:11: warning: imported module "fujitsu-notification-types" not used	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-eqpt-operations.yang --lint 2>&1": fujitsu-eqpt-operations.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-eqpt-operations.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-eqpt-operations.yang:35: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-eqpt-operations.yang:46: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-eqpt-operations.yang:70: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-eqpt-operations.yang:98: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-eqpt-operations.yang:126: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-eqpt-operations.yang:144: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-eqpt-operations.yang:162: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-eqpt-operations.yang:174: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement		Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: revision with same date on line 34 fujitsu-port.yang:39.3: warning(1054): Revision date has already been used Warning: Module 'fujitsu-notification-types' not used fujitsu-equipment.yang:11.3: warning(1015): import not used
fujitsu-equipment-dev@2018-12-11.yang	FAILED	fujitsu-equipment-dev.prod.yang:74: warning: the revision statements are not given in reverse chronological order	fujitsu-equipment-dev.prod.yang:9: warning: imported module "fujitsu-pm-types" not used fujitsu-equipment-dev.prod.yang:74: warning: the revision statements are not given in reverse chronological order fujitsu-equipment.yang:11: warning: imported module "fujitsu-notification-types" not used	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-equipment-dev.prod.yang --lint 2>&1": fujitsu-equipment-dev.prod.yang:9: warning: imported module "fujitsu-pm-types" not used fujitsu-equipment-dev.prod.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-equipment-dev.prod.yang:34: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-equipment-dev.prod.yang:38: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-equipment-dev.prod.yang:42: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-equipment-dev.prod.yang:46: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-equipment-dev.prod.yang:50: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-equipment-dev.prod.yang:54: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-equipment-dev.prod.yang:58: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-equipment-dev.prod.yang:62: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-equipment-dev.prod.yang:66: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-equipment-dev.prod.yang:70: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-equipment-dev.prod.yang:74: warning: the revision statements are not given in reverse chronological order fujitsu-equipment-dev.prod.yang:74: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement	libyang warn: Invalid value "binned" which does not fit the type (Invalid enumeration value "binned".). libyang warn: Previous warning generated by XPath subexpression[3] "pm-type = 'binned'" with context node "/fujitsu-equipment:eqpt/shelf/slot/subslot/port/subport/pm/pm-threshold/pm-th-binned". libyang warn: Previous warning generated by XPath subexpression[3] "pm-type = 'binned'" with context node "/fujitsu-equipment:eqpt/shelf/slot/subslot/port/pm/pm-threshold/pm-th-binned".	Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: revision with same date on line 34 fujitsu-port.yang:39.3: warning(1054): Revision date has already been used Warning: Module 'fujitsu-notification-types' not used fujitsu-equipment.yang:11.3: warning(1015): import not used Warning: revision with same date on line 44 fujitsu-pm-types.yang:49.3: warning(1054): Revision date has already been used Warning: Module 'fujitsu-pm-types' not used fujitsu-equipment-dev.prod.yang:9.3: warning(1015): import not used
fujitsu-equipment@2017-07-10.yang	FAILED		fujitsu-equipment.yang:11: warning: imported module "fujitsu-notification-types" not used	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-equipment.yang --lint 2>&1": fujitsu-equipment.yang:11: warning: imported module "fujitsu-notification-types" not used fujitsu-equipment.yang:35: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-equipment.yang:39: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-equipment.yang:48: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-equipment.yang:53: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement		Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: revision with same date on line 34 fujitsu-port.yang:39.3: warning(1054): Revision date has already been used Warning: Module 'fujitsu-notification-types' not used fujitsu-equipment.yang:11.3: warning(1015): import not used
fujitsu-ethernet-interfaces-common@2018-06-07.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-ethernet-interfaces-common.yang --lint 2>&1": fujitsu-ethernet-interfaces-common.yang:37: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ethernet-interfaces-common.yang:41: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ethernet-interfaces-common.yang:46: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-ethernet-interfaces-common.yang:50: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-ethernet-interfaces-common.yang:63: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-ethernet-interfaces-common.yang:64: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-ethernet-interfaces-common.yang:65: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement		Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used
fujitsu-ethernet-interfaces-dev@2018-09-18.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-ethernet-interfaces-dev.prod.yang 2>&1": /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-license.yang:32: warning: the revision statements are not given in reverse chronological order /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-user-security.yang:9: error: module 'tailf-aaa' not found	fujitsu-ethernet-interfaces-dev.prod.yang:11: warning: imported module "fujitsu-equipment" not used fujitsu-equipment.yang:11: warning: imported module "fujitsu-notification-types" not used fujitsu-license.yang:32: warning: the revision statements are not given in reverse chronological order fujitsu-system.yang:6: warning: imported module "fujitsu-entity-states" not used fujitsu-system.yang:15: warning: imported module "ietf-yang-types" not used fujitsu-system.yang:18: warning: imported module "ietf-netconf-acm" not used fujitsu-system.yang:33: warning: imported module "fujitsu-license" not used fujitsu-user-security.yang:9: warning: imported module "tailf-aaa" not used	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-ethernet-interfaces-dev.prod.yang --lint 2>&1": fujitsu-ethernet-interfaces-dev.prod.yang:1: error: RFC 8407: 4.8: statement "module" must have a "organization" substatement fujitsu-ethernet-interfaces-dev.prod.yang:11: warning: imported module "fujitsu-equipment" not used fujitsu-ethernet-interfaces-dev.prod.yang:29: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ethernet-interfaces-dev.prod.yang:33: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ethernet-interfaces-dev.prod.yang:37: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ethernet-interfaces-dev.prod.yang:41: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ethernet-interfaces-dev.prod.yang:45: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ethernet-interfaces-dev.prod.yang:52: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ethernet-interfaces-dev.prod.yang:60: error: keyword "description" not in canonical order (see RFC 6020, Section 12) fujitsu-ethernet-interfaces-dev.prod.yang:65: error: keyword "description" not in canonical order (see RFC 6020, Section 12)	libyang warn: Invalid value "metered" which does not fit the type (Invalid enumeration value "metered".). libyang warn: Previous warning generated by XPath subexpression[3] "pm-type = 'metered'" with context node "/ietf-interfaces:interfaces/interface/fujitsu-ethernet-interfaces:ethernet/pm/pm-threshold/pm-th-metered".	Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-ethernet-interfaces-dev.prod.yang 2>&1": Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: revision with same date on line 34 fujitsu-port.yang:39.3: warning(1054): Revision date has already been used Warning: Module 'fujitsu-notification-types' not used fujitsu-equipment.yang:11.3: warning(1015): import not used Error: 'fujitsu-user-security.yang' import of module 'tailf-aaa' failed fujitsu-user-security.yang:9.3: error(236): module not found Warning: top-level NP container 'security' is mandatory fujitsu-user-security.yang:91.3: warning(1048): top-level object is mandatory Warning: Module 'tailf-aaa' not used fujitsu-user-security.yang:9.3: warning(1015): import not used Error: 'fujitsu-security-certificates.yang' import of module 'fujitsu-user-security' failed fujitsu-security-certificates.yang:5.3: error(332): imported module has errors Error: object 'security' not found in module fujitsu-security-certificates in Xpath target /secu:security fujitsu-security-certificates.yang:79.3: error(250): definition not found Error: Module for prefix 'secu' not found fujitsu-security-certificates.yang:145.17: error(236): module not found Error: Module for prefix 'secu' not found fujitsu-security-certificates.yang:164.17: error(236): module not found Error: 'fujitsu-system.yang' import of module 'fujitsu-security-certificates' failed fujitsu-system.yang:21.3: error(236): module not found Error: 'fujitsu-system.yang' import of module 'fujitsu-user-security' failed fujitsu-system.yang:24.3: error(332): imported module has errors Error: 'fujitsu-system.yang' import of module 'tailf-xsd-types' failed fujitsu-system.yang:27.3: error(236): module not found Warning: revision dates not in descending order fujitsu-license.yang:32.3: warning(1035): bad revision-stmt order Warning: revision with same date on line 92 fujitsu-system.yang:96.3: warning(1054): Revision date has already been used Error: typedef definition for 'xs:duration' not found in module tailf-xsd-types fujitsu-system.yang:1712.16: error(250): definition not found Error: typedef definition for 'xs:duration' not found in module tailf-xsd-types fujitsu-system.yang:1851.16: error(250): definition not found Error: Module for prefix 'secu' not found fujitsu-system.yang:1750.23: error(236): module not found Warning: Module 'fujitsu-entity-states' not used fujitsu-system.yang:6.3: warning(1015): import not used Warning: Module 'ietf-yang-types' not used fujitsu-system.yang:15.3: warning(1015): import not used Warning: Module 'ietf-netconf-acm' not used fujitsu-system.yang:18.3: warning(1015): import not used Warning: Module 'fujitsu-license' not used fujitsu-system.yang:33.3: warning(1015): import not used Error: 'fujitsu-ethernet-interfaces.yang' import of module 'fujitsu-system' failed fujitsu-ethernet-interfaces.yang:15.3: error(236): module not found Error: object 'defaults' not found in module fujitsu-ethernet-interfaces in Xpath target /sys:defaults fujitsu-ethernet-interfaces.yang:663.3: error(250): definition not found Error: 'fujitsu-ethernet-interfaces-dev.prod.yang' import of module 'fujitsu-ethernet-interfaces' failed fujitsu-ethernet-interfaces-dev.prod.yang:8.3: error(250): definition not found Error: object 'ethernet' not found in path '/if:interfaces/if:interface/eth:ethernet/eth:link-oam' fujitsu-ethernet-interfaces-dev.prod.yang:212.2: error(251): definition segment not found Error: object 'ethernet' not found in path '/if:interfaces/if:interface/eth:ethernet/eth:transport/eth:policy-profile' fujitsu-ethernet-interfaces-dev.prod.yang:212.2: error(251): definition segment not found Error: object 'ethernet' not found in path '/if:interfaces/if:interface/eth:ethernet/eth:fec' fujitsu-ethernet-interfaces-dev.prod.yang:212.2: error(251): definition segment not found Error: object 'ethernet' not found in path '/if:interfaces/if:interface/eth:ethernet/eth:rate' fujitsu-ethernet-interfaces-dev.prod.yang:212.2: error(251): definition segment not found Error: object 'ethernet' not found in path '/if:interfaces/if:interface/eth:ethernet/eth:location' fujitsu-ethernet-interfaces-dev.prod.yang:212.2: error(251): definition segment not found Error: object 'ethernet' not found in path '/if:interfaces/if:interface/eth:ethernet/eth:testPattern' fujitsu-ethernet-interfaces-dev.prod.yang:212.2: error(251): definition segment not found Error: object 'ethernet' not found in path '/if:interfaces/if:interface/eth:ethernet/eth:transport/eth:transport-signal-failure' fujitsu-ethernet-interfaces-dev.prod.yang:212.2: error(251): definition segment not found Error: object 'ethernet' not found in path '/if:interfaces/if:interface/eth:ethernet/eth:transport/eth:backward-transport-signal-failure' fujitsu-ethernet-interfaces-dev.prod.yang:212.2: error(251): definition segment not found Error: object 'ethernet' not found in path '/if:interfaces/if:interface/eth:ethernet/eth:transport/eth:direction' fujitsu-ethernet-interfaces-dev.prod.yang:212.2: error(251): definition segment not found Error: object 'ethernet' not found in path '/if:interfaces/if:interface/eth:ethernet/eth:transport/eth:mac-fcs' fujitsu-ethernet-interfaces-dev.prod.yang:212.2: error(251): definition segment not found Error: object 'ethernet' not found in path '/if:interfaces/if:interface/eth:ethernet/eth:transport/eth:tx-clock-source' fujitsu-ethernet-interfaces-dev.prod.yang:212.2: error(251): definition segment not found Error: object 'ethernet' not found in path '/if:interfaces/if:interface/eth:ethernet/eth:pm/eth:pm-threshold/eth:pm-type' fujitsu-ethernet-interfaces-dev.prod.yang:212.2: error(251): definition segment not found Error: object 'ethernet' not found in path '/if:interfaces/if:interface/eth:ethernet/eth:pm/eth:pm-threshold/eth:pm-th-metered' fujitsu-ethernet-interfaces-dev.prod.yang:212.2: error(251): definition segment not found Error: object 'ethernet' not found in path '/if:interfaces/if:interface/eth:ethernet/eth:pm/eth:pm-threshold/eth:pm-th-binned/eth:pm-time-periods/eth:pm-time-period' fujitsu-ethernet-interfaces-dev.prod.yang:212.2: error(251): definition segment not found Error: object 'ethernet' not found in path '/if:interfaces/if:interface/eth:ethernet/eth:pm/eth:pm-threshold/eth:pm-th-binned/eth:pm-time-periods/eth:pm-value' fujitsu-ethernet-interfaces-dev.prod.yang:212.2: error(251): definition segment not found Warning: Module 'fujitsu-equipment' not used fujitsu-ethernet-interfaces-dev.prod.yang:11.3: warning(1015): import not used
fujitsu-ethernet-interfaces@2018-10-26.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/all_modules/fujitsu-ethernet-interfaces@2018-10-26.yang 2>&1": ./fujitsu-license@2015-08-02.yang:32: warning: the revision statements are not given in reverse chronological order ./tailf-aaa@2023-03-06.yang:103: error: unexpected keyword 'tailf:internal-dp'	/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-equipment.yang:11: warning: imported module "fujitsu-notification-types" not used /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-license.yang:32: warning: the revision statements are not given in reverse chronological order /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-system.yang:6: warning: imported module "fujitsu-entity-states" not used /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-system.yang:15: warning: imported module "ietf-yang-types" not used /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-system.yang:18: warning: imported module "ietf-netconf-acm" not used /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-system.yang:33: warning: imported module "fujitsu-license" not used /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-user-security.yang:9: warning: imported module "tailf-aaa" not used	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-ethernet-interfaces@2018-10-26.yang --lint 2>&1": fujitsu-ethernet-interfaces@2018-10-26.yang:38: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:42: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:47: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:51: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:55: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:59: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:63: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:67: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:71: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:84: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:100: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:101: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:114: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:180: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-ethernet-interfaces@2018-10-26.yang:317: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:341: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:344: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:368: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:373: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:376: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:379: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:382: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:385: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:388: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:442: error: keyword "config" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-ethernet-interfaces@2018-10-26.yang:443: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-ethernet-interfaces@2018-10-26.yang:626: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:645: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:653: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-ethernet-interfaces@2018-10-26.yang:664: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement	libyang warn: File name "fujitsu-license@2015-08-02.yang" does not match module revision "2017-06-13".	Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-ethernet-interfaces@2018-10-26.yang 2>&1": Error: 'fujitsu-ethernet-interfaces@2018-10-26.yang' import of module 'fujitsu-ethernet-interfaces-common' failed fujitsu-ethernet-interfaces@2018-10-26.yang:9.3: error(236): module not found Error: 'fujitsu-ethernet-interfaces@2018-10-26.yang' import of module 'fujitsu-ains-keywords' failed fujitsu-ethernet-interfaces@2018-10-26.yang:13.3: error(236): module not found Error: 'fujitsu-ethernet-interfaces@2018-10-26.yang' import of module 'fujitsu-system' failed fujitsu-ethernet-interfaces@2018-10-26.yang:16.3: error(236): module not found Error: grouping definition for 'eth-common:common-eth-attributes' not found in module fujitsu-ethernet-interfaces-common fujitsu-ethernet-interfaces@2018-10-26.yang:650.7: error(250): definition not found Error: grouping definition for 'ains:ains-prov-keywords' not found in module fujitsu-ains-keywords fujitsu-ethernet-interfaces@2018-10-26.yang:660.9: error(250): definition not found Error: grouping 'common-eth-attributes' not found fujitsu-ethernet-interfaces@2018-10-26.yang:650.7: error(250): definition not found Error: grouping 'ains-prov-keywords' not found fujitsu-ethernet-interfaces@2018-10-26.yang:660.9: error(250): definition not found Error: object 'defaults' not found in module fujitsu-ethernet-interfaces in Xpath target /sys:defaults fujitsu-ethernet-interfaces@2018-10-26.yang:664.3: error(250): definition not found
fujitsu-factory@2015-10-13.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-factory.yang --lint 2>&1": fujitsu-factory.yang:22: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
fujitsu-file-transfer-webui@2017-06-26.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-file-transfer-webui.yang --lint 2>&1": fujitsu-file-transfer-webui.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-file-transfer-webui.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-file-transfer-webui.yang:44: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement fujitsu-file-transfer-webui.yang:48: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-file-transfer-webui.yang:49: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-file-transfer-webui.yang:53: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-file-transfer-webui.yang:54: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-file-transfer-webui.yang:58: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-file-transfer-webui.yang:61: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
fujitsu-file-transfer@2017-06-26.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-file-transfer.yang --lint 2>&1": fujitsu-file-transfer.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-file-transfer.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-file-transfer.yang:53: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-file-transfer.yang:54: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-file-transfer.yang:65: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement fujitsu-file-transfer.yang:69: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-file-transfer.yang:70: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-file-transfer.yang:74: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-file-transfer.yang:75: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-file-transfer.yang:79: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-file-transfer.yang:82: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
fujitsu-fwdl@2015-09-28.yang	FAILED		fujitsu-equipment.yang:11: warning: imported module "fujitsu-notification-types" not used	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-fwdl.yang --lint 2>&1": fujitsu-fwdl.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-fwdl.yang:31: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-fwdl.yang:86: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-fwdl.yang:204: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-fwdl.yang:216: error: keyword "config" not in canonical order (see RFC 6020, Section 12) fujitsu-fwdl.yang:234: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement		Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: revision with same date on line 34 fujitsu-port.yang:39.3: warning(1054): Revision date has already been used Warning: Module 'fujitsu-notification-types' not used fujitsu-equipment.yang:11.3: warning(1015): import not used
fujitsu-gcc@2015-09-14.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-gcc.yang --lint 2>&1": fujitsu-gcc.yang:72: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
fujitsu-if-type@2018-04-09.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-if-type.yang --lint 2>&1": fujitsu-if-type.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-if-type.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-if-type.yang:42: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-if-type.yang:46: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-if-type.yang:50: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-if-type.yang:54: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-if-type.yang:58: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement
fujitsu-inventory@2014-12-02.yang	PASSED
fujitsu-ip@2018-07-13.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-ip.yang --lint 2>&1": fujitsu-ip.yang:33: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ip.yang:37: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ip.yang:41: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ip.yang:45: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ip.yang:49: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ip.yang:53: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ip.yang:57: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ip.yang:61: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ip.yang:65: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ip.yang:70: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-ip.yang:80: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-ip.yang:83: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-ip.yang:86: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-ip.yang:91: error: keyword "must" not in canonical order (see RFC 6020, Section 12) fujitsu-ip.yang:98: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-ip.yang:99: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-ip.yang:105: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-ip.yang:106: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-ip.yang:108: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-ip.yang:111: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
fujitsu-ipv4-unicast-routing@2018-01-22.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-ipv4-unicast-routing.yang 2>&1": fujitsu-ipv4-unicast-routing.yang:5: error: module 'ietf-routing' not found fujitsu-ipv4-unicast-routing.yang:8: error: module 'ietf-ipv4-unicast-routing' not found	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-ipv4-unicast-routing.yang 2>&1": fujitsu-ipv4-unicast-routing.yang:11: warning: imported module "ietf-interfaces" not used fujitsu-ipv4-unicast-routing.yang:17: warning: imported module "ietf-yang-types" not used fujitsu-ipv4-unicast-routing.yang:60: error: node ietf-routing::routing-instance is not found fujitsu-ipv4-unicast-routing.yang:65: error: "ietf-routing:routing-instance" in the path for onlink-outgoing-intf at fujitsu-ipv4-unicast-routing.yang:62 is not found fujitsu-ipv4-unicast-routing.yang:78: error: node ietf-routing::routing-instance is not found	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-ipv4-unicast-routing.yang --lint 2>&1": fujitsu-ipv4-unicast-routing.yang:11: warning: imported module "ietf-interfaces" not used fujitsu-ipv4-unicast-routing.yang:17: warning: imported module "ietf-yang-types" not used fujitsu-ipv4-unicast-routing.yang:39: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ipv4-unicast-routing.yang:43: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ipv4-unicast-routing.yang:47: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ipv4-unicast-routing.yang:51: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ipv4-unicast-routing.yang:55: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ipv4-unicast-routing.yang:60: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-ipv4-unicast-routing.yang:60: error: node ietf-routing::routing-instance is not found fujitsu-ipv4-unicast-routing.yang:63: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-ipv4-unicast-routing.yang:64: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-ipv4-unicast-routing.yang:71: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-ipv4-unicast-routing.yang:72: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-ipv4-unicast-routing.yang:78: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-ipv4-unicast-routing.yang:78: error: node ietf-routing::routing-instance is not found		Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-ipv4-unicast-routing.yang 2>&1": Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/rt:static-routes/v4ur:ipv4/v4ur:route/v4ur:next-hop/v4ur:next-hop-options' fujitsu-ipv4-unicast-routing.yang:60.3: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/rt:routes/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop' fujitsu-ipv4-unicast-routing.yang:78.3: error(251): definition segment not found Warning: Module 'ietf-ipv4-unicast-routing' not used fujitsu-ipv4-unicast-routing.yang:8.3: warning(1015): import not used Warning: Module 'ietf-interfaces' not used fujitsu-ipv4-unicast-routing.yang:11.3: warning(1015): import not used Warning: Module 'ietf-yang-types' not used fujitsu-ipv4-unicast-routing.yang:17.3: warning(1015): import not used
fujitsu-ipv6-unicast-routing@2018-01-22.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-ipv6-unicast-routing.yang 2>&1": fujitsu-ipv6-unicast-routing.yang:5: error: module 'ietf-routing' not found fujitsu-ipv6-unicast-routing.yang:8: error: module 'ietf-ipv6-unicast-routing' not found	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-ipv6-unicast-routing.yang 2>&1": fujitsu-ipv6-unicast-routing.yang:42: error: node ietf-routing::routing-instance is not found	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-ipv6-unicast-routing.yang --lint 2>&1": fujitsu-ipv6-unicast-routing.yang:33: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ipv6-unicast-routing.yang:37: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ipv6-unicast-routing.yang:42: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-ipv6-unicast-routing.yang:42: error: node ietf-routing::routing-instance is not found		Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-ipv6-unicast-routing.yang 2>&1": Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/rt:routes/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop' fujitsu-ipv6-unicast-routing.yang:42.3: error(251): definition segment not found Warning: Module 'ietf-ipv6-unicast-routing' not used fujitsu-ipv6-unicast-routing.yang:8.3: warning(1015): import not used
fujitsu-license@2015-08-02.yang	FAILED	fujitsu-license.yang:32: warning: the revision statements are not given in reverse chronological order	fujitsu-license.yang:32: warning: the revision statements are not given in reverse chronological order	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-license.yang --lint 2>&1": fujitsu-license.yang:32: warning: the revision statements are not given in reverse chronological order fujitsu-license.yang:38: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-license.yang:50: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-license.yang:58: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-license.yang:59: error: keyword "when" not in canonical order (see RFC 6020, Section 12) fujitsu-license.yang:60: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-license.yang:183: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-license.yang:185: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-license.yang:317: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement		Warning: revision dates not in descending order fujitsu-license.yang:32.3: warning(1035): bad revision-stmt order
fujitsu-lldp@2019-01-03.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-lldp.yang 2>&1": fujitsu-lldp.yang:15: error: module 'iana-afn-safi' not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-protocols.yang:28: warning: the revision statements are not given in reverse chronological order	fujitsu-lldp.yang:6: warning: imported module "ietf-yang-types" not used fujitsu-protocols.yang:28: warning: the revision statements are not given in reverse chronological order	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-lldp.yang --lint 2>&1": fujitsu-lldp.yang:6: warning: imported module "ietf-yang-types" not used fujitsu-lldp.yang:39: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-lldp.yang:43: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-lldp.yang:47: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-lldp.yang:51: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-lldp.yang:55: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-lldp.yang:59: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-lldp.yang:63: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-lldp.yang:79: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-lldp.yang:102: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-lldp.yang:110: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-lldp.yang:118: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-lldp.yang:124: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-lldp.yang:152: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-lldp.yang:157: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-lldp.yang:158: error: keyword "config" not in canonical order (see RFC 6020, Section 12) fujitsu-lldp.yang:164: error: RFC 8407: 4.14: statement "list" must have a "description" substatement		Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-lldp.yang 2>&1": Error: 'fujitsu-lldp.yang' import of module 'iana-afn-safi' failed fujitsu-lldp.yang:15.3: error(236): module not found Warning: revision dates not in descending order fujitsu-protocols.yang:28.3: warning(1035): bad revision-stmt order Error: typedef definition for 'ianaaf:address-family' not found in module iana-afn-safi fujitsu-lldp.yang:166.20: error(250): definition not found Warning: Module 'ietf-yang-types' not used fujitsu-lldp.yang:6.3: warning(1015): import not used
fujitsu-log@2018-09-24.yang	FAILED		fujitsu-equipment.yang:11: warning: imported module "fujitsu-notification-types" not used	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-log.yang --lint 2>&1": fujitsu-log.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-log.yang:35: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-log.yang:39: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-log.yang:43: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-log.yang:48: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-log.yang:52: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-log.yang:56: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-log.yang:61: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-log.yang:66: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-log.yang:71: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-log.yang:76: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-log.yang:78: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-log.yang:99: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-log.yang:114: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) fujitsu-log.yang:158: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-log.yang:206: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-log.yang:208: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement fujitsu-log.yang:245: error: RFC 8407: 4.14: statement "leaf-list" must have a "description" substatement fujitsu-log.yang:263: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-log.yang:271: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-log.yang:309: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-log.yang:340: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) fujitsu-log.yang:346: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-log.yang:349: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement		Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: revision with same date on line 34 fujitsu-port.yang:39.3: warning(1054): Revision date has already been used Warning: Module 'fujitsu-notification-types' not used fujitsu-equipment.yang:11.3: warning(1015): import not used
fujitsu-mac-addr@2016-02-01.yang	FAILED		fujitsu-equipment.yang:11: warning: imported module "fujitsu-notification-types" not used	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-mac-addr.yang --lint 2>&1": fujitsu-mac-addr.yang:29: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-mac-addr.yang:34: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-mac-addr.yang:50: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement		Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: revision with same date on line 34 fujitsu-port.yang:39.3: warning(1054): Revision date has already been used Warning: Module 'fujitsu-notification-types' not used fujitsu-equipment.yang:11.3: warning(1015): import not used
fujitsu-net-ospf@2018-01-22.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/all_modules/fujitsu-net-ospf@2018-01-22.yang 2>&1": ./ietf-ospf@2015-03-09.yang:704: error: grouping 'crypto-algorithm-types' in module 'ietf-key-chain' not found ./ietf-ospf@2015-03-09.yang:1952: error: node 'routing-instance' not found ./ietf-ospf@2015-03-09.yang:1952: error: node 'routing-protocols' not found ./ietf-ospf@2015-03-09.yang:1952: error: node 'routing-protocol' not found ./ietf-ospf@2015-03-09.yang:2155: error: node 'routing-instance' not found ./ietf-ospf@2015-03-09.yang:2155: error: node 'routing-protocols' not found ./ietf-ospf@2015-03-09.yang:2155: error: node 'routing-protocol' not found ./ietf-ospf@2015-03-09.yang:2397: error: node 'ribs' not found ./ietf-ospf@2015-03-09.yang:2397: error: node 'rib' not found ./ietf-ospf@2015-03-09.yang:2397: error: node 'routes' not found ./ietf-ospf@2015-03-09.yang:2397: error: node 'route' not found ./ietf-ospf@2015-03-09.yang:2435: error: typedef 'routing-instance-ref' in module 'ietf-routing' not found	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-net-ospf@2018-01-22.yang 2>&1": fujitsu-net-ospf@2018-01-22.yang:83: error: node ietf-routing::routing-instance is not found fujitsu-net-ospf@2018-01-22.yang:86: warning: node "ietf-ospf::af" is not found in "fujitsu-net-ospf::/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:1970 (at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:576): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:2121 (at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:576): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:601: error: grouping "crypto-algorithm-types" not found in module "ietf-key-chain" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:2151 (at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:1458): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:2151 (at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:1467): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:2169 (at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:1486): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:2169 (at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:1495): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:2187 (at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:1514): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:2187 (at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:1523): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:1946 (at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:1614): warning: node "ietf-routing::routing-instance" is not found in "ietf-routing::routing" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:1868: error: node ietf-routing::routing-instance is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:1907: error: type "routing-instance-ref" not found in module "ietf-routing" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:2003: error: node ietf-routing::routing-instance is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:2020: error: "ietf-routing:routing-instance" in the path for name at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:2018 is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:2038: error: node ietf-routing::routing-instance is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:2052: error: "ietf-routing:routing-instance" in the path for name at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:2050 is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:2064: error: node ietf-routing::routing-instance is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:2087: error: type "routing-instance-ref" not found in module "ietf-routing" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:2134: warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:2193: error: node ietf-routing::routing-instance is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:2207: error: "ietf-routing:routing-instance" in the path for name at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:2205 is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:2224: error: node ietf-routing::routing-instance is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:2238: error: "ietf-routing:routing-instance" in the path for name at /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:2236 is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:2292: error: node ietf-routing::routing-instance is not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-ospf.yang:2331: error: type "routing-instance-ref" not found in module "ietf-routing"	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-net-ospf@2018-01-22.yang --lint 2>&1": fujitsu-net-ospf@2018-01-22.yang:39: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-net-ospf@2018-01-22.yang:43: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-net-ospf@2018-01-22.yang:46: warning: RFC 8407: 4.4: statement "status" is given with its default value "current" fujitsu-net-ospf@2018-01-22.yang:52: warning: RFC 8407: 4.4: statement "status" is given with its default value "current" fujitsu-net-ospf@2018-01-22.yang:58: warning: RFC 8407: 4.4: statement "status" is given with its default value "current" fujitsu-net-ospf@2018-01-22.yang:63: warning: RFC 8407: 4.4: statement "status" is given with its default value "current" fujitsu-net-ospf@2018-01-22.yang:70: warning: RFC 8407: 4.4: statement "status" is given with its default value "current" fujitsu-net-ospf@2018-01-22.yang:83: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-net-ospf@2018-01-22.yang:83: error: node ietf-routing::routing-instance is not found fujitsu-net-ospf@2018-01-22.yang:86: warning: node "ietf-ospf::af" is not found in "fujitsu-net-ospf::/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance"	libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang /var/yang/all_modules/fujitsu-net-ospf@2018-01-22.yang 2>&1": libyang err : Augment target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance" from module "fujitsu-net-ospf" was not found. (Path "/fujitsu-net-ospf:{augment='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance'}".) libyang err : Augment target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" from module "ietf-ospf" was not found. (Path "/ietf-ospf:{augment='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol'}".) libyang err : Augment target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance" from module "ietf-ospf" was not found. (Path "/ietf-ospf:{augment='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance'}".) libyang err : Augment target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface" from module "ietf-ospf" was not found. (Path "/ietf-ospf:{augment='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface'}".) libyang err : Augment target node "/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" from module "ietf-ospf" was not found. (Path "/ietf-ospf:{augment='/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol'}".) libyang err : Augment target node "/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance" from module "ietf-ospf" was not found. (Path "/ietf-ospf:{augment='/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance'}".) libyang err : Augment target node "/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interfaces" from module "ietf-ospf" was not found. (Path "/ietf-ospf:{augment='/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interfaces'}".) libyang err : Augment target node "/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/rt:routes/rt:route" from module "ietf-ospf" was not found. (Path "/ietf-ospf:{augment='/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/rt:routes/rt:route'}".)	Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-net-ospf@2018-01-22.yang 2>&1": Error: 'ietf-ospf@2015-03-09.yang' import of module 'ietf-key-chain' failed ietf-ospf@2015-03-09.yang:24.3: error(236): module not found Error: typedef definition for 'key-chain:key-chain-ref' not found in module ietf-key-chain ietf-ospf@2015-03-09.yang:692.18: error(250): definition not found Error: grouping definition for 'key-chain:crypto-algorithm-types' not found in module ietf-key-chain ietf-ospf@2015-03-09.yang:704.13: error(250): definition not found Error: typedef definition for 'rt:routing-instance-ref' not found in module ietf-routing Source for ietf-routing: /var/yang/all_modules/ietf-routing@2018-03-13.yang ietf-ospf@2015-03-09.yang:2435.12: error(250): definition not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol' ietf-ospf@2015-03-09.yang:1952.3: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol' ietf-ospf@2015-03-09.yang:2155.3: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance' ietf-ospf@2015-03-09.yang:2095.3: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance' ietf-ospf@2015-03-09.yang:2309.3: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/rt:routes/rt:route' ietf-ospf@2015-03-09.yang:2397.3: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface' ietf-ospf@2015-03-09.yang:2129.3: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interfaces' ietf-ospf@2015-03-09.yang:2340.3: error(251): definition segment not found Warning: path failed (no nodes available): '/rt:routing/rt:routing-instance/rt:ribs/rt:rib/rt:name' Error: 'fujitsu-net-ospf@2018-01-22.yang' import of module 'ietf-ospf' revision '2015-03-09' failed fujitsu-net-ospf@2018-01-22.yang:14.3: error(250): definition not found Error: Module for prefix 'ospf' not found fujitsu-net-ospf@2018-01-22.yang:86.12: error(236): module not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance' fujitsu-net-ospf@2018-01-22.yang:83.3: error(251): definition segment not found
fujitsu-notification-types@2018-10-29.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-notification-types.yang --lint 2>&1": fujitsu-notification-types.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-notification-types.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-notification-types.yang:34: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-notification-types.yang:39: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-notification-types.yang:43: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-notification-types.yang:47: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-notification-types.yang:51: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-notification-types.yang:56: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-notification-types.yang:62: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-notification-types.yang:68: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-notification-types.yang:73: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-notification-types.yang:77: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-notification-types.yang:83: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-notification-types.yang:88: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-notification-types.yang:92: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
fujitsu-notifications@2015-11-20.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-notifications.yang --lint 2>&1": fujitsu-notifications.yang:27: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
fujitsu-optical-channel-interfaces-dev@2018-10-11.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-optical-channel-interfaces-dev.prod.yang 2>&1": /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-optical-channel-interfaces.yang:9: error: module 'iana-if-type' not found /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-optical-channel-interfaces.yang:42: warning: the revision statements are not given in reverse chronological order	fujitsu-optical-channel-interfaces.yang:42: warning: the revision statements are not given in reverse chronological order fujitsu-optical-channel-interfaces.yang:411: warning: explicit config statement is ignored	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-optical-channel-interfaces-dev.prod.yang --lint 2>&1": fujitsu-optical-channel-interfaces-dev.prod.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement fujitsu-optical-channel-interfaces-dev.prod.yang:1: error: RFC 8407: 4.8: statement "module" must have a "organization" substatement fujitsu-optical-channel-interfaces-dev.prod.yang:1: error: RFC 8407: 4.8: statement "module" must have a "description" substatement fujitsu-optical-channel-interfaces-dev.prod.yang:12: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces-dev.prod.yang:16: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces-dev.prod.yang:20: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces-dev.prod.yang:24: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces-dev.prod.yang:28: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces-dev.prod.yang:32: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces-dev.prod.yang:36: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces-dev.prod.yang:40: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces-dev.prod.yang:44: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces-dev.prod.yang:48: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces-dev.prod.yang:52: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces-dev.prod.yang:56: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces-dev.prod.yang:134: warning: RFC 8407: 4.4: statement "config" is given with its default value "true" fujitsu-optical-channel-interfaces-dev.prod.yang:135: error: keyword "units" not in canonical order (see RFC 6020, Section 12)	libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-optical-channel-interfaces-dev.prod.yang 2>&1": libyang err : Invalid deviation replacing "config" property "config true" which is not present. (Path "/fujitsu-optical-channel-interfaces-dev.prod:{deviation='/if:interfaces/if:interface/och:och/och:slot-width'}".)	Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: revision dates not in descending order fujitsu-optical-channel-interfaces.yang:42.3: warning(1035): bad revision-stmt order
fujitsu-optical-channel-interfaces@2017-07-14.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-optical-channel-interfaces.yang 2>&1": fujitsu-optical-channel-interfaces.yang:9: error: module 'iana-if-type' not found fujitsu-optical-channel-interfaces.yang:42: warning: the revision statements are not given in reverse chronological order	fujitsu-optical-channel-interfaces.yang:42: warning: the revision statements are not given in reverse chronological order fujitsu-optical-channel-interfaces.yang:411: warning: explicit config statement is ignored	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-optical-channel-interfaces.yang --lint 2>&1": fujitsu-optical-channel-interfaces.yang:38: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces.yang:42: warning: the revision statements are not given in reverse chronological order fujitsu-optical-channel-interfaces.yang:42: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces.yang:47: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces.yang:51: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces.yang:55: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces.yang:59: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces.yang:63: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces.yang:67: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces.yang:71: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces.yang:75: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-channel-interfaces.yang:116: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-optical-channel-interfaces.yang:349: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-channel-interfaces.yang:352: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-channel-interfaces.yang:376: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-optical-channel-interfaces.yang:384: error: keyword "config" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-optical-channel-interfaces.yang:385: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-optical-channel-interfaces.yang:402: error: RFC 8407: 4.14,4.16: statement "notification" must have a "description" substatement fujitsu-optical-channel-interfaces.yang:403: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-optical-channel-interfaces.yang:408: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-optical-channel-interfaces.yang:411: error: keyword "config" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-optical-channel-interfaces.yang:411: warning: explicit config statement is ignored fujitsu-optical-channel-interfaces.yang:412: error: keyword "type" not in canonical order (see RFC 6020, Section 12)		Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: revision dates not in descending order fujitsu-optical-channel-interfaces.yang:42.3: warning(1035): bad revision-stmt order
fujitsu-optical-tributary-signal-dev@2018-10-10.yang	FAILED	fujitsu-optical-tributary-signal-dev.prod.yang:56: warning: the revision statements are not given in reverse chronological order fujitsu-optical-tributary-signal-dev.prod.yang:60: warning: the revision statements are not given in reverse chronological order	fujitsu-optical-tributary-signal-dev.prod.yang:56: warning: the revision statements are not given in reverse chronological order fujitsu-optical-tributary-signal-dev.prod.yang:60: warning: the revision statements are not given in reverse chronological order	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-optical-tributary-signal-dev.prod.yang --lint 2>&1": fujitsu-optical-tributary-signal-dev.prod.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement fujitsu-optical-tributary-signal-dev.prod.yang:1: error: RFC 8407: 4.8: statement "module" must have a "organization" substatement fujitsu-optical-tributary-signal-dev.prod.yang:1: error: RFC 8407: 4.8: statement "module" must have a "description" substatement fujitsu-optical-tributary-signal-dev.prod.yang:12: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-tributary-signal-dev.prod.yang:16: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-tributary-signal-dev.prod.yang:20: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-tributary-signal-dev.prod.yang:24: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-tributary-signal-dev.prod.yang:28: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-tributary-signal-dev.prod.yang:32: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-tributary-signal-dev.prod.yang:36: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-tributary-signal-dev.prod.yang:40: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-tributary-signal-dev.prod.yang:44: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-tributary-signal-dev.prod.yang:48: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-tributary-signal-dev.prod.yang:52: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-tributary-signal-dev.prod.yang:56: warning: the revision statements are not given in reverse chronological order fujitsu-optical-tributary-signal-dev.prod.yang:56: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-tributary-signal-dev.prod.yang:60: warning: the revision statements are not given in reverse chronological order fujitsu-optical-tributary-signal-dev.prod.yang:60: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-tributary-signal-dev.prod.yang:75: error: keyword "description" not in canonical order (see RFC 6020, Section 12) fujitsu-optical-tributary-signal-dev.prod.yang:80: error: keyword "description" not in canonical order (see RFC 6020, Section 12) fujitsu-optical-tributary-signal-dev.prod.yang:270: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal-dev.prod.yang:301: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement		Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used
fujitsu-optical-tributary-signal-group-dev@2016-11-04.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-optical-tributary-signal-group-dev.prod.yang --lint 2>&1": fujitsu-optical-tributary-signal-group-dev.prod.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement fujitsu-optical-tributary-signal-group-dev.prod.yang:1: error: RFC 8407: 4.8: statement "module" must have a "organization" substatement fujitsu-optical-tributary-signal-group-dev.prod.yang:1: error: RFC 8407: 4.8: statement "module" must have a "description" substatement fujitsu-optical-tributary-signal-group-dev.prod.yang:12: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-tributary-signal-group-dev.prod.yang:20: error: keyword "description" not in canonical order (see RFC 6020, Section 12) fujitsu-optical-tributary-signal-group-dev.prod.yang:25: error: keyword "description" not in canonical order (see RFC 6020, Section 12) fujitsu-optical-tributary-signal-group-dev.prod.yang:30: error: keyword "description" not in canonical order (see RFC 6020, Section 12) fujitsu-optical-tributary-signal-group-dev.prod.yang:35: error: keyword "description" not in canonical order (see RFC 6020, Section 12) fujitsu-optical-tributary-signal-group-dev.prod.yang:88: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement		Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used
fujitsu-optical-tributary-signal-group@2015-04-10.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-optical-tributary-signal-group.yang --lint 2>&1": fujitsu-optical-tributary-signal-group.yang:37: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-tributary-signal-group.yang:78: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-optical-tributary-signal-group.yang:81: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-optical-tributary-signal-group.yang:83: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal-group.yang:86: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal-group.yang:214: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal-group.yang:217: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal-group.yang:227: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal-group.yang:230: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal-group.yang:237: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-optical-tributary-signal-group.yang:258: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-optical-tributary-signal-group.yang:286: error: RFC 8407: 4.14,4.16: statement "notification" must have a "description" substatement fujitsu-optical-tributary-signal-group.yang:287: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-optical-tributary-signal-group.yang:292: error: RFC 8407: 4.14: statement "container" must have a "description" substatement		Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used
fujitsu-optical-tributary-signal@2018-09-19.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-optical-tributary-signal.yang --lint 2>&1": fujitsu-optical-tributary-signal.yang:37: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-tributary-signal.yang:41: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-tributary-signal.yang:45: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-tributary-signal.yang:49: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-tributary-signal.yang:54: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-optical-tributary-signal.yang:66: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-optical-tributary-signal.yang:69: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-optical-tributary-signal.yang:71: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal.yang:74: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal.yang:77: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal.yang:256: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal.yang:259: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal.yang:435: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal.yang:438: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-optical-tributary-signal.yang:468: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-optical-tributary-signal.yang:504: error: RFC 8407: 4.14,4.16: statement "notification" must have a "description" substatement fujitsu-optical-tributary-signal.yang:512: error: RFC 8407: 4.14: statement "container" must have a "description" substatement		Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used
fujitsu-ospf@2015-11-04.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-ospf.yang 2>&1": fujitsu-ospf.yang:5: error: module 'ietf-routing' not found fujitsu-ospf.yang:14: error: module 'ietf-ospf', revision '2015-03-09' not found	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-ospf.yang 2>&1": fujitsu-ospf.yang:8: warning: imported module "ietf-yang-types" not used fujitsu-ospf.yang:11: warning: imported module "ietf-inet-types" not used fujitsu-ospf.yang:14: warning: imported module "ietf-ospf" not used fujitsu-ospf.yang:95: error: node ietf-routing::routing-instance is not found fujitsu-ospf.yang:158: error: node ietf-routing::routing-instance is not found standards/ietf-ospf.yang:1970 (at standards/ietf-ospf.yang:576): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" standards/ietf-ospf.yang:2121 (at standards/ietf-ospf.yang:576): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" standards/ietf-ospf.yang:601: error: grouping "crypto-algorithm-types" not found in module "ietf-key-chain" standards/ietf-ospf.yang:2151 (at standards/ietf-ospf.yang:1458): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" standards/ietf-ospf.yang:2151 (at standards/ietf-ospf.yang:1467): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" standards/ietf-ospf.yang:2169 (at standards/ietf-ospf.yang:1486): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" standards/ietf-ospf.yang:2169 (at standards/ietf-ospf.yang:1495): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" standards/ietf-ospf.yang:2187 (at standards/ietf-ospf.yang:1514): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" standards/ietf-ospf.yang:2187 (at standards/ietf-ospf.yang:1523): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" standards/ietf-ospf.yang:1946 (at standards/ietf-ospf.yang:1614): warning: node "ietf-routing::routing-instance" is not found in "ietf-routing::routing" standards/ietf-ospf.yang:1868: error: node ietf-routing::routing-instance is not found standards/ietf-ospf.yang:1907: error: type "routing-instance-ref" not found in module "ietf-routing" standards/ietf-ospf.yang:2003: error: node ietf-routing::routing-instance is not found standards/ietf-ospf.yang:2020: error: "ietf-routing:routing-instance" in the path for name at standards/ietf-ospf.yang:2018 is not found standards/ietf-ospf.yang:2038: error: node ietf-routing::routing-instance is not found standards/ietf-ospf.yang:2052: error: "ietf-routing:routing-instance" in the path for name at standards/ietf-ospf.yang:2050 is not found standards/ietf-ospf.yang:2064: error: node ietf-routing::routing-instance is not found standards/ietf-ospf.yang:2087: error: type "routing-instance-ref" not found in module "ietf-routing" standards/ietf-ospf.yang:2134: warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" standards/ietf-ospf.yang:2193: error: node ietf-routing::routing-instance is not found standards/ietf-ospf.yang:2207: error: "ietf-routing:routing-instance" in the path for name at standards/ietf-ospf.yang:2205 is not found standards/ietf-ospf.yang:2224: error: node ietf-routing::routing-instance is not found standards/ietf-ospf.yang:2238: error: "ietf-routing:routing-instance" in the path for name at standards/ietf-ospf.yang:2236 is not found standards/ietf-ospf.yang:2292: error: node ietf-routing::routing-instance is not found standards/ietf-ospf.yang:2331: error: type "routing-instance-ref" not found in module "ietf-routing"	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-ospf.yang --lint 2>&1": fujitsu-ospf.yang:8: warning: imported module "ietf-yang-types" not used fujitsu-ospf.yang:11: warning: imported module "ietf-inet-types" not used fujitsu-ospf.yang:14: warning: imported module "ietf-ospf" not used fujitsu-ospf.yang:39: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ospf.yang:50: warning: RFC 8407: 4.4: statement "status" is given with its default value "current" fujitsu-ospf.yang:55: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-ospf.yang:70: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-ospf.yang:78: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-ospf.yang:87: error: keyword "presence" not in canonical order (see RFC 6020, Section 12) fujitsu-ospf.yang:88: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-ospf.yang:95: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-ospf.yang:95: error: node ietf-routing::routing-instance is not found fujitsu-ospf.yang:100: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-ospf.yang:158: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-ospf.yang:158: error: node ietf-routing::routing-instance is not found	libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-ospf.yang 2>&1": libyang err : Not found node "key-chain-list" in path. (Schema location "/ietf-routing:routing-state/routing-instance/routing-protocols/routing-protocol/ietf-ospf:ospf/instance/area/interface/authentication/auth-type-selection/auth-trailer-key-chain/key-chain".)	Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-ospf.yang 2>&1": Error: 'fujitsu-ospf.yang' import of module 'ietf-ospf' revision '2015-03-09' failed fujitsu-ospf.yang:14.3: error(236): module not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance' fujitsu-ospf.yang:95.3: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface' fujitsu-ospf.yang:158.3: error(251): definition segment not found Warning: Module 'ietf-yang-types' not used fujitsu-ospf.yang:8.3: warning(1015): import not used Warning: Module 'ietf-inet-types' not used fujitsu-ospf.yang:11.3: warning(1015): import not used Warning: Module 'ietf-ospf' not used fujitsu-ospf.yang:14.3: warning(1015): import not used
fujitsu-otn-odu-interfaces-dev@2018-12-10.yang	FAILED		fujitsu-otn-odu-interfaces.yang:869: warning: "ianaift" looks like a prefix but is not defined fujitsu-otn-odu-interfaces.yang:921: warning: explicit config statement is ignored	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-otn-odu-interfaces-dev.prod.yang --lint 2>&1": fujitsu-otn-odu-interfaces-dev.prod.yang:31: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:35: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:39: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:43: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:47: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:51: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:55: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:59: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:63: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:67: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:71: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:75: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:79: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:83: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:88: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:92: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:97: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:101: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:105: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:109: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:113: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces-dev.prod.yang:117: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement	libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-otn-odu-interfaces-dev.prod.yang 2>&1": libyang err : Invalid deviation replacing "config" property "config false" which is not present. (Path "/fujitsu-otn-odu-interfaces-dev.prod:{deviation='/if:interfaces/if:interface/odu:odu/odu:direction'}".)	Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: Module 'fujitsu-notification-types' not used fujitsu-otn.yang:8.3: warning(1015): import not used Warning: compare value 'ianaift:otnOdu' invalid for object 'ietf-interfaces:type type:identityref' XPath:../if:type = 'ianaift:otnOdu' fujitsu-otn-odu-interfaces.yang: line 869: warning(1052): XPath compare value invalid for YANG type
fujitsu-otn-odu-interfaces@2018-02-02.yang	FAILED		fujitsu-otn-odu-interfaces.yang:869: warning: "ianaift" looks like a prefix but is not defined fujitsu-otn-odu-interfaces.yang:921: warning: explicit config statement is ignored	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-otn-odu-interfaces.yang --lint 2>&1": fujitsu-otn-odu-interfaces.yang:47: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces.yang:51: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces.yang:55: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces.yang:59: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces.yang:63: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces.yang:67: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces.yang:71: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces.yang:75: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces.yang:79: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces.yang:83: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces.yang:87: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces.yang:91: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces.yang:95: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces.yang:101: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces.yang:105: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces.yang:109: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces.yang:113: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces.yang:117: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-odu-interfaces.yang:370: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-otn-odu-interfaces.yang:390: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-otn-odu-interfaces.yang:425: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-otn-odu-interfaces.yang:444: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-otn-odu-interfaces.yang:450: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-otn-odu-interfaces.yang:501: error: keyword "config" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-otn-odu-interfaces.yang:502: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-otn-odu-interfaces.yang:512: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-otn-odu-interfaces.yang:646: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-otn-odu-interfaces.yang:652: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-otn-odu-interfaces.yang:654: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-otn-odu-interfaces.yang:657: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-otn-odu-interfaces.yang:660: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-otn-odu-interfaces.yang:666: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-otn-odu-interfaces.yang:694: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-otn-odu-interfaces.yang:725: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) fujitsu-otn-odu-interfaces.yang:728: error: keyword "min-elements" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-otn-odu-interfaces.yang:730: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-otn-odu-interfaces.yang:748: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-otn-odu-interfaces.yang:749: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-otn-odu-interfaces.yang:750: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-otn-odu-interfaces.yang:821: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-otn-odu-interfaces.yang:839: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-otn-odu-interfaces.yang:843: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-otn-odu-interfaces.yang:848: error: keyword "max-elements" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-otn-odu-interfaces.yang:849: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-otn-odu-interfaces.yang:854: error: keyword "max-elements" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-otn-odu-interfaces.yang:855: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-otn-odu-interfaces.yang:867: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-otn-odu-interfaces.yang:869: warning: "ianaift" looks like a prefix but is not defined fujitsu-otn-odu-interfaces.yang:875: error: keyword "config" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-otn-odu-interfaces.yang:876: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-otn-odu-interfaces.yang:912: error: RFC 8407: 4.14,4.16: statement "notification" must have a "description" substatement fujitsu-otn-odu-interfaces.yang:913: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-otn-odu-interfaces.yang:918: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-otn-odu-interfaces.yang:921: error: keyword "config" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-otn-odu-interfaces.yang:921: warning: explicit config statement is ignored fujitsu-otn-odu-interfaces.yang:922: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-otn-odu-interfaces.yang:933: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-otn-odu-interfaces.yang:936: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-otn-odu-interfaces.yang:939: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-otn-odu-interfaces.yang:942: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement		Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: Module 'fujitsu-notification-types' not used fujitsu-otn.yang:8.3: warning(1015): import not used Warning: compare value 'ianaift:otnOdu' invalid for object 'ietf-interfaces:type type:identityref' XPath:../if:type = 'ianaift:otnOdu' fujitsu-otn-odu-interfaces.yang: line 869: warning(1052): XPath compare value invalid for YANG type
fujitsu-otn-oducn-interfaces-dev@2018-10-29.yang	FAILED		fujitsu-equipment.yang:11: warning: imported module "fujitsu-notification-types" not used fujitsu-otn-odu-interfaces.yang:869: warning: "ianaift" looks like a prefix but is not defined fujitsu-otn-odu-interfaces.yang:921: warning: explicit config statement is ignored fujitsu-otn-oducn-interfaces.yang:18: warning: imported module "fujitsu-equipment" not used	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-otn-oducn-interfaces-dev.prod.yang --lint 2>&1": fujitsu-otn-oducn-interfaces-dev.prod.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement fujitsu-otn-oducn-interfaces-dev.prod.yang:1: error: RFC 8407: 4.8: statement "module" must have a "organization" substatement fujitsu-otn-oducn-interfaces-dev.prod.yang:1: error: RFC 8407: 4.8: statement "module" must have a "description" substatement fujitsu-otn-oducn-interfaces-dev.prod.yang:12: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-oducn-interfaces-dev.prod.yang:16: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-oducn-interfaces-dev.prod.yang:20: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-oducn-interfaces-dev.prod.yang:24: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-oducn-interfaces-dev.prod.yang:28: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-oducn-interfaces-dev.prod.yang:32: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-oducn-interfaces-dev.prod.yang:91: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement	libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-otn-oducn-interfaces-dev.prod.yang 2>&1": libyang err : Invalid deviation replacing "config" property "config false" which is not present. (Path "/fujitsu-otn-oducn-interfaces-dev.prod:{deviation='/if:interfaces/if:interface/oducn:oducn/oducn:rate'}".)	Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-otn-oducn-interfaces-dev.prod.yang 2>&1": Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: Module 'fujitsu-notification-types' not used fujitsu-otn.yang:8.3: warning(1015): import not used Warning: compare value 'ianaift:otnOdu' invalid for object 'ietf-interfaces:type type:identityref' XPath:../if:type = 'ianaift:otnOdu' fujitsu-otn-odu-interfaces.yang: line 869: warning(1052): XPath compare value invalid for YANG type Warning: revision with same date on line 34 fujitsu-port.yang:39.3: warning(1054): Revision date has already been used Warning: Module 'fujitsu-notification-types' not used fujitsu-equipment.yang:11.3: warning(1015): import not used Warning: Module 'fujitsu-equipment' not used fujitsu-otn-oducn-interfaces.yang:18.3: warning(1015): import not used Error: 'default' must not exist in deviate target '/if:interfaces/if:interface/oducn:oducn/oducn:standard/oducn:itu/oducn:tti-itu/oducn:tim-det-mode' fujitsu-otn-oducn-interfaces-dev.prod.yang:147.5: error(347): invalid deviate sub-clause
fujitsu-otn-oducn-interfaces@2018-04-04.yang	FAILED		fujitsu-otn-oducn-interfaces.yang:18: warning: imported module "fujitsu-equipment" not used fujitsu-equipment.yang:11: warning: imported module "fujitsu-notification-types" not used fujitsu-otn-odu-interfaces.yang:869: warning: "ianaift" looks like a prefix but is not defined fujitsu-otn-odu-interfaces.yang:921: warning: explicit config statement is ignored	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-otn-oducn-interfaces.yang --lint 2>&1": fujitsu-otn-oducn-interfaces.yang:18: warning: imported module "fujitsu-equipment" not used fujitsu-otn-oducn-interfaces.yang:52: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-oducn-interfaces.yang:56: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-oducn-interfaces.yang:60: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-oducn-interfaces.yang:159: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-otn-oducn-interfaces.yang:196: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-otn-oducn-interfaces.yang:243: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-otn-oducn-interfaces.yang:246: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-otn-oducn-interfaces.yang:248: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-otn-oducn-interfaces.yang:251: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-otn-oducn-interfaces.yang:263: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-otn-oducn-interfaces.yang:289: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-otn-oducn-interfaces.yang:321: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-otn-oducn-interfaces.yang:349: error: RFC 8407: 4.14,4.16: statement "notification" must have a "description" substatement fujitsu-otn-oducn-interfaces.yang:350: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-otn-oducn-interfaces.yang:355: error: RFC 8407: 4.14: statement "container" must have a "description" substatement		Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: Module 'fujitsu-notification-types' not used fujitsu-otn.yang:8.3: warning(1015): import not used Warning: compare value 'ianaift:otnOdu' invalid for object 'ietf-interfaces:type type:identityref' XPath:../if:type = 'ianaift:otnOdu' fujitsu-otn-odu-interfaces.yang: line 869: warning(1052): XPath compare value invalid for YANG type Warning: revision with same date on line 34 fujitsu-port.yang:39.3: warning(1054): Revision date has already been used Warning: Module 'fujitsu-notification-types' not used fujitsu-equipment.yang:11.3: warning(1015): import not used Warning: Module 'fujitsu-equipment' not used fujitsu-otn-oducn-interfaces.yang:18.3: warning(1015): import not used
fujitsu-otn-otu-interfaces-dev@2018-08-13.yang	FAILED		fujitsu-otn-otu-interfaces.yang:270: warning: "ianaift" looks like a prefix but is not defined fujitsu-otn-otu-interfaces.yang:307: warning: explicit config statement is ignored	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-otn-otu-interfaces-dev.prod.yang --lint 2>&1": fujitsu-otn-otu-interfaces-dev.prod.yang:31: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-otu-interfaces-dev.prod.yang:35: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-otu-interfaces-dev.prod.yang:39: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-otu-interfaces-dev.prod.yang:43: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-otu-interfaces-dev.prod.yang:47: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-otu-interfaces-dev.prod.yang:51: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-otu-interfaces-dev.prod.yang:55: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-otu-interfaces-dev.prod.yang:59: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-otu-interfaces-dev.prod.yang:63: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-otu-interfaces-dev.prod.yang:67: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-otu-interfaces-dev.prod.yang:71: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement	libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-otn-otu-interfaces-dev.prod.yang 2>&1": libyang err : Invalid deviation replacing "config" property "config false" which is not present. (Path "/fujitsu-otn-otu-interfaces-dev.prod:{deviation='/if:interfaces/if:interface/otu:otu/otu:direction'}".)	Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: Module 'fujitsu-notification-types' not used fujitsu-otn.yang:8.3: warning(1015): import not used Warning: compare value 'ianaift:otnOtu' invalid for object 'ietf-interfaces:type type:identityref' XPath:../if:type = 'ianaift:otnOtu' fujitsu-otn-otu-interfaces.yang: line 270: warning(1052): XPath compare value invalid for YANG type Warning: revision with same date on line 31 fujitsu-otn-otu-interfaces-dev.prod.yang:35.3: warning(1054): Revision date has already been used
fujitsu-otn-otu-interfaces@2018-01-09.yang	FAILED		fujitsu-otn-otu-interfaces.yang:270: warning: "ianaift" looks like a prefix but is not defined fujitsu-otn-otu-interfaces.yang:307: warning: explicit config statement is ignored	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-otn-otu-interfaces.yang --lint 2>&1": fujitsu-otn-otu-interfaces.yang:46: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-otu-interfaces.yang:50: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-otu-interfaces.yang:54: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-otu-interfaces.yang:58: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-otu-interfaces.yang:62: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-otu-interfaces.yang:114: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-otn-otu-interfaces.yang:149: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-otn-otu-interfaces.yang:268: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-otn-otu-interfaces.yang:270: warning: "ianaift" looks like a prefix but is not defined fujitsu-otn-otu-interfaces.yang:277: error: keyword "config" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-otn-otu-interfaces.yang:278: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-otn-otu-interfaces.yang:298: error: RFC 8407: 4.14,4.16: statement "notification" must have a "description" substatement fujitsu-otn-otu-interfaces.yang:299: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-otn-otu-interfaces.yang:304: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-otn-otu-interfaces.yang:307: error: keyword "config" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-otn-otu-interfaces.yang:307: warning: explicit config statement is ignored fujitsu-otn-otu-interfaces.yang:308: error: keyword "type" not in canonical order (see RFC 6020, Section 12)		Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: Module 'fujitsu-notification-types' not used fujitsu-otn.yang:8.3: warning(1015): import not used Warning: compare value 'ianaift:otnOtu' invalid for object 'ietf-interfaces:type type:identityref' XPath:../if:type = 'ianaift:otnOtu' fujitsu-otn-otu-interfaces.yang: line 270: warning(1052): XPath compare value invalid for YANG type
fujitsu-otn-otucn-interfaces-dev@2018-07-26.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-otn-otucn-interfaces-dev.prod.yang --lint 2>&1": fujitsu-otn-otucn-interfaces-dev.prod.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement fujitsu-otn-otucn-interfaces-dev.prod.yang:1: error: RFC 8407: 4.8: statement "module" must have a "organization" substatement fujitsu-otn-otucn-interfaces-dev.prod.yang:1: error: RFC 8407: 4.8: statement "module" must have a "description" substatement fujitsu-otn-otucn-interfaces-dev.prod.yang:12: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-otucn-interfaces-dev.prod.yang:16: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-otucn-interfaces-dev.prod.yang:20: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement	libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-otn-otucn-interfaces-dev.prod.yang 2>&1": libyang err : Invalid deviation replacing "config" property "config false" which is not present. (Path "/fujitsu-otn-otucn-interfaces-dev.prod:{deviation='/if:interfaces/if:interface/otucn:otucn/otucn:rate'}".)	Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: Module 'fujitsu-notification-types' not used fujitsu-otn.yang:8.3: warning(1015): import not used
fujitsu-otn-otucn-interfaces@2015-05-12.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-otn-otucn-interfaces.yang --lint 2>&1": fujitsu-otn-otucn-interfaces.yang:46: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn-otucn-interfaces.yang:80: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-otn-otucn-interfaces.yang:115: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-otn-otucn-interfaces.yang:127: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-otn-otucn-interfaces.yang:159: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-otn-otucn-interfaces.yang:185: error: RFC 8407: 4.14,4.16: statement "notification" must have a "description" substatement fujitsu-otn-otucn-interfaces.yang:186: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-otn-otucn-interfaces.yang:191: error: RFC 8407: 4.14: statement "container" must have a "description" substatement		Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: Module 'fujitsu-notification-types' not used fujitsu-otn.yang:8.3: warning(1015): import not used
fujitsu-otn@2018-07-24.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-otn.yang --lint 2>&1": fujitsu-otn.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn.yang:34: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn.yang:38: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn.yang:42: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-otn.yang:53: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-otn.yang:62: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-otn.yang:71: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-otn.yang:104: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-otn.yang:155: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-otn.yang:173: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-otn.yang:191: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-otn.yang:199: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-otn.yang:267: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-otn.yang:275: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement fujitsu-otn.yang:287: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement		Warning: Module 'fujitsu-notification-types' not used fujitsu-otn.yang:8.3: warning(1015): import not used
fujitsu-performance-monitoring-dev@2018-01-29.yang	FAILED		fujitsu-performance-monitoring.yang:5: warning: imported module "ietf-yang-types" not used	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-performance-monitoring-dev.prod.yang --lint 2>&1": fujitsu-performance-monitoring-dev.prod.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement fujitsu-performance-monitoring-dev.prod.yang:1: error: RFC 8407: 4.8: statement "module" must have a "organization" substatement fujitsu-performance-monitoring-dev.prod.yang:1: error: RFC 8407: 4.8: statement "module" must have a "description" substatement fujitsu-performance-monitoring-dev.prod.yang:9: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-performance-monitoring-dev.prod.yang:13: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-performance-monitoring-dev.prod.yang:17: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-performance-monitoring-dev.prod.yang:21: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement		Warning: Module 'ietf-yang-types' not used fujitsu-performance-monitoring.yang:5.3: warning(1015): import not used
fujitsu-performance-monitoring-typedefs@2018-01-11.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-performance-monitoring-typedefs.yang --lint 2>&1": fujitsu-performance-monitoring-typedefs.yang:27: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-performance-monitoring-typedefs.yang:31: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-performance-monitoring-typedefs.yang:115: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:128: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:158: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:179: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:206: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:207: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:210: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:213: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:218: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:219: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:220: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:225: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:234: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:235: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:237: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:250: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:252: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-performance-monitoring-typedefs.yang:253: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring-typedefs.yang:255: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:257: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-performance-monitoring-typedefs.yang:258: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring-typedefs.yang:263: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:264: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:266: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:268: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:271: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:272: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-performance-monitoring-typedefs.yang:273: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring-typedefs.yang:279: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:283: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring-typedefs.yang:285: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:293: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:295: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:298: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:301: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:304: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:312: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:315: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:321: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:322: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:326: error: keyword "config" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring-typedefs.yang:330: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:364: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:365: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-performance-monitoring-typedefs.yang:369: error: keyword "config" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring-typedefs.yang:373: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
fujitsu-performance-monitoring@2018-01-11.yang	FAILED		fujitsu-performance-monitoring.yang:5: warning: imported module "ietf-yang-types" not used	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-performance-monitoring.yang --lint 2>&1": fujitsu-performance-monitoring.yang:5: warning: imported module "ietf-yang-types" not used fujitsu-performance-monitoring.yang:33: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-performance-monitoring.yang:37: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-performance-monitoring.yang:41: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-performance-monitoring.yang:45: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-performance-monitoring.yang:49: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-performance-monitoring.yang:57: error: keyword "config" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:61: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:64: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:65: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:73: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:76: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:77: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:85: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:88: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:89: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:95: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:98: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:99: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:105: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:108: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:109: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:121: error: keyword "config" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:125: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:128: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:129: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:137: error: keyword "config" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:141: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:144: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:145: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:149: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:150: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:165: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring.yang:169: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring.yang:175: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-performance-monitoring.yang:188: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) fujitsu-performance-monitoring.yang:194: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12)		Warning: Module 'ietf-yang-types' not used fujitsu-performance-monitoring.yang:5.3: warning(1015): import not used
fujitsu-physical-inventory@2018-10-05.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-physical-inventory.yang --lint 2>&1": fujitsu-physical-inventory.yang:22: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-physical-inventory.yang:28: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-physical-inventory.yang:33: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-physical-inventory.yang:81: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
fujitsu-pm-types@2018-07-03.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-pm-types.yang --lint 2>&1": fujitsu-pm-types.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-pm-types.yang:31: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-pm-types.yang:38: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-pm-types.yang:44: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-pm-types.yang:49: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-pm-types.yang:53: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-pm-types.yang:57: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-pm-types.yang:61: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-pm-types.yang:65: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-pm-types.yang:70: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-pm-types.yang:76: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-pm-types.yang:82: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-pm-types.yang:86: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-pm-types.yang:90: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-pm-types.yang:94: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-pm-types.yang:98: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-pm-types.yang:102: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-pm-types.yang:107: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:111: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:115: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:119: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:123: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:127: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:131: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:135: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:139: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:143: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:147: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:151: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:155: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:159: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:163: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:167: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:171: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:175: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:179: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:183: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:187: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:191: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:195: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:199: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:203: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:207: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:211: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:215: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:219: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:223: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:227: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:231: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:235: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:239: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:243: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:247: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:251: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:255: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:259: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:263: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:267: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:271: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:275: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:279: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:283: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:287: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:291: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:295: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:299: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:303: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:307: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:311: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:315: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:319: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:323: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:327: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:331: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:335: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:339: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:343: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:347: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:351: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:355: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:359: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:363: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:367: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:371: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:375: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:379: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:383: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:387: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:391: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:395: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:399: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:403: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:407: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:411: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:415: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:419: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:423: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:427: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:431: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:435: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:439: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:443: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:447: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:451: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:455: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:459: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:463: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:467: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:471: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:475: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:479: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:483: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:487: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:491: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:495: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:499: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:503: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:507: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:511: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:515: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:519: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:523: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:527: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:531: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:535: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:539: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:543: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:547: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:551: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:555: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:559: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:563: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:567: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:571: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:575: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:579: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:583: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:587: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:591: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:595: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:599: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:603: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:607: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:611: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:615: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:619: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:623: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:627: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:631: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:635: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:639: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:643: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:647: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:651: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:655: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:659: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:663: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:667: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:671: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:675: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:679: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:683: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:687: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:691: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:695: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:699: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:703: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:707: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:711: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:715: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:719: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:723: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:727: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:731: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:735: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:739: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:743: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:747: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:751: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:755: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:759: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:763: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:767: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:771: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:775: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:779: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:783: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:787: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:791: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:795: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:799: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:803: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:807: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:811: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:815: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:819: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:823: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:827: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:831: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:835: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:839: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:843: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:847: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:851: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:855: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:859: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:863: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:867: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:871: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:875: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:879: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:883: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:887: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:891: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:895: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:899: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:903: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:907: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:911: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:915: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:919: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:923: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:927: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:931: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:935: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:939: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:943: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:947: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:951: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:955: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:959: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:963: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:967: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:971: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:975: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:979: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:983: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:987: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:991: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:995: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:999: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1003: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1007: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1011: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1015: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1019: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1023: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1027: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1031: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1035: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1039: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1043: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1047: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1051: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1055: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1059: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1063: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1067: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1071: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1075: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1079: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1083: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1087: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1091: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1095: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1099: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1103: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1107: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1111: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1115: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1119: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1123: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1127: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1131: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1135: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1139: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1143: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1147: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1151: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1155: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1159: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1163: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1167: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1171: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1175: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1179: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1183: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1187: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1191: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1195: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1199: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1203: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1207: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1211: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1215: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1219: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1223: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1227: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1231: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1235: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1239: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1243: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1247: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1251: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement fujitsu-pm-types.yang:1255: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement		Warning: revision with same date on line 44 fujitsu-pm-types.yang:49.3: warning(1054): Revision date has already been used
fujitsu-port@2018-10-05.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-port@2018-10-05.yang --lint 2>&1": fujitsu-port@2018-10-05.yang:29: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-port@2018-10-05.yang:35: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-port@2018-10-05.yang:40: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-port@2018-10-05.yang:45: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-port@2018-10-05.yang:49: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-port@2018-10-05.yang:53: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-port@2018-10-05.yang:58: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-port@2018-10-05.yang:82: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-port@2018-10-05.yang:129: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-port@2018-10-05.yang:132: error: RFC 8407: 4.14: statement "container" must have a "description" substatement		Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-port@2018-10-05.yang 2>&1": Error: 'fujitsu-port@2018-10-05.yang' import of module 'fujitsu-physical-inventory' failed fujitsu-port@2018-10-05.yang:5.3: error(236): module not found Error: 'fujitsu-port@2018-10-05.yang' import of module 'fujitsu-entity-states' failed fujitsu-port@2018-10-05.yang:8.3: error(236): module not found Error: 'fujitsu-port@2018-10-05.yang' import of module 'fujitsu-subport' failed fujitsu-port@2018-10-05.yang:11.3: error(236): module not found Error: 'fujitsu-port@2018-10-05.yang' import of module 'fujitsu-performance-monitoring-typedefs' failed fujitsu-port@2018-10-05.yang:14.3: error(236): module not found Warning: revision with same date on line 35 fujitsu-port@2018-10-05.yang:40.3: warning(1054): Revision date has already been used Error: grouping definition for 'entity-states:oper-status' not found in module fujitsu-entity-states fujitsu-port@2018-10-05.yang:121.5: error(250): definition not found Error: grouping definition for 'entity-states:admin-status' not found in module fujitsu-entity-states fujitsu-port@2018-10-05.yang:126.5: error(250): definition not found Error: grouping definition for 'physical-inventory:PhysicalInventory' not found in module fujitsu-physical-inventory fujitsu-port@2018-10-05.yang:133.7: error(250): definition not found Error: grouping definition for 'physical-inventory:fujitsu-port-pi' not found in module fujitsu-physical-inventory fujitsu-port@2018-10-05.yang:134.7: error(250): definition not found Error: grouping definition for 'pmtypedefs:pm-info' not found in module fujitsu-performance-monitoring-typedefs fujitsu-port@2018-10-05.yang:137.5: error(250): definition not found Error: grouping definition for 'subport:subPort' not found in module fujitsu-subport fujitsu-port@2018-10-05.yang:156.7: error(250): definition not found Error: grouping 'oper-status' not found fujitsu-port@2018-10-05.yang:121.5: error(250): definition not found Error: grouping 'admin-status' not found fujitsu-port@2018-10-05.yang:126.5: error(250): definition not found Error: grouping 'PhysicalInventory' not found fujitsu-port@2018-10-05.yang:133.7: error(250): definition not found Error: grouping 'fujitsu-port-pi' not found fujitsu-port@2018-10-05.yang:134.7: error(250): definition not found Error: grouping 'pm-info' not found fujitsu-port@2018-10-05.yang:137.5: error(250): definition not found Error: grouping 'subPort' not found fujitsu-port@2018-10-05.yang:156.7: error(250): definition not found Error: object 'subPortID' not found in module fujitsu-port in Xpath target subPortID fujitsu-port@2018-10-05.yang:155.7: error(250): definition not found Error: invalid identifier in key for list 'subport' (subPortID) fujitsu-port@2018-10-05.yang:155.7: error(250): definition not found
fujitsu-powerdraw@2017-04-04.yang	FAILED		fujitsu-equipment.yang:11: warning: imported module "fujitsu-notification-types" not used	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-powerdraw.yang --lint 2>&1": fujitsu-powerdraw.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement		Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: revision with same date on line 34 fujitsu-port.yang:39.3: warning(1054): Revision date has already been used Warning: Module 'fujitsu-notification-types' not used fujitsu-equipment.yang:11.3: warning(1015): import not used
fujitsu-ppp-interface@2019-02-07.yang	FAILED		fujitsu-ppp-interface.yang:109: warning: "ianaift" looks like a prefix but is not defined	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-ppp-interface.yang --lint 2>&1": fujitsu-ppp-interface.yang:32: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ppp-interface.yang:36: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ppp-interface.yang:40: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ppp-interface.yang:100: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-ppp-interface.yang:107: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-ppp-interface.yang:109: warning: "ianaift" looks like a prefix but is not defined fujitsu-ppp-interface.yang:116: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-ppp-interface.yang:139: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-ppp-interface.yang:144: error: RFC 8407: 4.14: statement "container" must have a "description" substatement		Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: compare value 'ianaift:ppp' invalid for object 'ietf-interfaces:type type:identityref' XPath:../if:type = 'ianaift:ppp' fujitsu-ppp-interface.yang: line 109: warning(1052): XPath compare value invalid for YANG type Warning: compare value 'ianaift:ppp' invalid for object 'ietf-interfaces:type type:identityref' XPath:../if:type = 'ianaift:ppp' fujitsu-ppp-interface.yang: line 141: warning(1052): XPath compare value invalid for YANG type
fujitsu-protocols@2016-04-01.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-protocols@2016-04-01.yang --lint 2>&1": fujitsu-protocols@2016-04-01.yang:24: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
fujitsu-radius-client@2016-10-27.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-radius-client.yang 2>&1": /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-user-security.yang:9: error: module 'tailf-aaa' not found	fujitsu-user-security.yang:9: warning: imported module "tailf-aaa" not used	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-radius-client.yang --lint 2>&1": fujitsu-radius-client.yang:29: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-radius-client.yang:33: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-radius-client.yang:81: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-radius-client.yang:86: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-radius-client.yang:89: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-radius-client.yang:177: error: keyword "ordered-by" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-radius-client.yang:180: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-radius-client.yang:185: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-radius-client.yang:188: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-radius-client.yang:267: error: keyword "ordered-by" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-radius-client.yang:270: error: keyword "type" not in canonical order (see RFC 6020, Section 12)		Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-radius-client.yang 2>&1": Error: 'fujitsu-user-security.yang' import of module 'tailf-aaa' failed fujitsu-user-security.yang:9.3: error(236): module not found Warning: top-level NP container 'security' is mandatory fujitsu-user-security.yang:91.3: warning(1048): top-level object is mandatory Warning: Module 'tailf-aaa' not used fujitsu-user-security.yang:9.3: warning(1015): import not used Error: 'fujitsu-radius-client.yang' import of module 'fujitsu-user-security' failed fujitsu-radius-client.yang:8.3: error(332): imported module has errors Error: object 'security' not found in module fujitsu-radius-client in Xpath target /secu:security fujitsu-radius-client.yang:81.3: error(250): definition not found
fujitsu-rasis-utils-framework@2018-09-26.yang	FAILED		fujitsu-rasis-utils-framework.yang:5: warning: imported module "fujitsu-equipment" not used fujitsu-equipment.yang:11: warning: imported module "fujitsu-notification-types" not used	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-rasis-utils-framework.yang --lint 2>&1": fujitsu-rasis-utils-framework.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement fujitsu-rasis-utils-framework.yang:5: warning: imported module "fujitsu-equipment" not used fujitsu-rasis-utils-framework.yang:19: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-rasis-utils-framework.yang:23: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-rasis-utils-framework.yang:27: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-rasis-utils-framework.yang:31: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-rasis-utils-framework.yang:35: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-rasis-utils-framework.yang:39: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-rasis-utils-framework.yang:43: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-rasis-utils-framework.yang:47: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-rasis-utils-framework.yang:51: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-rasis-utils-framework.yang:106: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement		Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: revision with same date on line 34 fujitsu-port.yang:39.3: warning(1054): Revision date has already been used Warning: Module 'fujitsu-notification-types' not used fujitsu-equipment.yang:11.3: warning(1015): import not used Warning: Module 'fujitsu-equipment' not used fujitsu-rasis-utils-framework.yang:5.3: warning(1015): import not used
fujitsu-routing@2018-01-22.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-routing.yang 2>&1": fujitsu-routing.yang:5: error: module 'ietf-routing' not found	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-routing.yang 2>&1": fujitsu-routing.yang:36: error: node ietf-routing::routing-instance is not found fujitsu-routing.yang:39: error: "ietf-routing:routing-instance" in the path for outgoing-interface at fujitsu-routing.yang:37 is not found	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-routing.yang --lint 2>&1": fujitsu-routing.yang:27: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-routing.yang:31: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-routing.yang:36: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-routing.yang:36: error: node ietf-routing::routing-instance is not found fujitsu-routing.yang:39: error: "ietf-routing:routing-instance" in the path for outgoing-interface at fujitsu-routing.yang:37 is not found		Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-routing.yang 2>&1": Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/rt:routes/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop' fujitsu-routing.yang:36.3: error(251): definition segment not found
fujitsu-scripting-utility@2017-09-22.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-scripting-utility.yang --lint 2>&1": fujitsu-scripting-utility.yang:22: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-scripting-utility.yang:31: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement fujitsu-scripting-utility.yang:34: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-scripting-utility.yang:35: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-scripting-utility.yang:39: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-scripting-utility.yang:40: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-scripting-utility.yang:44: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-scripting-utility.yang:45: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-scripting-utility.yang:64: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-scripting-utility.yang:67: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
fujitsu-security-certificates@2018-08-30.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-security-certificates.yang 2>&1": /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-user-security.yang:9: error: module 'tailf-aaa' not found	fujitsu-user-security.yang:9: warning: imported module "tailf-aaa" not used	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-security-certificates.yang --lint 2>&1": fujitsu-security-certificates.yang:25: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-security-certificates.yang:29: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-security-certificates.yang:34: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-security-certificates.yang:38: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-security-certificates.yang:79: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-security-certificates.yang:83: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-security-certificates.yang:84: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12) fujitsu-security-certificates.yang:85: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-security-certificates.yang:104: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-security-certificates.yang:105: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12) fujitsu-security-certificates.yang:106: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-security-certificates.yang:130: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-security-certificates.yang:153: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-security-certificates.yang:172: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement		Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-security-certificates.yang 2>&1": Error: 'fujitsu-user-security.yang' import of module 'tailf-aaa' failed fujitsu-user-security.yang:9.3: error(236): module not found Warning: top-level NP container 'security' is mandatory fujitsu-user-security.yang:91.3: warning(1048): top-level object is mandatory Warning: Module 'tailf-aaa' not used fujitsu-user-security.yang:9.3: warning(1015): import not used Error: 'fujitsu-security-certificates.yang' import of module 'fujitsu-user-security' failed fujitsu-security-certificates.yang:5.3: error(332): imported module has errors Error: object 'security' not found in module fujitsu-security-certificates in Xpath target /secu:security fujitsu-security-certificates.yang:79.3: error(250): definition not found Error: Module for prefix 'secu' not found fujitsu-security-certificates.yang:145.17: error(236): module not found Error: Module for prefix 'secu' not found fujitsu-security-certificates.yang:164.17: error(236): module not found
fujitsu-shelf@2018-04-03.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-shelf.yang --lint 2>&1": fujitsu-shelf.yang:35: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-shelf.yang:40: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-shelf.yang:44: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-shelf.yang:72: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-shelf.yang:116: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-shelf.yang:121: error: keyword "units" not in canonical order (see RFC 6020, Section 12) fujitsu-shelf.yang:123: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-shelf.yang:131: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-shelf.yang:139: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-shelf.yang:151: error: keyword "key" not in canonical order (see RFC 6020, Section 12)		Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: revision with same date on line 34 fujitsu-port.yang:39.3: warning(1054): Revision date has already been used
fujitsu-slot@2018-06-26.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-slot@2018-06-26.yang --lint 2>&1": fujitsu-slot@2018-06-26.yang:36: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-slot@2018-06-26.yang:41: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-slot@2018-06-26.yang:46: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-slot@2018-06-26.yang:51: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-slot@2018-06-26.yang:55: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-slot@2018-06-26.yang:90: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-slot@2018-06-26.yang:180: error: keyword "key" not in canonical order (see RFC 6020, Section 12)		Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/fujitsu-slot@2018-06-26.yang 2>&1": Error: 'fujitsu-slot@2018-06-26.yang' import of module 'fujitsu-subslot' failed fujitsu-slot@2018-06-26.yang:5.3: error(236): module not found Error: 'fujitsu-slot@2018-06-26.yang' import of module 'fujitsu-physical-inventory' failed fujitsu-slot@2018-06-26.yang:8.3: error(236): module not found Error: 'fujitsu-slot@2018-06-26.yang' import of module 'fujitsu-entity-states' failed fujitsu-slot@2018-06-26.yang:11.3: error(236): module not found Error: 'fujitsu-slot@2018-06-26.yang' import of module 'fujitsu-performance-monitoring-typedefs' failed fujitsu-slot@2018-06-26.yang:14.3: error(236): module not found Error: grouping definition for 'entity-states:oper-status' not found in module fujitsu-entity-states fujitsu-slot@2018-06-26.yang:82.5: error(250): definition not found Error: grouping definition for 'entity-states:admin-status' not found in module fujitsu-entity-states fujitsu-slot@2018-06-26.yang:87.5: error(250): definition not found Error: grouping definition for 'physical-inventory:PhysicalInventory' not found in module fujitsu-physical-inventory fujitsu-slot@2018-06-26.yang:105.7: error(250): definition not found Error: grouping definition for 'pmtypedefs:pm-info' not found in module fujitsu-performance-monitoring-typedefs fujitsu-slot@2018-06-26.yang:176.5: error(250): definition not found Error: grouping definition for 'subslot:subslot' not found in module fujitsu-subslot fujitsu-slot@2018-06-26.yang:181.7: error(250): definition not found Error: grouping 'oper-status' not found fujitsu-slot@2018-06-26.yang:82.5: error(250): definition not found Error: grouping 'admin-status' not found fujitsu-slot@2018-06-26.yang:87.5: error(250): definition not found Error: grouping 'PhysicalInventory' not found fujitsu-slot@2018-06-26.yang:105.7: error(250): definition not found Error: grouping 'pm-info' not found fujitsu-slot@2018-06-26.yang:176.5: error(250): definition not found Error: grouping 'subslot' not found fujitsu-slot@2018-06-26.yang:181.7: error(250): definition not found Error: object 'subslotID' not found in module fujitsu-slot in Xpath target subslotID fujitsu-slot@2018-06-26.yang:180.7: error(250): definition not found Error: invalid identifier in key for list 'subslot' (subslotID) fujitsu-slot@2018-06-26.yang:180.7: error(250): definition not found
fujitsu-ssh-host-key@2015-10-14.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-ssh-host-key.yang --lint 2>&1": fujitsu-ssh-host-key.yang:24: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ssh-host-key.yang:26: error: RFC 8407: 4.14: statement "rpc" must have a "description" substatement fujitsu-ssh-host-key.yang:36: error: RFC 8407: 4.14: statement "rpc" must have a "description" substatement fujitsu-ssh-host-key.yang:54: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-ssh-host-key.yang:57: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
fujitsu-state-timer@2015-04-01.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-state-timer.yang --lint 2>&1": fujitsu-state-timer.yang:22: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-state-timer.yang:27: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement
fujitsu-subport@2018-04-03.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-subport.yang --lint 2>&1": fujitsu-subport.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-subport.yang:35: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-subport.yang:55: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-subport.yang:83: error: keyword "default" not in canonical order (see RFC 6020, Section 12)		Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used
fujitsu-subslot@2018-04-03.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-subslot.yang --lint 2>&1": fujitsu-subslot.yang:36: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-subslot.yang:41: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-subslot.yang:45: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-subslot.yang:73: error: keyword "default" not in canonical order (see RFC 6020, Section 12)		Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: revision with same date on line 34 fujitsu-port.yang:39.3: warning(1054): Revision date has already been used
fujitsu-swdl@2018-06-22.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-swdl.yang --lint 2>&1": fujitsu-swdl.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-swdl.yang:35: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-swdl.yang:40: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-swdl.yang:44: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-swdl.yang:48: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-swdl.yang:55: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-swdl.yang:59: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-swdl.yang:64: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-swdl.yang:68: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-swdl.yang:100: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-swdl.yang:258: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-swdl.yang:315: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement fujitsu-swdl.yang:347: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-swdl.yang:391: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-swdl.yang:392: error: keyword "config" not in canonical order (see RFC 6020, Section 12) fujitsu-swdl.yang:400: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-swdl.yang:401: error: keyword "config" not in canonical order (see RFC 6020, Section 12)
fujitsu-system-dev@2017-03-20.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-system-dev.prod.yang 2>&1": /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-license.yang:32: warning: the revision statements are not given in reverse chronological order /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-user-security.yang:9: error: module 'tailf-aaa' not found	fujitsu-equipment.yang:11: warning: imported module "fujitsu-notification-types" not used fujitsu-license.yang:32: warning: the revision statements are not given in reverse chronological order fujitsu-system.yang:6: warning: imported module "fujitsu-entity-states" not used fujitsu-system.yang:15: warning: imported module "ietf-yang-types" not used fujitsu-system.yang:18: warning: imported module "ietf-netconf-acm" not used fujitsu-system.yang:33: warning: imported module "fujitsu-license" not used fujitsu-user-security.yang:9: warning: imported module "tailf-aaa" not used	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-system-dev.prod.yang --lint 2>&1": fujitsu-system-dev.prod.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system-dev.prod.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement		Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-system-dev.prod.yang 2>&1": Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: revision with same date on line 34 fujitsu-port.yang:39.3: warning(1054): Revision date has already been used Warning: Module 'fujitsu-notification-types' not used fujitsu-equipment.yang:11.3: warning(1015): import not used Error: 'fujitsu-user-security.yang' import of module 'tailf-aaa' failed fujitsu-user-security.yang:9.3: error(236): module not found Warning: top-level NP container 'security' is mandatory fujitsu-user-security.yang:91.3: warning(1048): top-level object is mandatory Warning: Module 'tailf-aaa' not used fujitsu-user-security.yang:9.3: warning(1015): import not used Error: 'fujitsu-security-certificates.yang' import of module 'fujitsu-user-security' failed fujitsu-security-certificates.yang:5.3: error(332): imported module has errors Error: object 'security' not found in module fujitsu-security-certificates in Xpath target /secu:security fujitsu-security-certificates.yang:79.3: error(250): definition not found Error: Module for prefix 'secu' not found fujitsu-security-certificates.yang:145.17: error(236): module not found Error: Module for prefix 'secu' not found fujitsu-security-certificates.yang:164.17: error(236): module not found Error: 'fujitsu-system.yang' import of module 'fujitsu-security-certificates' failed fujitsu-system.yang:21.3: error(236): module not found Error: 'fujitsu-system.yang' import of module 'fujitsu-user-security' failed fujitsu-system.yang:24.3: error(332): imported module has errors Error: 'fujitsu-system.yang' import of module 'tailf-xsd-types' failed fujitsu-system.yang:27.3: error(236): module not found Warning: revision dates not in descending order fujitsu-license.yang:32.3: warning(1035): bad revision-stmt order Warning: revision with same date on line 92 fujitsu-system.yang:96.3: warning(1054): Revision date has already been used Error: typedef definition for 'xs:duration' not found in module tailf-xsd-types fujitsu-system.yang:1712.16: error(250): definition not found Error: typedef definition for 'xs:duration' not found in module tailf-xsd-types fujitsu-system.yang:1851.16: error(250): definition not found Error: Module for prefix 'secu' not found fujitsu-system.yang:1750.23: error(236): module not found Warning: Module 'fujitsu-entity-states' not used fujitsu-system.yang:6.3: warning(1015): import not used Warning: Module 'ietf-yang-types' not used fujitsu-system.yang:15.3: warning(1015): import not used Warning: Module 'ietf-netconf-acm' not used fujitsu-system.yang:18.3: warning(1015): import not used Warning: Module 'fujitsu-license' not used fujitsu-system.yang:33.3: warning(1015): import not used Error: 'fujitsu-system-dev.prod.yang' import of module 'fujitsu-system' failed fujitsu-system-dev.prod.yang:5.3: error(236): module not found Error: object 'init-filter-timer' not found in module fujitsu-system-dev.prod in Xpath target /system:init-filter-timer fujitsu-system-dev.prod.yang:42.2: error(250): definition not found Error: object 'system' not found in module fujitsu-system-dev.prod in Xpath target /system:system/system:internal-rstp-enabled fujitsu-system-dev.prod.yang:42.2: error(250): definition not found
fujitsu-system-gnmi@2018-08-02.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-system-gnmi.yang 2>&1": /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-license.yang:32: warning: the revision statements are not given in reverse chronological order /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-user-security.yang:9: error: module 'tailf-aaa' not found	fujitsu-equipment.yang:11: warning: imported module "fujitsu-notification-types" not used fujitsu-license.yang:32: warning: the revision statements are not given in reverse chronological order fujitsu-system.yang:6: warning: imported module "fujitsu-entity-states" not used fujitsu-system.yang:15: warning: imported module "ietf-yang-types" not used fujitsu-system.yang:18: warning: imported module "ietf-netconf-acm" not used fujitsu-system.yang:33: warning: imported module "fujitsu-license" not used fujitsu-user-security.yang:9: warning: imported module "tailf-aaa" not used	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-system-gnmi.yang --lint 2>&1": fujitsu-system-gnmi.yang:4: error: keyword "yang-version" not in canonical order (see RFC 7950, Section 14) fujitsu-system-gnmi.yang:36: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system-gnmi.yang:40: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system-gnmi.yang:44: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system-gnmi.yang:48: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system-gnmi.yang:53: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system-gnmi.yang:58: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-system-gnmi.yang:67: error: keyword "must" not in canonical order (see RFC 7950, Section 14) fujitsu-system-gnmi.yang:84: error: keyword "must" not in canonical order (see RFC 7950, Section 14)		Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-system-gnmi.yang 2>&1": Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: revision with same date on line 34 fujitsu-port.yang:39.3: warning(1054): Revision date has already been used Warning: Module 'fujitsu-notification-types' not used fujitsu-equipment.yang:11.3: warning(1015): import not used Error: 'fujitsu-user-security.yang' import of module 'tailf-aaa' failed fujitsu-user-security.yang:9.3: error(236): module not found Warning: top-level NP container 'security' is mandatory fujitsu-user-security.yang:91.3: warning(1048): top-level object is mandatory Warning: Module 'tailf-aaa' not used fujitsu-user-security.yang:9.3: warning(1015): import not used Error: 'fujitsu-security-certificates.yang' import of module 'fujitsu-user-security' failed fujitsu-security-certificates.yang:5.3: error(332): imported module has errors Error: object 'security' not found in module fujitsu-security-certificates in Xpath target /secu:security fujitsu-security-certificates.yang:79.3: error(250): definition not found Error: Module for prefix 'secu' not found fujitsu-security-certificates.yang:145.17: error(236): module not found Error: Module for prefix 'secu' not found fujitsu-security-certificates.yang:164.17: error(236): module not found Error: 'fujitsu-system.yang' import of module 'fujitsu-security-certificates' failed fujitsu-system.yang:21.3: error(236): module not found Error: 'fujitsu-system.yang' import of module 'fujitsu-user-security' failed fujitsu-system.yang:24.3: error(332): imported module has errors Error: 'fujitsu-system.yang' import of module 'tailf-xsd-types' failed fujitsu-system.yang:27.3: error(236): module not found Warning: revision dates not in descending order fujitsu-license.yang:32.3: warning(1035): bad revision-stmt order Warning: revision with same date on line 92 fujitsu-system.yang:96.3: warning(1054): Revision date has already been used Error: typedef definition for 'xs:duration' not found in module tailf-xsd-types fujitsu-system.yang:1712.16: error(250): definition not found Error: typedef definition for 'xs:duration' not found in module tailf-xsd-types fujitsu-system.yang:1851.16: error(250): definition not found Error: Module for prefix 'secu' not found fujitsu-system.yang:1750.23: error(236): module not found Warning: Module 'fujitsu-entity-states' not used fujitsu-system.yang:6.3: warning(1015): import not used Warning: Module 'ietf-yang-types' not used fujitsu-system.yang:15.3: warning(1015): import not used Warning: Module 'ietf-netconf-acm' not used fujitsu-system.yang:18.3: warning(1015): import not used Warning: Module 'fujitsu-license' not used fujitsu-system.yang:33.3: warning(1015): import not used Error: 'fujitsu-system-gnmi.yang' import of module 'fujitsu-system' failed fujitsu-system-gnmi.yang:6.3: error(236): module not found Error: 'fujitsu-system-gnmi.yang' import of module 'fujitsu-user-security' failed fujitsu-system-gnmi.yang:9.3: error(332): imported module has errors Error: 'fujitsu-system-gnmi.yang' import of module 'fujitsu-security-certificates' failed fujitsu-system-gnmi.yang:12.3: error(236): module not found Error: typedef definition for 'sys:tlsVersion' not found in module fujitsu-system fujitsu-system-gnmi.yang:80.14: error(250): definition not found Error: object 'system' not found in module fujitsu-system-gnmi in Xpath target /sys:system/sys:services fujitsu-system-gnmi.yang:58.3: error(250): definition not found
fujitsu-system@2019-02-07.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-system.yang 2>&1": /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-license.yang:32: warning: the revision statements are not given in reverse chronological order /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-user-security.yang:9: error: module 'tailf-aaa' not found	fujitsu-system.yang:6: warning: imported module "fujitsu-entity-states" not used fujitsu-system.yang:15: warning: imported module "ietf-yang-types" not used fujitsu-system.yang:18: warning: imported module "ietf-netconf-acm" not used fujitsu-system.yang:33: warning: imported module "fujitsu-license" not used fujitsu-equipment.yang:11: warning: imported module "fujitsu-notification-types" not used fujitsu-license.yang:32: warning: the revision statements are not given in reverse chronological order fujitsu-user-security.yang:9: warning: imported module "tailf-aaa" not used	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-system.yang --lint 2>&1": fujitsu-system.yang:4: error: keyword "yang-version" not in canonical order (see RFC 7950, Section 14) fujitsu-system.yang:6: warning: imported module "fujitsu-entity-states" not used fujitsu-system.yang:15: warning: imported module "ietf-yang-types" not used fujitsu-system.yang:18: warning: imported module "ietf-netconf-acm" not used fujitsu-system.yang:33: warning: imported module "fujitsu-license" not used fujitsu-system.yang:57: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:61: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:65: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:69: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:73: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:78: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:83: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:87: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:92: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:96: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:100: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:105: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:110: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:114: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:118: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:122: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:126: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:131: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:135: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:139: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:143: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:147: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:152: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:156: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:160: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:164: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:168: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:172: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:179: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:183: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:187: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:192: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:197: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:202: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:206: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:210: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:215: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:219: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:224: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:228: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:232: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:236: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:240: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:244: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:248: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:252: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:257: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:261: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:265: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:269: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:273: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:277: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:281: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:285: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:289: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:293: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:297: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-system.yang:447: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-system.yang:467: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-system.yang:664: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-system.yang:699: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-system.yang:734: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-system.yang:754: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-system.yang:822: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-system.yang:900: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-system.yang:976: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-system.yang:1091: error: keyword "default" not in canonical order (see RFC 7950, Section 14) fujitsu-system.yang:1120: error: keyword "default" not in canonical order, expected "type" (see RFC 7950, Section 14) fujitsu-system.yang:1121: error: keyword "type" not in canonical order (see RFC 7950, Section 14) fujitsu-system.yang:1582: error: keyword "must" not in canonical order (see RFC 7950, Section 14) fujitsu-system.yang:1640: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-system.yang:1679: error: keyword "status" not in canonical order, expected "type" (see RFC 7950, Section 14) fujitsu-system.yang:1680: error: keyword "max-elements" not in canonical order (see RFC 7950, Section 14) fujitsu-system.yang:1681: error: keyword "type" not in canonical order (see RFC 7950, Section 14) fujitsu-system.yang:1682: error: keyword "ordered-by" not in canonical order (see RFC 7950, Section 14) fujitsu-system.yang:1690: error: keyword "status" not in canonical order, expected "type" (see RFC 7950, Section 14) fujitsu-system.yang:1691: error: keyword "max-elements" not in canonical order (see RFC 7950, Section 14) fujitsu-system.yang:1692: error: keyword "type" not in canonical order (see RFC 7950, Section 14) fujitsu-system.yang:1693: error: keyword "ordered-by" not in canonical order (see RFC 7950, Section 14) fujitsu-system.yang:1732: error: keyword "presence" not in canonical order (see RFC 7950, Section 14) fujitsu-system.yang:1745: error: keyword "presence" not in canonical order (see RFC 7950, Section 14) fujitsu-system.yang:1746: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement fujitsu-system.yang:1770: error: keyword "max-elements" not in canonical order, expected "type" (see RFC 7950, Section 14) fujitsu-system.yang:1771: error: keyword "type" not in canonical order (see RFC 7950, Section 14) fujitsu-system.yang:1778: error: keyword "max-elements" not in canonical order, expected "type" (see RFC 7950, Section 14) fujitsu-system.yang:1779: error: keyword "type" not in canonical order (see RFC 7950, Section 14) fujitsu-system.yang:1850: error: keyword "description" not in canonical order, expected "type" (see RFC 7950, Section 14) fujitsu-system.yang:1851: error: keyword "type" not in canonical order (see RFC 7950, Section 14) fujitsu-system.yang:1882: error: keyword "max-elements" not in canonical order, expected "type" (see RFC 7950, Section 14) fujitsu-system.yang:1883: error: keyword "type" not in canonical order (see RFC 7950, Section 14) fujitsu-system.yang:1894: error: keyword "max-elements" not in canonical order, expected "type" (see RFC 7950, Section 14) fujitsu-system.yang:1895: error: keyword "type" not in canonical order (see RFC 7950, Section 14) fujitsu-system.yang:1903: error: keyword "max-elements" not in canonical order, expected "type" (see RFC 7950, Section 14) fujitsu-system.yang:1904: error: keyword "type" not in canonical order (see RFC 7950, Section 14) fujitsu-system.yang:1916: error: keyword "max-elements" not in canonical order, expected "type" (see RFC 7950, Section 14) fujitsu-system.yang:1917: error: keyword "type" not in canonical order (see RFC 7950, Section 14) fujitsu-system.yang:1932: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-system.yang:1934: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-system.yang:1958: error: keyword "units" not in canonical order (see RFC 7950, Section 14) fujitsu-system.yang:1977: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-system.yang:2034: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-system.yang:2048: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-system.yang:2087: error: keyword "description" not in canonical order, expected "type" (see RFC 7950, Section 14) fujitsu-system.yang:2088: error: keyword "type" not in canonical order (see RFC 7950, Section 14) fujitsu-system.yang:2099: error: keyword "description" not in canonical order, expected "type" (see RFC 7950, Section 14) fujitsu-system.yang:2100: error: keyword "type" not in canonical order (see RFC 7950, Section 14) fujitsu-system.yang:2125: error: keyword "config" not in canonical order (see RFC 7950, Section 14) fujitsu-system.yang:2126: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-system.yang:2128: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-system.yang:2158: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-system.yang:2179: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-system.yang:2180: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-system.yang:2198: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-system.yang:2199: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-system.yang:2209: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-system.yang:2210: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-system.yang:2229: error: keyword "max-elements" not in canonical order, expected "type" (see RFC 7950, Section 14) fujitsu-system.yang:2230: error: keyword "type" not in canonical order (see RFC 7950, Section 14) fujitsu-system.yang:2239: error: keyword "max-elements" not in canonical order, expected "type" (see RFC 7950, Section 14) fujitsu-system.yang:2240: error: keyword "type" not in canonical order (see RFC 7950, Section 14) fujitsu-system.yang:2252: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-system.yang:2253: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-system.yang:2282: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-system.yang:2287: error: RFC 8407: 4.14: statement "rpc" must have a "description" substatement fujitsu-system.yang:2297: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-system.yang:2307: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-system.yang:2314: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-system.yang:2320: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement		Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-system.yang 2>&1": Warning: Module 'fujitsu-notification-types' not used fujitsu-entity-states.yang:8.3: warning(1015): import not used Warning: revision with same date on line 34 fujitsu-port.yang:39.3: warning(1054): Revision date has already been used Warning: Module 'fujitsu-notification-types' not used fujitsu-equipment.yang:11.3: warning(1015): import not used Error: 'fujitsu-user-security.yang' import of module 'tailf-aaa' failed fujitsu-user-security.yang:9.3: error(236): module not found Warning: top-level NP container 'security' is mandatory fujitsu-user-security.yang:91.3: warning(1048): top-level object is mandatory Warning: Module 'tailf-aaa' not used fujitsu-user-security.yang:9.3: warning(1015): import not used Error: 'fujitsu-security-certificates.yang' import of module 'fujitsu-user-security' failed fujitsu-security-certificates.yang:5.3: error(332): imported module has errors Error: object 'security' not found in module fujitsu-security-certificates in Xpath target /secu:security fujitsu-security-certificates.yang:79.3: error(250): definition not found Error: Module for prefix 'secu' not found fujitsu-security-certificates.yang:145.17: error(236): module not found Error: Module for prefix 'secu' not found fujitsu-security-certificates.yang:164.17: error(236): module not found Error: 'fujitsu-system.yang' import of module 'fujitsu-security-certificates' failed fujitsu-system.yang:21.3: error(236): module not found Error: 'fujitsu-system.yang' import of module 'fujitsu-user-security' failed fujitsu-system.yang:24.3: error(332): imported module has errors Error: 'fujitsu-system.yang' import of module 'tailf-xsd-types' failed fujitsu-system.yang:27.3: error(236): module not found Warning: revision dates not in descending order fujitsu-license.yang:32.3: warning(1035): bad revision-stmt order Warning: revision with same date on line 92 fujitsu-system.yang:96.3: warning(1054): Revision date has already been used Error: typedef definition for 'xs:duration' not found in module tailf-xsd-types fujitsu-system.yang:1712.16: error(250): definition not found Error: typedef definition for 'xs:duration' not found in module tailf-xsd-types fujitsu-system.yang:1851.16: error(250): definition not found Error: Module for prefix 'secu' not found fujitsu-system.yang:1750.23: error(236): module not found Warning: Module 'fujitsu-entity-states' not used fujitsu-system.yang:6.3: warning(1015): import not used Warning: Module 'ietf-yang-types' not used fujitsu-system.yang:15.3: warning(1015): import not used Warning: Module 'ietf-netconf-acm' not used fujitsu-system.yang:18.3: warning(1015): import not used Warning: Module 'fujitsu-license' not used fujitsu-system.yang:33.3: warning(1015): import not used
fujitsu-tacacs-plus-client@2018-08-02.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-tacacs-plus-client.yang 2>&1": /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-user-security.yang:9: error: module 'tailf-aaa' not found	fujitsu-user-security.yang:9: warning: imported module "tailf-aaa" not used	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-tacacs-plus-client.yang --lint 2>&1": fujitsu-tacacs-plus-client.yang:4: error: keyword "yang-version" not in canonical order (see RFC 7950, Section 14) fujitsu-tacacs-plus-client.yang:12: warning: imported module "fujitsu-user-security-typedefs" not used fujitsu-tacacs-plus-client.yang:33: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-tacacs-plus-client.yang:37: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-tacacs-plus-client.yang:41: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-tacacs-plus-client.yang:45: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-tacacs-plus-client.yang:49: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-tacacs-plus-client.yang:58: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-tacacs-plus-client.yang:62: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-tacacs-plus-client.yang:85: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement fujitsu-tacacs-plus-client.yang:90: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-tacacs-plus-client.yang:93: error: keyword "key" not in canonical order (see RFC 7950, Section 14) fujitsu-tacacs-plus-client.yang:158: error: keyword "ordered-by" not in canonical order, expected "type" (see RFC 7950, Section 14) fujitsu-tacacs-plus-client.yang:161: error: keyword "type" not in canonical order (see RFC 7950, Section 14) fujitsu-tacacs-plus-client.yang:166: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-tacacs-plus-client.yang:169: error: keyword "key" not in canonical order (see RFC 7950, Section 14) fujitsu-tacacs-plus-client.yang:226: error: keyword "ordered-by" not in canonical order, expected "type" (see RFC 7950, Section 14) fujitsu-tacacs-plus-client.yang:229: error: keyword "type" not in canonical order (see RFC 7950, Section 14) fujitsu-tacacs-plus-client.yang:235: error: keyword "description" not in canonical order, expected "type" (see RFC 7950, Section 14) fujitsu-tacacs-plus-client.yang:236: error: keyword "type" not in canonical order (see RFC 7950, Section 14) fujitsu-tacacs-plus-client.yang:237: error: keyword "max-elements" not in canonical order (see RFC 7950, Section 14) fujitsu-tacacs-plus-client.yang:238: error: keyword "must" not in canonical order (see RFC 7950, Section 14)		Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-tacacs-plus-client.yang 2>&1": Error: 'fujitsu-user-security.yang' import of module 'tailf-aaa' failed fujitsu-user-security.yang:9.3: error(236): module not found Warning: top-level NP container 'security' is mandatory fujitsu-user-security.yang:91.3: warning(1048): top-level object is mandatory Warning: Module 'tailf-aaa' not used fujitsu-user-security.yang:9.3: warning(1015): import not used Error: 'fujitsu-tacacs-plus-client.yang' import of module 'fujitsu-user-security' failed fujitsu-tacacs-plus-client.yang:9.3: error(332): imported module has errors Error: Module for prefix 'secu' not found fujitsu-tacacs-plus-client.yang:238.17: error(236): module not found Error: object 'security' not found in module fujitsu-tacacs-plus-client in Xpath target /secu:security fujitsu-tacacs-plus-client.yang:85.3: error(250): definition not found
fujitsu-threshold-crossover-types@2018-02-06.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-threshold-crossover-types.yang --lint 2>&1": fujitsu-threshold-crossover-types.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-threshold-crossover-types.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-threshold-crossover-types.yang:34: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-threshold-crossover-types.yang:38: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-threshold-crossover-types.yang:42: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-threshold-crossover-types.yang:46: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
fujitsu-user-security-dev@2017-08-28.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-user-security-dev.prod.yang 2>&1": /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-user-security.yang:9: error: module 'tailf-aaa' not found	fujitsu-user-security.yang:9: warning: imported module "tailf-aaa" not used	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-user-security-dev.prod.yang --lint 2>&1": fujitsu-user-security-dev.prod.yang:27: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security-dev.prod.yang:32: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security-dev.prod.yang:36: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement		Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-user-security-dev.prod.yang 2>&1": Error: 'fujitsu-user-security.yang' import of module 'tailf-aaa' failed fujitsu-user-security.yang:9.3: error(236): module not found Warning: top-level NP container 'security' is mandatory fujitsu-user-security.yang:91.3: warning(1048): top-level object is mandatory Warning: Module 'tailf-aaa' not used fujitsu-user-security.yang:9.3: warning(1015): import not used Error: 'fujitsu-user-security-dev.prod.yang' import of module 'fujitsu-user-security' failed fujitsu-user-security-dev.prod.yang:6.3: error(332): imported module has errors Warning: revision with same date on line 32 fujitsu-user-security-dev.prod.yang:36.3: warning(1054): Revision date has already been used Error: object 'usersec' not found in module fujitsu-user-security-dev.prod in Xpath target /fuser:usersec/fuser:idle-timeout fujitsu-user-security-dev.prod.yang:41.2: error(250): definition not found
fujitsu-user-security-typedefs@2018-12-07.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-user-security-typedefs.yang --lint 2>&1": fujitsu-user-security-typedefs.yang:23: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security-typedefs.yang:27: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security-typedefs.yang:31: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security-typedefs.yang:35: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security-typedefs.yang:39: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security-typedefs.yang:43: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security-typedefs.yang:47: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security-typedefs.yang:51: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security-typedefs.yang:55: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security-typedefs.yang:59: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security-typedefs.yang:63: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security-typedefs.yang:67: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security-typedefs.yang:71: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security-typedefs.yang:73: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-user-security-typedefs.yang:75: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs.yang:78: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs.yang:84: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-user-security-typedefs.yang:86: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs.yang:89: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs.yang:126: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security-typedefs.yang:135: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs.yang:216: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security-typedefs.yang:225: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs.yang:243: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs.yang:262: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs.yang:302: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs.yang:314: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs.yang:317: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs.yang:320: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs.yang:348: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-user-security-typedefs.yang:354: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-user-security-typedefs.yang:356: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs.yang:359: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs.yang:362: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs.yang:368: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-user-security-typedefs.yang:370: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs.yang:373: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs.yang:379: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement fujitsu-user-security-typedefs.yang:381: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs.yang:384: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security-typedefs.yang:387: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
fujitsu-user-security@2018-07-18.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-user-security.yang 2>&1": fujitsu-user-security.yang:9: error: module 'tailf-aaa' not found	fujitsu-user-security.yang:9: warning: imported module "tailf-aaa" not used	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-user-security.yang --lint 2>&1": fujitsu-user-security.yang:9: warning: imported module "tailf-aaa" not used fujitsu-user-security.yang:31: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security.yang:35: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security.yang:39: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security.yang:43: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security.yang:47: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security.yang:52: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security.yang:56: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security.yang:60: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security.yang:64: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security.yang:68: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security.yang:73: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security.yang:77: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security.yang:81: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security.yang:85: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security.yang:89: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-user-security.yang:91: error: RFC 8407: 4.10: top-level node security must not be mandatory fujitsu-user-security.yang:94: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-user-security.yang:97: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security.yang:98: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:101: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:104: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security.yang:105: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:106: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:110: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:111: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security.yang:112: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:113: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:115: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:116: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security.yang:117: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:118: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:120: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:121: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security.yang:122: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:125: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:128: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-user-security.yang:131: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security.yang:132: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:133: error: keyword "min-elements" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:134: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:135: error: keyword "ordered-by" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:139: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security.yang:140: error: keyword "max-elements" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:141: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:142: error: keyword "ordered-by" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:179: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security.yang:182: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:183: error: keyword "default" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:186: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security.yang:187: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:192: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security.yang:193: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:204: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security.yang:205: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:210: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security.yang:211: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:216: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security.yang:217: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:228: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security.yang:229: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:234: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security.yang:235: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:240: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security.yang:241: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:250: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:251: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:254: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:262: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:263: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:264: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security.yang:265: error: keyword "must" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:268: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:270: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:271: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security.yang:272: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:274: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:275: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security.yang:276: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:278: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:279: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security.yang:280: error: keyword "when" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:281: error: keyword "config" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:282: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:284: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:285: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security.yang:286: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:288: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:289: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security.yang:290: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:292: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:293: error: keyword "status" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security.yang:294: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:300: error: keyword "must" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:303: error: RFC 8407: 4.14: statement "list" must have a "description" substatement fujitsu-user-security.yang:305: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:306: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:310: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:313: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:316: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:317: error: keyword "must" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-user-security.yang:320: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:323: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement fujitsu-user-security.yang:337: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:343: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:349: error: keyword "mandatory" not in canonical order (see RFC 6020, Section 12) fujitsu-user-security.yang:355: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-user-security.yang:358: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement		Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-user-security.yang 2>&1": Error: 'fujitsu-user-security.yang' import of module 'tailf-aaa' failed fujitsu-user-security.yang:9.3: error(236): module not found Warning: top-level NP container 'security' is mandatory fujitsu-user-security.yang:91.3: warning(1048): top-level object is mandatory Warning: Module 'tailf-aaa' not used fujitsu-user-security.yang:9.3: warning(1015): import not used
fujitsu-ycable-protection-dev@2018-01-04.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-ycable-protection-dev.prod.yang --lint 2>&1": fujitsu-ycable-protection-dev.prod.yang:27: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement
fujitsu-ycable-protection@2018-05-08.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" fujitsu-ycable-protection.yang --lint 2>&1": fujitsu-ycable-protection.yang:23: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ycable-protection.yang:27: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ycable-protection.yang:32: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ycable-protection.yang:36: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ycable-protection.yang:40: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement fujitsu-ycable-protection.yang:45: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-ycable-protection.yang:63: error: keyword "units" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-ycable-protection.yang:64: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-ycable-protection.yang:77: error: RFC 8407: 4.14: statement "container" must have a "description" substatement fujitsu-ycable-protection.yang:79: error: keyword "units" not in canonical order, expected "type" (see RFC 6020, Section 12) fujitsu-ycable-protection.yang:80: error: keyword "type" not in canonical order (see RFC 6020, Section 12) fujitsu-ycable-protection.yang:125: error: keyword "key" not in canonical order (see RFC 6020, Section 12) fujitsu-ycable-protection.yang:130: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement fujitsu-ycable-protection.yang:133: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-ycable-protection.yang:136: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-ycable-protection.yang:139: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-ycable-protection.yang:154: error: RFC 8407: 4.14: statement "rpc" must have a "description" substatement fujitsu-ycable-protection.yang:172: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-ycable-protection.yang:175: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-ycable-protection.yang:178: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement fujitsu-ycable-protection.yang:181: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
iana-afn-safi@2013-07-04.yang	PASSED
iana-crypt-hash@2014-08-06.yang	PASSED
iana-if-type@2018-06-28.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" iana-if-type.yang --lint 2>&1": iana-if-type.yang:50: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement iana-if-type.yang:54: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement iana-if-type.yang:58: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement iana-if-type.yang:62: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement iana-if-type.yang:66: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement iana-if-type.yang:70: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement iana-if-type.yang:74: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement iana-if-type.yang:78: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement iana-if-type.yang:82: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement iana-if-type.yang:86: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement iana-if-type.yang:90: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement iana-if-type.yang:94: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement iana-if-type.yang:98: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement iana-if-type.yang:102: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement iana-if-type.yang:119: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:123: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:127: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:131: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:135: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:161: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:165: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:169: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:184: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:188: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:192: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:196: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:201: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:206: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:247: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:251: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:261: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:310: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:345: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:358: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:363: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:367: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:371: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:384: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:388: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:392: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:408: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement iana-if-type.yang:412: error: RFC 8407: 4.14: statement "identity" must have a "description" substatement
ietf-access-control-list-dev@2018-06-07.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/ietf-access-control-list-dev.yang 2>&1": ietf-access-control-list-dev.yang:6: error: module 'ietf-access-control-list' not found	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" ietf-access-control-list-dev.yang 2>&1": ietf-access-control-list-dev.yang:37: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:42: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:47: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:57: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:67: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:72: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:75: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:78: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:81: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:84: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:87: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:90: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:93: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:96: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:99: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:102: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:105: error: node ietf-access-control-list::access-lists is not found	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" ietf-access-control-list-dev.yang --lint 2>&1": ietf-access-control-list-dev.yang:27: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-access-control-list-dev.yang:31: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-access-control-list-dev.yang:35: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-access-control-list-dev.yang:37: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:42: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:47: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:57: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:67: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:72: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:75: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:78: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:81: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:84: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:87: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:90: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:93: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:96: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:99: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:102: error: node ietf-access-control-list::access-lists is not found ietf-access-control-list-dev.yang:105: error: node ietf-access-control-list::access-lists is not found		Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/ietf-access-control-list-dev.yang 2>&1": Error: 'ietf-access-control-list-dev.yang' import of module 'ietf-access-control-list' failed ietf-access-control-list-dev.yang:6.3: error(236): module not found Error: object 'access-lists' not found in module ietf-access-control-list-dev in Xpath target /acl:access-lists/acl:acl ietf-access-control-list-dev.yang:108.2: error(250): definition not found Error: object 'access-lists' not found in module ietf-access-control-list-dev in Xpath target /acl:access-lists/acl:acl/acl:access-list-entries/acl:ace ietf-access-control-list-dev.yang:108.2: error(250): definition not found Error: object 'access-lists' not found in module ietf-access-control-list-dev in Xpath target /acl:access-lists/acl:acl/acl:acl-name ietf-access-control-list-dev.yang:108.2: error(250): definition not found Error: object 'access-lists' not found in module ietf-access-control-list-dev in Xpath target /acl:access-lists/acl:acl/acl:access-list-entries/acl:ace/acl:rule-name ietf-access-control-list-dev.yang:108.2: error(250): definition not found Error: object 'access-lists' not found in module ietf-access-control-list-dev in Xpath target /acl:access-lists/acl:acl/acl:access-list-entries/acl:ace/acl:actions/acl:packet-handling ietf-access-control-list-dev.yang:108.2: error(250): definition not found Error: object 'access-lists' not found in module ietf-access-control-list-dev in Xpath target /acl:access-lists/acl:acl/acl:access-list-entries/acl:ace/acl:matches/acl:ace-type/acl:ace-ip/acl:ace-ip-version/acl:ace-ipv4/acl:destination-ipv4-network ietf-access-control-list-dev.yang:108.2: error(250): definition not found Error: object 'access-lists' not found in module ietf-access-control-list-dev in Xpath target /acl:access-lists/acl:acl/acl:access-list-entries/acl:ace/acl:matches/acl:ace-type/acl:ace-ip/acl:ace-ip-version/acl:ace-ipv6/acl:destination-ipv6-network ietf-access-control-list-dev.yang:108.2: error(250): definition not found Error: object 'access-lists' not found in module ietf-access-control-list-dev in Xpath target /acl:access-lists/acl:acl/acl:access-list-entries/acl:ace/acl:matches/acl:ace-type/acl:ace-ip/acl:ace-ip-version/acl:ace-ipv6/acl:flow-label ietf-access-control-list-dev.yang:108.2: error(250): definition not found Error: object 'access-lists' not found in module ietf-access-control-list-dev in Xpath target /acl:access-lists/acl:acl/acl:access-list-entries/acl:ace/acl:matches/acl:ace-type/acl:ace-ip/acl:dscp ietf-access-control-list-dev.yang:108.2: error(250): definition not found Error: object 'access-lists' not found in module ietf-access-control-list-dev in Xpath target /acl:access-lists/acl:acl/acl:access-list-entries/acl:ace/acl:matches/acl:ace-type/acl:ace-ip/acl:source-port-range ietf-access-control-list-dev.yang:108.2: error(250): definition not found Error: object 'access-lists' not found in module ietf-access-control-list-dev in Xpath target /acl:access-lists/acl:acl/acl:access-list-entries/acl:ace/acl:matches/acl:ace-type/acl:ace-ip/acl:destination-port-range ietf-access-control-list-dev.yang:108.2: error(250): definition not found Error: object 'access-lists' not found in module ietf-access-control-list-dev in Xpath target /acl:access-lists/acl:acl/acl:access-list-entries/acl:ace/acl:matches/acl:ace-type/acl:ace-eth ietf-access-control-list-dev.yang:108.2: error(250): definition not found Error: object 'access-lists' not found in module ietf-access-control-list-dev in Xpath target /acl:access-lists/acl:acl/acl:access-list-entries/acl:ace/acl:matches/acl:input-interface ietf-access-control-list-dev.yang:108.2: error(250): definition not found Error: object 'access-lists' not found in module ietf-access-control-list-dev in Xpath target /acl:access-lists/acl:acl/acl:access-list-entries/acl:ace/acl:matches/acl:absolute-time ietf-access-control-list-dev.yang:108.2: error(250): definition not found Error: object 'access-lists' not found in module ietf-access-control-list-dev in Xpath target /acl:access-lists/acl:acl/acl:acl-type ietf-access-control-list-dev.yang:108.2: error(250): definition not found Error: object 'access-lists' not found in module ietf-access-control-list-dev in Xpath target /acl:access-lists/acl:acl/acl:access-list-entries/acl:ace/acl:ace-oper-data ietf-access-control-list-dev.yang:108.2: error(250): definition not found Error: object 'access-lists' not found in module ietf-access-control-list-dev in Xpath target /acl:access-lists/acl:acl/acl:acl-oper-data ietf-access-control-list-dev.yang:108.2: error(250): definition not found
ietf-access-control-list@2015-03-17.yang	FAILED		Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" ietf-access-control-list.yang 2>&1": ietf-access-control-list.yang:136: error: there is already a child node to "matches" at ietf-access-control-list.yang:119 with the name "destination-network" defined at ietf-access-control-list.yang:133 (at /usr/local/share/yang/modules/ietf/ietf-packet-fields.yang:264) ietf-access-control-list.yang:136: error: there is already a child node to "matches" at ietf-access-control-list.yang:119 with the name "source-network" defined at ietf-access-control-list.yang:133 (at /usr/local/share/yang/modules/ietf/ietf-packet-fields.yang:277) ietf-access-control-list.yang:136: error: there is already a child node to "ace-ip" at ietf-access-control-list.yang:126 with the name "destination-network" defined at ietf-access-control-list.yang:133 (at /usr/local/share/yang/modules/ietf/ietf-packet-fields.yang:264) ietf-access-control-list.yang:136: error: there is already a child node to "ace-ip" at ietf-access-control-list.yang:126 with the name "source-network" defined at ietf-access-control-list.yang:133 (at /usr/local/share/yang/modules/ietf/ietf-packet-fields.yang:277) ietf-access-control-list.yang:147: error: grouping "metadata" not found in module "ietf-packet-fields"	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" ietf-access-control-list.yang --lint 2>&1": ietf-access-control-list.yang:136: error: there is already a child node to "matches" at ietf-access-control-list.yang:119 with the name "destination-network" defined at ietf-access-control-list.yang:133 (at /usr/local/share/yang/modules/ietf/ietf-packet-fields.yang:264) ietf-access-control-list.yang:136: error: there is already a child node to "matches" at ietf-access-control-list.yang:119 with the name "source-network" defined at ietf-access-control-list.yang:133 (at /usr/local/share/yang/modules/ietf/ietf-packet-fields.yang:277) ietf-access-control-list.yang:136: error: there is already a child node to "ace-ip" at ietf-access-control-list.yang:126 with the name "destination-network" defined at ietf-access-control-list.yang:133 (at /usr/local/share/yang/modules/ietf/ietf-packet-fields.yang:264) ietf-access-control-list.yang:136: error: there is already a child node to "ace-ip" at ietf-access-control-list.yang:126 with the name "source-network" defined at ietf-access-control-list.yang:133 (at /usr/local/share/yang/modules/ietf/ietf-packet-fields.yang:277) ietf-access-control-list.yang:147: error: grouping "metadata" not found in module "ietf-packet-fields"
ietf-alarms-dev@2017-02-01.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/all_modules/ietf-alarms-dev@2017-02-01.yang 2>&1": ./ietf-alarms@2019-09-11.yang:933: warning: The XPath expression references an undefined node: the node 'notify-status-changes' from module 'ietf-alarms' (in node 'control' from 'ietf-alarms') is not found ietf-alarms-dev@2017-02-01.yang:16: error: node 'shelved-alarms' not found ietf-alarms-dev@2017-02-01.yang:20: error: node 'cleared' not found ietf-alarms-dev@2017-02-01.yang:24: error: node 'cleared-not-closed' not found ietf-alarms-dev@2017-02-01.yang:28: error: node 'cleared-closed' not found ietf-alarms-dev@2017-02-01.yang:32: error: node 'not-cleared-closed' not found ietf-alarms-dev@2017-02-01.yang:36: error: node 'not-cleared-not-closed' not found ietf-alarms-dev@2017-02-01.yang:45: error: node 'related-alarms' not found ietf-alarms-dev@2017-02-01.yang:49: error: node 'impacted-resources' not found ietf-alarms-dev@2017-02-01.yang:53: error: node 'root-cause-resources' not found ietf-alarms-dev@2017-02-01.yang:65: error: node 'last-operator-state' not found ietf-alarms-dev@2017-02-01.yang:68: error: node 'last-operator' not found ietf-alarms-dev@2017-02-01.yang:72: error: node 'last-operator-text' not found ietf-alarms-dev@2017-02-01.yang:75: error: node 'last-operator-action' not found ietf-alarms-dev@2017-02-01.yang:82: error: node 'operator-action' not found ietf-alarms-dev@2017-02-01.yang:86: error: node 'compress' not found ietf-alarms-dev@2017-02-01.yang:90: error: node 'compress-alarms' not found ietf-alarms-dev@2017-02-01.yang:94: error: node 'set-operator-state' not found ietf-alarms-dev@2017-02-01.yang:98: error: node 'purge-alarms' not found ietf-alarms-dev@2017-02-01.yang:102: error: node 'max-alarm-history' not found	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" ietf-alarms-dev@2017-02-01.yang 2>&1": ietf-alarms-dev@2017-02-01.yang:16: error: node ietf-alarms::shelved-alarms is not found ietf-alarms-dev@2017-02-01.yang:20: error: node ietf-alarms::cleared is not found ietf-alarms-dev@2017-02-01.yang:24: error: node ietf-alarms::cleared-not-closed is not found ietf-alarms-dev@2017-02-01.yang:28: error: node ietf-alarms::cleared-closed is not found ietf-alarms-dev@2017-02-01.yang:32: error: node ietf-alarms::not-cleared-closed is not found ietf-alarms-dev@2017-02-01.yang:36: error: node ietf-alarms::not-cleared-not-closed is not found ietf-alarms-dev@2017-02-01.yang:45: error: node ietf-alarms::related-alarms is not found ietf-alarms-dev@2017-02-01.yang:49: error: node ietf-alarms::impacted-resources is not found ietf-alarms-dev@2017-02-01.yang:53: error: node ietf-alarms::root-cause-resources is not found ietf-alarms-dev@2017-02-01.yang:65: error: node ietf-alarms::last-operator-state is not found ietf-alarms-dev@2017-02-01.yang:68: error: node ietf-alarms::last-operator is not found ietf-alarms-dev@2017-02-01.yang:72: error: node ietf-alarms::last-operator-text is not found ietf-alarms-dev@2017-02-01.yang:75: error: node ietf-alarms::last-operator-action is not found ietf-alarms-dev@2017-02-01.yang:82: error: node ietf-alarms::operator-action is not found ietf-alarms-dev@2017-02-01.yang:86: error: node ietf-alarms::compress is not found ietf-alarms-dev@2017-02-01.yang:90: error: node ietf-alarms::compress-alarms is not found ietf-alarms-dev@2017-02-01.yang:94: error: node ietf-alarms::set-operator-state is not found ietf-alarms-dev@2017-02-01.yang:98: error: node ietf-alarms::purge-alarms is not found ietf-alarms-dev@2017-02-01.yang:102: error: node ietf-alarms::max-alarm-history is not found	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" ietf-alarms-dev@2017-02-01.yang --lint 2>&1": ietf-alarms-dev@2017-02-01.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement ietf-alarms-dev@2017-02-01.yang:1: error: RFC 8407: 4.8: statement "module" must have a "organization" substatement ietf-alarms-dev@2017-02-01.yang:1: error: RFC 8407: 4.8: statement "module" must have a "description" substatement ietf-alarms-dev@2017-02-01.yang:16: error: node ietf-alarms::shelved-alarms is not found ietf-alarms-dev@2017-02-01.yang:20: error: node ietf-alarms::cleared is not found ietf-alarms-dev@2017-02-01.yang:24: error: node ietf-alarms::cleared-not-closed is not found ietf-alarms-dev@2017-02-01.yang:28: error: node ietf-alarms::cleared-closed is not found ietf-alarms-dev@2017-02-01.yang:32: error: node ietf-alarms::not-cleared-closed is not found ietf-alarms-dev@2017-02-01.yang:36: error: node ietf-alarms::not-cleared-not-closed is not found ietf-alarms-dev@2017-02-01.yang:45: error: node ietf-alarms::related-alarms is not found ietf-alarms-dev@2017-02-01.yang:49: error: node ietf-alarms::impacted-resources is not found ietf-alarms-dev@2017-02-01.yang:53: error: node ietf-alarms::root-cause-resources is not found ietf-alarms-dev@2017-02-01.yang:65: error: node ietf-alarms::last-operator-state is not found ietf-alarms-dev@2017-02-01.yang:68: error: node ietf-alarms::last-operator is not found ietf-alarms-dev@2017-02-01.yang:72: error: node ietf-alarms::last-operator-text is not found ietf-alarms-dev@2017-02-01.yang:75: error: node ietf-alarms::last-operator-action is not found ietf-alarms-dev@2017-02-01.yang:82: error: node ietf-alarms::operator-action is not found ietf-alarms-dev@2017-02-01.yang:86: error: node ietf-alarms::compress is not found ietf-alarms-dev@2017-02-01.yang:90: error: node ietf-alarms::compress-alarms is not found ietf-alarms-dev@2017-02-01.yang:94: error: node ietf-alarms::set-operator-state is not found ietf-alarms-dev@2017-02-01.yang:98: error: node ietf-alarms::purge-alarms is not found ietf-alarms-dev@2017-02-01.yang:102: error: node ietf-alarms::max-alarm-history is not found	libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang /var/yang/all_modules/ietf-alarms-dev@2017-02-01.yang 2>&1": libyang err : Deviation(s) target node "/alarms:alarms/alarms:control/alarms:shelved-alarms" from module "ietf-alarms-dev" was not found. (Path "/ietf-alarms:{deviation='/alarms:alarms/alarms:control/alarms:shelved-alarms'}".) libyang err : Deviation(s) target node "/alarms:alarms/alarms:summary/alarms:cleared" from module "ietf-alarms-dev" was not found. (Path "/ietf-alarms:{deviation='/alarms:alarms/alarms:summary/alarms:cleared'}".) libyang err : Deviation(s) target node "/alarms:alarms/alarms:summary/alarms:cleared-not-closed" from module "ietf-alarms-dev" was not found. (Path "/ietf-alarms:{deviation='/alarms:alarms/alarms:summary/alarms:cleared-not-closed'}".) libyang err : Deviation(s) target node "/alarms:alarms/alarms:summary/alarms:cleared-closed" from module "ietf-alarms-dev" was not found. (Path "/ietf-alarms:{deviation='/alarms:alarms/alarms:summary/alarms:cleared-closed'}".) libyang err : Deviation(s) target node "/alarms:alarms/alarms:summary/alarms:not-cleared-closed" from module "ietf-alarms-dev" was not found. (Path "/ietf-alarms:{deviation='/alarms:alarms/alarms:summary/alarms:not-cleared-closed'}".) libyang err : Deviation(s) target node "/alarms:alarms/alarms:summary/alarms:not-cleared-not-closed" from module "ietf-alarms-dev" was not found. (Path "/ietf-alarms:{deviation='/alarms:alarms/alarms:summary/alarms:not-cleared-not-closed'}".) libyang err : Deviation(s) target node "/alarms:alarms/alarms:control/alarms:max-alarm-history" from module "ietf-alarms-dev" was not found. (Path "/ietf-alarms:{deviation='/alarms:alarms/alarms:control/alarms:max-alarm-history'}".) libyang err : Deviation(s) target node "/alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:related-alarms" from module "ietf-alarms-dev" was not found. (Path "/ietf-alarms:{deviation='/alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:related-alarms'}".) libyang err : Deviation(s) target node "/alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:impacted-resources" from module "ietf-alarms-dev" was not found. (Path "/ietf-alarms:{deviation='/alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:impacted-resources'}".) libyang err : Deviation(s) target node "/alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:root-cause-resources" from module "ietf-alarms-dev" was not found. (Path "/ietf-alarms:{deviation='/alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:root-cause-resources'}".) libyang err : Deviation(s) target node "/alarms:purge-alarms" from module "ietf-alarms-dev" was not found. (Path "/ietf-alarms:{deviation='/alarms:purge-alarms'}".) libyang err : Deviation(s) target node "/alarms:set-operator-state" from module "ietf-alarms-dev" was not found. (Path "/ietf-alarms:{deviation='/alarms:set-operator-state'}".) libyang err : Deviation(s) target node "/alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:last-operator-state" from module "ietf-alarms-dev" was not found. (Path "/ietf-alarms:{deviation='/alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:last-operator-state'}".) libyang err : Deviation(s) target node "/alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:last-operator" from module "ietf-alarms-dev" was not found. (Path "/ietf-alarms:{deviation='/alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:last-operator'}".) libyang err : Deviation(s) target node "/alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:last-operator-text" from module "ietf-alarms-dev" was not found. (Path "/ietf-alarms:{deviation='/alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:last-operator-text'}".) libyang err : Deviation(s) target node "/alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:last-operator-action" from module "ietf-alarms-dev" was not found. (Path "/ietf-alarms:{deviation='/alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:last-operator-action'}".) libyang err : Deviation(s) target node "/alarms:compress-alarms" from module "ietf-alarms-dev" was not found. (Path "/ietf-alarms:{deviation='/alarms:compress-alarms'}".) libyang err : Deviation(s) target node "/alarms:operator-action" from module "ietf-alarms-dev" was not found. (Path "/ietf-alarms:{deviation='/alarms:operator-action'}".) libyang err : Deviation(s) target node "/alarms:compress" from module "ietf-alarms-dev" was not found. (Path "/ietf-alarms:{deviation='/alarms:compress'}".)	Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/ietf-alarms-dev@2017-02-01.yang 2>&1": Error: 'ietf-alarms-dev@2017-02-01.yang' import of module 'ietf-alarms' failed ietf-alarms-dev@2017-02-01.yang:5.5: error(236): module not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:control/alarms:shelved-alarms ietf-alarms-dev@2017-02-01.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:summary/alarms:cleared ietf-alarms-dev@2017-02-01.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:summary/alarms:cleared-not-closed ietf-alarms-dev@2017-02-01.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:summary/alarms:cleared-closed ietf-alarms-dev@2017-02-01.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:summary/alarms:not-cleared-closed ietf-alarms-dev@2017-02-01.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:summary/alarms:not-cleared-not-closed ietf-alarms-dev@2017-02-01.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:alt-resource ietf-alarms-dev@2017-02-01.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:related-alarms ietf-alarms-dev@2017-02-01.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:impacted-resources ietf-alarms-dev@2017-02-01.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:root-cause-resources ietf-alarms-dev@2017-02-01.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:is-cleared ietf-alarms-dev@2017-02-01.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:status-change ietf-alarms-dev@2017-02-01.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:last-operator-state ietf-alarms-dev@2017-02-01.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:last-operator ietf-alarms-dev@2017-02-01.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:last-operator-text ietf-alarms-dev@2017-02-01.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:last-operator-action ietf-alarms-dev@2017-02-01.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:alarm-list/alarms:alarm/alarms:operator-action ietf-alarms-dev@2017-02-01.yang:110.2: error(250): definition not found Error: object 'operator-action' not found in module ietf-alarms-dev in Xpath target /alarms:operator-action ietf-alarms-dev@2017-02-01.yang:110.2: error(250): definition not found Error: object 'compress' not found in module ietf-alarms-dev in Xpath target /alarms:compress ietf-alarms-dev@2017-02-01.yang:110.2: error(250): definition not found Error: object 'compress-alarms' not found in module ietf-alarms-dev in Xpath target /alarms:compress-alarms ietf-alarms-dev@2017-02-01.yang:110.2: error(250): definition not found Error: object 'set-operator-state' not found in module ietf-alarms-dev in Xpath target /alarms:set-operator-state ietf-alarms-dev@2017-02-01.yang:110.2: error(250): definition not found Error: object 'purge-alarms' not found in module ietf-alarms-dev in Xpath target /alarms:purge-alarms ietf-alarms-dev@2017-02-01.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:control/alarms:max-alarm-history ietf-alarms-dev@2017-02-01.yang:110.2: error(250): definition not found Error: object 'alarms' not found in module ietf-alarms-dev in Xpath target /alarms:alarms/alarms:control/alarms:notify-status-changes ietf-alarms-dev@2017-02-01.yang:110.2: error(250): definition not found
ietf-alarms@2015-05-04.yang	PASSED
ietf-inet-types@2013-07-15.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" ietf-inet-types@2013-07-15.yang --lint 2>&1": ietf-inet-types@2013-07-15.yang:361: error: keyword "length" not in canonical order (see RFC 6020, Section 12)
ietf-interfaces-dev@2018-12-03.yang	FAILED		ietf-interfaces-dev.prod.yang:5: warning: imported module "fujitsu-equipment" not used /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/fujitsu-equipment.yang:11: warning: imported module "fujitsu-notification-types" not used	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" ietf-interfaces-dev.prod.yang --lint 2>&1": ietf-interfaces-dev.prod.yang:5: warning: imported module "fujitsu-equipment" not used ietf-interfaces-dev.prod.yang:29: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-interfaces-dev.prod.yang:33: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-interfaces-dev.prod.yang:37: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-interfaces-dev.prod.yang:41: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-interfaces-dev.prod.yang:45: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-interfaces-dev.prod.yang:49: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-interfaces-dev.prod.yang:53: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-interfaces-dev.prod.yang:57: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-interfaces-dev.prod.yang:61: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-interfaces-dev.prod.yang:65: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-interfaces-dev.prod.yang:69: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-interfaces-dev.prod.yang:73: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-interfaces-dev.prod.yang:77: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-interfaces-dev.prod.yang:81: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-interfaces-dev.prod.yang:85: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-interfaces-dev.prod.yang:89: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-interfaces-dev.prod.yang:93: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-interfaces-dev.prod.yang:97: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement		Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/standards/ietf-interfaces-dev.prod.yang 2>&1": Error: 'ietf-interfaces-dev.prod.yang' import of module 'fujitsu-equipment' failed ietf-interfaces-dev.prod.yang:5.3: error(236): module not found Error: Got 'semicolon', Expected: left brace ietf-interfaces-dev.prod.yang:109.16: error(245): wrong token type Error: Expected: body statement ietf-interfaces-dev.prod.yang:111.2: error(244): EOF reached Warning: Module 'fujitsu-equipment' not used ietf-interfaces-dev.prod.yang:5.3: warning(1015): import not used Warning: Module 'ietf-interfaces' not used ietf-interfaces-dev.prod.yang:8.3: warning(1015): import not used
ietf-interfaces@2014-05-08.yang	PASSED WITH WARNINGS			ietf-interfaces@2014-05-08.yang:243: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement ietf-interfaces@2014-05-08.yang:246: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-ip-dev@2019-02-07.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" ietf-ip-dev.yang --lint 2>&1": ietf-ip-dev.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-ip-dev.yang:34: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-ip-dev.yang:38: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-ip-dev.yang:42: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-ip-dev.yang:59: error: keyword "description" not in canonical order (see RFC 6020, Section 12) ietf-ip-dev.yang:67: error: keyword "description" not in canonical order (see RFC 6020, Section 12)
ietf-ip@2014-06-16.yang	PASSED
ietf-ipv4-unicast-routing-dev@2017-02-21.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/all_modules/ietf-ipv4-unicast-routing-dev@2017-02-21.yang 2>&1": ietf-ipv4-unicast-routing-dev@2017-02-21.yang:41: error: node 'routing-instance' not found ietf-ipv4-unicast-routing-dev@2017-02-21.yang:48: error: node 'fib-route' not found ietf-ipv4-unicast-routing-dev@2017-02-21.yang:52: error: node 'fib-route' not found ietf-ipv4-unicast-routing-dev@2017-02-21.yang:56: error: node 'fib-route' not found ietf-ipv4-unicast-routing-dev@2017-02-21.yang:60: error: node 'routing-instance' not found	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" ietf-ipv4-unicast-routing-dev@2017-02-21.yang 2>&1": ietf-ipv4-unicast-routing-dev@2017-02-21.yang:11: warning: imported module "ietf-ipv4-unicast-routing" not used ietf-ipv4-unicast-routing-dev@2017-02-21.yang:42: error: node ietf-routing::routing-instance is not found ietf-ipv4-unicast-routing-dev@2017-02-21.yang:48: error: node ietf-routing::fib-route is not found ietf-ipv4-unicast-routing-dev@2017-02-21.yang:52: error: node ietf-routing::fib-route is not found ietf-ipv4-unicast-routing-dev@2017-02-21.yang:56: error: node ietf-routing::fib-route is not found ietf-ipv4-unicast-routing-dev@2017-02-21.yang:62: error: node ietf-routing::routing-instance is not found	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" ietf-ipv4-unicast-routing-dev@2017-02-21.yang --lint 2>&1": ietf-ipv4-unicast-routing-dev@2017-02-21.yang:11: warning: imported module "ietf-ipv4-unicast-routing" not used ietf-ipv4-unicast-routing-dev@2017-02-21.yang:35: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-ipv4-unicast-routing-dev@2017-02-21.yang:42: error: node ietf-routing::routing-instance is not found ietf-ipv4-unicast-routing-dev@2017-02-21.yang:48: error: node ietf-routing::fib-route is not found ietf-ipv4-unicast-routing-dev@2017-02-21.yang:52: error: node ietf-routing::fib-route is not found ietf-ipv4-unicast-routing-dev@2017-02-21.yang:56: error: node ietf-routing::fib-route is not found ietf-ipv4-unicast-routing-dev@2017-02-21.yang:62: error: node ietf-routing::routing-instance is not found	libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang /var/yang/all_modules/ietf-ipv4-unicast-routing-dev@2017-02-21.yang 2>&1": libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/rt:static-routes/v4ur:ipv4/v4ur:route" from module "ietf-ipv4-unicast-routing-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/rt:static-routes/v4ur:ipv4/v4ur:route'}".) libyang err : Deviation(s) target node "/rt:fib-route/rt:input/rt:destination-address/v4ur:address" from module "ietf-ipv4-unicast-routing-dev" was not found. (Path "/ietf-routing:{deviation='/rt:fib-route/rt:input/rt:destination-address/v4ur:address'}".) libyang err : Deviation(s) target node "/rt:fib-route/rt:output/rt:route/v4ur:destination-prefix" from module "ietf-ipv4-unicast-routing-dev" was not found. (Path "/ietf-routing:{deviation='/rt:fib-route/rt:output/rt:route/v4ur:destination-prefix'}".) libyang err : Deviation(s) target node "/rt:fib-route/rt:output/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop/v4ur:next-hop-address" from module "ietf-ipv4-unicast-routing-dev" was not found. (Path "/ietf-routing:{deviation='/rt:fib-route/rt:output/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop/v4ur:next-hop-address'}".) libyang err : Deviation(s) target node "/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/rt:routes/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop/v4ur:next-hop-address" from module "ietf-ipv4-unicast-routing-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/rt:routes/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop/v4ur:next-hop-address'}".)	Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/ietf-ipv4-unicast-routing-dev@2017-02-21.yang 2>&1": Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/rt:static-routes/v4ur:ipv4/v4ur:route' ietf-ipv4-unicast-routing-dev@2017-02-21.yang:66.2: error(251): definition segment not found Error: object 'fib-route' not found in module ietf-routing in Xpath target /rt:fib-route/rt:input/rt:destination-address/v4ur:address ietf-ipv4-unicast-routing-dev@2017-02-21.yang:66.2: error(250): definition not found Error: object 'fib-route' not found in module ietf-routing in Xpath target /rt:fib-route/rt:output/rt:route/v4ur:destination-prefix ietf-ipv4-unicast-routing-dev@2017-02-21.yang:66.2: error(250): definition not found Error: object 'fib-route' not found in module ietf-routing in Xpath target /rt:fib-route/rt:output/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop/v4ur:next-hop-address ietf-ipv4-unicast-routing-dev@2017-02-21.yang:66.2: error(250): definition not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/rt:routes/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop/v4ur:next-hop-address' ietf-ipv4-unicast-routing-dev@2017-02-21.yang:66.2: error(251): definition segment not found Warning: Module 'ietf-ipv4-unicast-routing' not used ietf-ipv4-unicast-routing-dev@2017-02-21.yang:11.3: warning(1015): import not used
ietf-ipv4-unicast-routing@2015-05-25.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/all_modules/ietf-ipv4-unicast-routing@2015-05-25.yang 2>&1": ietf-ipv4-unicast-routing@2015-05-25.yang:103: error: node 'routing-instance' not found ietf-ipv4-unicast-routing@2015-05-25.yang:103: error: node 'routing-protocols' not found ietf-ipv4-unicast-routing@2015-05-25.yang:103: error: node 'routing-protocol' not found ietf-ipv4-unicast-routing@2015-05-25.yang:103: error: node 'static-routes' not found ietf-ipv4-unicast-routing@2015-05-25.yang:149: error: node 'fib-route' not found ietf-ipv4-unicast-routing@2015-05-25.yang:149: error: node 'input' not found ietf-ipv4-unicast-routing@2015-05-25.yang:149: error: node 'destination-address' not found ietf-ipv4-unicast-routing@2015-05-25.yang:164: error: node 'output' not found ietf-ipv4-unicast-routing@2015-05-25.yang:164: error: node 'route' not found ietf-ipv4-unicast-routing@2015-05-25.yang:179: error: node 'next-hop' not found ietf-ipv4-unicast-routing@2015-05-25.yang:179: error: node 'next-hop-options' not found ietf-ipv4-unicast-routing@2015-05-25.yang:179: error: node 'simple-next-hop' not found	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" ietf-ipv4-unicast-routing@2015-05-25.yang 2>&1": ietf-ipv4-unicast-routing@2015-05-25.yang:104: error: node ietf-routing::routing-instance is not found ietf-ipv4-unicast-routing@2015-05-25.yang:149: error: node ietf-routing::fib-route is not found ietf-ipv4-unicast-routing@2015-05-25.yang:164: error: node ietf-routing::fib-route is not found ietf-ipv4-unicast-routing@2015-05-25.yang:180: error: node ietf-routing::fib-route is not found	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" ietf-ipv4-unicast-routing@2015-05-25.yang --lint 2>&1": ietf-ipv4-unicast-routing@2015-05-25.yang:104: error: node ietf-routing::routing-instance is not found ietf-ipv4-unicast-routing@2015-05-25.yang:149: error: node ietf-routing::fib-route is not found ietf-ipv4-unicast-routing@2015-05-25.yang:164: error: node ietf-routing::fib-route is not found ietf-ipv4-unicast-routing@2015-05-25.yang:180: error: node ietf-routing::fib-route is not found	libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang /var/yang/all_modules/ietf-ipv4-unicast-routing@2015-05-25.yang 2>&1": libyang err : Augment target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/rt:static-routes" from module "ietf-ipv4-unicast-routing" was not found. (Path "/ietf-ipv4-unicast-routing:{augment='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/rt:static-routes'}".) libyang err : Augment target node "/rt:fib-route/rt:input/rt:destination-address" from module "ietf-ipv4-unicast-routing" was not found. (Path "/ietf-ipv4-unicast-routing:{augment='/rt:fib-route/rt:input/rt:destination-address'}".) libyang err : Augment target node "/rt:fib-route/rt:output/rt:route" from module "ietf-ipv4-unicast-routing" was not found. (Path "/ietf-ipv4-unicast-routing:{augment='/rt:fib-route/rt:output/rt:route'}".) libyang err : Augment target node "/rt:fib-route/rt:output/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop" from module "ietf-ipv4-unicast-routing" was not found. (Path "/ietf-ipv4-unicast-routing:{augment='/rt:fib-route/rt:output/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop'}".)	Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/ietf-ipv4-unicast-routing@2015-05-25.yang 2>&1": Error: object 'fib-route' not found in module ietf-routing in Xpath target /rt:fib-route/rt:input/rt:destination-address ietf-ipv4-unicast-routing@2015-05-25.yang:149.6: error(250): definition not found Error: object 'fib-route' not found in module ietf-routing in Xpath target /rt:fib-route/rt:output/rt:route ietf-ipv4-unicast-routing@2015-05-25.yang:164.6: error(250): definition not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/rt:static-routes' ietf-ipv4-unicast-routing@2015-05-25.yang:103.6: error(251): definition segment not found Error: object 'fib-route' not found in module ietf-routing in Xpath target /rt:fib-route/rt:output/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop ietf-ipv4-unicast-routing@2015-05-25.yang:179.6: error(250): definition not found
ietf-ipv6-unicast-routing-dev@2017-02-21.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/all_modules/ietf-ipv6-unicast-routing-dev@2017-02-21.yang 2>&1": ietf-ipv6-unicast-routing-dev@2017-02-21.yang:41: error: node 'routing-instance' not found ietf-ipv6-unicast-routing-dev@2017-02-21.yang:48: error: node 'fib-route' not found ietf-ipv6-unicast-routing-dev@2017-02-21.yang:52: error: node 'fib-route' not found ietf-ipv6-unicast-routing-dev@2017-02-21.yang:56: error: node 'fib-route' not found ietf-ipv6-unicast-routing-dev@2017-02-21.yang:60: error: node 'routing-instance' not found	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" ietf-ipv6-unicast-routing-dev@2017-02-21.yang 2>&1": ietf-ipv6-unicast-routing-dev@2017-02-21.yang:11: warning: imported module "ietf-ipv6-unicast-routing" not used ietf-ipv6-unicast-routing-dev@2017-02-21.yang:42: error: node ietf-routing::routing-instance is not found ietf-ipv6-unicast-routing-dev@2017-02-21.yang:48: error: node ietf-routing::fib-route is not found ietf-ipv6-unicast-routing-dev@2017-02-21.yang:52: error: node ietf-routing::fib-route is not found ietf-ipv6-unicast-routing-dev@2017-02-21.yang:56: error: node ietf-routing::fib-route is not found ietf-ipv6-unicast-routing-dev@2017-02-21.yang:62: error: node ietf-routing::routing-instance is not found	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" ietf-ipv6-unicast-routing-dev@2017-02-21.yang --lint 2>&1": ietf-ipv6-unicast-routing-dev@2017-02-21.yang:11: warning: imported module "ietf-ipv6-unicast-routing" not used ietf-ipv6-unicast-routing-dev@2017-02-21.yang:35: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-ipv6-unicast-routing-dev@2017-02-21.yang:42: error: node ietf-routing::routing-instance is not found ietf-ipv6-unicast-routing-dev@2017-02-21.yang:48: error: node ietf-routing::fib-route is not found ietf-ipv6-unicast-routing-dev@2017-02-21.yang:52: error: node ietf-routing::fib-route is not found ietf-ipv6-unicast-routing-dev@2017-02-21.yang:56: error: node ietf-routing::fib-route is not found ietf-ipv6-unicast-routing-dev@2017-02-21.yang:62: error: node ietf-routing::routing-instance is not found	libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang /var/yang/all_modules/ietf-ipv6-unicast-routing-dev@2017-02-21.yang 2>&1": libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/rt:static-routes/v6ur:ipv6/v6ur:route" from module "ietf-ipv6-unicast-routing-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/rt:static-routes/v6ur:ipv6/v6ur:route'}".) libyang err : Deviation(s) target node "/rt:fib-route/rt:input/rt:destination-address/v6ur:address" from module "ietf-ipv6-unicast-routing-dev" was not found. (Path "/ietf-routing:{deviation='/rt:fib-route/rt:input/rt:destination-address/v6ur:address'}".) libyang err : Deviation(s) target node "/rt:fib-route/rt:output/rt:route/v6ur:destination-prefix" from module "ietf-ipv6-unicast-routing-dev" was not found. (Path "/ietf-routing:{deviation='/rt:fib-route/rt:output/rt:route/v6ur:destination-prefix'}".) libyang err : Deviation(s) target node "/rt:fib-route/rt:output/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop/v6ur:next-hop-address" from module "ietf-ipv6-unicast-routing-dev" was not found. (Path "/ietf-routing:{deviation='/rt:fib-route/rt:output/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop/v6ur:next-hop-address'}".) libyang err : Deviation(s) target node "/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/rt:routes/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop/v6ur:next-hop-address" from module "ietf-ipv6-unicast-routing-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/rt:routes/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop/v6ur:next-hop-address'}".)	Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/ietf-ipv6-unicast-routing-dev@2017-02-21.yang 2>&1": Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/rt:static-routes/v6ur:ipv6/v6ur:route' ietf-ipv6-unicast-routing-dev@2017-02-21.yang:65.2: error(251): definition segment not found Error: object 'fib-route' not found in module ietf-routing in Xpath target /rt:fib-route/rt:input/rt:destination-address/v6ur:address ietf-ipv6-unicast-routing-dev@2017-02-21.yang:65.2: error(250): definition not found Error: object 'fib-route' not found in module ietf-routing in Xpath target /rt:fib-route/rt:output/rt:route/v6ur:destination-prefix ietf-ipv6-unicast-routing-dev@2017-02-21.yang:65.2: error(250): definition not found Error: object 'fib-route' not found in module ietf-routing in Xpath target /rt:fib-route/rt:output/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop/v6ur:next-hop-address ietf-ipv6-unicast-routing-dev@2017-02-21.yang:65.2: error(250): definition not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/rt:routes/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop/v6ur:next-hop-address' ietf-ipv6-unicast-routing-dev@2017-02-21.yang:65.2: error(251): definition segment not found Warning: Module 'ietf-ipv6-unicast-routing' not used ietf-ipv6-unicast-routing-dev@2017-02-21.yang:11.3: warning(1015): import not used
ietf-ipv6-unicast-routing@2015-05-25.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/all_modules/ietf-ipv6-unicast-routing@2015-05-25.yang 2>&1": ietf-ipv6-unicast-routing@2015-05-25.yang:505: error: node 'routing-instance' not found ietf-ipv6-unicast-routing@2015-05-25.yang:505: error: node 'routing-protocols' not found ietf-ipv6-unicast-routing@2015-05-25.yang:505: error: node 'routing-protocol' not found ietf-ipv6-unicast-routing@2015-05-25.yang:505: error: node 'static-routes' not found ietf-ipv6-unicast-routing@2015-05-25.yang:551: error: node 'fib-route' not found ietf-ipv6-unicast-routing@2015-05-25.yang:551: error: node 'input' not found ietf-ipv6-unicast-routing@2015-05-25.yang:551: error: node 'destination-address' not found ietf-ipv6-unicast-routing@2015-05-25.yang:566: error: node 'output' not found ietf-ipv6-unicast-routing@2015-05-25.yang:566: error: node 'route' not found ietf-ipv6-unicast-routing@2015-05-25.yang:581: error: node 'next-hop' not found ietf-ipv6-unicast-routing@2015-05-25.yang:581: error: node 'next-hop-options' not found ietf-ipv6-unicast-routing@2015-05-25.yang:581: error: node 'simple-next-hop' not found	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" ietf-ipv6-unicast-routing@2015-05-25.yang 2>&1": ietf-ipv6-unicast-routing@2015-05-25.yang:506: error: node ietf-routing::routing-instance is not found ietf-ipv6-unicast-routing@2015-05-25.yang:551: error: node ietf-routing::fib-route is not found ietf-ipv6-unicast-routing@2015-05-25.yang:566: error: node ietf-routing::fib-route is not found ietf-ipv6-unicast-routing@2015-05-25.yang:582: error: node ietf-routing::fib-route is not found	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" ietf-ipv6-unicast-routing@2015-05-25.yang --lint 2>&1": ietf-ipv6-unicast-routing@2015-05-25.yang:506: error: node ietf-routing::routing-instance is not found ietf-ipv6-unicast-routing@2015-05-25.yang:551: error: node ietf-routing::fib-route is not found ietf-ipv6-unicast-routing@2015-05-25.yang:566: error: node ietf-routing::fib-route is not found ietf-ipv6-unicast-routing@2015-05-25.yang:582: error: node ietf-routing::fib-route is not found	libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang /var/yang/all_modules/ietf-ipv6-unicast-routing@2015-05-25.yang 2>&1": libyang err : Augment target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/rt:static-routes" from module "ietf-ipv6-unicast-routing" was not found. (Path "/ietf-ipv6-unicast-routing:{augment='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/rt:static-routes'}".) libyang err : Augment target node "/rt:fib-route/rt:input/rt:destination-address" from module "ietf-ipv6-unicast-routing" was not found. (Path "/ietf-ipv6-unicast-routing:{augment='/rt:fib-route/rt:input/rt:destination-address'}".) libyang err : Augment target node "/rt:fib-route/rt:output/rt:route" from module "ietf-ipv6-unicast-routing" was not found. (Path "/ietf-ipv6-unicast-routing:{augment='/rt:fib-route/rt:output/rt:route'}".) libyang err : Augment target node "/rt:fib-route/rt:output/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop" from module "ietf-ipv6-unicast-routing" was not found. (Path "/ietf-ipv6-unicast-routing:{augment='/rt:fib-route/rt:output/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop'}".)	Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/ietf-ipv6-unicast-routing@2015-05-25.yang 2>&1": Error: object 'fib-route' not found in module ietf-routing in Xpath target /rt:fib-route/rt:input/rt:destination-address ietf-ipv6-unicast-routing@2015-05-25.yang:551.6: error(250): definition not found Error: object 'fib-route' not found in module ietf-routing in Xpath target /rt:fib-route/rt:output/rt:route ietf-ipv6-unicast-routing@2015-05-25.yang:566.6: error(250): definition not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/rt:static-routes' ietf-ipv6-unicast-routing@2015-05-25.yang:505.6: error(251): definition segment not found Error: object 'fib-route' not found in module ietf-routing in Xpath target /rt:fib-route/rt:output/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop ietf-ipv6-unicast-routing@2015-05-25.yang:581.6: error(250): definition not found
ietf-key-chain@2015-02-24.yang	PASSED
ietf-netconf-acm@2012-02-22.yang	FAILED	ietf-netconf-acm@2012-02-22.yang:103:16: warning: illegal character after \ ietf-netconf-acm@2012-02-22.yang:144:18: warning: illegal character after \	ietf-netconf-acm@2012-02-22.yang:103: warning: the escape sequence "\*" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning ietf-netconf-acm@2012-02-22.yang:144: warning: the escape sequence "\*" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning	ietf-netconf-acm@2012-02-22.yang:103: warning: the escape sequence "\*" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning ietf-netconf-acm@2012-02-22.yang:144: warning: the escape sequence "\*" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning	libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang /var/yang/all_modules/ietf-netconf-acm@2012-02-22.yang 2>&1": libyang err : Double-quoted string unknown special character '\*'. (Line number 103.) libyang err : Parsing module "ietf-netconf-acm" failed.
ietf-netconf-monitoring@2010-10-04.yang	PASSED WITH WARNINGS			ietf-netconf-monitoring@2010-10-04.yang:54: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement ietf-netconf-monitoring@2010-10-04.yang:55: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement ietf-netconf-monitoring@2010-10-04.yang:56: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement ietf-netconf-monitoring@2010-10-04.yang:384: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement
ietf-netconf-notifications@2012-02-06.yang	FAILED	ietf-netconf-notifications@2012-02-06.yang:286: warning: The XPath expression references an undefined node: the node 'confirm-event' from module 'ietf-netconf-notifications' is not found ietf-netconf-notifications@2012-02-06.yang:286: warning: The XPath expression references an undefined node: the node 'confirm-event' from module 'ietf-netconf-notifications' is not found ietf-netconf-notifications@2012-02-06.yang:286: warning: The XPath expression references an undefined node: the node 'confirm-event' from module 'ietf-netconf-notifications' is not found	ietf-netconf-notifications@2012-02-06.yang:286: warning: node "ietf-netconf-notifications::confirm-event" is not found in module "ietf-netconf-notifications"	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" ietf-netconf-notifications@2012-02-06.yang --lint 2>&1": ietf-netconf-notifications@2012-02-06.yang:95: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement ietf-netconf-notifications@2012-02-06.yang:286: warning: node "ietf-netconf-notifications::confirm-event" is not found in module "ietf-netconf-notifications"	libyang warn: Schema node "confirm-event" for parent "" not found; in expr "../confirm-event" with context node "/ietf-netconf-notifications:netconf-confirmed-commit".	Warning: no parent found in XPath expr '../confirm-event != 'timeout'' ietf-netconf-notifications@2012-02-06.yang:286.12: warning(1031): no parent node available
ietf-netconf-with-defaults@2011-06-01.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" ietf-netconf-with-defaults@2011-06-01.yang --lint 2>&1": ietf-netconf-with-defaults@2011-06-01.yang:56: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) ietf-netconf-with-defaults@2011-06-01.yang:59: error: keyword "type" not in canonical order (see RFC 6020, Section 12) ietf-netconf-with-defaults@2011-06-01.yang:97: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) ietf-netconf-with-defaults@2011-06-01.yang:101: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
ietf-netconf@2011-06-01.yang	PASSED
ietf-ospf-dev@2017-07-19.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/all_modules/ietf-ospf-dev@2017-07-19.yang 2>&1": ietf-ospf-dev@2017-07-19.yang:54: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:65: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:75: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:85: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:95: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:105: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:115: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:125: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:135: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:145: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:151: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:157: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:161: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:165: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:169: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:173: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:177: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:181: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:185: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:189: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:193: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:197: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:201: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:205: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:209: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:213: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:217: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:221: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:225: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:230: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:234: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:238: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:242: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:246: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:251: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:255: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:259: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:263: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:267: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:271: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:275: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:279: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:284: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:290: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:294: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:298: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:302: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:306: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:310: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:314: error: node 'routing-instance' not found ietf-ospf-dev@2017-07-19.yang:320: error: node 'routing-instance' not found	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" ietf-ospf-dev@2017-07-19.yang 2>&1": ietf-ospf-dev@2017-07-19.yang:5: warning: imported module "tailf-common" not used ietf-ospf-dev@2017-07-19.yang:9: warning: imported module "ietf-inet-types" not used ietf-ospf-dev@2017-07-19.yang:17: warning: imported module "ietf-ospf" not used ietf-ospf-dev@2017-07-19.yang:54: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:65: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:75: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:85: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:95: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:105: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:115: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:125: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:135: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:145: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:151: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:157: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:161: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:165: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:169: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:173: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:177: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:181: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:185: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:189: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:193: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:197: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:201: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:205: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:209: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:213: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:217: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:221: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:225: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:230: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:234: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:238: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:242: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:246: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:251: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:255: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:259: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:263: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:267: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:271: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:275: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:279: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:284: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:290: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:294: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:298: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:302: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:306: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:310: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:314: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:320: error: node ietf-routing::routing-instance is not found	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" ietf-ospf-dev@2017-07-19.yang --lint 2>&1": ietf-ospf-dev@2017-07-19.yang:5: warning: imported module "tailf-common" not used ietf-ospf-dev@2017-07-19.yang:9: warning: imported module "ietf-inet-types" not used ietf-ospf-dev@2017-07-19.yang:17: warning: imported module "ietf-ospf" not used ietf-ospf-dev@2017-07-19.yang:44: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-ospf-dev@2017-07-19.yang:49: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-ospf-dev@2017-07-19.yang:54: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:65: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:75: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:85: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:95: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:105: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:115: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:125: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:135: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:145: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:151: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:157: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:161: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:165: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:169: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:173: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:177: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:181: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:185: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:189: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:193: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:197: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:201: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:205: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:209: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:213: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:217: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:221: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:225: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:230: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:234: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:238: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:242: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:246: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:251: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:255: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:259: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:263: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:267: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:271: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:275: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:279: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:284: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:290: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:294: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:298: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:302: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:306: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:310: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:314: error: node ietf-routing::routing-instance is not found ietf-ospf-dev@2017-07-19.yang:320: error: node ietf-routing::routing-instance is not found	libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang /var/yang/all_modules/ietf-ospf-dev@2017-07-19.yang 2>&1": libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:admin-distance/ospf:granularity/ospf:detail/ospf:inter-area" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:admin-distance/ospf:granularity/ospf:detail/ospf:inter-area'}".) libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:admin-distance/ospf:granularity/ospf:detail/ospf:intra-area" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:admin-distance/ospf:granularity/ospf:detail/ospf:intra-area'}".) libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:admin-distance/ospf:external" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:admin-distance/ospf:external'}".) libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication/ospf:auth-type-selection/ospf:auth-trailer-key/ospf:key" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication/ospf:auth-type-selection/ospf:auth-trailer-key/ospf:key'}".) libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:hello-interval" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:hello-interval'}".) libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:cost" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:cost'}".) libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:dead-interval" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:dead-interval'}".) libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:retransmit-interval" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:retransmit-interval'}".) libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:transmit-delay" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:transmit-delay'}".) libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:area-id" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:area-id'}".) libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:graceful-restart/ospf:helper-enable" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:graceful-restart/ospf:helper-enable'}".) libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:admin-distance/ospf:granularity/ospf:coarse/ospf:internal" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:admin-distance/ospf:granularity/ospf:coarse/ospf:internal'}".) libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:nsr" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:nsr'}".) libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:protocol-shutdown" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:protocol-shutdown'}".) libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:maximum" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:maximum'}".) libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:mpls" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:mpls'}".) libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:topology" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:topology'}".) libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:sham-link" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:sham-link'}".) libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:demand-circuit" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:demand-circuit'}".) libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:multi-area" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:multi-area'}".) libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:lls" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:lls'}".) libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:prefix-suppression" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:prefix-suppression'}".) libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:bfd" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:bfd'}".) libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:ttl-security" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:ttl-security'}".) libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:protocol-shutdown" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:protocol-shutdown'}".) libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication/ospf:auth-type-selection/ospf:auth-trailer-key/ospf:crypto-algorithm/ospf:algorithm/ospf:hmac-sha-1-12" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication/ospf:auth-type-selection/ospf:auth-trailer-key/ospf:crypto-algorithm/ospf:algorithm/ospf:hmac-sha-1-12'}".) libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication/ospf:auth-type-selection/ospf:auth-trailer-key/ospf:crypto-algorithm/ospf:algorithm/ospf:sha-1" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication/ospf:auth-type-selection/ospf:auth-trailer-key/ospf:crypto-algorithm/ospf:algorithm/ospf:sha-1'}".) libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication/ospf:auth-type-selection/ospf:auth-trailer-key/ospf:crypto-algorithm/ospf:algorithm/ospf:hmac-sha-1" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication/ospf:auth-type-selection/ospf:auth-trailer-key/ospf:crypto-algorithm/ospf:algorithm/ospf:hmac-sha-1'}".) libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication/ospf:auth-type-selection/ospf:auth-trailer-key/ospf:crypto-algorithm" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication/ospf:auth-type-selection/ospf:auth-trailer-key/ospf:crypto-algorithm'}".) libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication/ospf:auth-type-selection/ospf:auth-trailer-key/ospf:crypto-algorithm/ospf:algorithm/ospf:hmac-sha-256" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication/ospf:auth-type-selection/ospf:auth-trailer-key/ospf:crypto-algorithm/ospf:algorithm/ospf:hmac-sha-256'}".) libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication/ospf:auth-type-selection/ospf:auth-trailer-key/ospf:crypto-algorithm/ospf:algorithm/ospf:hmac-sha-384" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication/ospf:auth-type-selection/ospf:auth-trailer-key/ospf:crypto-algorithm/ospf:algorithm/ospf:hmac-sha-384'}".) libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication/ospf:auth-type-selection/ospf:auth-trailer-key/ospf:crypto-algorithm/ospf:algorithm/ospf:hmac-sha-512" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication/ospf:auth-type-selection/ospf:auth-trailer-key/ospf:crypto-algorithm/ospf:algorithm/ospf:hmac-sha-512'}".) libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:topology" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:topology'}".) libyang err : Deviation(s) target node "/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:topology" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:topology'}".) libyang err : Deviation(s) target node "/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:static-neighbors" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:static-neighbors'}".) libyang err : Deviation(s) target node "/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:multi-area" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:multi-area'}".) libyang err : Deviation(s) target node "/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:ttl-security" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:ttl-security'}".) libyang err : Deviation(s) target node "/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication'}".) libyang err : Deviation(s) target node "/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:link-scope-lsas" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:link-scope-lsas'}".) libyang err : Deviation(s) target node "/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:protocol-shutdown" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:protocol-shutdown'}".) libyang err : Deviation(s) target node "/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:area-scope-lsas/ospf:area-scope-lsa/ospf:raw-data" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:area-scope-lsas/ospf:area-scope-lsa/ospf:raw-data'}".) libyang err : Deviation(s) target node "/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:as-scope-lsas/ospf:as-scope-lsa/ospf:raw-data" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:as-scope-lsas/ospf:as-scope-lsa/ospf:raw-data'}".) libyang err : Deviation(s) target node "/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:router-id" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:router-id'}".) libyang err : Deviation(s) target node "/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:area-scope-lsas/ospf:area-scope-lsa/ospf:version/ospf:ospfv2/ospf:ospfv2/ospf:body/ospf:opaque" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:area-scope-lsas/ospf:area-scope-lsa/ospf:version/ospf:ospfv2/ospf:ospfv2/ospf:body/ospf:opaque'}".) libyang err : Deviation(s) target node "/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:as-scope-lsas/ospf:as-scope-lsa/ospf:version/ospf:ospfv2/ospf:ospfv2/ospf:body/ospf:opaque" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:as-scope-lsas/ospf:as-scope-lsa/ospf:version/ospf:ospfv2/ospf:ospfv2/ospf:body/ospf:opaque'}".) libyang err : Deviation(s) target node "/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:topology" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:topology'}".) libyang err : Deviation(s) target node "/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:area-scope-lsas/ospf:area-scope-lsa/ospf:version/ospf:ospfv3" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:area-scope-lsas/ospf:area-scope-lsa/ospf:version/ospf:ospfv3'}".) libyang err : Deviation(s) target node "/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:as-scope-lsas/ospf:as-scope-lsa/ospf:version/ospf:ospfv3" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:as-scope-lsas/ospf:as-scope-lsa/ospf:version/ospf:ospfv3'}".) libyang err : Deviation(s) target node "/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:operation-mode" from module "ietf-ospf-dev" was not found. (Path "/ietf-routing:{deviation='/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:operation-mode'}".)	Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/ietf-ospf-dev@2017-07-19.yang 2>&1": Error: 'ietf-ospf-dev@2017-07-19.yang' import of module 'tailf-common' failed ietf-ospf-dev@2017-07-19.yang:5.3: error(236): module not found Error: 'ietf-ospf-dev@2017-07-19.yang' import of module 'ietf-ospf' failed ietf-ospf-dev@2017-07-19.yang:17.3: error(236): module not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:admin-distance/ospf:granularity/ospf:detail/ospf:inter-area' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:admin-distance/ospf:granularity/ospf:detail/ospf:intra-area' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:admin-distance/ospf:external' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication/ospf:auth-type-selection/ospf:auth-trailer-key/ospf:key' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:hello-interval' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:cost' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:dead-interval' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:retransmit-interval' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:transmit-delay' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:area-id' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:graceful-restart/ospf:helper-enable' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:admin-distance/ospf:granularity/ospf:coarse/ospf:internal' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:nsr' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:protocol-shutdown' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:maximum' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:mpls' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:topology' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:sham-link' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:demand-circuit' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:multi-area' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:lls' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:prefix-suppression' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:bfd' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:ttl-security' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:protocol-shutdown' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication/ospf:auth-type-selection/ospf:auth-trailer-key/ospf:crypto-algorithm/ospf:algorithm/ospf:hmac-sha-1-12' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication/ospf:auth-type-selection/ospf:auth-trailer-key/ospf:crypto-algorithm/ospf:algorithm/ospf:sha-1' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication/ospf:auth-type-selection/ospf:auth-trailer-key/ospf:crypto-algorithm/ospf:algorithm/ospf:hmac-sha-1' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication/ospf:auth-type-selection/ospf:auth-trailer-key/ospf:crypto-algorithm' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication/ospf:auth-type-selection/ospf:auth-trailer-key/ospf:crypto-algorithm/ospf:algorithm/ospf:hmac-sha-256' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication/ospf:auth-type-selection/ospf:auth-trailer-key/ospf:crypto-algorithm/ospf:algorithm/ospf:hmac-sha-384' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication/ospf:auth-type-selection/ospf:auth-trailer-key/ospf:crypto-algorithm/ospf:algorithm/ospf:hmac-sha-512' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:topology' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:topology' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:static-neighbors' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:multi-area' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:ttl-security' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:authentication' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:link-scope-lsas' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface/ospf:protocol-shutdown' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:area-scope-lsas/ospf:area-scope-lsa/ospf:raw-data' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:as-scope-lsas/ospf:as-scope-lsa/ospf:raw-data' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:router-id' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:area-scope-lsas/ospf:area-scope-lsa/ospf:version/ospf:ospfv2/ospf:ospfv2/ospf:body/ospf:opaque' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:as-scope-lsas/ospf:as-scope-lsa/ospf:version/ospf:ospfv2/ospf:ospfv2/ospf:body/ospf:opaque' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:topology' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:area-scope-lsas/ospf:area-scope-lsa/ospf:version/ospf:ospfv3' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:as-scope-lsas/ospf:as-scope-lsa/ospf:version/ospf:ospfv3' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:operation-mode' ietf-ospf-dev@2017-07-19.yang:325.10: error(251): definition segment not found Warning: Module 'tailf-common' not used ietf-ospf-dev@2017-07-19.yang:5.3: warning(1015): import not used Warning: Module 'ietf-inet-types' not used ietf-ospf-dev@2017-07-19.yang:9.3: warning(1015): import not used Warning: Module 'ietf-ospf' not used ietf-ospf-dev@2017-07-19.yang:17.3: warning(1015): import not used
ietf-ospf@2015-03-09.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/all_modules/ietf-ospf@2015-03-09.yang 2>&1": ietf-ospf@2015-03-09.yang:704: error: grouping 'crypto-algorithm-types' in module 'ietf-key-chain' not found ietf-ospf@2015-03-09.yang:1952: error: node 'routing-instance' not found ietf-ospf@2015-03-09.yang:1952: error: node 'routing-protocols' not found ietf-ospf@2015-03-09.yang:1952: error: node 'routing-protocol' not found ietf-ospf@2015-03-09.yang:2155: error: node 'routing-instance' not found ietf-ospf@2015-03-09.yang:2155: error: node 'routing-protocols' not found ietf-ospf@2015-03-09.yang:2155: error: node 'routing-protocol' not found ietf-ospf@2015-03-09.yang:2397: error: node 'ribs' not found ietf-ospf@2015-03-09.yang:2397: error: node 'rib' not found ietf-ospf@2015-03-09.yang:2397: error: node 'routes' not found ietf-ospf@2015-03-09.yang:2397: error: node 'route' not found ietf-ospf@2015-03-09.yang:2435: error: typedef 'routing-instance-ref' in module 'ietf-routing' not found	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" ietf-ospf@2015-03-09.yang 2>&1": ietf-ospf@2015-03-09.yang:139: error: "ietf-routing:routing-instance" in the path for name at ietf-ospf@2015-03-09.yang:2111 is not found ietf-ospf@2015-03-09.yang:139: error: "ietf-routing:routing-instance" in the path for name at ietf-ospf@2015-03-09.yang:2141 is not found ietf-ospf@2015-03-09.yang:139: error: "ietf-routing:routing-instance" in the path for name at ietf-ospf@2015-03-09.yang:2324 is not found ietf-ospf@2015-03-09.yang:139: error: "ietf-routing:routing-instance" in the path for name at ietf-ospf@2015-03-09.yang:2352 is not found ietf-ospf@2015-03-09.yang:139: error: "ietf-routing:routing-instance" in the path for rib-ref at ietf-ospf@2015-03-09.yang:137 is not found ietf-ospf@2015-03-09.yang:2058 (at ietf-ospf@2015-03-09.yang:680): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:2208 (at ietf-ospf@2015-03-09.yang:680): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:704: error: grouping "crypto-algorithm-types" not found in module "ietf-key-chain" ietf-ospf@2015-03-09.yang:1953: error: node ietf-routing::routing-instance is not found ietf-ospf@2015-03-09.yang:2096: error: node ietf-routing::routing-instance is not found ietf-ospf@2015-03-09.yang:2131: error: node ietf-routing::routing-instance is not found ietf-ospf@2015-03-09.yang:2156: error: node ietf-routing::routing-instance is not found ietf-ospf@2015-03-09.yang:2224: warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:2240: warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:2245: warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:2266: warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:2271: warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:2293: warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:2298: warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:2311: error: node ietf-routing::routing-instance is not found ietf-ospf@2015-03-09.yang:2342: error: node ietf-routing::routing-instance is not found ietf-ospf@2015-03-09.yang:2398: error: node ietf-routing::routing-instance is not found ietf-ospf@2015-03-09.yang:2435: error: type "routing-instance-ref" not found in module "ietf-routing"	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" ietf-ospf@2015-03-09.yang --lint 2>&1": ietf-ospf@2015-03-09.yang:139: error: "ietf-routing:routing-instance" in the path for name at ietf-ospf@2015-03-09.yang:2111 is not found ietf-ospf@2015-03-09.yang:139: error: "ietf-routing:routing-instance" in the path for name at ietf-ospf@2015-03-09.yang:2141 is not found ietf-ospf@2015-03-09.yang:139: error: "ietf-routing:routing-instance" in the path for name at ietf-ospf@2015-03-09.yang:2324 is not found ietf-ospf@2015-03-09.yang:139: error: "ietf-routing:routing-instance" in the path for name at ietf-ospf@2015-03-09.yang:2352 is not found ietf-ospf@2015-03-09.yang:139: error: "ietf-routing:routing-instance" in the path for rib-ref at ietf-ospf@2015-03-09.yang:137 is not found ietf-ospf@2015-03-09.yang:2058 (at ietf-ospf@2015-03-09.yang:680): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:2208 (at ietf-ospf@2015-03-09.yang:680): warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:704: error: grouping "crypto-algorithm-types" not found in module "ietf-key-chain" ietf-ospf@2015-03-09.yang:1115: warning: RFC 8407: 4.11.3,4.14: statement "bit" should have a "description" substatement ietf-ospf@2015-03-09.yang:1468: warning: RFC 8407: 4.11.3,4.14: statement "bit" should have a "description" substatement ietf-ospf@2015-03-09.yang:1470: warning: RFC 8407: 4.11.3,4.14: statement "bit" should have a "description" substatement ietf-ospf@2015-03-09.yang:1472: warning: RFC 8407: 4.11.3,4.14: statement "bit" should have a "description" substatement ietf-ospf@2015-03-09.yang:1474: warning: RFC 8407: 4.11.3,4.14: statement "bit" should have a "description" substatement ietf-ospf@2015-03-09.yang:1953: error: node ietf-routing::routing-instance is not found ietf-ospf@2015-03-09.yang:2096: error: node ietf-routing::routing-instance is not found ietf-ospf@2015-03-09.yang:2131: error: node ietf-routing::routing-instance is not found ietf-ospf@2015-03-09.yang:2156: error: node ietf-routing::routing-instance is not found ietf-ospf@2015-03-09.yang:2224: warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:2240: warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:2245: warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:2266: warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:2271: warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:2293: warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:2298: warning: node "ietf-routing::type" is not found in "ietf-ospf::/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol" ietf-ospf@2015-03-09.yang:2311: error: node ietf-routing::routing-instance is not found ietf-ospf@2015-03-09.yang:2342: error: node ietf-routing::routing-instance is not found ietf-ospf@2015-03-09.yang:2398: error: node ietf-routing::routing-instance is not found ietf-ospf@2015-03-09.yang:2435: error: type "routing-instance-ref" not found in module "ietf-routing"	libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang /var/yang/all_modules/ietf-ospf@2015-03-09.yang 2>&1": libyang err : Referenced type "rt:routing-instance-ref" not found. (Path "/ietf-ospf:if-state-change/{uses='notification-instance-hdr'}/routing-instance".)	Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/ietf-ospf@2015-03-09.yang 2>&1": Error: 'ietf-ospf@2015-03-09.yang' import of module 'ietf-key-chain' failed ietf-ospf@2015-03-09.yang:24.3: error(236): module not found Error: typedef definition for 'key-chain:key-chain-ref' not found in module ietf-key-chain ietf-ospf@2015-03-09.yang:692.18: error(250): definition not found Error: grouping definition for 'key-chain:crypto-algorithm-types' not found in module ietf-key-chain ietf-ospf@2015-03-09.yang:704.13: error(250): definition not found Error: typedef definition for 'rt:routing-instance-ref' not found in module ietf-routing Source for ietf-routing: /var/yang/all_modules/ietf-routing@2018-03-13.yang ietf-ospf@2015-03-09.yang:2435.12: error(250): definition not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol' ietf-ospf@2015-03-09.yang:1952.3: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol' ietf-ospf@2015-03-09.yang:2155.3: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance' ietf-ospf@2015-03-09.yang:2095.3: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance' ietf-ospf@2015-03-09.yang:2309.3: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/rt:routes/rt:route' ietf-ospf@2015-03-09.yang:2397.3: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interface' ietf-ospf@2015-03-09.yang:2129.3: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:routing-protocols/rt:routing-protocol/ospf:ospf/ospf:instance/ospf:area/ospf:interfaces' ietf-ospf@2015-03-09.yang:2340.3: error(251): definition segment not found Warning: path failed (no nodes available): '/rt:routing/rt:routing-instance/rt:ribs/rt:rib/rt:name'
ietf-packet-fields@2015-06-11.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" ietf-packet-fields.yang --lint 2>&1": ietf-packet-fields.yang:71: error: keyword "must" not in canonical order, expected "type" (see RFC 6020, Section 12) ietf-packet-fields.yang:74: error: keyword "type" not in canonical order (see RFC 6020, Section 12) ietf-packet-fields.yang:91: error: keyword "must" not in canonical order, expected "type" (see RFC 6020, Section 12) ietf-packet-fields.yang:94: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
ietf-restconf-monitoring@2017-01-26.yang	PASSED
ietf-restconf@2017-01-26.yang	FAILED					Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/ietf-restconf@2017-01-26.yang 2>&1": Error: 'ietf-restconf@2017-01-26.yang' import of module 'tailf-common' failed ietf-restconf@2017-01-26.yang:8.3: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' ietf-restconf@2017-01-26.yang:6.3: error(236): module not found
ietf-routing-dev@2018-07-26.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/ietf-routing-dev.yang 2>&1": ietf-routing-dev.yang:5: error: module 'ietf-routing' not found	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" ietf-routing-dev.yang 2>&1": ietf-routing-dev.yang:36: error: node ietf-routing::routing-instance is not found ietf-routing-dev.yang:41: error: node ietf-routing::routing-instance is not found ietf-routing-dev.yang:46: error: node ietf-routing::fib-route is not found ietf-routing-dev.yang:49: error: node ietf-routing::routing-instance is not found ietf-routing-dev.yang:52: error: node ietf-routing::routing-instance is not found ietf-routing-dev.yang:55: error: prefix "if" is not defined (reported only once)	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" ietf-routing-dev.yang --lint 2>&1": ietf-routing-dev.yang:27: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-routing-dev.yang:31: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-routing-dev.yang:36: error: node ietf-routing::routing-instance is not found ietf-routing-dev.yang:41: error: node ietf-routing::routing-instance is not found ietf-routing-dev.yang:46: error: node ietf-routing::fib-route is not found ietf-routing-dev.yang:49: error: node ietf-routing::routing-instance is not found ietf-routing-dev.yang:52: error: node ietf-routing::routing-instance is not found ietf-routing-dev.yang:55: error: prefix "if" is not defined (reported only once)	libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/ietf-routing-dev.yang 2>&1": libyang err : No module connected with the prefix "if" found (prefix format schema stored mapping). (Schema location "/ietf-routing:routing/routing-instance/interfaces/interface".)	Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/ietf-routing-dev.yang 2>&1": Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance' ietf-routing-dev.yang:57.5: error(251): definition segment not found Error: object 'routing-instance' not found in path '/rt:routing/rt:routing-instance/rt:routing-protocols/rt:routing-protocol' ietf-routing-dev.yang:57.5: error(251): definition segment not found Error: object 'fib-route' not found in module ietf-routing in Xpath target /rt:fib-route ietf-routing-dev.yang:57.5: error(250): definition not found Error: object 'routing-instance' not found in path '/rt:routing-state/rt:routing-instance/rt:ribs/rt:rib/rt:routes/rt:route/rt:next-hop/rt:next-hop-options/rt:simple-next-hop/rt:outgoing-interface' ietf-routing-dev.yang:57.5: error(251): definition segment not found
ietf-routing@2015-05-25.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" ietf-routing@2015-05-25.yang --lint 2>&1": ietf-routing@2015-05-25.yang:297: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) ietf-routing@2015-05-25.yang:298: error: keyword "type" not in canonical order (see RFC 6020, Section 12) ietf-routing@2015-05-25.yang:493: error: keyword "description" not in canonical order, expected "type" (see RFC 6020, Section 12) ietf-routing@2015-05-25.yang:494: error: keyword "type" not in canonical order (see RFC 6020, Section 12)
ietf-syslog-dev@2018-05-07.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/ietf-syslog-dev.yang 2>&1": ietf-syslog-dev.yang:86: error: unexpected keyword 'mandatory' ietf-syslog-dev.yang:140: error: unexpected keyword 'mandatory'	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" ietf-syslog-dev.yang 2>&1": ietf-syslog-dev.yang:86: error: the "mandatory" property cannot be deviate deleted in node "ietf-syslog::selector-facility" ietf-syslog-dev.yang:140: error: the "mandatory" property cannot be deviate deleted in node "ietf-syslog::selector-facility"	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" ietf-syslog-dev.yang --lint 2>&1": ietf-syslog-dev.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-syslog-dev.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-syslog-dev.yang:34: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-syslog-dev.yang:38: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-syslog-dev.yang:42: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-syslog-dev.yang:46: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-syslog-dev.yang:52: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-syslog-dev.yang:56: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-syslog-dev.yang:61: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement ietf-syslog-dev.yang:86: error: the "mandatory" property cannot be deviate deleted in node "ietf-syslog::selector-facility" ietf-syslog-dev.yang:140: error: the "mandatory" property cannot be deviate deleted in node "ietf-syslog::selector-facility"	libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/ietf-syslog-dev.yang 2>&1": libyang err : Deviate "delete" does not support keyword "mandatory". (Line number 86.) libyang err : Parsing module "ietf-syslog-dev" failed.	Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/ietf-syslog-dev.yang 2>&1": Error: 'ietf-syslog-dev.yang' import of module 'ietf-syslog' failed ietf-syslog-dev.yang:6.3: error(236): module not found Error: mandatory-stmt cannot be deleted ietf-syslog-dev.yang:86.7: error(347): invalid deviate sub-clause Error: mandatory-stmt cannot be deleted ietf-syslog-dev.yang:140.7: error(347): invalid deviate sub-clause Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:console ietf-syslog-dev.yang:168.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:buffer ietf-syslog-dev.yang:168.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:file/slg:log-file ietf-syslog-dev.yang:168.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:file/slg:log-file/slg:name ietf-syslog-dev.yang:168.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:file/slg:log-file/slg:log-selector/slg:selector-facility/slg:no-log-facility ietf-syslog-dev.yang:168.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:file/slg:log-file/slg:log-selector/slg:selector-facility/slg:log-facility/slg:log-facility/slg:compare-op ietf-syslog-dev.yang:168.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:file/slg:log-file/slg:log-selector/slg:pattern-match ietf-syslog-dev.yang:168.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:file/slg:log-file/slg:structured-data ietf-syslog-dev.yang:168.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:file/slg:log-file/slg:file-archive ietf-syslog-dev.yang:168.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:remote/slg:destination ietf-syslog-dev.yang:168.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:remote/slg:destination/slg:name ietf-syslog-dev.yang:168.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:remote/slg:destination/slg:transport/slg:udp/slg:udp/slg:port ietf-syslog-dev.yang:168.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:remote/slg:destination/slg:transport/slg:tcp/slg:tcp/slg:port ietf-syslog-dev.yang:168.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:remote/slg:destination/slg:transport/slg:tls ietf-syslog-dev.yang:168.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:remote/slg:destination/slg:log-selector/slg:selector-facility/slg:no-log-facility ietf-syslog-dev.yang:168.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:remote/slg:destination/slg:log-selector/slg:selector-facility/slg:log-facility/slg:log-facility/slg:compare-op ietf-syslog-dev.yang:168.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:remote/slg:destination/slg:log-selector/slg:pattern-match ietf-syslog-dev.yang:168.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:remote/slg:destination/slg:destination-facility ietf-syslog-dev.yang:168.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:remote/slg:destination/slg:source-interface ietf-syslog-dev.yang:168.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:remote/slg:destination/slg:structured-data ietf-syslog-dev.yang:168.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:remote/slg:destination/slg:syslog-sign ietf-syslog-dev.yang:168.2: error(250): definition not found Error: object 'syslog' not found in module ietf-syslog-dev in Xpath target /slg:syslog/slg:actions/slg:session ietf-syslog-dev.yang:168.2: error(250): definition not found
ietf-syslog-types@2016-07-08.yang	PASSED
ietf-syslog@2016-07-08.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" ietf-syslog.yang --lint 2>&1": ietf-syslog.yang:274: error: RFC 8407: 4.10: top-level node syslog must not be mandatory		Warning: top-level NP container 'syslog' is mandatory ietf-syslog.yang:274.3: warning(1048): top-level object is mandatory
ietf-yang-library@2016-06-21.yang	PASSED
ietf-yang-patch@2017-02-22.yang	PASSED
ietf-yang-smiv2@2012-06-22.yang	PASSED
ietf-yang-types@2013-07-15.yang	PASSED
iputil@2015-04-10.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" iputil.yang --lint 2>&1": iputil.yang:1: warning: RFC 8407: 4.1: no module name prefix string used iputil.yang:22: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement iputil.yang:27: error: RFC 8407: 4.14: statement "rpc" must have a "description" substatement iputil.yang:29: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:32: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:38: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:41: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:44: error: RFC 8407: 4.14: statement "list" must have a "description" substatement iputil.yang:45: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:49: error: RFC 8407: 4.14: statement "container" must have a "description" substatement iputil.yang:50: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:53: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:59: error: RFC 8407: 4.14: statement "rpc" must have a "description" substatement iputil.yang:61: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:66: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:69: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:72: error: RFC 8407: 4.14: statement "list" must have a "description" substatement iputil.yang:73: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:77: error: RFC 8407: 4.14: statement "container" must have a "description" substatement iputil.yang:78: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:81: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:87: error: RFC 8407: 4.14: statement "rpc" must have a "description" substatement iputil.yang:89: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:94: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:97: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:100: error: RFC 8407: 4.14: statement "list" must have a "description" substatement iputil.yang:101: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:107: error: RFC 8407: 4.14: statement "rpc" must have a "description" substatement iputil.yang:109: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:114: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:117: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement iputil.yang:120: error: RFC 8407: 4.14: statement "list" must have a "description" substatement iputil.yang:121: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
openconfig-extensions@2017-01-29.yang	PASSED WITH WARNINGS			openconfig-extensions@2017-01-29.yang:33: warning: RFC 8407: 4.4: statement "yin-element" is given with its default value "false"
openconfig-inet-types@2017-08-24.yang	FAILED					Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/openconfig-inet-types@2017-08-24.yang 2>&1": Error: 'openconfig-inet-types@2017-08-24.yang' import of module 'openconfig-extensions' failed openconfig-inet-types@2017-08-24.yang:7.3: error(236): module not found Load module 'openconfig-extensions' failed (module not found) Error: failure importing module 'openconfig-extensions' openconfig-inet-types@2017-08-24.yang:34.3: error(236): module not found Warning: revision with same date on line 48 openconfig-inet-types@2017-08-24.yang:54.3: warning(1054): Revision date has already been used
openconfig-telemetry-dev@2018-12-14.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/openconfig-telemetry-dev.yang 2>&1": openconfig-telemetry-dev.yang:5: error: module 'openconfig-telemetry' not found	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" openconfig-telemetry-dev.yang 2>&1": openconfig-telemetry-dev.yang:160: error: node openconfig-telemetry::local-source-address is not found openconfig-telemetry-dev.yang:163: error: node openconfig-telemetry::originated-qos-marking is not found openconfig-telemetry-dev.yang:166: error: node openconfig-telemetry::heartbeat-interval is not found	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" openconfig-telemetry-dev.yang --lint 2>&1": openconfig-telemetry-dev.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement openconfig-telemetry-dev.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement openconfig-telemetry-dev.yang:35: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement openconfig-telemetry-dev.yang:39: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement openconfig-telemetry-dev.yang:45: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement openconfig-telemetry-dev.yang:50: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement openconfig-telemetry-dev.yang:77: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement openconfig-telemetry-dev.yang:132: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement openconfig-telemetry-dev.yang:133: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement openconfig-telemetry-dev.yang:160: error: node openconfig-telemetry::local-source-address is not found openconfig-telemetry-dev.yang:163: error: node openconfig-telemetry::originated-qos-marking is not found openconfig-telemetry-dev.yang:166: error: node openconfig-telemetry::heartbeat-interval is not found	libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/openconfig-telemetry-dev.yang 2>&1": libyang err : Multiple deviations of "/oc-telemetry:telemetry-system/oc-telemetry:subscriptions/oc-telemetry:persistent/oc-telemetry:subscription/oc-telemetry:config/oc-telemetry:originated-qos-marking" with one of them being "not-supported". (Path "/openconfig-telemetry-dev:{deviation='/oc-telemetry:telemetry-system/oc-telemetry:subscriptions/oc-telemetry:persistent/oc-telemetry:subscription/oc-telemetry:config/oc-telemetry:originated-qos-marking'}".)	Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/openconfig-telemetry-dev.yang 2>&1": Error: 'openconfig-telemetry-dev.yang' import of module 'openconfig-telemetry' failed openconfig-telemetry-dev.yang:5.3: error(236): module not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:subscriptions/oc-telemetry:persistent/oc-telemetry:subscription/oc-telemetry:config/oc-telemetry:originated-qos-marking openconfig-telemetry-dev.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:subscriptions/oc-telemetry:persistent/oc-telemetry:subscription/oc-telemetry:config/oc-telemetry:local-source-address openconfig-telemetry-dev.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:subscriptions/oc-telemetry:persistent/oc-telemetry:subscription/oc-telemetry:sensor-profiles/oc-telemetry:sensor-profile/oc-telemetry:config/oc-telemetry:heartbeat-interval openconfig-telemetry-dev.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:subscriptions/oc-telemetry:persistent/oc-telemetry:subscription/oc-telemetry:sensor-profiles/oc-telemetry:sensor-profile/oc-telemetry:config/oc-telemetry:sample-interval openconfig-telemetry-dev.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:subscriptions/oc-telemetry:persistent/oc-telemetry:subscription/oc-telemetry:config/oc-telemetry:protocol openconfig-telemetry-dev.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:subscriptions/oc-telemetry:persistent/oc-telemetry:subscription/oc-telemetry:config/oc-telemetry:subscription-name openconfig-telemetry-dev.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:destination-groups/oc-telemetry:destination-group/oc-telemetry:destinations/oc-telemetry:destination/oc-telemetry:config/oc-telemetry:destination-address openconfig-telemetry-dev.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:destination-groups/oc-telemetry:destination-group/oc-telemetry:destinations/oc-telemetry:destination/oc-telemetry:config/oc-telemetry:destination-port openconfig-telemetry-dev.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:destination-groups/oc-telemetry:destination-group/oc-telemetry:config/oc-telemetry:group-id openconfig-telemetry-dev.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:sensor-groups/oc-telemetry:sensor-group/oc-telemetry:config/oc-telemetry:sensor-group-id openconfig-telemetry-dev.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:subscriptions/oc-telemetry:persistent/oc-telemetry:subscription/oc-telemetry:config/oc-telemetry:encoding openconfig-telemetry-dev.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:sensor-groups/oc-telemetry:sensor-group/oc-telemetry:state openconfig-telemetry-dev.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:sensor-groups/oc-telemetry:sensor-group/oc-telemetry:sensor-paths/oc-telemetry:sensor-path/oc-telemetry:config/oc-telemetry:exclude-filter openconfig-telemetry-dev.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:sensor-groups/oc-telemetry:sensor-group/oc-telemetry:sensor-paths/oc-telemetry:sensor-path/oc-telemetry:state openconfig-telemetry-dev.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:destination-groups/oc-telemetry:destination-group/oc-telemetry:state openconfig-telemetry-dev.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:destination-groups/oc-telemetry:destination-group/oc-telemetry:destinations/oc-telemetry:destination/oc-telemetry:state openconfig-telemetry-dev.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:subscriptions/oc-telemetry:persistent/oc-telemetry:subscription/oc-telemetry:state openconfig-telemetry-dev.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:subscriptions/oc-telemetry:persistent/oc-telemetry:subscription/oc-telemetry:sensor-profiles/oc-telemetry:sensor-profile/oc-telemetry:config/oc-telemetry:suppress-redundant openconfig-telemetry-dev.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:subscriptions/oc-telemetry:persistent/oc-telemetry:subscription/oc-telemetry:sensor-profiles/oc-telemetry:sensor-profile/oc-telemetry:state openconfig-telemetry-dev.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:subscriptions/oc-telemetry:persistent/oc-telemetry:subscription/oc-telemetry:destination-groups/oc-telemetry:destination-group/oc-telemetry:state openconfig-telemetry-dev.yang:181.2: error(250): definition not found Error: object 'telemetry-system' not found in module openconfig-telemetry-dev in Xpath target /oc-telemetry:telemetry-system/oc-telemetry:subscriptions/oc-telemetry:dynamic openconfig-telemetry-dev.yang:181.2: error(250): definition not found
openconfig-telemetry-types@2017-02-20.yang	PASSED
openconfig-telemetry@2017-02-20.yang	UNKNOWN				Warning: revision with same date on line 41 openconfig-inet-types.yang:46.3: warning(1054): Revision date has already been used
tailf-aaa@2015-06-16.yang	FAILED	tailf-aaa@2015-06-16.yang:246:20: warning: illegal character after \	tailf-aaa@2015-06-16.yang:246: warning: the escape sequence "\h" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning	Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" tailf-aaa@2015-06-16.yang --lint 2>&1": tailf-aaa@2015-06-16.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement tailf-aaa@2015-06-16.yang:23: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-aaa@2015-06-16.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-aaa@2015-06-16.yang:37: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-aaa@2015-06-16.yang:45: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-aaa@2015-06-16.yang:53: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-aaa@2015-06-16.yang:62: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-aaa@2015-06-16.yang:67: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-aaa@2015-06-16.yang:72: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-aaa@2015-06-16.yang:77: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-aaa@2015-06-16.yang:82: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-aaa@2015-06-16.yang:87: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-aaa@2015-06-16.yang:92: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-aaa@2015-06-16.yang:97: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-aaa@2015-06-16.yang:100: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-aaa@2015-06-16.yang:105: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-aaa@2015-06-16.yang:111: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-aaa@2015-06-16.yang:113: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-aaa@2015-06-16.yang:114: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-aaa@2015-06-16.yang:118: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement tailf-aaa@2015-06-16.yang:119: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:123: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:127: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:131: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:135: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:139: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:143: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:147: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:151: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:155: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:161: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-aaa@2015-06-16.yang:164: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-aaa@2015-06-16.yang:166: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-aaa@2015-06-16.yang:168: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-aaa@2015-06-16.yang:170: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:174: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:179: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:184: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:188: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:194: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:205: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:211: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:217: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:228: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-aaa@2015-06-16.yang:232: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-aaa@2015-06-16.yang:235: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:238: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:241: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:244: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:246: warning: the escape sequence "\h" is unsafe in double quoted strings - pass the flag --lax-quote-checks to avoid this warning tailf-aaa@2015-06-16.yang:250: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-aaa@2015-06-16.yang:252: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:255: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-aaa@2015-06-16.yang:259: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:262: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-aaa@2015-06-16.yang:264: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:272: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-aaa@2015-06-16.yang:276: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:281: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:289: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-aaa@2015-06-16.yang:295: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-aaa@2015-06-16.yang:300: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:303: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:307: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-aaa@2015-06-16.yang:310: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:315: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-aaa@2015-06-16.yang:323: error: RFC 8407: 4.14: statement "container" must have a "description" substatement	libyang err : Problem occurred while running command "yanglint -i -p /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang /var/yang/all_modules/tailf-aaa@2015-06-16.yang 2>&1": libyang err : Double-quoted string unknown special character '\h'. (Line number 246.) libyang err : Parsing module "tailf-aaa" failed.	Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/tailf-aaa@2015-06-16.yang 2>&1": Error: 'tailf-aaa@2015-06-16.yang' import of module 'tailf-common' failed tailf-aaa@2015-06-16.yang:14.3: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:4.3: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:121.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:125.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:129.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:133.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:137.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:141.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:145.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:149.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:153.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:157.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:162.5: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:165.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:167.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:199.11: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:200.13: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:201.13: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:202.15: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:208.17: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:209.17: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:214.17: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:215.17: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:220.17: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:221.17: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:172.13: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:177.13: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:182.13: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:191.13: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:197.13: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:229.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:275.5: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:278.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:284.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:293.5: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:296.5: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:305.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:309.7: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:312.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:318.9: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-aaa@2015-06-16.yang:325.7: error(236): module not found
tailf-acm@2013-03-07.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" tailf-acm.yang --lint 2>&1": tailf-acm.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement tailf-acm.yang:15: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-acm.yang:22: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-acm.yang:29: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement tailf-acm.yang:60: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement tailf-acm.yang:71: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement tailf-acm.yang:154: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement
tailf-common-monitoring@2013-06-14.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" tailf-common-monitoring@2013-06-14.yang --lint 2>&1": tailf-common-monitoring@2013-06-14.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement tailf-common-monitoring@2013-06-14.yang:15: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common-monitoring@2013-06-14.yang:21: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common-monitoring@2013-06-14.yang:29: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common-monitoring@2013-06-14.yang:35: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common-monitoring@2013-06-14.yang:42: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common-monitoring@2013-06-14.yang:48: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common-monitoring@2013-06-14.yang:59: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:64: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:73: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:75: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:101: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:103: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:114: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:133: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:166: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:168: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:169: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:172: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:181: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:194: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:218: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:230: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:234: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:235: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:236: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:237: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:270: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:299: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:309: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:310: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:311: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:312: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:313: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:324: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:333: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:336: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:341: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:353: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:358: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:363: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:366: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:371: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:376: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:379: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:384: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:389: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:401: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:404: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:407: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:420: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:421: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:422: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:426: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:430: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:434: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:438: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:442: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:446: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:450: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:457: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:459: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:460: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:461: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:466: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:470: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:475: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:479: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:485: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:489: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:490: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:491: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:510: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:512: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:586: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:604: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:621: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:644: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-monitoring@2013-06-14.yang:659: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:660: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:661: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:662: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:675: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:687: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:688: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:689: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:690: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common-monitoring@2013-06-14.yang:701: error: RFC 8407: 4.14: statement "list" must have a "description" substatement
tailf-common-query@2017-12-15.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" tailf-common-query@2017-12-15.yang --lint 2>&1": tailf-common-query@2017-12-15.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement tailf-common-query@2017-12-15.yang:44: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common-query@2017-12-15.yang:50: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common-query@2017-12-15.yang:56: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common-query@2017-12-15.yang:62: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common-query@2017-12-15.yang:184: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-common-query@2017-12-15.yang:206: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-common-query@2017-12-15.yang:219: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-common-query@2017-12-15.yang:226: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement tailf-common-query@2017-12-15.yang:228: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-common-query@2017-12-15.yang:231: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-common-query@2017-12-15.yang:251: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement		Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/tailf-common-query@2017-12-15.yang 2>&1": Error: 'tailf-common-query@2017-12-15.yang' import of module 'tailf-common' failed tailf-common-query@2017-12-15.yang:8.3: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-common-query@2017-12-15.yang:121.13: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-common-query@2017-12-15.yang:130.13: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-common-query@2017-12-15.yang:137.13: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-common-query@2017-12-15.yang:143.13: error(236): module not found
tailf-common@2017-09-28.yang	FAILED	Problem occurred while running command "/opt/confd/bin/confdc --yangpath /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang -w TAILF_MUST_NEED_DEPENDENCY -c /var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang/third_party/tailf-common.yang 2>&1": /opt/confd/src/confd/yang/tailf-cli-extensions.yang:0: error: expected revision '2017-08-23', got '2021-12-17'		Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" tailf-common.yang --lint 2>&1": tailf-common.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement tailf-common.yang:19: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:33: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:49: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:56: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:64: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:71: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:83: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:100: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:107: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:115: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:129: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:136: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:143: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:151: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:158: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:167: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:184: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:191: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:204: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:211: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:218: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:233: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:241: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:248: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:253: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:261: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:277: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:284: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:300: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:307: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:316: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:323: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:330: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:340: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:351: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:358: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:366: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:373: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:390: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:399: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:422: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:433: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:452: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:464: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:472: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-common.yang:740: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:741: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:742: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:743: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:744: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:745: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:1104: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:1105: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:1106: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:1141: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:1142: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:1143: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:1178: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:1179: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:2937: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:2938: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:2939: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:3462: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:3463: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:3464: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:3481: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:3482: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:3483: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:3484: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:3485: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:3498: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:3499: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-common.yang:3500: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-cli-extensions.yang:1: error: RFC 8407: 4.8: statement "submodule" must have a "contact" substatement tailf-cli-extensions.yang:20: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:27: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:34: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:41: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:57: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:63: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:70: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:78: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:87: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:97: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:106: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:114: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:124: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:134: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:142: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:149: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:159: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:168: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:176: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:183: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:203: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:210: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:226: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:235: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:245: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:269: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-cli-extensions.yang:2176: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-cli-extensions.yang:2177: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-cli-extensions.yang:2178: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-meta-extensions.yang:1: error: RFC 8407: 4.8: statement "submodule" must have a "contact" substatement tailf-meta-extensions.yang:12: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-meta-extensions.yang:19: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-meta-extensions.yang:26: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-meta-extensions.yang:33: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-meta-extensions.yang:40: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-meta-extensions.yang:49: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-meta-extensions.yang:55: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-meta-extensions.yang:61: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-meta-extensions.yang:67: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement
tailf-confd-monitoring@2013-06-14.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" tailf-confd-monitoring@2013-06-14.yang --lint 2>&1": tailf-confd-monitoring@2013-06-14.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement tailf-confd-monitoring@2013-06-14.yang:15: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-confd-monitoring@2013-06-14.yang:21: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-confd-monitoring@2013-06-14.yang:27: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-confd-monitoring@2013-06-14.yang:33: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-confd-monitoring@2013-06-14.yang:39: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-confd-monitoring@2013-06-14.yang:45: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-confd-monitoring@2013-06-14.yang:50: error: RFC 8407: 4.14: statement "container" must have a "description" substatement
tailf-kicker@2017-09-28.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" tailf-kicker.yang --lint 2>&1": tailf-kicker.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement tailf-kicker.yang:19: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-kicker.yang:29: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-kicker.yang:39: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-kicker.yang:45: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-kicker.yang:53: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-kicker.yang:97: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-kicker.yang:177: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-kicker.yang:264: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
tailf-netconf-monitoring@2016-11-24.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" tailf-netconf-monitoring.yang --lint 2>&1": tailf-netconf-monitoring.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement tailf-netconf-monitoring.yang:23: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-netconf-monitoring.yang:30: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-netconf-monitoring.yang:37: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-netconf-monitoring.yang:44: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-netconf-monitoring.yang:51: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-netconf-monitoring.yang:58: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-netconf-monitoring.yang:65: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-netconf-monitoring.yang:134: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement tailf-netconf-monitoring.yang:144: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-netconf-monitoring.yang:168: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-netconf-monitoring.yang:169: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-netconf-monitoring.yang:170: warning: RFC 8407: 4.11.3,4.14: statement "enum" should have a "description" substatement tailf-netconf-monitoring.yang:187: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement tailf-netconf-monitoring.yang:201: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement tailf-netconf-monitoring.yang:223: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement tailf-netconf-monitoring.yang:230: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-netconf-monitoring.yang:232: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-netconf-monitoring.yang:235: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-netconf-monitoring.yang:239: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-netconf-monitoring.yang:243: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-netconf-monitoring.yang:247: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-netconf-monitoring.yang:258: error: RFC 8407: 4.14: statement "augment" must have a "description" substatement tailf-netconf-monitoring.yang:263: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
tailf-netconf-query@2017-01-06.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" tailf-netconf-query@2017-01-06.yang --lint 2>&1": tailf-netconf-query@2017-01-06.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement tailf-netconf-query@2017-01-06.yang:34: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-netconf-query@2017-01-06.yang:40: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-netconf-query@2017-01-06.yang:45: error: RFC 8407: 4.14: statement "rpc" must have a "description" substatement tailf-netconf-query@2017-01-06.yang:53: error: RFC 8407: 4.14: statement "rpc" must have a "description" substatement tailf-netconf-query@2017-01-06.yang:58: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-netconf-query@2017-01-06.yang:63: error: RFC 8407: 4.14: statement "rpc" must have a "description" substatement tailf-netconf-query@2017-01-06.yang:68: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-netconf-query@2017-01-06.yang:73: error: RFC 8407: 4.14: statement "rpc" must have a "description" substatement tailf-netconf-query@2017-01-06.yang:78: error: RFC 8407: 4.14: statement "rpc" must have a "description" substatement		Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/tailf-netconf-query@2017-01-06.yang 2>&1": Error: 'tailf-netconf-query@2017-01-06.yang' import of module 'tailf-common' failed tailf-netconf-query@2017-01-06.yang:5.3: error(236): module not found Error: 'tailf-netconf-query@2017-01-06.yang' import of module 'tailf-common-query' failed tailf-netconf-query@2017-01-06.yang:8.3: error(236): module not found Error: grouping definition for 'tfcq:start-query-parameters' not found in module tailf-common-query tailf-netconf-query@2017-01-06.yang:47.7: error(250): definition not found Error: 'input' must define at least 1 data-def-stmt tailf-netconf-query@2017-01-06.yang:48.5: error(413): missing data definition statement Error: grouping definition for 'tfcq:query-handle' not found in module tailf-common-query tailf-netconf-query@2017-01-06.yang:50.7: error(250): definition not found Error: 'output' must define at least 1 data-def-stmt tailf-netconf-query@2017-01-06.yang:51.5: error(413): missing data definition statement Error: grouping definition for 'tfcq:query-handle' not found in module tailf-common-query tailf-netconf-query@2017-01-06.yang:55.7: error(250): definition not found Error: 'input' must define at least 1 data-def-stmt tailf-netconf-query@2017-01-06.yang:56.5: error(413): missing data definition statement Error: grouping definition for 'tfcq:query-result' not found in module tailf-common-query tailf-netconf-query@2017-01-06.yang:59.9: error(250): definition not found Error: 'output' must define at least 1 data-def-stmt tailf-netconf-query@2017-01-06.yang:61.5: error(413): missing data definition statement Error: grouping definition for 'tfcq:start-query-parameters' not found in module tailf-common-query tailf-netconf-query@2017-01-06.yang:65.7: error(250): definition not found Error: 'input' must define at least 1 data-def-stmt tailf-netconf-query@2017-01-06.yang:66.5: error(413): missing data definition statement Error: grouping definition for 'tfcq:query-result' not found in module tailf-common-query tailf-netconf-query@2017-01-06.yang:69.9: error(250): definition not found Error: 'output' must define at least 1 data-def-stmt tailf-netconf-query@2017-01-06.yang:71.5: error(413): missing data definition statement Error: grouping definition for 'tfcq:reset-query-parameters' not found in module tailf-common-query tailf-netconf-query@2017-01-06.yang:75.7: error(250): definition not found Error: 'input' must define at least 1 data-def-stmt tailf-netconf-query@2017-01-06.yang:76.5: error(413): missing data definition statement Error: grouping definition for 'tfcq:query-handle' not found in module tailf-common-query tailf-netconf-query@2017-01-06.yang:80.7: error(250): definition not found Error: 'input' must define at least 1 data-def-stmt tailf-netconf-query@2017-01-06.yang:81.5: error(413): missing data definition statement Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-netconf-query@2017-01-06.yang:83.3: error(236): module not found Error: grouping 'start-query-parameters' not found tailf-netconf-query@2017-01-06.yang:47.7: error(250): definition not found Error: grouping 'query-handle' not found tailf-netconf-query@2017-01-06.yang:50.7: error(250): definition not found Error: grouping 'query-handle' not found tailf-netconf-query@2017-01-06.yang:55.7: error(250): definition not found Error: grouping 'query-result' not found tailf-netconf-query@2017-01-06.yang:59.9: error(250): definition not found Error: grouping 'start-query-parameters' not found tailf-netconf-query@2017-01-06.yang:65.7: error(250): definition not found Error: grouping 'query-result' not found tailf-netconf-query@2017-01-06.yang:69.9: error(250): definition not found Error: grouping 'reset-query-parameters' not found tailf-netconf-query@2017-01-06.yang:75.7: error(250): definition not found Error: grouping 'query-handle' not found tailf-netconf-query@2017-01-06.yang:80.7: error(250): definition not found
tailf-rest-query@2017-01-06.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" tailf-rest-query@2017-01-06.yang --lint 2>&1": tailf-rest-query@2017-01-06.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement tailf-rest-query@2017-01-06.yang:27: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-rest-query@2017-01-06.yang:34: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-rest-query@2017-01-06.yang:42: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement		Problem occurred while running command "yangdump-pro --config=/etc/yumapro/yangdump-pro-allinclusive.conf /var/yang/all_modules/tailf-rest-query@2017-01-06.yang 2>&1": Error: 'tailf-rest-query@2017-01-06.yang' import of module 'tailf-common' failed tailf-rest-query@2017-01-06.yang:7.3: error(236): module not found Error: 'tailf-rest-query@2017-01-06.yang' import of module 'tailf-common-query' failed tailf-rest-query@2017-01-06.yang:10.3: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-rest-query@2017-01-06.yang:50.3: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-rest-query@2017-01-06.yang:66.3: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-rest-query@2017-01-06.yang:84.3: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-rest-query@2017-01-06.yang:99.3: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-rest-query@2017-01-06.yang:115.3: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-rest-query@2017-01-06.yang:131.3: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-rest-query@2017-01-06.yang:147.3: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-rest-query@2017-01-06.yang:164.3: error(236): module not found Load module 'tailf-common' failed (module not found) Error: failure importing module 'tailf-common' tailf-rest-query@2017-01-06.yang:5.3: error(236): module not found Warning: Module 'tailf-common-query' not used tailf-rest-query@2017-01-06.yang:10.3: warning(1015): import not used
tailf-webui@2013-03-07.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" tailf-webui.yang --lint 2>&1": tailf-webui.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement tailf-webui.yang:20: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-webui.yang:25: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-webui.yang:28: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-webui.yang:30: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-webui.yang:32: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-webui.yang:35: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:39: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-webui.yang:41: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:45: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:49: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:53: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:58: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-webui.yang:61: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-webui.yang:64: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:69: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-webui.yang:70: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:74: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:78: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:82: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:86: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:90: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement tailf-webui.yang:93: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-webui.yang:94: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:95: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12) tailf-webui.yang:97: error: keyword "type" not in canonical order (see RFC 6020, Section 12) tailf-webui.yang:104: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-webui.yang:105: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:109: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:110: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12) tailf-webui.yang:112: error: keyword "type" not in canonical order (see RFC 6020, Section 12) tailf-webui.yang:122: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-webui.yang:124: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-webui.yang:126: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:130: error: RFC 8407: 4.14: statement "choice" must have a "description" substatement tailf-webui.yang:132: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:133: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12) tailf-webui.yang:135: error: keyword "type" not in canonical order (see RFC 6020, Section 12) tailf-webui.yang:137: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:138: error: keyword "mandatory" not in canonical order, expected "type" (see RFC 6020, Section 12) tailf-webui.yang:140: error: keyword "type" not in canonical order (see RFC 6020, Section 12) tailf-webui.yang:151: error: RFC 8407: 4.14: statement "container" must have a "description" substatement tailf-webui.yang:154: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-webui.yang:159: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:164: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-webui.yang:169: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-webui.yang:176: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-webui.yang:182: error: RFC 8407: 4.14: statement "list" must have a "description" substatement tailf-webui.yang:190: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement tailf-webui.yang:191: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:195: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:201: error: RFC 8407: 4.14: statement "grouping" must have a "description" substatement tailf-webui.yang:202: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:206: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement tailf-webui.yang:210: error: RFC 8407: 4.14: statement "leaf" must have a "description" substatement
tailf-xsd-types@2017-11-20.yang	FAILED			Problem occurred while running command "python3 /usr/local/bin/pyang --path="/var/yang/tmp/module_compilation/yangmodels/yang/vendor/fujitsu/FSS2-API-Yang/T600/1.1/yang" tailf-xsd-types@2017-11-20.yang --lint 2>&1": tailf-xsd-types@2017-11-20.yang:1: error: RFC 8407: 4.8: statement "module" must have a "contact" substatement tailf-xsd-types@2017-11-20.yang:1: error: RFC 8407: 4.8: statement "module" must have a "organization" substatement tailf-xsd-types@2017-11-20.yang:14: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-xsd-types@2017-11-20.yang:21: error: RFC 8407: 4.8: statement "revision" must have a "reference" substatement tailf-xsd-types@2017-11-20.yang:26: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-xsd-types@2017-11-20.yang:32: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-xsd-types@2017-11-20.yang:38: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-xsd-types@2017-11-20.yang:44: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-xsd-types@2017-11-20.yang:50: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-xsd-types@2017-11-20.yang:56: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-xsd-types@2017-11-20.yang:62: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-xsd-types@2017-11-20.yang:68: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement tailf-xsd-types@2017-11-20.yang:74: error: RFC 8407: 4.13,4.14: statement "typedef" must have a "description" substatement