-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing destination-udp-port
leaf from bridge-domains.vxlan
grouping
#20
Comments
Also, I found that if I will configure the device using netconf with the following XML, it will work <rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"><edit-config xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<target>
<candidate/>
</target>
<config><configuration xmlns="http://yang.juniper.net/junos/conf/root">
<routing-instances xmlns="http://yang.juniper.net/junos/conf/routing-instances">
<instance>
<name>ABCD</name>
<bridge-domains>
<domain>
<name>ABC</name>
<vlan-id>2900</vlan-id>
<routing-interface>irb.2900</routing-interface>
<vxlan>
<vni>7900</vni>
<multicast-group>224.0.0.1</multicast-group>
<destination-udp-port>8745</destination-udp-port>
</vxlan>
<proxy-mac>
<irb/>
</proxy-mac>
</domain>
</bridge-domains>
</instance>
</routing-instances>
</configuration>
</config>
</edit-config>
</rpc> Seems only the YANG models needs to be updated in order to add that leaf |
Can I know the family of junos device you are using and I see you are using models from junos/ yang family directory? Can you also share the 'show system information' command outut? |
@rampolisetty yes, I am using those models for some parts of configuration. Related to my issue, am using this models for routing-instances: This is the junos version on the device: Junos: 22.2R2.10 |
Hi,
I want to used Juniper YANG models to create a configuration template and I noticed that
destination-udp-port
leaf is missing frombridge-domains.vxlan
grouping.Also, I can see the same on device CLI, that parameter is missing
But, it will be recognise once I enter the command
Thank you!
The text was updated successfully, but these errors were encountered: