OC OSPF

Packages:

  • openconfig-network-instance.yang
  • openconfig-routing-policy.yang and openconfig-ospf-policy

Configuring OSPF PID in a Default Network Instance

Configuring OSPF PID in a Default Network Instance
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <config>
                <identifier xmlns:oc-pol-types="http://openconfig.net/yang/policy-types">oc-pol-types:OSPF</identifier>
                <name>1</name>
              </config>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>

Container: protocols


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

router ospf 1

Configuring an OSPF Router ID in a Default Network Instance

Configuring an OSPF Router ID in a Default Network Instance
 <rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <global>
                  <config>
                    <router-id>1.1.1.1</router-id>
                  </config>
                </global>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>

Container: protocols/ospfv2/gobal/config

Type: Config Data


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

router ospf 1
router-id 1.1.1.1

Deleting an OSPF Router ID

Deleting an OSPF Router ID
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <global>
                  <config>
                    <router-id xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" nc:operation="delete">1.1.1.1</router-id>
                  </config>
                </global>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

no router-id 1.1.1.1

Configuring an OSPF Router ID in a Non-Default VRF (vrf=ospfvrf)

Configuring an OSPF Router ID in a Non-Default VRF (vrf=ospfvrf)
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>ospfvrf</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <global>
                  <config>
                    <router-id>1.1.1.1</router-id>
                  </config>
                </global>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

router ospf 1
 vrf ospfvrf
  router-id 1.1.1.1

Replacing an OSPF Router ID

Replacing an OSPF Router ID
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>ospfvrf</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <global>
                  <config>
                    <router-id xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" nc:operation="replace">2.2.2.2</router-id>
                  </config>
                </global>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

router ospf 1
 vrf ospfvrf
  router-id 2.2.2.2

Querying the OSPF Router ID in the Default VRF

Querying the OSPF Router ID in the Default VRF
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <get-config>
    <source>
      <running/>
    </source>
    <filter>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <global>
                  <config>
                    <router-id/>
                  </config>
                </global>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </filter>
  </get-config>
</rpc>


CLI Command

The output for the CLI command is equivalent to the payload examples displayed in the pane on the right.

show run ospf | i router-id

Configuring OSPF Log Adjacency Changes

Configuring OSPF Log Adjacency Changes
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <global>
                  <config>
                    <log-adjacency-changes>true</log-adjacency-changes>
                  </config>
                </global>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>

Container: protocols/ospfv2/gobal/config


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

log-adjacency-changes

Deleting OSPF Log Adjacency Changes

Deleting OSPF Log Adjacency Changes
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <global>
                  <config>
                    <log-adjacency-changes xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" nc:operation="delete">true</log-adjacency-changes>
                  </config>
                </global>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

no log-adjacency-changes

Unconfiguring OSPF Log Adjacency Changes

Unconfiguring OSPF Log Adjacency Changes
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <global>
                  <config>
                    <log-adjacency-changes>false</log-adjacency-changes>
                  </config>
                </global>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

no log-adjacency-changes

Querying OSPF Log Adjacency Changes

Querying OSPF Log Adjacency Changes
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <get-config>
    <source>
      <running/>
    </source>
    <filter>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <global>
                  <config>
                    <log-adjacency-changes/>
                  </config>
                </global>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </filter>
  </get-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

show run ospf | i log

Deviations for OSPF Log Adjacency Changes

Deviations for OSPF Log Adjacency Changes

Note: Only log-adjacency-changes can be configured through OpenConfig.


Values and Behaviors

  • False - None
  • True - Brief
  • Detail - Unmapped

Creating SPF Timers

Creating SPF Timers
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <global>
                  <timers>
                    <spf>
                      <config>
                        <initial-delay>250</initial-delay>
                        <maximum-delay>2000</maximum-delay>
                      </config>
                    </spf>
                  </timers>
                </global>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>

Container: protocols/ospfv2/gobal/config/timers/spf/config


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

timers throttle spf 250 1000 2000

Querying SPF Timers

Querying SPF Timers
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <get-config>
    <source>
      <running/>
    </source>
    <filter>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <global>
                  <timers>
                    <spf>
                      <config>
                        <initial-delay/>
                        <maximum-delay/>
                      </config>
                    </spf>
                  </timers>
                </global>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </filter>
  </get-config>
