Quick Series 26 : MPLS INSTALL PREFIX – JNPR Usage

Dec 02

Rakesh Mjncie, service-provider 1 Comment

Hi,

The post gives a perspective on usage of Install Prefix keyword. We all know Juniper has Different set of tables.

  1. inet.0 – igp populated
  2. inet.3 (ldp/rsvp) populated (used by BGP for Routing-Lookups)

Below is the Topology

 

Topology.png

I have extensively used Groups and Logical-systems  on VMX and Frankly i have not tried to include that as that will even more bore-you down

Lets see the behavior from R1 to R4, if you watch closely, see the NH lookup for inet.0

1_route_lookup

Lets change things a bit and see what happens

2_command

Lets see lookup table now

3_final_verification

As we can see the Push Label now and also the Route gets Installed as RSVP route into inet.0 table.

Regards

Rakesh M

 

 

 

 

 

 

 

Quick Scenario -3 – Bgp Local-as

Aug 12

Rakesh MUncategorized , , , , , , , , , , , , , No Comments

 

Hi,

3rd post in the quick series is about BGP local-as

BGP Local-AS

“The local-AS feature allows a router to appear to be a member of a second Autonomous systems (AS), in addition to its real AS. This feature can only be used for true eBGP peers. You cannot use this feature  for two peers that are members of different confederation sub-ASs”

 

Requirement – R1 needs to peer with R2 with As number 400 while all other Routers to peer with R2 should use a AS number of 200

 

Capture

As we can see, R2 is acting as Local-as 400 for R1 and AS 2 for R3

 

finalscreenoutput

 

Regards

Rakesh

Quick Scenario -2 – Bgp Communities – (no-advertise)

Aug 11

Rakesh MUncategorized , , , , , , , , , , , , , No Comments

Hi,

2nd post in the quick series is about BGP community no-advertise

Community – No-Advertise

“No-Advertise is similar to No-export, While no-export does not export routes to another AS, this goes further and it will not export route to both ebgp or ibgp neighbors as well.”

Requirement – Make sure R1 advertises its routes to R2, and R2 should not advertise the routes to either EBGP or IBGP neighbors

Topology

TOPOLOGY

Before confiuring anything

before-community

 

ON R1

 

access-list 99 permit host 1.1.1.1

route-map NO-ADV-COMM permit 10
match ip address 99
set community no-advertise

router bgp 100
nei 9.9.12.2 route-map NO-ADV-COMM out

final

 

Regards

Rakesh

 

 

 

 

 

Quick Scenario -1 – Bgp Communities – (no-export)

Aug 10

Rakesh MUncategorized , , , , , , , , , , , , , No Comments

Hi,

This will be a series of posts in which i shall be posting some quick scenario labbings. Mostly i have designed these so that I can relate to some stuff which i do not often use, nevertheless will blog all small topics

Community – No-export

“NO-EXPORT is commonly used within an AS to instruct routers not to export a prefix to eBGP neighbors. For instance, subnets of a larger block can be advertised to influence external AS best-path selection, and those not required for this traffic engineering purpose may be tagged NO-EXPORT to prevent them from being leaked to the Internet (and thus contributing to unnecessary global routing table growth). If a neighboring AS accepts this community, it can be used to selectively leak more specifics for traffic engineering but limit their propagation to just one AS.”

Requirement – R1 has its loopback advertised to R3 via BGP. Make sure the advertisement stays within the AS and should not go to another AS Router in this Case R3

no-export scenario

Before community addition – Routing Table of R3

pic1

AS we can see below route is not seen R3.

pic2.final

Regards

Rakesh M

Close Bitnami banner
Bitnami