I agree w/ Jan -- it's not clear if you're asking how to exclude modules in Pioneer? or are you looking for some "simple" way to compare (what might be considered "duplicate" modules? (which they aren't)
several modules are include, typically only when an "openconfig" module and IOS-XE module are handling a function.
-- "openconfig" which is meant to a very "vanilla" lowest-common-denominator model that "all" vendors can deploy...
-- "cisco-ios-xe" modules would be exposing every aspect of a device config.
in this case, looking at the YANG model for IOS-XE
File: Cisco-IOS-XE-acl.yang
(skip)
container ace-rule {
leaf action {
type enumeration {
enum deny;
enum permit;
}
}
leaf protocol {
type union {
type uint8 {
range "0..255";
}
type enumeration {
enum ahp;
enum esp;
enum hbh;
enum icmp;
enum ipv6;
enum pcp;
enum sctp;
enum tcp;
enum udp;
}
}
}
you can see exactly the structure you show in your XML.
However, in the "openconfig" module, it's just a "string"... in a leaf called "description" (sounds weird but this
seems to be where the "string" of your rule happens...)
File: openconfig-acl.yang
// Access List Entries
grouping access-list-entries-config {
description
"Access List Entries (ACE) config.";
leaf sequence-id {
type uint32;
description
"The sequence id determines the order in which ACL entries
are applied. The sequence id must be unique for each entry
in an ACL set. Target devices should apply the ACL entry
rules in the order determined by sequence id, rather than
the relying only on order in the list.";
}
leaf description {
type string;
description
"A user-defined description, or comment, for this Access List
Entry.";
}
}
as Jan pointed out these are "unrelated" modules - and just delete the openconfig one... recompile and good to go...
Essentially both models can be used but one may have gaps. I recompiled and everything works fine now.