</rpc>


CLI Command

The output for the CLI command is equivalent to the payload examples displayed in the pane on the right.

show run ospf | i "timers throttle spf"

Deleting SPF Timers

Deleting SPF Timers
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <global>
                  <timers>
                    <spf>
                      <config>
                        <initial-delay xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" nc:operation="delete">250</initial-delay>
                        <maximum-delay xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" nc:operation="delete">2000</maximum-delay>
                      </config>
                    </spf>
                  </timers>
                </global>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

no timers throttle spf 250 1000 2000

Replacing SPF Timers

Replacing SPF Timers
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <global>
                  <timers>
                    <spf>
                      <config>
                        <initial-delay xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" nc:operation="replace">350</initial-delay>
                        <maximum-delay xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" nc:operation="replace">2500</maximum-delay>
                      </config>
                    </spf>
                  </timers>
                </global>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

timers throttle spf 350 1000 2500

Configuring Graceful Restart in OSPF

Configuring Graceful Restart in OSPF
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <global>
                  <graceful-restart>
                    <config>
                      <enabled>true</enabled>
                    </config>
                  </graceful-restart>
                </global>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>

Container: protocols/ospfv2/gobal/config/graceful-restart/config


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

graceful-restart

Disabling Graceful Restart in OSPF

Disabling Graceful Restart in OSPF
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <global>
                  <graceful-restart>
                    <config>
                      <enabled>false</enabled>
                    </config>
                  </graceful-restart>
                </global>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

no graceful-restart

Deviations for OSPF Graceful Restart

Deviations for OSPF Graceful Restart

  • Graceful restart is enabled by default in the Cisco Nexus 9000 Series with a grace period of 60 sec. The graceful restart can be set to True or False.
  • The grace period cannot be configured.
  • graceful-restart helper-only is not supported.

Configuring OSPF Area Identifier

Configuring OSPF Area Identifier
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.0</identifier>
                    <interfaces>
                      <interface>
                        <id>eth1/1</id>
                        <config>
                          <id>eth1/1</id>
                        </config>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>

Container: protocols/ospfv2/areas/config


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

ip router ospf 1 area 0.0.0.0

Querying the OSPF Area Identifier

Querying the OSPF Area Identifier
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <get-config>
    <source>
      <running/>
    </source>
    <filter>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.0</identifier>
                    <config>
                      <identifier/>
                    </config>
                    <interfaces>
                      <interface>
                        <id>eth1/1</id>
                        <config>
                          <id/>
                        </config>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </filter>
  </get-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

show run ospf

Configuring OSPF Priority

Configuring OSPF Priority
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.0</identifier>
                    <interfaces>
                      <interface>
                        <id>eth1/1</id>
                        <config>
                          <id>eth1/1</id>
                          <priority>110</priority>
                        </config>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>

Container: protocols/ospfv2/areas/(area)/interfaces/config

List: area


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

ip ospf priority 110

Querying OSPF Priority

Querying OSPF Priority
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <get-config>
    <source>
      <running/>
    </source>
    <filter>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.0</identifier>
                    <interfaces>
                      <interface>
                        <id>eth1/1</id>
                        <config>
                          <id/>
                          <priority/>
                        </config>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </filter>
  </get-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

show run ospf | i prio

Deleting the OSPF Priority

Deleting the OSPF Priority
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.0</identifier>
                    <interfaces>
                      <interface>
                        <id>eth1/1</id>
                        <config>
                          <id>eth1/1</id>
                          <priority xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" nc:operation="delete">101</priority>
                        </config>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

no ip ospf priority 110

Configuring OSPF Network Type (Broadcast)

Configuring OSPF Network Type (Broadcast)
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>OC</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.201</identifier>
                    <interfaces>
                      <interface>
                        <id>vlan200</id>
                        <config>
                          <id>vlan200</id>
                          <network-type xmlns:oc-ospf-types="http://openconfig.net/yang/ospf-types">oc-ospf-types:BROADCAST_NETWORK</network-type>
                        </config>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

ip ospf network broadcast

Configuring the Network Type for Ethernet Interfaces

