{"id":368,"date":"2013-06-12T03:19:19","date_gmt":"2013-06-12T00:19:19","guid":{"rendered":"https:\/\/telcocloudbridge.com\/?p=368"},"modified":"2013-06-12T03:19:19","modified_gmt":"2013-06-12T00:19:19","slug":"three-things-operators-should-know-about-combining-ipmpls-and-optical-protection","status":"publish","type":"post","link":"https:\/\/telecomlighthouse.com\/blog\/three-things-operators-should-know-about-combining-ipmpls-and-optical-protection\/","title":{"rendered":"Three things, Operators should know about combining Protection on IP\/MPLS and Optical Layers."},"content":{"rendered":"

 <\/p>\n

\n

If\u00a0\u00a0an Operator decides\u00a0to\u00a0deploy Multi-layer protection using both IP\/MPLS and Optical domain, he faces a number of challenges: IP\/MPLS and Optical control planes work\u00a0separately\u00a0in transport networks; they are, usually, disjoint and do not communicate\u00a0with\u00a0each other. IP\/MPLS circuits\u00a0are\u00a0provisioned as one of the services\u00a0for\u00a0optical layer<\/a> with no co-ordination\u00a0between<\/b>\u00a0them. While the \u201cdisjoint\u201d protection strategy may work.but\u00a0it is NOT a very efficient way in the long run.<\/span><\/p>\n

Operators who chooses to adopt a pure IP+ Optical protection\/restoration model<\/a> (in comparison to other models that include OTN as intermediate layer)\u00a0should consider the following three things:<\/span><\/p>\n

    \n
  1. Tight Integration between IP\/MPLS and Optical Control Plane:<\/b>\u00a0For the model to bring down CAPEX and resource efficiency, there should be a tight integration between the NMS (Network Management System) of IP\/MPLS and that of Optical domain, resulting in seamless integration. When fiber cut happens, how different layers would react and in which order, shall follow a proper sequence. \u00a0IP\/MPLS should \u00a0know the optical resources and routes through GMPLS NNI+ interface enabling it to make better routing decisions<\/a>.The signaling between the two layers can better optimize resources and informed decisions on when and which protection should come into play, once fiber cut happens.<\/span><\/li>\n
  2. IPoDWDM.<\/b>\u00a0If operators choose a pure IP and Optical path(with no OTN switching layer) the IPoDWDM \u00a0option makes sense. This will, further, bring down transponders’ cost. Otherwise, adding an overlay of back to back ports (grey ports of router to transponder on DWDM) can make the cost of lambda high.<\/span><\/li>\n
  3. Organizational\u00a0Structure:<\/b>\u00a0Last but not the least, operator must look into its own\u00a0organizational\u00a0structure. Operator should align its own\u00a0organizational\u00a0structure with its planned \u00a0technological integration. Most importantly, if transport and IP departments are separate entitites, it is time to look closely at\u00a0reorganization\u00a0. As \u201cTransport\u201d and \u201cIP\u201d merge as technology, organisational structure should follow suit. Therefore, one department that plans and operates both IP and Transport \u00a0makes sense<\/a> in such cases. The model of having combined network protection\/restoration strategy only works if there is a tight integration between the structure, processes, operations and management of both transport and IP groups. This has been found to have worked successfully in those organisations where there is one group that is responsible for the transport and IP part. Operators\u00a0should align their department strategies keeping in view \u00a0these changes in networks today.<\/span><\/li>\n<\/ol>\n<\/div>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n

     <\/p>\n","protected":false},"excerpt":{"rendered":"

      If\u00a0\u00a0an Operator decides\u00a0to\u00a0deploy Multi-layer protection using both IP\/MPLS and Optical domain, he faces a number of challenges: IP\/MPLS and Optical control planes work\u00a0separately\u00a0in transport networks; they are, usually, disjoint and do not communicate\u00a0with\u00a0each other. IP\/MPLS circuits\u00a0are\u00a0provisioned as one of the services\u00a0for\u00a0optical layer with no co-ordination\u00a0between\u00a0them. While the \u201cdisjoint\u201d protection strategy may work.but\u00a0it is NOT […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[],"class_list":["post-368","post","type-post","status-publish","format-standard","hentry","category-transport"],"_links":{"self":[{"href":"https:\/\/telecomlighthouse.com\/wp-json\/wp\/v2\/posts\/368","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/telecomlighthouse.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/telecomlighthouse.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/telecomlighthouse.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/telecomlighthouse.com\/wp-json\/wp\/v2\/comments?post=368"}],"version-history":[{"count":0,"href":"https:\/\/telecomlighthouse.com\/wp-json\/wp\/v2\/posts\/368\/revisions"}],"wp:attachment":[{"href":"https:\/\/telecomlighthouse.com\/wp-json\/wp\/v2\/media?parent=368"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/telecomlighthouse.com\/wp-json\/wp\/v2\/categories?post=368"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/telecomlighthouse.com\/wp-json\/wp\/v2\/tags?post=368"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}