summaryrefslogtreecommitdiffstats
path: root/v3po/api/src/main/yang/v3po.yang
diff options
context:
space:
mode:
authorMarek Gradzki <mgradzki@cisco.com>2016-10-31 15:46:41 +0100
committerMarek Gradzki <mgradzki@cisco.com>2016-10-31 15:46:41 +0100
commitb10781b9ba682beaf23aa5d6183afa222aa93206 (patch)
treec96add7ec9184a4ace5d49360e481e94c0afa8e1 /v3po/api/src/main/yang/v3po.yang
parent51d5709128535d4da018f6ed7570877de6d6f405 (diff)
Add support for ipv6 vrf
Change-Id: I3372d4156a19157ca431cb29c23de33161f6cfc0 Signed-off-by: Marek Gradzki <mgradzki@cisco.com>
Diffstat (limited to 'v3po/api/src/main/yang/v3po.yang')
-rw-r--r--v3po/api/src/main/yang/v3po.yang9
1 files changed, 7 insertions, 2 deletions
diff --git a/v3po/api/src/main/yang/v3po.yang b/v3po/api/src/main/yang/v3po.yang
index d3869abaf..f272a489a 100644
--- a/v3po/api/src/main/yang/v3po.yang
+++ b/v3po/api/src/main/yang/v3po.yang
@@ -442,10 +442,15 @@ module v3po {
}
container routing {
- leaf vrf-id { // todo no routing info for oper, is it possible to get it from the vpp?
+ // TODO (HONEYCOMB-127): add routing info for oper
+ leaf ipv4-vrf-id {
+ type uint32;
+ }
+ leaf ipv6-vrf-id {
type uint32;
- default 0;
}
+ description
+ "Defines VRF tables used for ipv4 and ipv6 traffic";
}
container vhost-user {