Epipe service with QinQ SAP and dot1q SAP

fortune123
Member
Posts: 4
Joined: 21 Oct 2015 10:23

Epipe service with QinQ SAP and dot1q SAP

Post by fortune123 »

Hi all,


I am still a newbie to the ALU world and your assistance will be greatly appreciated .
I need to find out if it is possible to have an Epipe service with QinQ SAP and dot1q SAP on the same physical port (1/1/3).
Please see below for more info.

S/W Release 7.0 Rev.08 on a SAS-T

epipe 1 svc-sap-type qinq-inner-tag-preserve customer 1 create
sap 1/1/3:10.45 create
no shutdown
exit
sap 1/1/3:85 create
no shutdown
exit
no shutdown
:?:
paramount
Member
Posts: 83
Joined: 11 Jan 2015 17:18
Contact:

Re: Epipe service with QinQ SAP and dot1q SAP

Post by paramount »

Hi,

I don't believe you can do it as you show above, as the physical port will either be configured as qinq or dot1q, so will complain on one of the commands.

The only way (to my knowledge) to achieve above is to enable port as qinq, then for the second sap, use sap 1/1/3:85.*, this should do it I think (but will obviously also match any qinq packets too with outer tag of 85.

Cheers
fortune123
Member
Posts: 4
Joined: 21 Oct 2015 10:23

Re: Epipe service with QinQ SAP and dot1q SAP

Post by fortune123 »

Dear Paramount,

Thank you for your response,Please correct me if my understanding is incorrect.

sap 1/1/3:85.* - means , i will match traffic with an outer tag of 85 and an inner tag of any(all tags).

Now what will happen to traffic ingressing that epipe with a single tag of 85?
mivens
Member
Posts: 262
Joined: 28 Sep 2012 06:34

Re: Epipe service with QinQ SAP and dot1q SAP

Post by mivens »

* matches a tag of <0..4095> or untagged.

So 85.* matches ethernet frames with an outer tag of 85 and with any inner tag or with no inner tag.

From 13.0R1 there is also the 'null' keyword to match 'no tag' if "new-qinq-untagged-sap" is enabled.
fortune123
Member
Posts: 4
Joined: 21 Oct 2015 10:23

Re: Epipe service with QinQ SAP and dot1q SAP

Post by fortune123 »

Dear mivens

Thank you for your response , unfortunately the feature is not supported on 7210 SAS-T running TiMOS-B-7.0.R8 code.

Please see below error

*A:test>config>service>epipe$ sap 1/1/13:850.* create
MINOR: SVCMGR #218 Feature not supported

:(
zeips
Member
Posts: 32
Joined: 13 Feb 2013 09:41

Re: Epipe service with QinQ SAP and dot1q SAP

Post by zeips »

it should work, just make a new epipe:
epipe 1 customer 1 create
"People still move, networks still don't."
fortune123
Member
Posts: 4
Joined: 21 Oct 2015 10:23

Re: Epipe service with QinQ SAP and dot1q SAP

Post by fortune123 »

Hey There ,

i found a work around if you configure as below (i) it doesn't work
(i)
epipe 1 svc-sap-type qinq-inner-tag-preserve customer 1 create
*A:test>config>service>epipe$ sap 1/1/13:850.* create
MINOR: SVCMGR #218 Feature not supported

but you configure the epipe as svc-sap-type any works

epipe 1 customer 1 svc-sap-type any create
*A:test>config>service>epipe$ sap 1/1/13:850.* create
User avatar
thekotaksampah
Member
Posts: 100
Joined: 06 Jan 2014 20:04

Re: Epipe service with QinQ SAP and dot1q SAP

Post by thekotaksampah »

Code: Select all

svc-sap-type any
so the conclusion is command in the code, isn't it?. :D
Technical Blog: ngoprek.achyarnurandi.id
sipani909
Member
Posts: 1
Joined: 25 Mar 2016 16:25

Re: Epipe service with QinQ SAP and dot1q SAP

Post by sipani909 »

Does anyone see the following?

*A:NS1221C0668>config>service# epipe 500 customer 1 svc-sap-type qinq-inner-tag-preserve create
MINOR: CLI The service-id does not correspond to the specified service type.

I am trying to have my inner tag preserved when traversing the network.
zeips
Member
Posts: 32
Joined: 13 Feb 2013 09:41

Re: Epipe service with QinQ SAP and dot1q SAP

Post by zeips »

Are you sure the service-id 500 is not already used by other service?
"People still move, networks still don't."
Post Reply

Return to “7210 SAS”