[j-nsp] RPF for peering interfaces

2009-12-05 Thread The Dark One 
Experts,
what is the general opinion from ISP out there about using RPF on external 
peering interfaces?
And which variant:
-loose active-path
-loose feasible-path
-strict active-path
-strict feasible-path

?


___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

[j-nsp] BCP for RE protection

2009-09-08 Thread The Dark One 
Experts,
are you aware of 'best common practice' for RE protection in an SP environment?
Thanks,
TheDarkOne

Я в Моем Мире - http://my.mail.ru/list/thedarkone/
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

[j-nsp] understanding 'show route ... extensive'

2009-09-01 Thread The Dark One 
Experts,
the output of this command presents a huge amount of information of which a big 
share is quite cryptic. Do you know if there is a reference table that explains 
field by field the output of this command. Probably the most complex is 'show 
route protocol bgp extensive'
Thanks,
bit.

Я в Моем Мире - http://my.mail.ru/list/thedarkone/
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

[j-nsp] ISIS on aggregate-ethernet

2009-08-13 Thread The Dark One 
Experts, is the following true?

If ISIS is configured across an ae interface, due to the hashing algorithm, all 
hello frames will use the same member link; due to the convergence time for 
LACP being higher than ISIS holdtime of the adjacency, if that link fails, ISIS 
will flap before reconverging over the remaining member link(s).
For this reason it is probably not such a great idea this set-up.

Cheers,
TheDarkOne.
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] OSPF default in TSA

2009-05-15 Thread The Dark One 
That is exactly the point :-)
I have created an area 0 adjacency and the default is sent to the 
totally-stubby-area

Thank you very much for help.



-Original Message-
From: Harry Reynolds ha...@juniper.net
To: The Dark One thedark...@list.ru, Juniper Puckjuniper-nsp@puck.nether.net
Date: Thu, 14 May 2009 13:47:43 -0700
Subject: RE: [j-nsp] OSPF default in TSA

 Does rc2 have an area 0 adjacency up? If not I believe active backbone 
 detection suppresses the default. Looks likes its area 0 lsdb is all 
 self-populated.
 
 Regards
 
 http://www.juniper.net/techpubs/software/junos/junos94/swconfig-routing/configuring-the-backbone-area-and-other-areas.html
 
 
 
 
 
  
 
 -Original Message-
 From: juniper-nsp-boun...@puck.nether.net 
 [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of The Dark One
 Sent: Thursday, May 14, 2009 1:24 PM
 To: Juniper Puck
 Subject: [j-nsp] OSPF default in TSA
 
 Experts,
 according to JNCIP_studyguide pag 179:
 Juniper Networks routers do not automatically generate a default route when 
 operating as an ABR attached to a stub or not-so-stubby area. With JUNOS 
 software, you must configure a default metric before a default route will be 
 advertised!
 
 But router 'itp' doesn't get it :-( any idea why and how?
 Thanks!
 
 rc2 show configuration routing-instances RI protocols ospf   
 area 13.246.165.176 {
 stub default-metric 1 no-summaries;
 interface ge-5/2/1.176;
 }
 area 0.0.0.0 {
 interface ge-5/2/0.314;
 }
 
 rc2 show ospf database instance RI
 
 OSPF database, Area 0.0.0.0
  Type   ID   Adv Rtr   Seq  Age  Opt  Cksum  Len 
 Router  *13.246.165.177   13.246.165.177   0x8004   119  0x22 0x1813  36
 Summary *13.246.165.151   13.246.165.177   0x8004   119  0x22 0x712a  28
 Summary *13.246.165.176   13.246.165.177   0x8004   119  0x22 0x4248  28
 
 OSPF database, Area 13.246.165.176
  Type   ID   Adv Rtr   Seq  Age  Opt  Cksum  Len 
 Router   13.246.165.151   13.246.165.151   0x8006   266  0x20 0x8f14  48
 Router  *13.246.165.177   13.246.165.177   0x8008   119  0x20 0xeed0  36
 Network *13.246.165.177   13.246.165.177   0x8003   119  0x20 0x12db  32
 
 l...@hu-bud01a-rc2 show ospf neighbor instance RI 
 Address  Interface  State ID   Pri  Dead
 13.246.165.178   ge-5/2/1.176   Full  13.246.165.151 136
 
 ~
 
 itp#show ip interface brief | ex una
 Interface  IP-Address  OK? Method Status
 Protocol
 FastEthernet0/013.246.165.178  YES manual up
 up  
 Loopback0  13.246.165.151  YES manual up
 up  
 
 itp#show running-config | s router ospf
 router ospf 1
  router-id 13.246.165.151
  log-adjacency-changes
  area 13.246.165.176 stub
  network 0.0.0.0 255.255.255.255 area 13.246.165.176 itp#show ip route  
 Gateway of last resort is not set
 
  13.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
 C   13.246.165.151/32 is directly connected, Loopback0
 C   13.246.165.176/29 is directly connected, FastEthernet0/0
 
 
 itp#show ip ospf database 
 
 OSPF Router with ID (13.246.165.151) (Process ID 1)
 
 Router Link States (Area 13.246.165.176)
 
 Link ID ADV Router  Age Seq#   Checksum Link count
 13.246.165.151  13.246.165.151  424 0x8006 0x008F14 2
 13.246.165.177  13.246.165.177  278 0x8008 0x00EED0 1
 
 Net Link States (Area 13.246.165.176)
 
 Link ID ADV Router  Age Seq#   Checksum
 13.246.165.177  13.246.165.177  278 0x8003 0x0012DB
 
 ___
 juniper-nsp mailing list juniper-nsp@puck.nether.net 
 https://puck.nether.net/mailman/listinfo/juniper-nsp
 

___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

[j-nsp] OSPF default in TSA

2009-05-14 Thread The Dark One 
Experts,
according to JNCIP_studyguide pag 179:
Juniper Networks routers do not automatically generate a default route when
operating as an ABR attached to a stub or not-so-stubby area. With JUNOS
software, you must configure a default metric before a default route will be
advertised!

But router 'itp' doesn't get it :-( any idea why and how?
Thanks!

rc2 show configuration routing-instances RI protocols ospf   
area 13.246.165.176 {
stub default-metric 1 no-summaries;
interface ge-5/2/1.176;
}
area 0.0.0.0 {
interface ge-5/2/0.314;
}

rc2 show ospf database instance RI 

OSPF database, Area 0.0.0.0
 Type   ID   Adv Rtr   Seq  Age  Opt  Cksum  Len 
Router  *13.246.165.177   13.246.165.177   0x8004   119  0x22 0x1813  36
Summary *13.246.165.151   13.246.165.177   0x8004   119  0x22 0x712a  28
Summary *13.246.165.176   13.246.165.177   0x8004   119  0x22 0x4248  28

OSPF database, Area 13.246.165.176
 Type   ID   Adv Rtr   Seq  Age  Opt  Cksum  Len 
Router   13.246.165.151   13.246.165.151   0x8006   266  0x20 0x8f14  48
Router  *13.246.165.177   13.246.165.177   0x8008   119  0x20 0xeed0  36
Network *13.246.165.177   13.246.165.177   0x8003   119  0x20 0x12db  32

l...@hu-bud01a-rc2 show ospf neighbor instance RI 
Address  Interface  State ID   Pri  Dead
13.246.165.178   ge-5/2/1.176   Full  13.246.165.151 136

~

itp#show ip interface brief | ex una
Interface  IP-Address  OK? Method Status
Protocol
FastEthernet0/013.246.165.178  YES manual upup  

Loopback0  13.246.165.151  YES manual upup  


itp#show running-config | s router ospf
router ospf 1
 router-id 13.246.165.151
 log-adjacency-changes
 area 13.246.165.176 stub
 network 0.0.0.0 255.255.255.255 area 13.246.165.176
itp#show ip route 

Gateway of last resort is not set

 13.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C   13.246.165.151/32 is directly connected, Loopback0
C   13.246.165.176/29 is directly connected, FastEthernet0/0


itp#show ip ospf database 

OSPF Router with ID (13.246.165.151) (Process ID 1)

Router Link States (Area 13.246.165.176)

Link ID ADV Router  Age Seq#   Checksum Link count
13.246.165.151  13.246.165.151  424 0x8006 0x008F14 2
13.246.165.177  13.246.165.177  278 0x8008 0x00EED0 1

Net Link States (Area 13.246.165.176)

Link ID ADV Router  Age Seq#   Checksum
13.246.165.177  13.246.165.177  278 0x8003 0x0012DB

___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

[j-nsp] encapsulation flexible-ethernet-services

2009-05-04 Thread The Dark One 
Experts,
I can find the example at this URL:

http://www.juniper.net/techpubs/software/junos/junos95/mx-solutions-guide/frameset.html

using encapsulation flexible-ethernet-services

but I can not find any explanation for what 'flexible-ethernet-services' really 
is and does

Any pointer?
Thanks,
The DarkOne


Я в Моем Мире - http://my.mail.ru/list/thedarkone/

___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] EoMPLS and routing

