Skip to content
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

Open
rcicu opened this issue Mar 28, 2023 · 3 comments
Open

Missing destination-udp-port leaf from bridge-domains.vxlan grouping #20

rcicu opened this issue Mar 28, 2023 · 3 comments

Comments

@rcicu
Copy link

rcicu commented Mar 28, 2023

Hi,

I want to used Juniper YANG models to create a configuration template and I noticed that destination-udp-port leaf is missing from bridge-domains.vxlan grouping.
Also, I can see the same on device CLI, that parameter is missing

device@v8529# set routing-instances ABCD bridge-domains ACB vxlan ?
Possible completions:
+ apply-groups         Groups from which to inherit configuration data
+ apply-groups-except  Don't inherit configuration data from these groups
  decapsulate-accept-inner-vlan  Accept VXLAN packets with inner VLAN
  encapsulate-inner-vlan  Retain inner VLAN in the packet
  ingress-node-replication  Enable ingress node replication
  multicast-group      Multicast group registered for VXLAN segment
  ovsdb-managed        Bridge-domain is managed remotely via VXLAN OVSDB Controller
+ static-remote-vtep-list  Configure bridge domain specific static remote VXLAN tunnel endpoints
  translation-vni      Translated VXLAN identifier (1..16777214)
  unreachable-vtep-aging-timer  Unreachable VXLAN tunnel endpoint removal timer (300..1800 seconds)
  vni                  VXLAN identifier (0..16777214)
[edit]

But, it will be recognise once I enter the command

set routing-instances ABCD instance-type virtual-switch
set routing-instances ABCD bridge-domains ABC vxlan destination-udp-port 8472

Thank you!

@rcicu
Copy link
Author

rcicu commented Mar 28, 2023

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

@rampolisetty
Copy link

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?

@rcicu
Copy link
Author

rcicu commented Mar 31, 2023

@rampolisetty yes, I am using those models for some parts of configuration. Related to my issue, am using this models for routing-instances: [email protected]

This is the junos version on the device: Junos: 22.2R2.10

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants