[j-nsp] Issue: CPSS (Alcatel-NewBridge Protocol) over L2circuit Martini over Ethernet MPLS Core

[Angel Bardarov]

Is the FR resource in NB3600 "up"? Can you share configs from your 
working scenario - the one with E1 between PE1 and PE2?
BTW I think that you should "chanalize" your E1 interface if you have 
FRS or FRE in your NB3600 because as far as I remember there is no way 
to crossconnect unchanalized E1 interface to FR resource in FRS card.
Regards,
Angel Bardarov

FAHAD ALI KHAN wrote:
> In our current Network Newbridge 3600 are used for Serial
> Aggregation.Beforemigration to MPLS,Intercity E1s was terminated on
> NB3600 and the NB3600s
> were managed via NMS by Newbridge propriety management protocol
> CPSS.Aftershifting E1s to MPLS nodes a UNI is created between Juniper
> MPLS Node and
> NB3600 over either E1 or V.35 and CPSS is carried over L2 circuit among
> nodes. Refer to the bellow diagram.
>
> [NB3600]---fr_uni---(PE1)----E1----(PE2)---fr_uni---[NB3600]----[NB NMS]
> *Problem:*
> There is no issue with CPSS while the conectivity b/w the two MPLS nodes is
> over E1 or E3.The problem occurs when the connectivity b/w the two MPLS
> nodes is over Fast Ethernet, here the CPSS is not carried over L2Circuit
> even though LSP and L2 circuit at both ends are up. This was also tested
> with L2 Connections. Refer to the diagram
>
> [NB3600]---fr_uni---(PE1)----FE----(PE2)---fr_uni---[NB3600]----[NB NMS]
>
> below is the config.
>
> *PE1*
> fe-0/0/0
> description "conctd to PE2";
> mtu 1546;
> unit 0 {
> family inet {
> address 192.168.0.1/30;}
> family mpls;}
>
> e1-1/0/0
> description "conctd to NB3600";
> encapsulation frame-relay-ccc;
> lmi {
> lmi-type ansi;}
> unit 0 {
> encapsulation frame-relay-ccc;
> point-to-point;
> dlci 513;
> family ccc;}
>
> l2circuit
> neighbor 192.168.1.254
> interface e1-1/0/0.0 {
> virtual-circuit-id 513}}
>
> *PE2*
> fe-0/0/0
> description "conctd to PE1";
> mtu 1546;
> unit 0 {
> family inet {
> address 192.168.0.2/30;}
> family mpls;}
>
> e1-1/0/0
> description "conctd to NB3600";
> encapsulation frame-relay-ccc;
> lmi {
> lmi-type ansi;}
> unit 0 {
> encapsulation frame-relay-ccc;
> point-to-point;
> dlci 513;
> family ccc;}
> l2circuit
> neighbor 192.168.0.254 {
> interface e1-1/0/0.0 {
> virtual-circuit-id 513;
> }}
>
> Can ay one suggest the solution?
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
>