You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ydk.errors.YPYServiceProviderError: <?xml version="1.0"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="1">
<rpc-error>
<error-type>protocol</error-type>
<error-tag>missing-element</error-tag>
<error-severity>error</error-severity>
<error-path xmlns:ns1="http://cisco.com/ns/yang/Cisco-IOS-XR-ipv4-smiap-cfg">ns1:ipv4-virtual/ns1:vrfs/ns1:vrf[vrf-name = 'default']/ns1:address/ns1:address</error-path>
<error-info>
<bad-element>address</bad-element>
<error-message>mandatory leaf missing from request, please add it and try again.</error-message>
</error-info>
</rpc-error>
</rpc-reply>
Full logs are attached in file: ipv4_smiap.log
System Information
Python Version 2.7
Route Operating System: CISCO-IOS-XR ipv4_smiap.log
The text was updated successfully, but these errors were encountered:
ghost
changed the title
Error:"mandatory leaf missing from request" but configuration of leaf is given
Cisco-IOS-XR-ipv4-smiap-cfg.yang: Error "mandatory leaf missing from request" but configuration of leaf is given
Oct 9, 2017
ghost
changed the title
Cisco-IOS-XR-ipv4-smiap-cfg.yang: Error "mandatory leaf missing from request" but configuration of leaf is given
Cisco-IOS-XR-ipv4-smiap-cfg module: Error "mandatory leaf missing from request" but configuration of leaf is given
Oct 9, 2017
Issue tracker is ONLY used for reporting bugs. Please use the YDK Community for any support issues.
Expected Behavior
Configurations for IPv4 virtual address for management interfaces should reply with ok
Current Behavior
No ok in reply received from device. (RPC reply as mandatory leaf missing from request)
Steps to Reproduce
Your Script
Logs
Full logs are attached in file: ipv4_smiap.log
System Information
Python Version 2.7
Route Operating System: CISCO-IOS-XR
ipv4_smiap.log
The text was updated successfully, but these errors were encountered: