Hi Hongjun,
Firstly i would like to thank you for your support. This link was a great
help and i was able to get the configuration for classifier and i can see
the packets coming to nsh-classifier node in the packet trace.
I need some more support on the below items:
1. It would be a great if you can share me the configuration in VPP through
CLI for SFF and proxy.
2. Is there any performance statistics that SFC feature can support like
capacity, throughput etc..
Currently i was stuck at the below problem.
3. Now i can get the packet at *nsh-classifier* node. But it fails to
lookup in the ip4-table.
Below is my configuration for vxlan-gpe:
vpp# sh vxlan-gpe
[0] local: 192.168.20.1 remote: 192.168.20.2 vxlan VNI 100 next-protocol
nsh fibs: (encap 0, decap 0)
Ping to SF ip address is success
vpp# ping 192.168.20.2 source GigabitEthernet0/10/0
64 bytes from 192.168.20.2: icmp_seq=1 ttl=64 time=.3264 ms
64 bytes from 192.168.20.2: icmp_seq=2 ttl=64 time=.1723 ms
Below is the packet trace:
vpp# show trace
------------------- Start of thread 0 vpp_main -------------------
Packet 1
00:35:34:038659: dpdk-input
GigabitEthernet0/9/0 rx queue 0
buffer 0x4cf2: current data 0, length 124, free-list 0, clone-count 0,
totlen-nifb 0, trace 0x0
PKT MBUF: port 0, nb_segs 1, pkt_len 124
buf_len 2176, data_len 124, ol_flags 0x0, data_off 128, phys_addr
0x7e033cc0
packet_type 0x0
IP4: 08:00:27:aa:bb:21 -> 08:00:27:aa:bb:01
UDP: 192.168.0.10 -> 192.0.0.1
tos 0x00, ttl 255, length 110, checksum 0x4923
fragment id 0xf1a7
UDP: 1024 -> 1024
length 90, checksum 0xffff
00:35:34:038709: ethernet-input
IP4: 08:00:27:aa:bb:21 -> 08:00:27:aa:bb:01
00:35:34:038717: l2-input
l2-input: sw_if_index 1 dst 08:00:27:aa:bb:01 src 08:00:27:aa:bb:21
00:35:34:038720: l2-input-classify
l2-classify: sw_if_index 1, table 0, offset c0, next 17
00:35:34:038722: nsh-classifier
nsh ver 0 ttl 3 len 6 (24 bytes) md_type 1 next_protocol 1
service path 185 service index 255
c1 1 c2 2 c3 3 c4 4
00:35:34:038731: vxlan-gpe-encap
VXLAN-GPE-ENCAP: tunnel 2
00:35:34:038734: ip4-lookup
fib 0 dpo-idx 0 flow hash: 0x00000000
IP6_HOP_BY_HOP_OPTIONS: 0.0.0.2 -> 0.0.0.3
version 0, header length 0
tos 0xc6, ttl 0, length 257, checksum 0x0001 (should be 0xffff)
fragment id 0x006c offset 53240, flags MORE_FRAGMENTSDONT_FRAGMENT
00:35:34:038737: ip4-drop
IP6_HOP_BY_HOP_OPTIONS: 0.0.0.2 -> 0.0.0.3
version 0, header length 0
tos 0xc6, ttl 0, length 257, checksum 0x0001 (should be 0xffff)
fragment id 0x006c offset 53240, flags MORE_FRAGMENTSDONT_FRAGMENT
00:35:34:038738: error-drop
ip4-input: ip4 adjacency drop
--
Thanks & regards,
Phaneendra Manda.
On Thu, Nov 2, 2017 at 5:02 PM, Ni, Hongjun <hongjun...@intel.com> wrote:
> Hi Phaneendra,
>
>
>
> Please refer to below link to see how to configure it and packet trace:
>
> https://wiki.fd.io/view/File:NSH-Classifier-Output.png
>
>
>
> -Hongjun
>
>
>
> *From:* Phaneendra Manda [mailto:mphaneen...@gmail.com]
> *Sent:* Wednesday, November 1, 2017 4:39 PM
> *To:* Ni, Hongjun <hongjun...@intel.com>
> *Cc:* vpp-dev@lists.fd.io; nsh_sfc-...@lists.fd.io
> *Subject:* Re: [vpp-dev] [SFC] Query regarding SFC classifier
> configuration for ip4 traffic
>
>
>
> Hi Hongjun,
>
>
>
> Thank your very much for your support.
>
>
>
> I have tried this configuration for UDP packets and below is my
> configuration
>
>
>
> classify table mask l3 ip4 proto
>
> classify session l2-input-hit-next input-node nsh-classifier table-index 0
> match l3 ip4 proto 17 opaque-index 47615
>
> set int l2 bridge GigabitEthernet0/9/0 1 1
>
> set interface l2 input classify intfc GigabitEthernet0/9/0 ip4-table 0
>
>
>
> When i send a UDP packet, the packet reaches till "*l2-input-classify*"
> and goes to "*l2-learn*" node. How can i direct the packet to "
> *nsh-classifier*" node?
>
>
>
> Trace output below :
>
>
>
> *00:49:42:211037: dpdk-input*
>
> * GigabitEthernet0/9/0 rx queue 0*
>
> * buffer 0x4d8e: current data 0, length 132, free-list 0, clone-count 0,
> totlen-nifb 0, trace 0x1*
>
> * PKT MBUF: port 0, nb_segs 1, pkt_len 132*
>
> * buf_len 2176, data_len 132, ol_flags 0x0, data_off 128, phys_addr
> 0x74d32280*
>
> * packet_type 0x0*
>
> * IP4: 08:00:27:aa:bb:21 -> 08:00:27:aa:bb:01 802.1ad vlan 100 802.1ad
> vlan 20*
>
> * UDP: 192.168.0.10 -> 192.0.0.1*
>
> * tos 0x00, ttl 255, length 110, checksum 0x4923*
>
> * fragment id 0xf1a7*
>
> * UDP: 1024 -> 1024*
>
> * length 90, checksum 0xffff*
>
> *00:49:42:211084: ethernet-input*
>
> * IP4: 08:00:27:aa:bb:21 -> 08:00:27:aa:bb:01 802.1ad vlan 100 802.1ad
> vlan 20*
>
> *00:49:42:211093: l2-input*
>
> * l2-input: sw_if_index 1 dst 08:00:27:aa:bb:01 src 08:00:27:aa:bb:21*
>
> *00:49:42:211096: l2-input-classify*
>
> * l2-classify: sw_if_index 1, table -1, offset 0, next 12*
>
> *00:49:42:211099: l2-learn*
>
> * l2-learn: sw_if_index 1 dst 08:00:27:aa:bb:01 src 08:00:27:aa:bb:21
> bd_index 1*
>
> *00:49:42:211102: l2-fwd*
>
> * l2-fwd: sw_if_index 1 dst 08:00:27:aa:bb:01 src 08:00:27:aa:bb:21
> bd_index 1*
>
> *00:49:42:211104: l2-flood*
>
> * l2-flood: sw_if_index 1 dst 08:00:27:aa:bb:01 src 08:00:27:aa:bb:21
> bd_index 1*
>
> *00:49:42:211105: error-drop*
>
> * l2-flood: L2 replication complete*
>
>
>
>
>
> --
>
> Thanks & regards,
>
> Phaneendra Manda.
>
>
>
>
>
> On Wed, Nov 1, 2017 at 8:27 AM, Ni, Hongjun <hongjun...@intel.com> wrote:
>
> Hi Phaneendra,
>
>
>
> Please try below scripts:
>
>
>
> classify table mask l3 ip4 proto
>
> classify session l2-input-hit-next input-node nsh-classifier table-index 0
> match l3 ip4 proto 6 opaque-index 47615
>
> set int l2 bridge TenGigabitEthernet5/0/0 1 1
>
> set interface l2 input classify intfc TenGigabitEthernet5/0/0 ip4-table 0
>
>
>
> -Hongjun
>
>
>
> *From:* vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] *On
> Behalf Of *Phaneendra Manda
> *Sent:* Tuesday, October 31, 2017 8:11 PM
> *To:* vpp-dev@lists.fd.io
> *Subject:* [vpp-dev] [SFC] Query regarding SFC classifier configuration
> for ip4 traffic
>
>
>
> Hi All,
>
>
>
> I am trying out SFC with VPP for ip4 traffic on dpdk interface. I have few
> queries.
>
>
>
> 1. I would like to know what is the configuration for IP4 traffic to reach
> the nsh-classifier node in VPP using vppctl ?
>
>
>
> I am trying with the following command for redirecting ip4 traffic to
> nsh-classifier node. But the command throws error: "Table index
> required"
>
>
>
> classify table mask l3 ip4 proto
>
> * classify session hit-next input-node nsh-classifier table-index 0
> match l3 ip4 proto 17 opaque-index 47615 -- This command throws
> error*
>
>
>
>
>
> 2. Do i need to associate interface with classifier table created?
>
>
>
> Thanks in advance :)
>
>
>
> --
>
> Thanks & regards,
>
> Phaneendra Manda.
>
>
>
>
>
>
>
_______________________________________________
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
