[j-nsp] Interconnecting logical routers via FPC3-E

[Robert Kern]

Hi,

one more question: Even if I have a M320 E3-FPC Type 3 - they called it
enhanced FPC, Tunnel PIC or AS PIC is still needed for creating virtual
interfaces?

Thanks.

Robert

On Sat, Apr 18, 2009 at 7:08 PM, Robert Kern <cj11st at gmail.com> wrote:

> Thanks guys for your answers.
>
> BR
>
> Robert
>
>
> On Sat, Apr 18, 2009 at 5:48 PM, Erdem Sener <erdems at gmail.com> wrote:
>
>> Hi,
>>
>>  AFAIK lt- interfaces are treated like any other interface from a
>> firewall/policer and CoS perspective; e.g:
>>
>> unit 0 {
>>    encapsulation ethernet;
>>     peer-unit 1;
>>    family inet {
>>         policer {
>>            input policer_500meg;
>>            output policer_500meg;
>>        }
>>        address 12.12.12.1/30;
>>    }
>> }
>>
>> router> show interfaces lt-11/3/0.0 extensive | match policer
>>      Policer: Input: policer_500meg-lt-11/3/0.0-inet-i, Output:
>> policer_500meg-lt-11/3/0.0-inet-o
>>
>> Furthermore, in a MX platform, you can use a port in 'tunnel services'
>> mode (without requiring
>> a services (tunnel, AS, MS) PIC, where you can also specify the
>> bandwitdh, such as:
>>
>> erdem at mx-re0# show chassis
>> redundancy {
>>    failover {
>>        on-loss-of-keepalives;
>>    }
>>    graceful-switchover;
>> }
>> routing-engine {
>>    on-disk-failure disk-failure-action reboot;
>> }
>> fpc 11 {
>>    pic 3 {
>>        tunnel-services {
>>            bandwidth 10g; #### this is a 10gig ethernet port
>>        }
>>    }
>> }
>>
>> erdem at mx-re0# set chassis fpc 11 pic 3 tunnel-services bandwidth ?
>> Possible completions:
>>  1g                   1 gigabit per second <<<<<< you may choose to
>> use it as a 1gig 'tunnel' interface.
>>  10g                  10 gigabits per second
>>
>> This would effectively create interfaces such as vt-11/3/0, lt-11/3/0,
>> gr-11/3/0, mt-11/3/0 etc.
>>
>> HTH,
>> Erdem
>>
>>
>> On Sat, Apr 18, 2009 at 5:22 PM, Stacy W. Smith <stacy at acm.org> wrote:
>> > There are different Tunnel PICs depending upon the type of FPC in which
>> they
>> > are being installed. Each of these offer differing amounts of tunnel
>> > bandwidth. The PB-TUNNEL is for Type 3 FPCs and is inherently limited to
>> > 10Gbps of tunneling bandwidth. See page 3 of
>> > http://www.juniper.net/us/en/local/pdf/datasheets/1000092-en.pdf for
>> more
>> > details.
>> >
>> > I'm pretty QOS illiterate, so I don't know if you might be able to apply
>> > policers to lt interfaces to further limit the bandwidth. Maybe someone
>> else
>> > can comment on this.
>> >
>> > --Stacy
>> >
>> >
>> > On Apr 18, 2009, at 3:44 AM, Robert Kern wrote:
>> >
>> >> Hi Stacy,
>> >>
>> >> thanks for answer. Is there a way to limit the traffic between
>> >> logical-routers to 10Ge for example and what is the bandwidth
>> limitation for
>> >> a tunnel between LRs.
>> >>
>> >> Regards,
>> >>
>> >> Robert
>> >>
>> >> On Sat, Apr 18, 2009 at 7:29 AM, Stacy W. Smith <stacy at acm.org> wrote:
>> >>
>> >> On Apr 17, 2009, at 10:57 PM, Robert Kern wrote:
>> >>
>> >> Hi Guys,
>> >>
>> >> I have a question about interconnection logical-routers on M320 via
>> >> FPC3-E.
>> >> Interconnection should be internal (not via physical ports) and limited
>> to
>> >> 10Ge for example.
>> >>
>> >> What kind of configuration do I need for such logical connection - I
>> >> belive
>> >> no other HW is needed for that.
>> >>
>> >> Tnx for answers.
>> >>
>> >> Robert
>> >>
>> >> You need a logical tunnel (lt) interface. That requires either a tunnel
>> >> PIC, AS PIC, or MS PIC.
>> >>
>> >> Assuming you have an lt interface, the configuration looks like this:
>> >>
>> >> logical-systems {
>> >>   R11 {
>> >>       interfaces {
>> >>           lt-1/1/0 {
>> >>               unit 2 {
>> >>                   description "R11 LR to Default LR on unit 1";
>> >>                   encapsulation vlan;
>> >>                   vlan-id 1;
>> >>                   peer-unit 1;
>> >>                   family inet {
>> >>                       address 192.168.21.6/30;
>> >>                   }
>> >>               }
>> >>           }
>> >>       }
>> >>   }
>> >> }
>> >> interfaces {
>> >>   lt-1/1/0 {
>> >>       unit 1 {
>> >>           description "Default LR to R11 LR on unit 2";
>> >>           encapsulation vlan;
>> >>           vlan-id 1;
>> >>           peer-unit 2;
>> >>           family inet {
>> >>               address 192.168.21.5/30;
>> >>           }
>> >>       }
>> >>   }
>> >> }
>> >>
>> >> --Stacy
>> >>
>> >>
>> >
>> > _______________________________________________
>> > juniper-nsp mailing list juniper-nsp at puck.nether.net
>> > https://puck.nether.net/mailman/listinfo/juniper-nsp
>> >
>>
>
>