OC IF-IP
Packages:
- openconfig-if-ip.yang
- openconfig-if-ip-ext.yang
Configuring an IPv4 Routed Interface
Configuring an IPv4 Routed Interface
Request:
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<running/>
</target>
<config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
<interfaces xmlns="http://openconfig.net/yang/interfaces" xmlns:oc-ip="http://openconfig.net/yang/interfaces/ip">
<interface>
<name>eth2/16</name>
<config>
<type xmlns:ianaift="urn:ietf:params:xml:ns:yang:iana-if-type">ianaift:ethernetCsmacd</type>
</config>
<subinterfaces>
<subinterface>
<index>0</index>
<oc-ip:ipv4>
<oc-ip:addresses>
<oc-ip:address>
<oc-ip:ip>10.1.1.1</oc-ip:ip>
<oc-ip:config>
<oc-ip:ip>10.1.1.1</oc-ip:ip>
<oc-ip:prefix-length>24</oc-ip:prefix-length>
</oc-ip:config>
</oc-ip:address>
</oc-ip:addresses>
</oc-ip:ipv4>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
</config>
</edit-config>
</rpc>
Response:
<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<ok/>
</rpc-reply>
Container: Config Data
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
interface eth2/16
ip address 10.1.1.1/24
Configuring an IPv4 Sub-Interface
Configuring an IPv4 Sub-Interface
Request:
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<running/>
</target>
<config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
<interfaces xmlns="http://openconfig.net/yang/interfaces" xmlns:oc-ip="http://openconfig.net/yang/interfaces/ip">
<interface>
<name>eth2/16</name>
<config>
<type xmlns:ianaift="urn:ietf:params:xml:ns:yang:iana-if-type">ianaift:ethernetCsmacd</type>
</config>
<subinterfaces>
<subinterface>
<index>10</index>
<oc-ip:ipv4>
<oc-ip:addresses>
<oc-ip:address>
<oc-ip:ip>10.1.1.1</oc-ip:ip>
<oc-ip:config>
<oc-ip:ip>10.1.1.1</oc-ip:ip>
<oc-ip:prefix-length>24</oc-ip:prefix-length>
</oc-ip:config>
</oc-ip:address>
</oc-ip:addresses>
</oc-ip:ipv4>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
</config>
</edit-config>
</rpc>
Response:
<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<ok/>
</rpc-reply>
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
interface eth2/16.10
ip address 10.1.1.1/24
Configuring an IPv4 SVI
Configuring an IPv4 SVI
Request:
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<running/>
</target>
<config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
<interfaces xmlns="http://openconfig.net/yang/interfaces" xmlns:oc-ip="http://openconfig.net/yang/interfaces/ip" xmlns:oc-vlan="http://openconfig.net/yang/vlan">
<interface>
<name>vlan121</name>
<config>
<type xmlns:ianaift="urn:ietf:params:xml:ns:yang:iana-if-type">ianaift:l2vlan</type>
</config>
<oc-vlan:routed-vlan>
<oc-ip:ipv4>
<oc-ip:addresses>
<oc-ip:address>
<oc-ip:ip>100.1.2.1</oc-ip:ip>
<oc-ip:config>
<oc-ip:ip>100.1.2.1</oc-ip:ip>
<oc-ip:prefix-length>24</oc-ip:prefix-length>
</oc-ip:config>
</oc-ip:address>
</oc-ip:addresses>
</oc-ip:ipv4>
</oc-vlan:routed-vlan>
</interface>
</interfaces>
</config>
</edit-config>
</rpc>
Response:
<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<ok/>
</rpc-reply>
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
interface vlan121
ip address 100.1.2.1/24
Configuring an IPv4 Loopback Interface
Configuring a Loopback Interface
Request:
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<running/>
</target>
<config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
<interfaces xmlns="http://openconfig.net/yang/interfaces" xmlns:oc-ip="http://openconfig.net/yang/interfaces/ip">
<interface>
<name>lo0</name>
<config>
<type xmlns:ianaift="urn:ietf:params:xml:ns:yang:iana-if-type">ianaift:softwareLoopback</type>
</config>
<subinterfaces>
<subinterface>
<index>0</index>
<oc-ip:ipv4>
<oc-ip:addresses>
<oc-ip:address>
<oc-ip:ip>111.111.111.111</oc-ip:ip>
<oc-ip:config>
<oc-ip:ip>111.111.111.111</oc-ip:ip>
<oc-ip:prefix-length>32</oc-ip:prefix-length>
</oc-ip:config>
</oc-ip:address>
</oc-ip:addresses>
</oc-ip:ipv4>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
</config>
</edit-config>
</rpc>
Response:
<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<ok/>
</rpc-reply>
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
interface loopback0
ip address 111.111.111.111/32
Configuring an IPv4 Neighbor
Configuring an IPv4 Neighbor
Request:
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<running/>
</target>
<config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
<interfaces xmlns="http://openconfig.net/yang/interfaces" xmlns:oc-ip="http://openconfig.net/yang/interfaces/ip" xmlns:oc-vlan="http://openconfig.net/yang/vlan">
<interface>
<name>vlan121</name>
<config>
<type xmlns:ianaift="urn:ietf:params:xml:ns:yang:iana-if-type">ianaift:l2vlan</type>
</config>
<oc-vlan:routed-vlan>
<oc-ip:ipv4>
<oc-ip:addresses>
<oc-ip:address>
<oc-ip:ip>100.1.2.1</oc-ip:ip>
<oc-ip:config>
<oc-ip:ip>100.1.2.1</oc-ip:ip>
<oc-ip:prefix-length>24</oc-ip:prefix-length>
</oc-ip:config>
</oc-ip:address>
</oc-ip:addresses>
<oc-ip:neighbors>
<oc-ip:neighbor>
<oc-ip:ip>100.1.2.10</oc-ip:ip>
<oc-ip:config>
<oc-ip:ip>100.1.2.10</oc-ip:ip>
<oc-ip:link-layer-address>1.1.2</oc-ip:link-layer-address>
</oc-ip:config>
</oc-ip:neighbor>
</oc-ip:neighbors>
</oc-ip:ipv4>
</oc-vlan:routed-vlan>
</interface>
</interfaces>
</config>
</edit-config>
</rpc>
Response:
<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<ok/>
</rpc-reply>
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
interface vlan121
ip address 100.1.2.1/24
ip arp 10.1.2.10 1.1.2
Querying an IPv4 Neighbor with Neighbor Index
Querying an IPv4 Neighbor with Neighbor Index
Request:
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<get>
<filter>
<interfaces xmlns="http://openconfig.net/yang/interfaces" xmlns:oc-ip="http://openconfig.net/yang/interfaces/ip" xmlns:oc-vlan="http://openconfig.net/yang/vlan">
<interface>
<name>vlan1504</name>
<oc-vlan:routed-vlan>
<oc-ip:ipv4>
<oc-ip:neighbors>
<oc-ip:neighbor>
<oc-ip:ip>18.2.1.100</oc-ip:ip>
</oc-ip:neighbor>
</oc-ip:neighbors>
</oc-ip:ipv4>
</oc-vlan:routed-vlan>
</interface>
</interfaces>
</filter>
</get>
</rpc>
Response:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<data>
<interfaces xmlns="http://openconfig.net/yang/interfaces">
<interface>
<name>vlan1504</name>
<routed-vlan xmlns="http://openconfig.net/yang/vlan">
<ipv4 xmlns="http://openconfig.net/yang/interfaces/ip">
<neighbors>
<neighbor>
<ip>18.2.1.100</ip>
<config>
<ip>18.2.1.100</ip>
<link-layer-address>00:01:00:01:00:10</link-layer-address>
</config>
</neighbor>
</neighbors>
</ipv4>
</routed-vlan>
</interface>
</interfaces>
</data>
</rpc-reply>
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
interface vlan1504; ip arp 18.2.1.100 0001.0001.0010
Querying an IPv4 Interface at the Container
Querying an IPv4 Interface at the Container
Request:
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<get-config>
<source><running/></source>
<filter>
<interfaces xmlns="http://openconfig.net/yang/interfaces" xmlns:oc-ip="http://openconfig.net/yang/interfaces/ip" xmlns:oc-vlan="http://openconfig.net/yang/vlan">
<interface>
<name>vlan1502</name>
<oc-vlan:routed-vlan>
<oc-ip:ipv4/>
</oc-vlan:routed-vlan>
</interface>
</interfaces>
</filter>
</get-config>
</rpc>
Response:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<data>
<interfaces xmlns="http://openconfig.net/yang/interfaces">
<interface>
<name>vlan1502</name>
<routed-vlan xmlns="http://openconfig.net/yang/vlan">
<ipv4 xmlns="http://openconfig.net/yang/interfaces/ip">
<addresses>
<address>
<config>
<ip>18.2.1.2</ip>
<prefix-length>24</prefix-length>
</config>
<ip>18.2.1.2</ip>
</address>
</addresses>
</ipv4>
</routed-vlan>
</interface>
</interfaces>
</data>
</rpc-reply>
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
interface vlan1502; ipv4 address 18.2.1.2/24
Configuring an IPv6 Routed Interface
Configuring an IPv6 Routed Interface
Request:
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<running/>
</target>
<config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
<interfaces xmlns="http://openconfig.net/yang/interfaces" xmlns:oc-ip="http://openconfig.net/yang/interfaces/ip">
<interface>
<name>eth2/16</name>
<config>
<type xmlns:ianaift="urn:ietf:params:xml:ns:yang:iana-if-type">ianaift:ethernetCsmacd</type>
</config>
<subinterfaces>
<subinterface>
<index>0</index>
<oc-ip:ipv6>
<oc-ip:addresses>
<oc-ip:address>
<oc-ip:ip>100:1:1::1</oc-ip:ip>
<oc-ip:config>
<oc-ip:ip>100:1:1::1</oc-ip:ip>
<oc-ip:prefix-length>64</oc-ip:prefix-length>
</oc-ip:config>
</oc-ip:address>
</oc-ip:addresses>
</oc-ip:ipv6>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
</config>
</edit-config>
</rpc>
Response:
<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<ok/>
</rpc-reply>
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
interface eth2/16
ipv6 address 100:1:1::1/64
Configuring an IPv6 Sub-Interface
Configuring an IPv6 Sub-Interface
Request:
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<running/>
</target>
<config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
<interfaces xmlns="http://openconfig.net/yang/interfaces" xmlns:oc-ip="http://openconfig.net/yang/interfaces/ip">
<interface>
<name>eth2/16</name>
<config>
<type xmlns:ianaift="urn:ietf:params:xml:ns:yang:iana-if-type">ianaift:ethernetCsmacd</type>
</config>
<subinterfaces>
<subinterface>
<index>10</index>
<oc-ip:ipv6>
<oc-ip:addresses>
<oc-ip:address>
<oc-ip:ip>100:1:1::1</oc-ip:ip>
<oc-ip:config>
<oc-ip:ip>100:1:1::1</oc-ip:ip>
<oc-ip:prefix-length>64 </oc-ip:prefix-length>
</oc-ip:config>
</oc-ip:address>
</oc-ip:addresses>
</oc-ip:ipv6>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
</config>
</edit-config>
</rpc>
Response:
<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<ok/>
</rpc-reply>
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
interface eth2/16.10
ipv6 address 100:1:1::1/64
Configuring an IPv6 SVI
Configuring an IPv6 SVI
Request:
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<running/>
</target>
<config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
<interfaces xmlns="http://openconfig.net/yang/interfaces" xmlns:oc-ip="http://openconfig.net/yang/interfaces/ip" xmlns:oc-vlan="http://openconfig.net/yang/vlan">
<interface>
<name>vlan121</name>
<config>
<type xmlns:ianaift="urn:ietf:params:xml:ns:yang:iana-if-type">ianaift:l2vlan</type>
</config>
<oc-vlan:routed-vlan>
<oc-ip:ipv6>
<oc-ip:addresses>
<oc-ip:address>
<oc-ip:ip>100:1:1::1</oc-ip:ip>
<oc-ip:config>
<oc-ip:ip>100:1:1::1</oc-ip:ip>
<oc-ip:prefix-length>64</oc-ip:prefix-length>
</oc-ip:config>
</oc-ip:address>
</oc-ip:addresses>
</oc-ip:ipv6>
</oc-vlan:routed-vlan>
</interface>
</interfaces>
</config>
</edit-config>
</rpc>
Response:
<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<ok/>
</rpc-reply>
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
interface vlan121
ipv6 address 100:1:1::1/64
Configuring an IPv6 Loopback Interface
Configuring an IPv6 Loopback Interface
Request:
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<candidate/>
</target>
<config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
<interfaces xmlns="http://openconfig.net/yang/interfaces" xmlns:oc-ip="http://openconfig.net/yang/interfaces/ip">
<interface>
<name>lo0</name>
<config>
<type xmlns:ianaift="urn:ietf:params:xml:ns:yang:iana-if-type">ianaift:softwareLoopback</type>
</config>
<subinterfaces>
<subinterface>
<index>0</index>
<oc-ip:ipv6>
<oc-ip:addresses>
<oc-ip:address>
<oc-ip:ip>111:111:111::111</oc-ip:ip>
<oc-ip:config>
<oc-ip:ip>111:111:111::111</oc-ip:ip>
<oc-ip:prefix-length>128</oc-ip:prefix-length>
</oc-ip:config>
</oc-ip:address>
</oc-ip:addresses>
</oc-ip:ipv6>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
</config>
</edit-config>
</rpc>
Response:
<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<ok/>
</rpc-reply>
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
interface loopback0
ipv6 address 111:111:111::111/128
Configuring an IPv6 Neighbor
Configuring an IPv6 Neighbor
Request:
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target>
<running/>
</target>
<config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
<interfaces xmlns="http://openconfig.net/yang/interfaces" xmlns:oc-ip="http://openconfig.net/yang/interfaces/ip" xmlns:oc-vlan="http://openconfig.net/yang/vlan">
<interface>
<name>vlan121</name>
<config>
<type xmlns:ianaift="urn:ietf:params:xml:ns:yang:iana-if-type">ianaift:l2vlan</type>
</config>
<oc-vlan:routed-vlan>
<oc-ip:ipv6>
<oc-ip:addresses>
<oc-ip:address>
<oc-ip:ip>100:1:1::1</oc-ip:ip>
<oc-ip:config>
<oc-ip:ip>100:1:1::1</oc-ip:ip>
<oc-ip:prefix-length>64</oc-ip:prefix-length>
</oc-ip:config>
</oc-ip:address>
</oc-ip:addresses>
<oc-ip:neighbors>
<oc-ip:neighbor>
<oc-ip:ip>100:1:1::10</oc-ip:ip>
<oc-ip:config>
<oc-ip:ip>100:1:1::10</oc-ip:ip>
<oc-ip:link-layer-address>1.1.2</oc-ip:link-layer-address>
</oc-ip:config>
</oc-ip:neighbor>
</oc-ip:neighbors>
</oc-ip:ipv6>
</oc-vlan:routed-vlan>
</interface>
</interfaces>
</config>
</edit-config>
</rpc>
Response:
<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<ok/>
</rpc-reply>
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
interface vlan121
ipv6 address 100:1:1::1/64
ipv6 neighbor 100:1:1::10 1.1.2
Configuring IPv6 Autoconfig on a Management Interface
Configuring IPv6 Autoconfig on a Management Interface
Request:
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target><running/></target>
<config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
<interfaces xmlns="http://openconfig.net/yang/interfaces" xmlns:oc-ip="http://openconfig.net/yang/interfaces/ip" xmlns:oc-ip-ext="http://openconfig.net/yang/interfaces/ip-ext">
<interface>
<name>mgmt0</name>
<config>
<type xmlns:ianaift="urn:ietf:params:xml:ns:yang:iana-if-type">ianaift:ethernetCsmacd</type>
</config>
<subinterfaces>
<subinterface>
<index>0</index>
<oc-ip:ipv6>
<oc-ip:addresses>
<oc-ip:address>
<oc-ip:ip>2001:420:5445:2021::211:f2</oc-ip:ip>
<oc-ip:config>
<oc-ip:ip>2001:420:5445:2021::211:f2</oc-ip:ip>
<oc-ip:prefix-length>118</oc-ip:prefix-length>
</oc-ip:config>
</oc-ip:address>
</oc-ip:addresses>
<oc-ip-ext:autoconf>
<oc-ip-ext:config>
<oc-ip-ext:create-global-addresses>true</oc-ip-ext:create-global-addresses>
</oc-ip-ext:config>
</oc-ip-ext:autoconf>
</oc-ip:ipv6>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
</config>
</edit-config>
</rpc>
Response:
<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<ok/>
</rpc-reply>
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
interface mgmt0
ipv6 address autoconfig
Deleting an IPv6 Autoconfig on a Management Interface
Deleting an IPv6 Autoconfig on a Management Interface
Request:
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<edit-config>
<target><running/></target>
<config xmlns:xc="urn:ietf:params:xml:ns:netconf:base:1.0">
<interfaces xmlns="http://openconfig.net/yang/interfaces" xmlns:oc-ip="http://openconfig.net/yang/interfaces/ip" xmlns:oc-ip-ext="http://openconfig.net/yang/interfaces/ip-ext">
<interface>
<name>mgmt0</name>
<config>
<type xmlns:ianaift="urn:ietf:params:xml:ns:yang:iana-if-type">ianaift:ethernetCsmacd</type>
</config>
<subinterfaces>
<subinterface>
<index>0</index>
<oc-ip:ipv6>
<oc-ip-ext:autoconf>
<oc-ip-ext:config>
<oc-ip-ext:create-global-addresses xc:operation="delete"/>
</oc-ip-ext:config>
</oc-ip-ext:autoconf>
</oc-ip:ipv6>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
</config>
</edit-config>
</rpc>
Response:
<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<ok/>
</rpc-reply>
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
interface mgmt0
no ipv6 address autoconfig
Querying an IPv6 Interface at Addresses Level
Querying an IPv6 Interface at Addresses Level
Request:
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<get-config>
<source><running/></source>
<filter>
<interfaces xmlns="http://openconfig.net/yang/interfaces" xmlns:oc-ip="http://openconfig.net/yang/interfaces/ip" xmlns:oc-vlan="http://openconfig.net/yang/vlan">
<interface>
<name>vlan1502</name>
<oc-vlan:routed-vlan>
<oc-ip:ipv6>
<oc-ip:addresses/>
</oc-ip:ipv6>
</oc-vlan:routed-vlan>
</interface>
</interfaces>
</filter>
</get-config>
</rpc>
Response:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<data>
<interfaces xmlns="http://openconfig.net/yang/interfaces">
<interface>
<name>vlan1502</name>
<routed-vlan xmlns="http://openconfig.net/yang/vlan">
<ipv6 xmlns="http://openconfig.net/yang/interfaces/ip">
<addresses>
<address>
<config>
<ip>18:2:1::2</ip>
<prefix-length>64</prefix-length>
</config>
<ip>18:2:1::2</ip>
</address>
</addresses>
</ipv6>
</routed-vlan>
</interface>
</interfaces>
</data>
</rpc-reply>
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
interface vlan1502; ipv6 address 18:2:1::2/64
Querying an IPv6 Interface with an Address Prefix
Querying an IPv6 Interface with an Address Prefix
Request:
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<get-config>
<source><running/></source>
<filter>
<interfaces xmlns="http://openconfig.net/yang/interfaces" xmlns:oc-ip="http://openconfig.net/yang/interfaces/ip">
<interface>
<name>mgmt0</name>
<subinterfaces>
<subinterface>
<index>0</index>
<oc-ip:ipv6>
<oc-ip:addresses>
<oc-ip:address>
<oc-ip:ip>2001:420:5445:2021::211:f2</oc-ip:ip>
</oc-ip:address>
</oc-ip:addresses>
</oc-ip:ipv6>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
</filter>
</get-config>
</rpc>
Response:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<data>
<interfaces xmlns="http://openconfig.net/yang/interfaces">
<interface>
<name>mgmt0</name>
<subinterfaces>
<subinterface>
<index>0</index>
<ipv6 xmlns="http://openconfig.net/yang/interfaces/ip">
<addresses>
<address>
<ip>2001:420:5445:2021::211:f2</ip>
<config>
<ip>2001:420:5445:2021::211:f2</ip>
<prefix-length>118</prefix-length>
</config>
</address>
</addresses>
</ipv6>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
</data>
</rpc-reply>
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
interface mgmt0; ipv6 address 2001:420:5445:2021::211:f2/118
Querying IPv6 Neighbors with Neighbors Container
Querying IPv6 Neighbors with Neighbors Container
Request:
<rpc message-id="101" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
<get>
<filter>
<interfaces xmlns="http://openconfig.net/yang/interfaces" xmlns:oc-ip="http://openconfig.net/yang/interfaces/ip">
<interface>
<name>mgmt0</name>
<subinterfaces>
<subinterface>
<index>0</index>
<oc-ip:ipv6>
<oc-ip:neighbors/>
</oc-ip:ipv6>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
</filter>
</get>
</rpc>
Response:
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="101">
<data>
<interfaces xmlns="http://openconfig.net/yang/interfaces">
<interface>
<name>mgmt0</name>
<subinterfaces>
<subinterface>
<index>0</index>
<ipv6 xmlns="http://openconfig.net/yang/interfaces/ip">
<neighbors>
<neighbor>
<config>
<ip>2001:420:5445:2021::211:f1</ip>
<link-layer-address>00:01:00:01:00:12</link-layer-address>
</config>
<ip>2001:420:5445:2021::211:f1</ip>
</neighbor>
<neighbor>
<config>
<ip>4::101</ip>
<link-layer-address>00:01:00:01:00:07</link-layer-address>
</config>
<ip>4::101</ip>
</neighbor>
<neighbor>
<config>
<ip>4::100</ip>
<link-layer-address>00:01:00:01:00:06</link-layer-address>
</config>
<ip>4::100</ip>
</neighbor>
<neighbor>
<config>
<ip>3::100</ip>
<link-layer-address>00:01:00:01:00:07</link-layer-address>
</config>
<ip>3::100</ip>
</neighbor>
</neighbors>
</ipv6>
</subinterface>
</subinterfaces>
</interface>
</interfaces>
</data>
</rpc-reply>
CLI Commands
The CLI commands are equivalent to the payload examples displayed in the pane on the right.
interface mgmt0; ipv6 neighbor 2001:420:5445:2021::211:f1 1.1.12