[vpp-dev] Fwd: VPP Service chaining with NSH
|
James Neil Guichard
[Moving to nsh_sfc-dev alias …]
Thanks John. Yes, the example in the document is correct.
Jim
From: "John Lo (loj)" <loj@...>
Date: Friday, April 1, 2016 at 2:01 PM To: Suman Kpatra/KOL/TCS <suman.kpatra@...>, Jim Guichard <jguichar@...> Cc: "vpp-dev@..." <vpp-dev@...>, pratik dave <pratik.dave@...> Subject: RE: [vpp-dev] Fwd: VPP Service chaining with NSH It should be “next-ip4” instead of “nextip4”
vpp# nsh vxlan help tunnel nsh vxlan tunnel src <ip4-addr> dst <ip4-addr> c1 <nn> c2 <nn> c3 <nn> c4 <nn> spi <nn> si <nn> vni <nn> [encap-fib-id <nn>] [decap-fib-id <nn>] [o-bit <1|0>] [c-bit <1|0>] [md-type <nn>][next-ip4][next-ip6][next-ethernet][next-nsh] [tlv <xx>][decap-next [ip4|ip6|ethernet|nsh-encap]][del]
John
From:
vpp-dev-bounces@... [mailto:vpp-dev-bounces@...]
On Behalf Of Suman Kpatra/KOL/TCS Sent: Friday, April 01, 2016 1:43 PM
To: Jim Guichard (jguichar) Cc: vpp-dev@...; pratik dave Subject: [vpp-dev] Fwd: VPP Service chaining with NSH
Dear Jim,
Getting this following error while configuring the nsh vxlan tunnel in vpp while following your document.
root@vpp:~# vppctl nsh vxlan tunnel src 192.168.50.70 dst 192.168.50.91 c1 9901 c2 9902 c3 9903 c4 9904 spi 1 si 255 vni 16777215 mdtype
1 nextip4 decapnext nshvxlangpe
We have installed vpp on a kvm vm. Could you please help us with this error.
Thanks, Suman
From:
"Suman Kpatra/KOL/TCS" <986788@...> Dear Jim,
Thanks for the document that you shared. Will definitely follow the same and try out with kvm vms , would keep you posted about the progress. If you can explain the following
#!/bin/bash
python3 sff_client.py remotesffip=192.168.50.91 remotesffport=4790 sfpid=1 sfpindex=255 encapsulate=gpenshipv4 innersrcip=10.1.1.1 innerdestip=10.1.1.2 ctx1=9901 ctx2=9902 ctx3=9903 ctx4=9904
1) what does this innersrcip=10.1.1.1 innerdestip=10.1.1.2 represent? 2) what does these ctx1,ctx2,ctx3,ctx4 represent? 3) how can we achieve this nsh service chaining with ipv6?
Another input required, can we achieve the same service chaining scenario as you mentioned in the document with segment routing ipv6 in VPP. Suman
From:
"Suman Kpatra/KOL/TCS" <986788@...> Dear Jim,
Thanks for the document that you shared. Will definitely follow the same and try out with kvm vms , would keep you posted about the progess.
Another input required, can we achieve the same service chaining scenario as you mentioned in the document with segment routing ipv6 in VPP. Suman
From:
"Jim Guichard (jguichar)" <jguichar@...> Hi Suman,
Ive attached a small document that shows a basic demo setup; you should be able to grab what you need from there.
Jim
From:
<vpp-dev-bounces@...> on behalf of Suman Kpatra/KOL/TCS <suman.kpatra@...>
Dear All,
Could you please share the some configuration details regarding service chaining for the following scenario via NSH vxlan tunnel/gre tunnel:
service1--> VPP-->service2-->VPP-->service3
or if you could explain some usecase with configuration using the below nsh command
vppctl nsh vxlan help tunnel nsh vxlan tunnel src <ip4-addr> dst <ip4-addr> c1 <nn> c2 <nn> c3 <nn> c4 <nn> spi <nn> si <nn> vni <nn> [encap-fib-id <nn>] [decap-fib-id <nn>] [o-bit <1|0>] [c-bit <1|0>] [md-type <nn>][next-ip4][next-ip6][next-ethernet][next-nsh] [tlv <xx>][decap-next [ip4|ip6|ethernet|nsh-encap]][del]
Thanks, Suman
=====-----=====-----=====
|
|
|
|