Re: [j-nsp] Advertise inactive route EBGP session

2016-12-01 Thread David Lockuan 
Hi Mileto,

Maybe you need to change the default preference of static route to value
major (as 180 or 200) , with this the bgp route will be preference over
static route.

Best regards,

---
David


On Wed, Nov 30, 2016 at 4:46 PM, Mileto Tales 
wrote:

> Hello,
>
>
> I'm not having success to advertise the best BGP inactive route to my eBGP
> peer. My scenario is very simple. I have configured one static route "set
> routing-options static route 192.168.0.0/24 next-hop 10.0.1.1" and I'm
> receiving this same route by eBGP.
>
>
>
> 192.168.0.0/24 (2 entries, 1 announced)
> *Static Preference: 5
> Next hop type: Router, Next hop index: 596
> Address: 0x3e5e47c
> Next-hop reference count: 14
> Next hop: 10.0.1.1 via xe-1/3/0.0, selected
> Session Id: 0x2f5a
> State: 
> Local AS: 100
> Age: 32:19
> Validation State: unverified
> Task: RT
> Announcement bits (3): 0-KRT 7-BGP_RT_Background 8-Resolve
> tree 2
> Communities: 6:6
>  BGPPreference: 170/-301
> Next hop type: Router, Next hop index: 596
> Address: 0x3e5e47c
> Next-hop reference count: 14
> Source: 10.0.1.1
> Next hop: 10.0.1.1 via xe-1/3/0.0, selected
> Session Id: 0x2f5a
> State: 
> Inactive reason: Route Preference
> Local AS: 100 Peer AS: 200
> Age: 1d 20:50:59
> Validation State: unverified
> Task: BGP_200.10.0.1.1+39577
> Announcement bits (1): 7-BGP_RT_Background
> AS path: 200 200 I
> Communities: 1:1
> Accepted
> Localpref: 300
> Router ID: 200.200.200.200
>
>
> I want to keep the static route configured in the router and advertise BGP
> learned route to another eBGP peers. In my understanding the
> advertise-inactive configuration inside the BGP group was supposed to work
> in this scenario. I add this configuration, cleared the BGP session and I'm
> still having problems to advertise the inactive route.
>
>
> Another test that I did:I created a policy matching on routes that are in
> inactive state and tried to export then. If I remove the static route then
> the BGP is advertised (best route)
>
>
> Anyone have this configuration working?
>
>
>
> MT
>
> ___
> 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] Help needed regarding the Eompls tunnel in Juniper & Cisco

2016-12-01 Thread Ahsan Rasheed 
Hi All,

We are having some serious issue with one customer circuit.We are using eompls 
vlan based & we are unable to pass traffic over eompls (l2)tunnel between Cisco 
3550 switches if we use specifically Cisco 6503 ,Cisco 6504 & 6506 etc. If we 
use Cisco switch 6524 instead of Cisco 6503 it is working.

{(Cisco 3550 switch)--->(Cisco 6524)>(Juniper ACX 4000)>(Cisco 3550) 
}-->This setup is working.I am able to pass traffic end to end between Cisco 
3550's.

{(Cisco 3550 switch1)--->(Cisco 6503 or Cisco 6506))>(Juniper ACX 
4000)>(Cisco 3550 switch2) }-->This setup is not working.

Cisco 3550 switch1 vlan 1089(1.1.1.1/30)---trunk->sub interface eompls vlan 
1089(Cisco 6503)->(ACX 4000)terminating tunnel on sub interface vlan 
1089->Cisco 3550 switch2-trunk-vlan 1089(1.1.1.2/30)

We are using bgp & ospf between Cisco 6503 & Juniper ACX 4000. Vlan 1089  as 
svi we are using on Cisco 3550 switch1 and allowing vlan 1089 as trunk 
connecting back to Cisco 6503,eompls vlan 1089 tunnel is configured on sub int 
on 6503 facing Cisco 3550 switch 1.Cisco 6503 is connected with juniper ACX 
4000 & running bgp & ospf between each other.On ACX 4000 juniper eompls vlan 
based tunnel is terminating on sub interface facing Cisco 3550 switch 2. With 
Sup720 I was unable to pass traffic over tunnels although l2 eompls tunnel 1089 
is up on both (Cisco 6503 & Juniper). See below.


Below are the outputs & commands which i was running.


ACX 4000 Juniper:

chi> show l2circuit connections
Layer-2 Circuit Connections:
Neighbor: 63.250.238.225
Interface Type  St Time last up  # Up trans
ge-1/1/0.1089(vc 1089)rmt   Up Jan  2 12:45:23 2010   1
  Remote PE: 63.250.238.225, Negotiated control-word: No
  Incoming label: 299776, Outgoing label: 19
  Negotiated PW status TLV: No
  Local interface: ge-1/1/0.1089, Status: Up, Encapsulation: VLAN
chi> show ospf neighbor
Address  Interface  State ID   Pri  Dead
10.252.0.85  xe-0/2/0.0 Full  63.250.238.225 139

chi> show bgp summary
Groups: 1 Peers: 1 Down peers: 0
Table  Tot Paths  Act Paths SuppressedHistory Damp StatePending
inet.0
  15 13  0  0  0  0
