Hi!
I'm trying to un-concatenate an STM16 - STM16 interfaces into 4xSTM4
links on a dark fiber link, however I simply can't get the links to
come up in either SDH or SONET modes.
[EMAIL PROTECTED]> show interfaces so-1/1/0:0
Physical interface: so-1/1/0:0, Enabled, Physical link is Down
Interfa
Hi,
On Thu, Jun 26, 2008 at 01:03:18PM +0900, [EMAIL PROTECTED] wrote:
> I see the same message whenever issuing 'show vrrp' from CLI. I heard
> that this can be ignored because this is a meaningless message.
Indeed, that's what another off-list reply indicated as well,
supposed to be fixed in 9.
Hm, that's sounds good,
Also, i have another L2 ASPIC in my hand and will install that later on to
see if lsq interface appears.
Thanks Stefan
-Original Message-
From: Stefan Fouant [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 26, 2008 6:13 PM
To: Ilker YILMAZ
Cc: [EMAIL PROTECTED]; j
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
:)
FPC 0E-FPC
PIC 2 REV 14 750-014895 DH5587MultiServices 100
PIC 3 REV 17 750-007626 CZ173010x CHE1 IQ
There is no predefined and configureable lsq interface seen at M10i when you
run "show
thanks
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
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
Hello,
You can change preference of rsvp signaled lsps globally or per LSP :
set protocols mpls preference 10
or only for particular lsp:
set protocols mpls label-switched-path xxx preference 10
Krasi
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:juniper-nsp-
> [EMAIL PROTE
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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 26, 200
Geez... I think that just won the award for the most technical
acryonyms ever used in a single sentence!
--
Stefan Fouant
Principal Network Engineer
NeuStar, Inc. - http://www.neustar.biz
GPG Key ID: 0xB5E3803D
On Thu, Jun 26, 2008 at 10:26 AM, Alex <[EMAIL PROTECTED]> wrote:
> Samuel,
> p2mp RSV
Thanks
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Samuel,
p2mp RSVP LSP egress LSR lo0.0 IP@ are not present in inet.0/inet.3 and
therefore unicast traffic cannot use NGEN MVPN p2mp LSP.
If you have p2p RSVP LSP and you stll want to use LDP (cannot imagine why
but let's assume so) then consider changing next-hops of IPv4
unicast/L3VPN/L2VPN ro
Of course, you may also need to do some filtering or modify protocol
preferences to ensure that the RSVP routes are not populated into your
unicast routing tables or if they are, that they should be less
preferred than your LDP routes.
--
Stefan Fouant
Principal Network Engineer
NeuStar, Inc. - h
You should be able to do this by configuring PIM/MSDP to use inet.2
for RPF, then use rib groups and policy to make sure you import your
direct routes, IGP routes, and RSVP routes (but not LDP routes) into inet.2.
--
Stefan Fouant
Principal Network Engineer
NeuStar, Inc. - http://www.neustar.biz
Hi group,
This is my "problem":
We have an MPLS backbone using LDP. We are configuring Next Gen MVPN.
For that we have to configure RSVP on all the core router. The problem
is that we would like to keep LDP for the data and RSVP for the
multicast, but like RSVP has a preference of 7 and LDP has
> 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/
If I use commit full stil not resolve,
But if I reboot this system again, it 's solved
Thanks
Amin
On Fri, Jun 20, 2008 at 9:58 PM, Erdem Sener <[EMAIL PROTECTED]> wrote:
> Hi Amin,
>
> I'm not sure I follow you .. If I understand you correctly:
>
> a- upgrade from xxx ---> 8.4R3.4 ---> 8.5R
17 matches
Mail list logo