Configuring the Network Type for Ethernet Interfaces
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>OC</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.201</identifier>
                    <interfaces>
                      <interface>
                        <id>eth1/1</id>
                        <config>
                          <id>eth1/1</id>
                          <network-type xmlns:oc-ospf-types="http://openconfig.net/yang/ospf-types">oc-ospf-types:BROADCAST_NETWORK</network-type>
                        </config>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>

Querying the OSPF Network Type

Querying the OSPF Network Type
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <get-config>
    <source>
      <running/>
    </source>
    <filter>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>OC</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.201</identifier>
                    <interfaces>
                      <interface>
                        <id>vlan 200</id>
                        <config>
                          <network-type/>
                        </config>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </filter>
  </get-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

show run ospf

Configuring the OSPF Network Type (Point to Point)

 Configuring the OSPF Network Type (Point to Point)
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>OC</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.201</identifier>
                    <interfaces>
                      <interface>
                        <id>vlan200</id>
                        <config>
                          <id>vlan200</id>
                          <network-type xmlns:oc-ospf-types="http://openconfig.net/yang/ospf-types">oc-ospf-types:POINT_TO_POINT_NETWORK</network-type>
                        </config>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

ip ospf network point-to-point

Replacing the OSPF Network Type (Point to Point)

Replacing the OSPF Network Type (Point to Point)
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>OC</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.201</identifier>
                    <interfaces>
                      <interface>
                        <id>vlan200</id>
                        <config>
                          <id>vlan200</id>
                          <network-type xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" nc:operation="replace">oc-ospf-types:BROADCAST_NETWORK</network-type>
                        </config>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

ip ospf network <network-type>

Deleting the OSPF Network Type (Broadcast)

 Deleting the OSPF Network Type (Broadcast)
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>OC</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.201</identifier>
                    <interfaces>
                      <interface>
                        <id>vlan200</id>
                        <config>
                          <id>vlan200</id>
                          <network-type xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" nc:operation="delete"/>
                        </config>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

no ip ospf network broadcast

Configuring OSPF MD5 Authentication Type

Configuring OSPF MD5 Authentication Type
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>OC</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.200</identifier>
                    <interfaces>
                      <interface>
                        <id>vlan200</id>
                        <config>
                          <id>vlan200</id>
                          <authentication-type>md5</authentication-type>
                        </config>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

ip ospf authentication message-digest

Configuring the Authentication Type in Ethernet Interfaces

Configuring the Authentication Type in Ethernet Interfaces
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.0</identifier>
                    <interfaces>
                      <interface>
                        <id>eth1/1</id>
                        <config>
                          <authentication-type>md5</authentication-type>
                        </config>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>

Querying OSPF MD5 Authentication Type

Querying OSPF MD5 Authentication Type
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <get-config>
    <source>
      <running/>
    </source>
    <filter>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>OC</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <interfaces>
                      <interface>
                        <id>vlan200</id>
                        <config>
                          <authentication-type/>
                        </config>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </filter>
  </get-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

show run ospf

Querying the OSPF Interfaces Container (MD5 Authentication Type)

Querying the OSPF Interfaces Container (MD5 Authentication Type)
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <get-config>
    <source>
      <running/>
    </source>
    <filter>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>OC</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <interfaces/>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </filter>
  </get-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

show run ospf

Configuring a NULL Authentication Type

Configuring a NULL Authentication Type
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>OC</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.200</identifier>
                    <interfaces>
                      <interface>
                        <id>vlan200</id>
                        <config>
                          <id>vlan200</id>
                          <authentication-type>none</authentication-type>
                        </config>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

ip ospf authentication null

Deleting the NULL Authentication Type

Deleting the NULL Authentication Type
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>OC</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.0</identifier>
                    <interfaces>
                      <interface>
                        <id>vlan200</id>
                        <config>
                          <id>vlan200</id>
                          <authentication-type xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" nc:operation="delete"/>
                        </config>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

no ip ospf authentication null

Removing the MD5 Authentication Type

Removing the MD5 Authentication Type
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>OC</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.201</identifier>
                    <interfaces>
                      <interface>
                        <id>vlan200</id>
                        <config>
                          <id>vlan200</id>
                          <authentication-type xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" nc:operation="remove">md5</authentication-type>
                        </config>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

no ip ospf authentication message-digest

Configuring OSPF Metric