Peer AS  InPkt OutPktOutQ   Flaps Last Up/Dwn 
State|#Active/Received/Accepted/Damped...
63.250.238.22530373179200   0   0 1:21:40 
13/15/15/0   0/0/0/0

show ldp neighbor
AddressInterface  Label space ID Hold time
63.250.238.225 lo0.0  63.250.238.225:0 40
63.250.250.219 lo0.0  0.0.0.0:00
10.252.0.85xe-0/2/0.0 63.250.238.225:0 11

set interfaces xe-0/2/0 mtu 9192
set interfaces xe-0/2/0 unit 0 bandwidth 10g
set interfaces xe-0/2/0 unit 0 family inet mtu 1546
set interfaces xe-0/2/0 unit 0 family inet address 10.252.0.86/30
set interfaces xe-0/2/0 unit 0 family mpls

set interfaces ge-1/1/0 vlan-tagging
set interfaces ge-1/1/0 mtu 1564
set interfaces ge-1/1/0 media-type copper
set interfaces ge-1/1/0 encapsulation flexible-ethernet-services
set interfaces ge-1/1/0 unit 0 vlan-id 2062
set interfaces ge-1/1/0 unit 0 family inet address 10.254.62.9/29 primary
set interfaces ge-1/1/0 unit 0 family inet address 63.250.226.153/30
set interfaces ge-1/1/0 unit 1089 encapsulation vlan-ccc
set interfaces ge-1/1/0 unit 1089 vlan-id 1089

set protocols mpls interface xe-0/2/0.0
set protocols ospf area 0.0.0.0 interface lo0.0
set protocols ospf area 0.0.0.0 interface xe-0/2/0.0 interface-type p2p
set protocols ospf area 0.0.0.0 interface xe-0/2/0.0 authentication md5 1 key 
"$9$a9JUHf5F6CuZU9puOSyX7-wgJDikqP5ZGtu1IcS"
set protocols ldp interface xe-0/2/0.0 allow-subnet-mismatch

set protocols ldp interface lo0.0
set protocols l2circuit neighbor 63.250.238.225 interface ge-1/1/0.1089 
virtual-circuit-id 1089


ACX 4000 i am using Junos:jinstall-ppc-12.3X54-D27.1-domestic-signed.tgz

Cisco 6503:
Test#show mpls l2transport vc detail
Local interface: Gi2/2.1089 up, line protocol up, Eth VLAN 1089 up
  Destination address: 63.250.250.225, VC ID: 1089, VC status: up
Output interface: Gi2/1, imposed label stack {299776}
Preferred path: not configured
Default path: active
Next hop: 10.252.0.86
  Load Balance: none
  Flow Label: Disabled
  Create time: 00:05:52, last status change time: 00:03:30
  Signaling protocol: LDP, peer 63.250.250.225:0 up
Targeted Hello: 63.250.238.225(LDP Id) -> 63.250.250.225, LDP is UP
Status TLV support (local/remote)   : enabled/not supported
  LDP route watch   : enabled
  Label/status state machine: established, LruRru
  Last local dataplane   status rcvd: No fault
  Last local SSS circuit status rcvd: No fault
  Last local SSS circuit status sent:

Re: [j-nsp] Advertise inactive route EBGP session

2016-12-01 Thread Olivier Benghozi 
It's expected to work according to 
https://www.juniper.net/documentation/en_US/junos/topics/example/bgp-advertise-inactive.html
 

So, aren't you trying to advertise an AS200 route to an AS200 router ? In that 
case you would need to add advertise-peer-as.

> Le 30 nov. 2016 à 22:46, Mileto Tales  a écrit :
> 
> Hello,
> 
> 
> I'm not having success to advertise the best BGP inactive route to my eBGP 
> peer. My scenario is very simple. I have configured one static route "set 
> routing-options static route 192.168.0.0/24 next-hop 10.0.1.1" and I'm 
> receiving this same route by eBGP.
> 
> I want to keep the static route configured in the router and advertise BGP 
> learned route to another eBGP peers. In my understanding the 
> advertise-inactive configuration inside the BGP group was supposed to work in 
> this scenario. I add this configuration, cleared the BGP session and I'm 
> still having problems to advertise the inactive route.
> 
> 
> Another test that I did:I created a policy matching on routes that are in 
> inactive state and tried to export then. If I remove the static route then 
> the BGP is advertised (best route)
> 
> 
> Anyone have this configuration working?

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

Re: [j-nsp] Advertise inactive route EBGP session

2016-12-01 Thread Maximiliano Villalba 
Mileto,

Hi, could you let me clear? What do you want is, readvertise the learned
route to another eBGP peer?

I that case you need to configure a police for export all routes learned
from bgp.

an example
https://www.juniper.net/techpubs/en_US/junos/topics/example/routing-protocol-bgp-security-internal-peering-session-configuring-cli.html

Congrats.
El 30/11/2016 a las 6:46 p. m., Mileto Tales escribió:
> I add this configuration, cleared the BGP session and I'm still having
> problems to advertise the inactive route. 


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