[j-nsp] M5 & CHDS3-QPP
Dan Evans
pzdevans at gmail.com
Tue Apr 5 17:00:35 EDT 2005
I don't see anything out of place in the config. What are you seeing
in the 'show interface t1-x/x/y extensive' outputs? Where are the
problems? Layer 1, 2, 3? Do you have any other mlppp bundles that are
working that aren't using an IQ CHDS3 PIC?
-Dan
On Apr 5, 2005 3:39 PM, Khawaja, Kashif <Kashif.Khawaja at broadwing.com> wrote:
> It does have an EFEB and the configuration in use is as follows:
>
> interfaces {
> traceoptions {
> file mlppp size 2m files 2;
> }
> ct3-0/0/0 {
> description DS3;
> t3-options {
> no-cbit-parity;
> }
> partition 1-28 interface-type t1;
> }
> t1-0/0/0:1 {
> encapsulation ppp;
> unit 0 {
> family mlppp {
> bundle ls-0/3/0.5;
> }
> }
> }
> t1-0/0/0:2 {
> encapsulation ppp;
> unit 0 {
> family mlppp {
> bundle ls-0/3/0.5;
> }
> }
> }
> t1-0/0/0:3 {
> unit 0 {
> family inet {
> address 10.1.3.1/30;
> }
> }
> }
>
> ls-0/3/0 {
> traceoptions {
> flag all;
> }
> unit 5 {
> description MLPPP-BUNDLE-ATLNGA1-CLARKCONS;
> encapsulation multilink-ppp;
> mrru 1502;
> family inet {
> address 10.254.27.1/30;
> }
> }
>
> Then these interfaces are parts of a routing instance
>
> routing-instances {
> test {
> instance-type virtual-router;
> interface t1-0/0/0:3.0;
> interface ls-0/3/0.5;
> routing-options {
> forwarding-table {
> export FLOW-BALANCE;
> }
> }
> protocols {
> ospf {
> traceoptions {
> file ospf-debug size 2m files 3;
> flag packets;
> flag timer;
> flag event;
> }
> area 0.0.0.0 {
> interface t1-0/0/0:3.0;
> interface ls-0/3/0.5;
> }
> }
>
> Thanks.
>
> -----Original Message-----
> From: Dan Evans [mailto:pzdevans at gmail.com]
> Sent: Tuesday, April 05, 2005 2:09 PM
> To: Khawaja, Kashif
> Cc: juniper-nsp at puck.nether.net
> Subject: Re: [j-nsp] M5 & CHDS3-QPP
>
> Can you paste in your config. I have several 4xCHDS3 IQ PIC's in
> production without any problems.
>
> -Daniel Evans
> JNCIE #0084
>
More information about the juniper-nsp
mailing list