Configuring OSPF Metric
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>OC</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.200</identifier>
                    <interfaces>
                      <interface>
                        <id>vlan200</id>
                        <config>
                          <id>vlan200</id>
                          <metric>10</metric>
                        </config>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

ip ospf cost 10

Configuring the Cost for Ethernet Insterfaces

Configuring the Cost for Ethernet Insterfaces
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.0</identifier>
                    <interfaces>
                      <interface>
                        <id>eth1/1</id>
                        <config>
                          <metric>10</metric>
                        </config>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>

Querying the OSPF Metric

Querying the OSPF Metric
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <get-config>
    <source>
      <running/>
    </source>
    <filter>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>OC</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.1</identifier>
                    <interfaces>
                      <interface>
                        <id>vlan200</id>
                        <config>
                          <metric/>
                        </config>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </filter>
  </get-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

show run ospf

Querying the OSPF Metric

Querying the OSPF Metric
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <get>
    <filter>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>OC</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.200</identifier>
                    <interfaces>
                      <interface>
                        <config>
                          <metric/>
                        </config>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </filter>
  </get>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

show run ospf

Replacing the OSPF Metric from 10 to 20

Replacing the OSPF Metric from 10 to 20 
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>OC</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.200</identifier>
                    <interfaces>
                      <interface>
                        <id>vlan200</id>
                        <config>
                          <id>vlan200</id>
                          <metric xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" nc:operation="replace">20</metric>
                        </config>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

ip ospf cost 20

Deleting the OSPF Metric

Deleting the OSPF Metric
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>OC</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.200</identifier>
                    <interfaces>
                      <interface>
                        <id>vlan200</id>
                        <config>
                          <id>vlan200</id>
                          <metric xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" nc:operation="delete"/>
                        </config>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

no ip ospf cost 20

Configuring OSPF Passive Interface

Configuring OSPF Passive Interface
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.0</identifier>
                    <interfaces>
                      <interface>
                        <id>vlan200</id>
                        <config>
                          <id>vlan200</id>
                          <passive>true</passive>
                        </config>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

ip ospf passive-interface

Configuring OSPF Passive Interface in an Ethernet Interface

Configuring OSPF Passive Interface in an Ethernet Interface
<rpc xmln
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.0</identifier>
                    <interfaces>
                      <interface>
                        <id>eth1/1</id>
                        <config>
                          <passive>true</passive>
                        </config>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>

Querying OSPF Passive Interface

Querying OSPF Passive Interface
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <get-config>
    <source>
      <running/>
    </source>
    <filter>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.0</identifier>
                    <interfaces>
                      <interface>
                        <id>vlan200</id>
                        <config>
                          <id/>
                          <passive/>
                        </config>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </filter>
  </get-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

show run ospf

Deleting an OSPF Passive Interface Configuration

Deleting an OSPF Passive Interface Configuration
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.0</identifier>
                    <interfaces>
                      <interface>
                        <id>vlan200</id>
                        <config>
                          <id>vlan200</id>
                          <passive xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" nc:operation="delete"/>
                        </config>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

no ip ospf passive-interface

Disabling OSPF Passive Interface

Disabling OSPF Passive Interface
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.0</identifier>
                    <interfaces>
                      <interface>
                        <id>vlan200</id>
                        <config>
                          <id>vlan200</id>
                          <passive>false</passive>
                        </config>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

no ip ospf passive-interface

Configuring an OSPF Dead Interval

Configuring an OSPF Dead Interval
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.0</identifier>
                    <interfaces>
                      <interface>
                        <id>vlan200</id>
                        <config>
                          <id>vlan200</id>
                        </config>
                        <timers>
                          <config>
                            <dead-interval>80</dead-interval>
                          </config>
                        </timers>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>

Container: protocols/ospfv2/areas/(area)/interfaces/interface/timers

List: interface


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

ip ospf dead-interval 80

Configuring an OSPF Dead Interval for Ethernet Interfaces

Configuring an OSPF Dead Interval for Ethernet Interfaces
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.0</identifier>
                    <interfaces>
                      <interface>
                        <id>eth1/1</id>
                        <timers>
                          <config>
                            <dead-interval>80</dead-interval>
                          </config>
                        </timers>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>

Configuring an OSPF Hello Interval