2009-03-25 Thread The Dark One 
Arda,
if R1 and R3 are connected via EoMPLS they are virtually connected by a cable, 
so they are in the same subnet.
This means that BGP is not multihop. My question is different though:
can R3 locally route from the EoMPLS endpoint, or the endpoint must be 
connected to an physical interface.
Thanks,
TheDarkOne

-Original Message-
From: Arda Balkanay ardabalka...@gmail.com
To: The Dark One thedark...@list.ru, Juniper Puck 
juniper-nsp@puck.nether.net
Date: Tue, 24 Mar 2009 17:50:12 +0200
Subject: Re: [j-nsp] EoMPLS and routing

 Hi,
 R1 and R3 can form a multihop bgp session if you only require bgp between R1
 and R3.
 Do you need to share the same network at R1 and R3 ? I mean that do you need
 to form a backtoback ip connectivity ?
 
 
 On Tue, Mar 24, 2009 at 5:22 PM, The Dark One thedark...@list.ru wrote:
 
  R2 and R3 are the endpoints of an EoMPLS circuit
  R1 is physically connected to the EoMPLS endpoint on R2
 
  R1 -- R2 ==EoMPLS== R3
 
  Is it possible for R1 to talk IP with R3, for instance establish a BGP
  session?
  ___
  juniper-nsp mailing list juniper-nsp@puck.nether.net
  https://puck.nether.net/mailman/listinfo/juniper-nsp
 
 
 

___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

[j-nsp] EoMPLS and routing

2009-03-24 Thread The Dark One 
R2 and R3 are the endpoints of an EoMPLS circuit
R1 is physically connected to the EoMPLS endpoint on R2

R1 -- R2 ==EoMPLS== R3

Is it possible for R1 to talk IP with R3, for instance establish a BGP session?
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

[j-nsp] Olive FPC range

2009-02-28 Thread The Dark One 
Experts,
do you know if and how to extend the FPC range in order to avoid the following 
nasty error?
The interface of course will not be physically present in olive, but this will 
allow to validate the config anyway.

Also a solution could be to disable the FPC value check at all, if I only knew 
how to do it..

Cheers,
The Dark One

l...@olive-02# set protocols pim interface ge-7/2/0.0
  ^
fpc value outside range 0..5 for '7/2/0.0' in 'ge-7/2/0.0' at 'ge-7/2/0.0'

___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp