Re: [j-nsp] Re : IPv6 Routing Headers

2007-04-25 Thread Eli Dart
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Pekka Savola wrote: > On Tue, 24 Apr 2007, Kevin Oberman wrote: >>> Kevin, >>> >>> Slide 20 of the presentation states that RH processing can not be >>> deavtivat> ed on Juniper routers. Not sure whether that applies to >>> JunOS, JunosE or bo> th. >

Re: [j-nsp] MPLS OAM not triggering LSP

2007-04-25 Thread sthaug
> Sinan, have you tried enabling bfd for the igp session that is in turn > supporting the rsvp session? I've not tested personally but have > indications from developers that bfd will inform the igp of the link > down, and this will in turn cause the igp to start updating the TED, > which in turn

[j-nsp] ATM <-> Ethernet TCC or VPLS, converting from cisco

2007-04-25 Thread Will Orton
Hey all, I have a working config running on a Cisco 7206 I've inherited. It looks like a TCC between an ATM DS3 PVC and a fast-E VLAN: interface ATM1/0 no ip address atm scrambling cell-payload atm framing cbitplcp no atm ilmi-keepalive no atm enable-ilmi-trap pvc 1/100 l2transport u

Re: [j-nsp] MPLS OAM not triggering LSP

2007-04-25 Thread Harry Reynolds
Sinan, have you tried enabling bfd for the igp session that is in turn supporting the rsvp session? I've not tested personally but have indications from developers that bfd will inform the igp of the link down, and this will in turn cause the igp to start updating the TED, which in turn triggers c

[j-nsp] runaway MAC interrupt count

2007-04-25 Thread andy
Hi, Ive seen this a couple of times lately and I cant seem to find any related doc's as to explain what this issue is. Would be grateful if someone could enlighten me as to what this represents. The error is: Message from [EMAIL PROTECTED] cfeb at Apr 25 14:35:13 ... ibis-gw-2 cfeb SGE(1/0): r

[j-nsp] OSPF Neighbor doesn't recover automatically

2007-04-25 Thread h-tsuji
Hi dear all, I found something wrong with OSPF neighbor establishment. OSPF network type is p2mp. After make neighbore down and then recover the link, never established to Full state. the remote M10i is always "init" state. so I tried issue the "restart routing" command, then established OSPF nei

[j-nsp] M10i OSPF Neighbor trouble

2007-04-25 Thread h-tsuji
Hi dear all, I found something wrong with OSPF neighbor establishment. OSPF network type is p2mp. After make neighbore down and then recover the link, never established to Full state. the remote M10i is always "init" state. so I tried issue the "restart routing" command, then established OSPF nei

Re: [j-nsp] MPLS OAM not triggering LSP

2007-04-25 Thread Dario
Sail, The Tunnel is only for be informed when the triggered interface is failing or not. When the interface is ok the tunnel will be up and when it fails the tunnel is down. Is a bit tricky ;) I'll try to explain it. Suposse you want to check the ge between router A and B: RouterA --

Re: [j-nsp] MPLS OAM not triggering LSP

2007-04-25 Thread Dario
Dear all, I've tried BFD with LSPs but I wasn't able to make it work. If you've the possibility to use a Tunnel PIC - with a ficticious interface (f.e. with private address) and static routes (via the end-point of the interface you want to trigger) with BFD - is a good option, it works for me

Re: [j-nsp] M7i and M10i problems - TRACE ROUTE

2007-04-25 Thread GIULIANO (UOL)
People, Thanks a lot for your answer, but in our case, we are not in a MPLS/VPN environment. The juniper M10i router is in a border location in our network and it establishes network peering along with 5 different telecom operator companies. Because we are a cable TV operator, our clients and

Re: [j-nsp] MPLS OAM not triggering LSP

2007-04-25 Thread Sailendra Mahanty
Hi Sinan, Current version of JunOS that you are using, logs an error message when LSP goes down because of BFD as mentioned in page-191 of the following doc. However it doesn't make the LSP down. http://www.juniper.net/techpubs/software/junos/junos81/swconfig81-mpls-apps/download/swconfig81-mpl

Re: [j-nsp] M7i and M10i problems - TRACE ROUTE

2007-04-25 Thread EVAN WILLIAMS
agree with alex & paulo, allowing propagate and decriment ttl allows your users to see hops in the network and in MPLS LSP deployment why allow them to shoot you with bullets of your own making. IMHO Best common practice no-propagate/ detriment TTL BTW found this is a useful guide http://check

[j-nsp] MPLS OAM not triggering LSP

2007-04-25 Thread Sinan İlkiz
Hi all, We are trying to achieve fast convergence times for one of our links. We can not detect link failures in this link directly, i.e. interface never goes down in case of failures. We decided that we can benefit from BFD for LSPs. We are testing this configuration; label-switched-path ls