Configuring an OSPF Hello Interval
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.0</identifier>
                    <interfaces>
                      <interface>
                        <id>vlan200</id>
                        <config>
                          <id>vlan200</id>
                        </config>
                        <timers>
                          <config>
                            <hello-interval>20</hello-interval>
                          </config>
                        </timers>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

ip ospf hello-interval 20

Configuring a Hello Interval for Ethernet Interfaces

Configuring a Hello Interval for Ethernet Interfaces
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.0</identifier>
                    <interfaces>
                      <interface>
                        <id>eth1/1</id>
                        <timers>
                          <config>
                            <hello-interval>20</hello-interval>
                          </config>
                        </timers>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>

Configuring OSPF Retransmission Interval

Configuring OSPF Retransmission Interval
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.0</identifier>
                    <interfaces>
                      <interface>
                        <id>vlan200</id>
                        <config>
                          <id>vlan200</id>
                        </config>
                        <timers>
                          <config>
                            <retransmission-interval>10</retransmission-interval>
                          </config>
                        </timers>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

ip ospf retransmit-interval 10

Querying the OSPF Timers Container (Hello, Dead, and Retransmission Interval)

Querying the OSPF Timers Container (Hello, Dead, and Retransmission Interval)
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <get-config>
    <source>
      <running/>
    </source>
    <filter>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.0</identifier>
                    <interfaces>
                      <interface>
                        <id>vlan200</id>
                        <timers/>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </filter>
  </get-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

show run ospf

Deleting an IP OSPF Hello Interval

Deleting an IP OSPF Hello Interval
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.0</identifier>
                    <interfaces>
                      <interface>
                        <id>vlan200</id>
                        <config>
                          <id>vlan200</id>
                        </config>
                        <timers>
                          <config>
                            <hello-interval xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" nc:operation="delete"/>
                          </config>
                        </timers>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

no ip ospf hello-interval 20

Deleting an IP OSPF Dead Interval

Deleting an IP OSPF Dead Interval
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.0</identifier>
                    <interfaces>
                      <interface>
                        <id>vlan200</id>
                        <config>
                          <id>vlan200</id>
                        </config>
                        <timers>
                          <config>
                            <dead-interval xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" nc:operation="delete"/>
                          </config>
                        </timers>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

no ip ospf dead-interval 80

Deleting IP OSPF Retransmission Interval

Deleting IP OSPF Retransmission Interval
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.0</identifier>
                    <interfaces>
                      <interface>
                        <id>vlan200</id>
                        <config>
                          <id>vlan200</id>
                        </config>
                        <timers>
                          <config>
                            <retransmission-interval xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" nc:operation="delete"/>
                          </config>
                        </timers>
                      </interface>
                    </interfaces>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

no ip ospf retransmit-interval 10

Configuring a Match OSPF Area Policy

Configuring a Match OSPF Area Policy
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <routing-policy xmlns="http://openconfig.net/yang/routing-policy">
        <policy-definitions>
          <policy-definition>
            <name>test</name>
            <statements>
              <statement>
                <name>10</name>
                <conditions>
                  <ospf-conditions xmlns="http://openconfig.net/yang/ospf-policy">
                    <config>
                      <area-eq>10</area-eq>
                    </config>
                  </ospf-conditions>
                </conditions>
              </statement>
            </statements>
          </policy-definition>
        </policy-definitions>
      </routing-policy>
    </config>
  </edit-config>
</rpc>

Container: routing-policy/policy-definitions/statements/conditions


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

match ospf-area 10

Querying a Match OSPF Area Policy

Querying a Match OSPF Area Policy
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <get-config>
    <source>
      <running/>
    </source>
    <filter>
      <routing-policy xmlns="http://openconfig.net/yang/routing-policy">
        <policy-definitions/>
      </routing-policy>
    </filter>
  </get-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

show run ospf

Deleting a Match OSPF Area Policy

Deleting a Match OSPF Area Policy
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <routing-policy xmlns="http://openconfig.net/yang/routing-policy">
        <policy-definitions>
          <policy-definition>
            <name>test</name>
            <statements>
              <statement>
                <name>10</name>
                <conditions>
                  <ospf-conditions xmlns="http://openconfig.net/yang/ospf-policy">
                    <config>
                      <area-eq xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" nc:operation="delete"/>
                    </config>
                  </ospf-conditions>
                </conditions>
              </statement>
            </statements>
          </policy-definition>
        </policy-definitions>
      </routing-policy>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

