{"id":84,"date":"2012-08-17T13:55:07","date_gmt":"2012-08-17T10:55:07","guid":{"rendered":"https:\/\/mobiletransport.wordpress.com\/?p=84"},"modified":"2012-08-17T13:55:07","modified_gmt":"2012-08-17T10:55:07","slug":"why-using-ce-vlan-id-preservation-matters-in-carrier-ethernet","status":"publish","type":"post","link":"https:\/\/telecomlighthouse.com\/?p=84","title":{"rendered":"Why using CE-VLAN ID Preservation matters in Carrier Ethernet?"},"content":{"rendered":"<p>Ideally VLAN ID Preservation should be preserved ( CE-VLAN ID = Yes). After all, why it should matter, changing VLAN IDs. Having same VLANs IDs make it operationally efficient for both operator and customer. Operator can trace the circuit well, so can the end customer by just knowing the VLAN IDs. Not to forget that it would be easy to setup such an EVC \u00a0since the VLAN ID to EVC map will be much simple in this case.<\/p>\n<p>In this post I will explain that why it is needed to set VLAN Preservation ID = NO<\/p>\n<p>Let\u2019s see the example of setting VLAN Preservation ID = YES and its advantages. See the diagram 1 below, customer has two campuses with the same VLAN number 14. Obviously this situation demands that VLAN Preservation ID should be set to YES. Why asking the end customer to change VLAN IDs in the first place ?<\/p>\n<p><a href=\"https:\/\/telecomlighthouse.com\/wp-content\/uploads\/2012\/08\/ce-vlan-id-1.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-86\" title=\"ce vlan id =1\" alt=\"\" src=\"https:\/\/telecomlighthouse.com\/wp-content\/uploads\/2012\/08\/ce-vlan-id-1.png\" height=\"157\" width=\"584\" \/><\/a><\/p>\n<p>Lets see a second scenario in which two campuses of the same customer are connected to each other but both have different VLANs. The obvious advantage here for using VLAN Preservation ID= No is to let the service provider do the switch and hence in that case the service provider will switch the VLAN ID from 15 to 14 \u00a0before handing the traffic to B while the converse will be true when handing the traffic to A. This is shown in diagram 2 below.<\/p>\n<p><a href=\"https:\/\/telecomlighthouse.com\/wp-content\/uploads\/2012\/08\/ce-vlan-id-2.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-87\" title=\"ce vlan id =2\" alt=\"\" src=\"https:\/\/telecomlighthouse.com\/wp-content\/uploads\/2012\/08\/ce-vlan-id-2.png\" height=\"155\" width=\"584\" \/><\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Ideally VLAN ID Preservation should be preserved ( CE-VLAN ID = Yes). After all, why it should matter, changing VLAN IDs. Having same VLANs IDs make it operationally efficient for both operator and customer. Operator can trace the circuit well, so can the end customer by just knowing the VLAN IDs. Not to forget that [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[13],"tags":[],"class_list":["post-84","post","type-post","status-publish","format-standard","hentry","category-transport"],"_links":{"self":[{"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=\/wp\/v2\/posts\/84","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=84"}],"version-history":[{"count":0,"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=\/wp\/v2\/posts\/84\/revisions"}],"wp:attachment":[{"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=84"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=84"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/telecomlighthouse.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=84"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}