[j-nsp] bgp route advertisements

[Murphy, Jay, DOH]

It is a hacked FreeBSD kernel, so the concept will be as if you are
using a shell, when programming it for particular functions. 



Jay Murphy 
IP Network Specialist 
NM Department of Health 
ITSD - IP Network Operations 
Santa Fe, New Mexico 87502 
Bus. Ph.: 505.827.2851
"We move the information that moves your world." 






-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net
[mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of
michael.firth at bt.com
Sent: Wednesday, November 05, 2008 1:06 PM
To: harbor235 at gmail.com; juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] bgp route advertisements

> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net
> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Mike Johnson
> Sent: 05 November 2008 18:45
> To: juniper-nsp at puck.nether.net
> Subject: [j-nsp] bgp route advertisements
> 
> I need some assistance advertising routes via JUNOS, I am familiar 
> with Cisco CLI.
> I must say JUNOS does not make sense to me, yet.
> 
> Could someone explain the basics of JUNOS CLI and how it rerlates to 
> routing.
> It appears you configure BGP under protocols and then to advertise you

> define a policy.
> I am not sure why things are seperated??
> 

As well as the other suggestions, it would probably be useful to you to
have a look at Chapter 4 (Routing Policy) of the JNCIA study guide
available online at:

http://www.juniper.net/training/certification/JNCIA_studyguide.pdf

It covers what the JunOS routing policy is all about, and goes a long
way to explaining why things are architected the way they are.

The basic summary is that the reason that they are separated is to make
the configuration consistent across all routing protocols.

No matter which routing protocols you are using, and which routes you
want to move between them, the configuration becomes very similar - you
configure a policy to select the routes, and then apply the policy under
the protocol(s) of your choice.

Like a lot of JunOS features, it appears complex to begin with, but
actually is very well structured once you get used to it.

> Here is what I have, BGP is up but I am unable to advertise a local 
> network?
> Is there any good docs for understanding the setup an/or conversion 
> from Cisco?

Basically, what you need is something similar to the following:

protocols {
    bgp {
        log-updown;
        peer-as 100;
        local-as 101;
        group Cisco {
            export advertise-directs; <-- Add this line
            type external;
            neighbor 10.77.1.2;
        }
    }
}
policy-options {
    policy-statement advertise-directs {
        term directs {
            from {
                protocol direct; <-- Match directly connected routes
		    route-filter 10.77.1.1/24 orlonger; <-- Your subnet
on ge-0/0/0
                route-filter 10.101.101.1/32 exact; <-- Your lo0 route
                interface [ ge-0/0/0.0 lo0.0 ]; <-- You can
alternatively give a list of interfaces
            }
            then accept; <-- Accept the matched routes
        }
        term others {
            then reject; <-- Reject any other routes in the forwarding
table
        }
    }
}

The bits beginning '<--' are my comments, and are not part of the
config. You can specify either route filters, or interfaces (or other
options about the routes you are interested in).

Hope this helps

Michael
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

______________________________________________________________________
This inbound email has been scanned by the MessageLabs Email Security
System.
______________________________________________________________________


Confidentiality Notice: This e-mail, including all attachments is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited unless specifically provided under the New Mexico Inspection of Public Records Act. If you are not the intended recipient, please contact the sender and destroy all copies of this message. -- This email has been scanned by the Sybari - Antigen Email System.