no match ospf-area 10

Configuring Set Metric Type OSPF Policy (Type-1)

Configuring Set Metric Type OSPF Policy (Type-1)
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <routing-policy xmlns="http://openconfig.net/yang/routing-policy">
        <policy-definitions>
          <policy-definition>
            <name>test</name>
            <statements>
              <statement>
                <name>10</name>
                <actions>
                  <ospf-actions xmlns="http://openconfig.net/yang/ospf-policy">
                    <set-metric>
                      <config>
                        <metric-type>EXTERNAL_TYPE_1</metric-type>
                      </config>
                    </set-metric>
                  </ospf-actions>
                </actions>
              </statement>
            </statements>
          </policy-definition>
        </policy-definitions>
      </routing-policy>
    </config>
  </edit-config>
</rpc>

Container: routing-policy/policy-definitions/statements/actions


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

set metric-type type-1

Configuring Set Metric Type OSPF Policy (Type-2)

Configuring Set Metric Type OSPF Policy (Type-2)
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <routing-policy xmlns="http://openconfig.net/yang/routing-policy">
        <policy-definitions>
          <policy-definition>
            <name>test</name>
            <statements>
              <statement>
                <name>10</name>
                <actions>
                  <ospf-actions xmlns="http://openconfig.net/yang/ospf-policy">
                    <set-metric>
                      <config>
                        <metric-type>EXTERNAL_TYPE_2</metric-type>
                      </config>
                    </set-metric>
                  </ospf-actions>
                </actions>
              </statement>
            </statements>
          </policy-definition>
        </policy-definitions>
      </routing-policy>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

set metric-type type-2

Querying Set Metric Type OSPF Policies

Querying  Set Metric Type OSPF Policies
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <get-config>
    <source>
      <running/>
    </source>
    <filter>
      <routing-policy xmlns="http://openconfig.net/yang/routing-policy">
        <policy-definitions>
          <policy-definition>
            <name>test</name>
            <statements>
              <statement>
                <name>10</name>
                <actions>
                  <ospf-actions xmlns="http://openconfig.net/yang/ospf-policy">
                    <set-metric>
                      <config>
                        <metric-type/>
                      </config>
                    </set-metric>
                  </ospf-actions>
                </actions>
              </statement>
            </statements>
          </policy-definition>
        </policy-definitions>
      </routing-policy>
    </filter>
  </get-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

show run rpm

Configuring LSA Timers (Initial Delay and Maximum Delay)

Configuring LSA Timers (Initial Delay and Maximum Delay)
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <global>
                  <timers>
                    <lsa-generation>
                      <config>
                        <initial-delay>200</initial-delay>
                        <maximum-delay>2500</maximum-delay>
                      </config>
                    </lsa-generation>
                  </timers>
                </global>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>

Container: protocols/ospfv2/gobal/config/timers/lsa-generation/config


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

timers throttle lsa 200 5000 2500

Querying LSA Timers (Initial Delay and Maximum Delay)

Querying LSA Timers (Initial Delay and Maximum Delay)
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <get-config>
    <source>
      <running/>
    </source>
    <filter>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <global>
                  <timers>
                    <lsa-generation>
                      <config>
                        <initial-delay/>
                        <maximum-delay/>
                      </config>
                    </lsa-generation>
                  </timers>
                </global>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </filter>
  </get-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

show run ospf

Deleting LSA Timers (Initial Delay and Maximum Delay)

Deleting LSA Timers (Initial Delay and Maximum Delay)
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <global>
                  <timers>
                    <lsa-generation>
                      <config>
                        <initial-delay xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" nc:operation="delete"/>
                        <maximum-delay xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" nc:operation="delete"/>
                      </config>
                    </lsa-generation>
                  </timers>
                </global>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

