Frame relay ccc
Hi Guys,
I have been trying to figure this out but any help would be great.
Configuring Layer2 Switching Cross-Connects Using CCC - JUNOS 9.5 MPLS Applications Configuration Guide
So looking at the KB I did get by ccc working. Now I was wondering how to extend this.
For eg in the same example I would like to add a 3rd router say "D", now A needs to connect to D. That would mean that I configure the "B" router with another DLCI and switch it to Router D. But this always gives out an error.
Any guys can give me some input on what I am doing wrong.
-Hoogen
I have been trying to figure this out but any help would be great.
Configuring Layer2 Switching Cross-Connects Using CCC - JUNOS 9.5 MPLS Applications Configuration Guide
So looking at the KB I did get by ccc working. Now I was wondering how to extend this.
For eg in the same example I would like to add a 3rd router say "D", now A needs to connect to D. That would mean that I configure the "B" router with another DLCI and switch it to Router D. But this always gives out an error.
Any guys can give me some input on what I am doing wrong.
-Hoogen
IS-IS Sleeps.
BGP peers are quiet.
Something must be wrong.
BGP peers are quiet.
Something must be wrong.
Comments
-
hoogen82 Member Posts: 272This is what I got on Router A
unit 534 {
family inet {
address 10.0.0.1/24 {
multipoint-destination 10.0.0.2 dlci 534;
multipoint-destination 10.0.0.3 dlci 535;
}
}
}
Commit fails with this error
regress@A# commit
[edit interfaces t1-1/0/1]
'unit 534'
A DLCI is required
error: configuration check-out failed
[edit]
regress@A#
and the router on which I have the frame-relay ccc I have this..
root> show configuration interfaces
t1-1/0/0 {
dce;
encapsulation frame-relay-ccc;
unit 34 {
encapsulation frame-relay-ccc;
point-to-point;
dlci 534;
}
unit 35 {
encapsulation frame-relay-ccc;
point-to-point;
dlci 535;
}
}
t1-1/0/1 {
dce;
encapsulation frame-relay-ccc;
unit 53 {
encapsulation frame-relay-ccc;
point-to-point;
dlci 553;
}
unit 54 {
encapsulation frame-relay-ccc;
point-to-point;
dlci 554;
}
}
t1-2/0/0 {
dce;
encapsulation frame-relay-ccc;
unit 43 {
encapsulation frame-relay-ccc;
point-to-point;
dlci 543;
}
unit 45 {
encapsulation frame-relay-ccc;
point-to-point;
dlci 545;
}
}
root>
root> show configuration protocols
mpls {
interface all;
}
connections {
interface-switch A-C {
interface t1-1/0/0.34;
interface t1-2/0/0.43;
}
interface-switch C-D {
interface t1-1/0/1.54;
interface t1-2/0/0.45;
}
interface-switch A-D {
interface t1-1/0/0.35;
interface t1-1/0/1.53;
}
}
root>IS-IS Sleeps.
BGP peers are quiet.
Something must be wrong. -
hoogen82 Member Posts: 272Figured it out
whoa had to go to JNCIP book to get it..
regress@parbat> show configuration interfaces
t1-1/0/1 {
encapsulation frame-relay;
unit 0 {
multipoint;
family inet {
address 10.0.0.1/24 {
multipoint-destination 10.0.0.2 dlci 534;
multipoint-destination 10.0.0.3 dlci 535;
}
}
}
}
regress@A>IS-IS Sleeps.
BGP peers are quiet.
Something must be wrong. -
Aldur Member Posts: 1,460ha, nicely done!
When I saw your original post I was thinking that I remembered something from the IP book about this. But it looks like you beat me to the punch"Bribe is such an ugly word. I prefer extortion. The X makes it sound cool."
-Bender -
hoogen82 Member Posts: 272Thank you for the post Aldur.. I have this Cisco all over my mind. So it is good fun unlearning and learning again for the Juniper.. I just am building my lab up.. have some courses coming up next month.. So expect a lot of posts from me..hopefully I will love the JUNOS..IS-IS Sleeps.
BGP peers are quiet.
Something must be wrong.