Quantcast
Channel: Routing topics
Viewing all articles
Browse latest Browse all 2062

Protect an STM-1 interface.

$
0
0

Hello,

 

I have to protect an STM-1 interface that's connected to ADM device.

Currently we have only one router carrying these "unpacked" E1s and transported accross MPLS/IP network by using l2circuits.

 

I have made a search on Junos Documentation (http://www.juniper.net/documentation/en_US/junos15.1/topics/concept/sonet-aps-msp-overview.html) and found something about APS, however this documentation says that APS implementation doesn't work with l2circuits, I can't find anything on documentation regarding protect STM-1 using l2circuits. Can you please help find out this documentation?

 

Below the current scenario.

 

Thanks in Advance

 

Current scenario:

 

ADM ------ MX10 -------- MPLS/IP Network

 

Protected scenario desired:

 

ADM-------------MX10 ----------------------------- |

             |                                                               |--------------MPLS/IP Network

             |-------- MX10 ------------------------------|

 

 

Current configuration at unprotected router:

 

chassis{

    fpc 1 {
           pic 2 {
                  framing sdh;
                  vtmapping klm;
          }
     }

}

 

Interfaces {

cau4-1/2/0 {
partition 1-63 interface-type e1;
}
cstm1-1/2/0 {
no-partition interface-type cau4;
}
cau4-1/2/1 {
partition 1-63 interface-type e1;
}
cstm1-1/2/1 {
no-partition interface-type cau4;
}
e1-1/2/1:1 {
encapsulation satop;
unit 0;
}
e1-1/2/1:2 {
encapsulation satop;
unit 0;
}
e1-1/2/1:3 {
encapsulation satop;
unit 0;
}
e1-1/2/1:4 {
encapsulation satop;
unit 0;
}
e1-1/2/1:5 {
encapsulation satop;
unit 0;
}
e1-1/2/1:6 {
encapsulation satop;
unit 0;
}
e1-1/2/1:7 {
encapsulation satop;
unit 0;
}
e1-1/2/1:8 {
encapsulation satop;
unit 0;
}
e1-1/2/1:9 {
encapsulation satop;
unit 0;
}
e1-1/2/1:10 {
encapsulation satop;
unit 0;
}
cau4-1/2/2 {
partition 1-63 interface-type e1;
}
cstm1-1/2/2 {
no-partition interface-type cau4;
}
e1-1/2/2:25 {
encapsulation satop;
unit 0;
}
e1-1/2/2:26 {
encapsulation satop;
unit 0;
}
e1-1/2/2:29 {
encapsulation satop;
unit 0;
}
e1-1/2/2:30 {
encapsulation satop;
unit 0;
}
cau4-1/2/3 {
partition 1-63 interface-type e1;
}
cstm1-1/2/3 {
no-partition interface-type cau4;
}

}

 

Protocols{

 

l2circuit {
neighbor 10.14.3.3;
neighbor 10.14.3.11 {
interface e1-1/2/1:1.0 {
virtual-circuit-id 351012301;
description RtES5-AsdES2-GRI-E1-1;
ignore-encapsulation-mismatch;
ignore-mtu-mismatch;
}
interface e1-1/2/1:2.0 {
virtual-circuit-id 351022302;
description RtES5-AsdES2-GRI-E1-2;
ignore-encapsulation-mismatch;
ignore-mtu-mismatch;
}
interface e1-1/2/1:3.0 {
virtual-circuit-id 351032303;
description RtES5-AsdES2-GRI-E1-3;
ignore-encapsulation-mismatch;
ignore-mtu-mismatch;
}
interface e1-1/2/1:4.0 {
virtual-circuit-id 351042304;
description RtES5-AsdES2-GRI-E1-4;
ignore-encapsulation-mismatch;
ignore-mtu-mismatch;
}
interface e1-1/2/1:5.0 {
virtual-circuit-id 351052305;
description RtES5-AsdES2-GRI-E1-5;
ignore-encapsulation-mismatch;
ignore-mtu-mismatch;
}

}

--- not displayed all the l2circuits on the router.

}

 

 


Viewing all articles
Browse latest Browse all 2062

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>