`no timers throttle lsa 200 5000 2500

Replacing LSA Timers (Initial Delay and Maximum Delay)

Replacing LSA Timers (Initial Delay and Maximum Delay)
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <global>
                  <timers>
                    <lsa-generation>
                      <config>
                        <initial-delay xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" nc:operation="replace">300</initial-delay>
                        <maximum-delay xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" nc:operation="replace">3000</maximum-delay>
                      </config>
                    </lsa-generation>
                  </timers>
                </global>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

timers throttle lsa 300 5000 3000

Configuring Max Metric (router-lsa include-stub)

Configuring Max Metric (router-lsa include-stub)
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <global>
                  <timers>
                    <max-metric>
                      <config>
                        <set>true</set>
                        <include>oc-ospf-types:MAX_METRIC_INCLUDE_STUB</include>
                      </config>
                    </max-metric>
                  </timers>
                </global>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>

Container: protocols/ospfv2/gobal/config/timers/max-metric/config


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

max-metric router-lsa include-stub

Configuring Max Metric (router-lsa external-lsa)

Configuring Max Metric (router-lsa external-lsa)
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <global>
                  <timers>
                    <max-metric>
                      <config>
                        <set>true</set>
                        <include>oc-ospf-types:MAX_METRIC_INCLUDE_TYPE2_EXTERNAL</include>
                      </config>
                    </max-metric>
                  </timers>
                </global>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

max-metric router-lsa external-lsa

Configuring Max Metric (router-lsa external-lsa With Trigger on-startup and Timeout)

Configuring Max Metric (router-lsa external-lsa With Trigger on-startup and Timeout)
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <global>
                  <timers>
                    <max-metric>
                      <config>
                        <set>true</set>
                        <timeout>250</timeout>
                        <include>oc-ospf-types:MAX_METRIC_INCLUDE_TYPE2_EXTERNAL</include>
                        <trigger>oc-ospf-types:MAX_METRIC_ON_SYSTEM_BOOT</trigger>
                      </config>
                    </max-metric>
                  </timers>
                </global>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

max-metric router-lsa external-lsa on-startup 250

Querying Max Metric (router-lsa external-lsa With Trigger on-startup and Timeout)

Querying Max Metric (router-lsa external-lsa With Trigger on-startup and Timeout)
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <get-config>
    <source>
      <running/>
    </source>
    <filter>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <global>
                  <timers>
                    <max-metric>
                      <config>
                        <set/>
                        <timeout/>
                        <include/>
                        <trigger/>
                      </config>
                    </max-metric>
                  </timers>
                </global>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </filter>
  </get-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

show run ospf

Deleting Max Metric

Deleting Max Metric
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <global>
                  <timers>
                    <max-metric>
                      <config>
                        <set xmlns:nc="urn:ietf:params:xml:ns:netconf:base:1.0" nc:operation="delete">true</set>
                      </config>
                    </max-metric>
                  </timers>
                </global>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

no max-metric router-lsa external-lsa on-startup 250

Disablng Max Metric

Disablng Max Metric
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <global>
                  <timers>
                    <max-metric>
                      <config>
                        <set>false</set>
                      </config>
                    </max-metric>
                  </timers>
                </global>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

no max-metric router-lsa external-lsa on-startup 250

Configuring OSPF Virtual Link 
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <edit-config>
    <target>
      <running/>
    </target>
    <config>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.1</identifier>
                    <virtual-links>
                      <virtual-link>
                        <remote-router-id>3.3.3.3</remote-router-id>
                        <config>
                          <remote-router-id>3.3.3.3</remote-router-id>
                        </config>
                      </virtual-link>
                    </virtual-links>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </config>
  </edit-config>
</rpc>

Container: protocols/ospfv2/areas/area/virtual-links


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

area 0.0.0.1 virtual-link 3.3.3.3

Querying OSPF Virtual Links
<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
  <get-config>
    <source>
      <running/>
    </source>
    <filter>
      <network-instances xmlns="http://openconfig.net/yang/network-instance">
        <network-instance>
          <name>default</name>
          <protocols>
            <protocol>
              <identifier>OSPF</identifier>
              <name>1</name>
              <ospfv2>
                <areas>
                  <area>
                    <identifier>0.0.0.1</identifier>
                    <virtual-links/>
                  </area>
                </areas>
              </ospfv2>
            </protocol>
          </protocols>
        </network-instance>
      </network-instances>
    </filter>
  </get-config>
</rpc>


CLI Commands

The CLI commands are equivalent to the payload examples displayed in the pane on the right.

show run ospf

Other Deviations:

  • A router ID cannot be configured under a VRF (the property not mapped).
  • Whitespace after VRF instance name is illegal (path: /network-instances/network-instance/config/name).