[j-nsp] Load-Balance on Internet Processor II

Stefan Fouant sfouant at gmail.com
Thu Jun 26 11:13:01 EDT 2008


Yep, you can't run Layer 2 and Layer 3 services on that PIC at the
same time.  If you've got the sp interface configured, it sounds to me
like you might have some Layer 3 services configured.

If you do a 'set chassis fpc 0 pic 2 adaptive-services service-package
layer-2' you'll convert that MS-PIC to run in Layer 2 mode.  Of
course, you'll probably need to get rid of any associated sp-0/2/0
interface configuration as well.

HTHs.

--
Stefan Fouant
Principal Network Engineer
NeuStar, Inc. - http://www.neustar.biz
GPG Key ID: 0xB5E3803D

On Thu, Jun 26, 2008 at 11:07 AM, Ilker YILMAZ <ilkeryilmaz17 at gmail.com> wrote:
>
> :)
>
> FPC 0                                                    E-FPC
>  PIC 2          REV 14   750-014895   DH5587            MultiServices 100
>  PIC 3          REV 17   750-007626   CZ1730            10x CHE1 IQ
>
> There is no predefined and configureable lsq interface seen at M10i when you
> run "show interfaces" though.. As i understand from your explanation that
> the lsq-0/2/0 interface should already exists as we already have MSPIC at
> FPC 0 but;
>
> ilker# set interfaces lsq-0/2/0 unit 0 family inet address 1.2.3.4/32
>
> [edit]
> ilker# commit check
> [edit]
>  'interfaces'
>    sp-0/2/0 and lsq-0/2/0 cannot be configured on the same physical
> interface
> error: configuration check-out failed
>
> That's why i was asking for it to be sure..
>
> Any clues about it?
>
>
>
> -----Original Message-----
> From: Stefan Fouant [mailto:sfouant at gmail.com]
> Sent: Thursday, June 26, 2008 5:55 PM
> To: Ilker YILMAZ
> Cc: sthaug at nethelp.no; juniper-nsp at puck.nether.net
> Subject: Re: [j-nsp] Load-Balance on Internet Processor II
>
> Dude... it's lsq-x/x/x... x/x/x corresponds to whatever FPC/PIC combination
> you've got your AS or MS PIC installed.  The slot should always be 0 on
> these interfaces.  So if you've got an MS-PIC installed in FPC 2, PIC 1...
> the interface should be lsq-2/1/0.
>
> Do a 'show chassis hardware' to identify where your PIC is installed.
> --
> Stefan Fouant
> Principal Network Engineer
> NeuStar, Inc. - http://www.neustar.biz
> GPG Key ID: 0xB5E3803D
>
> On Thu, Jun 26, 2008 at 10:39 AM, Ilker YILMAZ <ilkeryilmaz17 at gmail.com>
> wrote:
>>
>> Thanks Steinar & Erdem for your help, i see ls-0/0/0 interface at
>> J4350 whereas i have no clue about at M10i interface naming for MLPPP.
>>
>> Does anybody have information on that?
>>
>> Thanks!
>> Ilker
>>
>> -----Original Message-----
>> From: sthaug at nethelp.no [mailto:sthaug at nethelp.no]
>> Sent: Thursday, June 26, 2008 12:35 PM
>> To: ilkeryilmaz17 at gmail.com
>> Cc: juniper-nsp at puck.nether.net
>> Subject: Re: [j-nsp] Load-Balance on Internet Processor II
>>
>>> Do you know which interface naming is available at J4350 & M10i for
>>> MLPPP
>> ?
>>> I see ls-0/0/0 interface at J4350 and lsi.x at M10i (Includes MSPIC)
>>
>> Interface naming depends on what PICs you have. Here's an example from
>> an M7i with ASM, channelized STM-1 and 4 E1s in a bundle using the ASM:
>>
>> e1-0/2/0:1              up    up
>> e1-0/2/0:1.0            up    up   mlppp    lsq-1/2/0.1
>> e1-0/2/0:2              up    up
>> e1-0/2/0:2.0            up    up   mlppp    lsq-1/2/0.1
>> e1-0/2/0:3              up    up
>> e1-0/2/0:3.0            up    up   mlppp    lsq-1/2/0.1
>> e1-0/2/0:4              up    up
>> e1-0/2/0:4.0            up    up   mlppp    lsq-1/2/0.1
>> lsq-1/2/0               up    up
>> lsq-1/2/0.1             up    up   inet     192.168.10.5/30
>>
>> Steinar Haug, Nethelp consulting, sthaug at nethelp.no
>>
>>
>>
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>
>
>
>
> --
> Stefan Fouant
> Principal Network Engineer
> NeuStar, Inc. - http://www.neustar.biz
> GPG Key ID: 0xB5E3803D
>
>
>



-- 
Stefan Fouant
Principal Network Engineer
NeuStar, Inc. - http://www.neustar.biz
GPG Key ID: 0xB5E3803D


More information about the juniper-nsp mailing list