Known Issues in OpenConfig Plugin 1.1.0

PLUG-9351

For OpenConfig telemetry when using the openconfig-bgp model, the sample interval has a delay of approximately 5 seconds.

PLUG-9301

When using the openconfig-interfaces model, a Delete operation on a GRE tunnel resets the configuration instead of deleting the configuration. For example:
interfaces/interface[name=tunnel.10]/tunnel/ipv6/addresses/address/config

PLUG-9224

When using the openconfig-network-instance model, address objects are not supported with policy forwarding.

PLUG-9198

When using the openconfig-system, setting system nodes with a JSON file may cause NTP errors on PA-3XXX Series firewalls.

PLUG-9148

When using the openconfig-zones model, the deletion of an empty-zone trigger a PAN-OS commit.

PLUG-9144

When using the openconfig-network-instances model, a get that uses a key at the network-instance level but specifies a key in the child containers could fail if the specified key does not exist in all network-instances. For example a get request on the path /network-instances/network-instance/policy-forwarding/policies/policy[policy-id=Example] on a named policy-id returns
data not found for forwarding-policy 'default' (network-instances:policies)
if example doesn’t exist at on all network-instances.

PLUG-9038

For the openconfig-network-instances model, doing a get on network-instance/protocols/protocol returns the connect protocol, but this protocol can’t be set. The get output returns:
{ "default-metric": 0, "enabled": true, "identifier": "DIRECTLY_CONNECTED", "name": "connect" }

PLUG-9021

For the openconfig-network-instances model, performing a get on an interface for the network instances model for a main interface returns with a 0 subinterface, for example: Ethernet1/4.0. The set request is accepted without subinterface 0, for example: Ethernet1/4

PLUG-8997

For the openconfig-hagroups model, Active/Active mode is returned in the get response, although only Active/Passive mode is currently supported.

PLUG-8932

For the openconfig-bgp model, doing a delete at
/network-instances/.../protocol/bgp
causes a failed commit. To delete a BGP configuration, you must both delete the BGP instance and then disable it.

PLUG-8928

Doing a get using the
...
wildcard returns only config leaf-nodes.

PLUG-8872

When using the openconfig-components model, the subscribe request returns components with 2 back slashes, for example:
Slot1(Temperature @ Front Left[U62\\]

PLUG-8816

Subscribe requests don’t support JSON_IETF outputs.

PLUG-8789

When using the openconfig-network-instances model, the path under protocols/protocol can’t be filtered based on name and identifier. For example: Doing a get on protocols/protocol[name=bgp][identifier=BGP]/static-routes returns all nodes specified for both BGP and static-routes.

PLUG-8733

When using the openconfig-network-instances model, doing a get at /network-instances/network-instance[name=*]/tables doesn’t return IPV6 address families for BGP configurations.

PLUG-8618

When using the openconfig-ha model, setting the management interface for the path /ha-groups/ha-group/control-link returns an error.

PLUG-8614

When using the openconfig-ha model, you can’t configure an IPv4 and IPv6 addresses for management interfaces.

PLUG-8972

when using the openconfig-ha model, deletion of ha-group/control-link and ha-group/data-link is not supported.

PLUG-8698

When using the openconfig-routing-policy model, only IPv4 type IP addresses are supported.

PLUG-9476

When using the openconfig-bgp model, the get response for /bgp/neighbors/neighbor/config(state)/peer-as is always 0 for an IPv6 IBGP peer.

Recommended For You