[VPNSERVICE-2] Invalid range Exception in setDpnId Created: 20/May/15 Updated: 30/Oct/17 Resolved: 22/May/15 |
|
| Status: | Resolved |
| Project: | vpnservice |
| Component/s: | General |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Vishal Thapar | Assignee: | Vishal Thapar |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Severity: | critical |
| External issue ID: | 3292 |
| Description |
|
Ran into following exception when trying to configure VPnInterface when using vpnservice with openstack/OVSDB. 2015-05-19 23:46:16,518 | ERROR | ult-dispatcher-3 | DataChangeListener | 276 - org.opendaylight.controller.sal-distributed-datastore - 1.2.0.SNAPSHOT | Error notifying listener org.opendaylight.vpnservice.fibmanager.FibManager When using mininet dpnId is within range for 'long' but with OVSDB it uses a dpnid which is bigger than that. Note that most physical switches use a combination of mac-address and/or some other parameter to generate DatapathId, so dpnId will most of the times be bigger than range for long. |
| Comments |
| Comment by Vishal Thapar [ 20/May/15 ] |
|
Correction: long is 64bit, so that is not the issue. Problem is that l3nexthop.yang defines dpnId as uint32: rpc getEgressPointer { leaf vpnId { type uint32;} /* optional */ leaf ipPrefix {type string;} leaf nexthopIp {type string;} } output { leaf egressPointer {type uint32;} } So, when trying to set a dpnInd with bigger value than uint32, it is causing this exception. |
| Comment by Vishal Thapar [ 22/May/15 ] |
|
Fixed by: |