[j-nsp] VLAN/ATM TCC
James Feger
jfeger-j-nsp at feger.net
Wed Feb 23 00:06:39 EST 2005
Thomas,
This is a working configuration taking ATM and putting it into a vlan,
with a mixed family/set on the gig-e. You didnt say exactly what was
broken, but something we ran into was a typo on the remote/proxy IP's, we
had them flipped initially.
ge-3/0/0 {
vlan-tagging;
link-mode full-duplex;
encapsulation flexible-ethernet-services;
unit 0 {
vlan-id 10;
family inet {
filter {
input cflowd;
}
address x.x.x.x/xx;
}
}
unit 1 {
encapsulation vlan-tcc;
vlan-id 105;
family tcc {
proxy {
inet-address a.a.a.a;
}
remote {
inet-address b.b.b.b;
}
}
}
}
at-3/2/1 {
clocking external;
atm-options {
vpi 110;
}
t3-options {
no-payload-scrambler;
atm-encapsulation direct;
}
unit 0 {
encapsulation atm-tcc-snap;
point-to-point;
vci 110.100;
}
}
Then I have the two interfaces (at-3/2/1.0 and ge-3/0/0.1) in the mpls
interfaces list, and on the interface-switch stuff in the connections
Hope this helps.
James
On Tue, 22 Feb 2005, Thomas Salmen wrote:
>
> Okay, cool, so I *do* need to set the encapsulation on the physical
> interface? Is a configuration like this valid? E.g with a mix of TCC and
> non-TCC interfaces? Is this even possible?
>
> thomas at NCT_M02# show interfaces ge-1/3/0
> vlan-tagging;
> mtu 9000;
> encapsulation extended-vlan-tcc;
> unit 900 {
> vlan-id 900;
> family inet {
> address 10.100.1.1/26;
> }
> }
> unit 910 {
> encapsulation vlan-tcc;
> vlan-id 910;
> family tcc {
> proxy {
> inet-address 10.1.1.1;
> }
> remote {
> inet-address 10.1.1.2;
> }
> }
> }
>
> /thomas
>
>>
>> Try to put encap for physical and logical interface.
>> HTH.
>> ----- Original Message -----
>> From: "Thomas Salmen" <tsalmen at orcon.net.nz>
>> To: <juniper-nsp at puck.nether.net>
>> Sent: Tuesday, February 22, 2005 11:17 AM
>> Subject: [j-nsp] VLAN/ATM TCC
>>
>>
>>>
>>> Greetings,
>>>
>>> I'm trying to configure a TCC connection between an ATM PVC and an
>>> Ethernet
>>> VLAN, but I'm having some difficulties doing so.
>>>
>>> The docs have some really great examples on how to do everything else,
>> but
>>> nothing that quite matches what I want to do. This is basically what I'm
>>> trying to achieve:
>>>
>>> thomas at NCT_M02# show interfaces ge-1/3/0
>>> vlan-tagging;
>>> mtu 9000;
>>> unit 910 {
>>> encapsulation vlan-tcc;
>>> vlan-id 910;
>>> family tcc {
>>> proxy {
>>> inet-address 10.1.1.1;
>>> }
>>> remote {
>>> inet-address 10.1.1.2;
>>> }
>>> }
>>> }
>>>
>>> thomas at NCT_M02# show interfaces at-0/1/1 unit 939
>>> encapsulation atm-tcc-snap;
>>> vci 0.939;
>>> shaping {
>>> vbr peak 27m sustained 27m burst 32;
>>> }
>>> oam-liveness {
>>> up-count 2;
>>> down-count 5;
>>> }
>>>
>>> thomas at NCT_M02# show protocols
>>> mpls {
>>> interface at-0/1/1.939;
>>> interface ge-1/3/0.910;
>>> }
>>> connections {
>>> interface-switch test-tcc {
>>> interface at-0/1/1.939;
>>> interface ge-1/3/0.910;
>>> }
>>> }
>>>
>>> But it ain't workin. The docs here:
>>>
>>> http://www.juniper.net/techpubs/software/junos/junos64/swconfig64-
>> interfaces
>>> /html/interfaces-ethernet-config21.html
>>>
>>> seem to indicate I need to specify the encapsulation type as vlan-tcc
>>> (maybe?) on the physical interface as a whole - does this mean I cannot
>>> mix
>>> and match standard and TCC subinterfaces on the same physical interface?
>>>
>>> Cheers,
>>> Thomas
>>>
>>>
>>> _______________________________________________
>>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>>> http://puck.nether.net/mailman/listinfo/juniper-nsp
>>>
>>
>
>
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp
>
More information about the juniper-nsp
mailing list