rszarecki
rszarecki
> * [Cisco XR OS Control Plane Queue](https://content.cisco.com/chapter.sjs?uri=/searchable/chapter/content/en/us/td/docs/ios-xml/ios/qos_plcshp/configuration/15-mt/qos-plcshp-15-mt-book/qos-plcshp-cpp.html.xml#GUID-F05A63BE-DC5E-4D0B-9B61-FA8B78F5ECAB) thresholding feature defines queues as part of it's control plane traffic features This is link to legacy IOS. Not IOS-XR. AFAIK IOS...
#### EXAMPLE: Let assume deployment where we have single network-instance "DEFAULT" running one BGP instance "BGP" and one ISIS instance "isis". ``` /network-instances/network-instance[name=default]/protocols/protocol[identifier=BGP][name=BGP]: { ... } /network-instances/network-instance[name=default]/protocols/protocol[identifier=ISIS][name=isis]: { ... }...
I have looked into this some time ago. Any logic expressed with ‘install-protocol-eq’ could be expressed with ‘match-protocol-instance’ However opposite is not true. ‘Match-protocol-instance’ is functional superset. -------------- Rafal Szarecki...
Regarding bandwidth encoding in OpenConfig. In contrast to CLI, the user would be OpenConfig client/software. So why not keep baldwidth in on-the-wire format to avoid uncertanity?
With `oc-bgp-pol:community-member*` deprecated, there is no way to efficiently express: - "any community with ASN 1234" - with this PR we would need to list 65535 individual communities. - "...
It is illogical to define IP FRAGMENTATION match as /acl/acl-sets/acl-set/acl-entries/acl-entry/transport/state/builtin-detail - "FRAGMENT" - Matches non-zero values of the fragment-offset field" of IPv4 HEADER. Not L4/TCP/UDP/ICMP/.... - "FRAGMENT" is not applicable...
I can offer different view point here: Observe that community-set has leaf-list[]. Observe that match-set-type is attribute of community-set. Not a method. Hence ALL|ANY|INVERT match-set-type applys to elements of list,...
@dplore @aashaikh I see 2 issues with current "table-connections" redistribution model, if we assume existence of multiple instances of given protocol. 1. Two instances of src-protocol may have routes to...
- for telematry we shall stream and collect`/network-instances/network-instance/afts/next-hops/next-hop/state/counters` for: - for NH#201 and NH#202. to collect **ENCAPSULATION** counters and wECMP among tunnels. - for NH#1, NH#2, NH#10, NH#11, NH100, NH101...
@dplore 1. from my point of view, we can deprecate `/network-instances/network-instance/tables/ ` completly. 2. we need both `src/dst-protocol` and `src/dst-instance-name`. This is because instance name is free-text-string and can be...