Hi ppl !
Have an mols cloud core on ALU gear with 7210 SAS-M as PE's
the scheme for the service (e-pipe) is:
CE1--PE1---mpls cloud---PE2--CE2
CE1, CE2 are cisco devices.
CE1 is connected with a trunk port to PE1, one of the s-tags is configured for this particular service.
CE2 is also connected with trunk port to PE2, but all traffic(tagged,untagged, l2cp) belongs to this service.
Please, help with the config details for the PE physical ports facing CE's and service (VP LAN, SAP..) configuration.
Regards, Alex.
,
VPLS LAN configuration question
Re: VPLS LAN configuration question
Hi,
Do you want to have additional tag between CE1-PE1 to distinguish one service from another while one CE2--PE2 only one service will be available?
Do you want to have additional tag between CE1-PE1 to distinguish one service from another while one CE2--PE2 only one service will be available?
"People still move, networks still don't."
Re: VPLS LAN configuration question
Hi!
CE1-PE1 link is an inter-SP link, so services are segregated on outer tag on a trunk (s-tag) (that should be popped on ingress PE1)
CE2-PE2 link is an access link for one customer, PE2 must receive untagged, dot1q tagged traffic, that should go through the VPLS and exit PE1 with the pushed upper tag(s-tag).
Yes, this is right.zeips wrote:Do you want to have additional tag between CE1-PE1 to distinguish one service from another while one CE2--PE2 only one service will be available?
CE1-PE1 link is an inter-SP link, so services are segregated on outer tag on a trunk (s-tag) (that should be popped on ingress PE1)
CE2-PE2 link is an access link for one customer, PE2 must receive untagged, dot1q tagged traffic, that should go through the VPLS and exit PE1 with the pushed upper tag(s-tag).
Re: VPLS LAN configuration question
Ok, I presume you have sdp-s configured on both PE-s, then configure qinq encap-type on port x/x/x on PE1 and dot1q encap-type on PE2.
Secondly if you have service already configured you should tune up below config accordingly to the existing one.
On PE1
On PE2
This shall guarantee the whole traffic from PE2(tagged, untagged) to be passed within vpls to PE1 where it gets s-tag and flows to your CE1.
Try it out and let us know if it works for you.
Secondly if you have service already configured you should tune up below config accordingly to the existing one.
On PE1
Code: Select all
/configure service vpls # customer # create
/configure service vpls # sap x/x/x:<s-tag>.* create
/configure service vpls # spoke-sdp #:1111 create
/configure service vpls # no shut
Code: Select all
/configure service vpls # customer # create
/configure service vpls # sap x/x/x:* create
/configure service vpls # spoke-sdp #:1111 create
/configure service vpls # no shut
Try it out and let us know if it works for you.
"People still move, networks still don't."
-
- Member
- Posts: 3
- Joined: 08 Jul 2020 11:45
Re: VPLS LAN configuration question
Hello
I have two 7210 SAS-T nokia that are to remplace cisco in my companies backbone
I would like to have the commande lines for the creation of several vlans on one port [ ex : vlas id ( 10,20,30) on port 1/1/13 ]
Thanks !!
I have two 7210 SAS-T nokia that are to remplace cisco in my companies backbone
I would like to have the commande lines for the creation of several vlans on one port [ ex : vlas id ( 10,20,30) on port 1/1/13 ]
Thanks !!
Re: VPLS LAN configuration question
Hi
configure port as - encap-type dot1q
1/1/13:10
1/1/13:20
1/1/13:30
configure port as - encap-type dot1q
1/1/13:10
1/1/13:20
1/1/13:30