-
Bug
-
Resolution: Done
-
Medium
-
None
-
None
Empty lisp oper data looks like this:
GET /restconf/operational/lisp:lisp-state
{"lisp-state":{"lisp-feature-data":{"eid-table":{"vni-table":[{"virtual-network-identifier":0,"vrf-subtable":{"table-id":0}}]},"pitr-cfg":{"locator-set":"N/A"}},"enable":false}}
When I add a "remote negative vrf" mapping:
PUT /restconf/config/lisp:lisp
{"lisp": {"lisp-feature-data": {"eid-table": {"vni-table": [{"vrf-subtable": {"remote-mappings": {"remote-mapping": {"id": "remote_map_vrf", "rlocs": {"locator": {"priority": 1, "weight": 1, "address": "192.168.0.3"}}, "eid": {"address-type": "ietf-lisp-address-types:ipv4-afi", "virtual-network-id": 4, "ipv4": "192.168.0.2"}}}}, "virtual-network-identifier": 4}]}}, "enable": true}}
the configuration is accepted (code 200) and the mapping is visible in VPP dump.
But when I GET lisp oper data:
GET /restconf/operational/lisp:lisp-state
{"lisp-state":{"lisp-feature-data":{"eid-table":{"vni-table":[{"virtual-network-identifier":0,"vrf-subtable":{"table-id":0}}]},"pitr-cfg":{"locator-set":"N/A"}},"enable":true}}
There is almost no change compared to an empty lisp configuration. Only the "enable" leaf reflects actual VPP status.
- blocks
-
CSIT-424 HC Test: LISP
- Done
- is blocked by
-
HONEYCOMB-279 leafed sub-container not resolved as modification
- Complete
- relates to
-
HONEYCOMB-283 Lisp plugin trying to reinitialize existing VRF subtables
- Complete