[OVSDB-149] No entry for VLXAN+NSH tunnel type Created: 03/May/15 Updated: 11/May/15 Resolved: 11/May/15 |
|
| Status: | Resolved |
| Project: | ovsdb |
| Component/s: | Southbound.Open_vSwitch |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Thomas Bachman | Assignee: | Sam Hague |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 3102 |
| Priority: | Highest |
| Description |
|
The GBP and SFC integration uses a VXLAN + NSH tunnel type between SFC and GBP nodes. There's only a single "vxlan" tunnel type currently, so there's no way to select the additional encap. We should add an identity to select the additional encap. |
| Comments |
| Comment by Thomas Bachman [ 11/May/15 ] |
|
This is covered by the regular VXLAN tunnel type – NSH comes from addition of options, and UDP port. |