The script is being generated.
Bu the result is :

By Jason W.

OID VIEW Web Information

ciscoBgp4MIB	1.3.6.1.4.1.9.9.187
ciscoBgp4NotifyPrefix	1.3.6.1.4.1.9.9.187.0
cbgpFsmStateChange	1.3.6.1.4.1.9.9.187.0.1
cbgpBackwardTransition	1.3.6.1.4.1.9.9.187.0.2
cbgpPrefixThresholdExceeded	1.3.6.1.4.1.9.9.187.0.3
cbgpPrefixThresholdClear	1.3.6.1.4.1.9.9.187.0.4
ciscoBgp4MIBObjects	1.3.6.1.4.1.9.9.187.1
cbgpRoute	1.3.6.1.4.1.9.9.187.1.1
cbgpRouteTable	1.3.6.1.4.1.9.9.187.1.1.1
cbgpRouteEntry	1.3.6.1.4.1.9.9.187.1.1.1.1
cbgpRouteAfi	1.3.6.1.4.1.9.9.187.1.1.1.1.1
cbgpRouteMedPresent	1.3.6.1.4.1.9.9.187.1.1.1.1.10
cbgpRouteMultiExitDisc	1.3.6.1.4.1.9.9.187.1.1.1.1.11
cbgpRouteLocalPrefPresent	1.3.6.1.4.1.9.9.187.1.1.1.1.12
cbgpRouteLocalPref	1.3.6.1.4.1.9.9.187.1.1.1.1.13
cbgpRouteAtomicAggregate	1.3.6.1.4.1.9.9.187.1.1.1.1.14
cbgpRouteAggregatorAS	1.3.6.1.4.1.9.9.187.1.1.1.1.15
cbgpRouteAggregatorAddrType	1.3.6.1.4.1.9.9.187.1.1.1.1.16
cbgpRouteAggregatorAddr	1.3.6.1.4.1.9.9.187.1.1.1.1.17
cbgpRouteBest	1.3.6.1.4.1.9.9.187.1.1.1.1.18
cbgpRouteUnknownAttr	1.3.6.1.4.1.9.9.187.1.1.1.1.19
cbgpRouteSafi	1.3.6.1.4.1.9.9.187.1.1.1.1.2
cbgpRoutePeerType	1.3.6.1.4.1.9.9.187.1.1.1.1.3
cbgpRoutePeer	1.3.6.1.4.1.9.9.187.1.1.1.1.4
cbgpRouteAddrPrefix	1.3.6.1.4.1.9.9.187.1.1.1.1.5
cbgpRouteAddrPrefixLen	1.3.6.1.4.1.9.9.187.1.1.1.1.6
cbgpRouteOrigin	1.3.6.1.4.1.9.9.187.1.1.1.1.7
cbgpRouteASPathSegment	1.3.6.1.4.1.9.9.187.1.1.1.1.8
cbgpRouteNextHop	1.3.6.1.4.1.9.9.187.1.1.1.1.9
cbgpPeer	1.3.6.1.4.1.9.9.187.1.2
cbgpPeerTable	1.3.6.1.4.1.9.9.187.1.2.1
cbgpPeerEntry	1.3.6.1.4.1.9.9.187.1.2.1.1
cbgpPeerPrefixAccepted	1.3.6.1.4.1.9.9.187.1.2.1.1.1
cbgpPeerPrefixDenied	1.3.6.1.4.1.9.9.187.1.2.1.1.2
cbgpPeerPrefixLimit	1.3.6.1.4.1.9.9.187.1.2.1.1.3
cbgpPeerPrefixAdvertised	1.3.6.1.4.1.9.9.187.1.2.1.1.4
cbgpPeerPrefixSuppressed	1.3.6.1.4.1.9.9.187.1.2.1.1.5
cbgpPeerPrefixWithdrawn	1.3.6.1.4.1.9.9.187.1.2.1.1.6
cbgpPeerLastErrorTxt	1.3.6.1.4.1.9.9.187.1.2.1.1.7
cbgpPeerPrevState	1.3.6.1.4.1.9.9.187.1.2.1.1.8
cbgpPeerCapsTable	1.3.6.1.4.1.9.9.187.1.2.2
cbgpPeerCapsEntry	1.3.6.1.4.1.9.9.187.1.2.2.1
cbgpPeerCapCode	1.3.6.1.4.1.9.9.187.1.2.2.1.1
cbgpPeerCapIndex	1.3.6.1.4.1.9.9.187.1.2.2.1.2
cbgpPeerCapValue	1.3.6.1.4.1.9.9.187.1.2.2.1.3
cbgpPeerAddrFamilyTable	1.3.6.1.4.1.9.9.187.1.2.3
cbgpPeerAddrFamilyEntry	1.3.6.1.4.1.9.9.187.1.2.3.1
cbgpPeerAddrFamilyAfi	1.3.6.1.4.1.9.9.187.1.2.3.1.1
cbgpPeerAddrFamilySafi	1.3.6.1.4.1.9.9.187.1.2.3.1.2
cbgpPeerAddrFamilyName	1.3.6.1.4.1.9.9.187.1.2.3.1.3
cbgpPeerAddrFamilyPrefixTable	1.3.6.1.4.1.9.9.187.1.2.4
cbgpPeerAddrFamilyPrefixEntry	1.3.6.1.4.1.9.9.187.1.2.4.1
cbgpPeerAcceptedPrefixes	1.3.6.1.4.1.9.9.187.1.2.4.1.1
cbgpPeerDeniedPrefixes	1.3.6.1.4.1.9.9.187.1.2.4.1.2
cbgpPeerPrefixAdminLimit	1.3.6.1.4.1.9.9.187.1.2.4.1.3
cbgpPeerPrefixThreshold	1.3.6.1.4.1.9.9.187.1.2.4.1.4
cbgpPeerPrefixClearThreshold	1.3.6.1.4.1.9.9.187.1.2.4.1.5
cbgpPeerAdvertisedPrefixes	1.3.6.1.4.1.9.9.187.1.2.4.1.6
cbgpPeerSuppressedPrefixes	1.3.6.1.4.1.9.9.187.1.2.4.1.7
cbgpPeerWithdrawnPrefixes	1.3.6.1.4.1.9.9.187.1.2.4.1.8
ciscoBgp4NotificationPrefix	1.3.6.1.4.1.9.9.187.2
ciscoBgp4MIBConformance	1.3.6.1.4.1.9.9.187.3
ciscoBgp4MIBCompliances	1.3.6.1.4.1.9.9.187.3.1
ciscoBgp4MIBCompliance	1.3.6.1.4.1.9.9.187.3.1.1
ciscoBgp4MIBComplianceRev1	1.3.6.1.4.1.9.9.187.3.1.2
ciscoBgp4MIBComplianceRev2	1.3.6.1.4.1.9.9.187.3.1.3
ciscoBgp4MIBGroups	1.3.6.1.4.1.9.9.187.3.2
ciscoBgp4RouteGroup	1.3.6.1.4.1.9.9.187.3.2.1
ciscoBgp4PeerGroup	1.3.6.1.4.1.9.9.187.3.2.2
ciscoBgp4NotificationsGroup	1.3.6.1.4.1.9.9.187.3.2.3
ciscoBgp4PeerGroup1	1.3.6.1.4.1.9.9.187.3.2.4
ciscoBgp4NotificationsGroup1	1.3.6.1.4.1.9.9.187.3.2.5

Activate / Deactivate Command is more like disabling / enabling configuration in JunOS.
The purpose is just to keep the setting / configuration by disabling / deactivating it.
Once you need to activate just one step to do

Drawback is keeping more config file size.
For small config changes is fine to have.

Here the steps example deactivating a term in a policy option - policy statement named “IMPORT-PCCW”

Steps :
===================================================
admin@junOS# deactivate term prefered-outgoing

[edit policy-options policy-statement IMPORT-PCCW]
admin@junOS# show
inactive: term prefered-outgoing {
from as-path PACNET;
then {
local-preference 6200;
accept;
}
}
term else {
from as-path ALL ;
then reject;
}

[edit policy-options policy-statement IMPORT-PCCW]

admin@junOS# commit
commit complete

[edit policy-options policy-statement IMPORT-PCCW]
====================================================

The Effect :

a. Before :

admin@junOS# run show bgp summary
Groups: 11 Peers: 13 Down peers: 4
Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
inet.0            926409     313202          0          0          0          3
Peer               AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Damped…
xxx.yyy.ddd.aaa     ABCD     349732    19848       0       0  6d 21:04:56    40/300121/0          0/0/0

b. After :

admin@junOS# run show bgp summary
Groups: 11 Peers: 13 Down peers: 4
Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
inet.0            926409     313202          0          0          0          3
Peer               AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Damped…
xxx.yyy.ddd.aaa   ABCD     349732    19848       0       0  6d 21:04:56    0/300123/0          0/0/0

– Daily Juniper Simple Notes
– a. rahman isnaini r.sutan

For a cheap IPv6 Solution using an OpenSource Router Engine.

BGP6 Configuration:
a. Remove default BGP ASN & Set Yours.
bgpd# configure terminal
bgpd(config)#no router bgp 7675
bgpd(config)# router bgp 100
bgpd#

b. Set Prefix-List for Filtering for Outgoing & Incoming IPv6 routes from/to Upstreams:

bgpd# conf t
bgpd(config)# ipv6 prefix-list IPv6-UPSTREAM-IN description ALLOW-IPv6-/32-LESS-ONLY
bgpd(config)# ipv6 prefix-list IPv6-UPSTREAM-IN seq 10 permit ::/0 le 32
bgpd(config)# ipv6 prefix-list IPv6-UPSTREAM-OUT seq 10 permit 2402:ac00::/32
bgpd(config)# ipv6 prefix-list IPv6-UPSTREAM-OUT seq 100 deny ::/0 le 128
bgpd(config)# end
bgpd#

c. Set Policy for Incoming/Outgoing IPv6 Routes

bgpd# conf t
bgpd(config)#
bgpd(config)# route-map IPv6-UP1-IN permit 10
bgpd(config-route-map)# match ipv6 address prefix-list IPv6-UPSTREAM-IN
bgpd(config-route-map)#end
bgpd(config)#
bgpd(config)# route-map IPv6-UP1-OUT permit 10
bgpd(config-route-map)# match ipv6 address prefix-list IPv6-UPSTREAM-OUT
bgpd(config-route-map)#end
bgpd(config)#
bgpd(config)# route-map IPv6-UP2-IN permit 10
bgpd(config-route-map)# match ipv6 address prefix-list IPv6-UPSTREAM-IN
bgpd(config-route-map)#end
bgpd(config)#
bgpd(config)# route-map IPv6-UP2-OUT permit 10
bgpd(config-route-map)# match ipv6 address prefix-list IPv6-UPSTREAM-OUT
bgpd(config-route-map)#end
bgpd(config)#

d. Set BGP6 Neighbors to Upstream 1 & Upstream 2:

bgpd(config)#router bgp 100
bgpd(config-router)# address-family ipv6
bgpd(config-router-af)#neighbor 2404:170:251::a:a:15 activate
bgpd(config-router-af)# neighbor 2404:170:251::a:a:15 remote-as 150
bgpd(config-router-af)#neighbor 2404:170:251::a:a:15 route-map IPv6-USPTREAM-IN in
bgpd(config-router-af)#neighbor 2404:170:251::a:a:15 route-map IPv6-UPSTREAM-OUT out
bgpd(config-router-af)#network 2402:ac00::/32
bgpd(config-router-af)#neighbor 2402:DC60:251::a:a:15 activate
bgpd(config-router-af)# neighbor 2402:DC60:251::a:a:15 remote-as 200
bgpd(config-router-af)#neighbor 2402:DC60:251::a:a:15 route-map IPv6-USPTREAM-IN in
bgpd(config-router-af)#neighbor 2402:DC60:251::a:a:15 route-map IPv6-UPSTREAM-OUT out
bgpd(config-router-af)#network 2402:ac00::/32
bgpd(config-router-af)#end
bgpd#

e. Check Your BGP connections:

bgpd# sh bgp summary
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
2404:170:251::a:a:15
4 150 927 17 0 0 0 00:00:01 4
2402:DC0:251::a:a:15
4 200 927 17 0 0 0 00:00:01 3
Total number of neighbors 2

f. Cross Check Your Prefix on Your Upstream:

Upstream1#show bgp ipv6 neighbors 2404:170:251::A:A:16 routes
BGP table version is 3185444, local router ID is 202.53.251.195
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 2402:AC00::/32 2404:170:251::A:A:16 0 0 200 i

Upstream1#show bgp ipv6 neighbors 2402:DC60:251::A:A:16 routes
BGP table version is 7745271, local router ID is 118.91.224.100
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 2402:AC00::/32 2402:DC60:251::A:A:16 0 0 200 i

rgs
a. rahman isnaini r.sutan

Your Interface :
==========

admin@JunOS#show
description ***TO-BGP-PEER***;
vlan-id 8;
family inet6 {
address 2404:170:251::A:A:1A/126;
}
[edit interfaces ge-1/3/0 unit 8]

The Command : refer to http://www.ip-stories.com/

BGP Setting :
=========

admin@JunOS#show
type external;
neighbor 2404:170:251::A:A:19 {
description CUSTOMER-IPV6;
import IPv6-CUSTOMER-IMPORT;
export IPv6-CUSTOMER-EXPORT;
peer-as 3940;
}

[edit protocols bgp group eBGP-IPv6]

The command :
admin@JunOS# set type external [different ASN]
admin@JunOS# set neighbor 2404:170:251::A:A:19 import IPv6-CUSTOMER-IMPORT export IPv6-CUSTOMER-EXPORT peer-as 3940
admin@JunOS# commit

Policy Setting :
==========

admin@JunOS#
policy-statement IPv6-CUSTOMER-IMPORT {
from as-path ALL;
then accept;
}
policy-statement IPv6-CUSTOMER-EXPORT {
from as-path ALL;
then reject;
}

as-path ALL .*

[edit policy-options]

The command :

admin@JunOS# set policy-statement IPv6-CUSTOMER-IMPORT from as-path ALL

[edit policy-options]
admin@JunOS# set policy-statement IPv6-CUSTOMER-IMPORT then accept

[edit policy-options]
admin@JunOS# set policy-statement IPv6-CUSTOMER-EXPORT from as-path ALL

[edit policy-options]
admin@JunOS# set policy-statement IPv6-CUSTOMER-EXPORT then reject
admin@JunOS# set as-path ALL .*
admin@JunOS# commit

BGP Status :
========

admin@JunOS# run show bgp summary
Groups: 17 Peers: 18 Down peers: 4
Table          Tot Paths  Act Paths Suppressed    History Damp State    Pending
inet.0           1206977     309046          0          0          0          0
inet6.0             2416       2414          0          0          0          0
Peer               AS      InPkt     OutPkt    OutQ   Flaps Last Up/Dwn State|#Active/Received/Damped…
2404:170:251::a:a:19  9340       1897          6       0       0        1:31 Establ
inet6.0: 2414/2416/0

a. rahman isnaini r.sutan

route-server>show bgp ipv6  unicast 2402:ac00::/32
BGP routing table entry for 2402:AC00::/32, version 519345
Paths: (1 available, best #1, table Global-IPv6-Table)
Not advertised to any peer
13645 19151 6939 45147 9340 45729
2001:5B8:FFFF::8 from 2001:5B8:FFFF::8 (64.135.0.1)
Origin IGP, localpref 100, valid, external, best
Community: 13645:3121

Special Thanks to Pak Yudha APJII Hostmaster
Aladi Saputra &  Ebenz Sarbeni.

by
a. rahman isnaini r.sutan

If you are [used to] so familiar with CISCO .IlI..IlI. [Purchase "Used & Refurbished" Cisco]
And it always hard to find the online JunOS documentation sometimes
Next-Hop Self command was one of them.

Anyway directly I’d like to tell that you WILL NEVER found this next-hop self command in BGP configuration of M Series.
It’s located under a term of a Policy Statement as a choice of action to be taken after “THEN”.
Here :

admin@JunOS# set term policy-options policy-statement LINK-1-EXPORT term PREFIX-1 then next-hop self

Here the policy-statement LINK-1-EXPORT looks like :

admin@JunOS# show
term PREFIX-1 {
from {
prefix-list PREFIX-NETWORK-A;
}
then {
local-preference 5000;
next-hop self;
accept;
}
}
term ISP-D {
from {
as-path ISP-D;
}
then {
local-preference 5000;
next-hop self;
accept;
}
}
term else {
then reject;
}

This kind of configuration is very useful two load balance routes/prefixes volume between two routers which connected by two non-equal link using iBGP.
Why ? it might happened these ways :

- You have announced separated prefixes over this two links [bgp session].
- You might have configured local-preference to have some prefixes to pass first link and others to the second link.
- The traffic would only fill one link ?.
- You have to announce each of prefix next-hops to the right link ?

It’s all waste of your time.
Just do as a Simple of above configuration, you will have your traffic fills both link follows the number of announced prefixes.

.
== BEFORE ===
admin@JunOS2> show route 192.168.250.0

192.168.250.0/23    *[BGP/170] 00:00:01, MED 0, localpref 2500, from 10.172.224.100
AS path: 4390 I
> to 10.172.224.113 via fe-1/1/2.0
[BGP/170] 03:06:29, MED 0, localpref 100
AS path: 4390 I
> to 10.172.224.113 via fe-1/1/2.0

admin@JunOS2> show route 192.168.250.0

192.168.250.0/23    *[BGP/170] 00:00:01, MED 0, localpref 2500, from 10.172.224.100
AS path: 4390 I
> to 10.172.224.113 via fe-1/1/2.0
[BGP/170] 03:06:29, MED 0, localpref 100
AS path: 4390 I
> to 10.172.224.113 via fe-1/1/2.0

admin@JunOS2> show route 192.168.250.0

192.168.250.0/23    *[BGP/170] 00:00:01, MED 0, localpref 2500, from 10.172.224.100
AS path: 4390 I
> to 10.172.224.113 via fe-1/1/2.0
[BGP/170] 03:06:29, MED 0, localpref 100
AS path: 4390 I
> to 10.172.224.113 via fe-1/1/2.0

== AFTER ===
admin@JunOS2> show route 192.168.250.0

192.168.250.0/23    *[BGP/170] 00:00:01, MED 0, localpref 2500, from 10.172.224.100
AS path: 4390 I
> to 10.172.224.109 via fe-1/1/1.0
[BGP/170] 03:06:29, MED 0, localpref 100
AS path: 4390 I
> to 10.172.224.113 via fe-1/1/2.0

a. rahman isnaini r.sutan

admin@junOS# run show route advertising-protocol bgp 192.168.188.169

inet.0: 302188 destinations, 1452821 routes (301467 active, 0 holddown, 1146073 hidden)
Prefix                  Nexthop              MED     Lclpref    AS path
* 0.0.0.0/0               Self                                    I

Sometimes customers are running their layer 3 processing on a lack resources hardware.
And multihoming is also a good choise.
Therefor they need only an injected default via BGP connection as a primary outgoing with one their upstream and have a higher metric static default route with others.

Here what I have simply done :

1. Ensure that you have 0.0.0.0/0 in your routing table
admin@junOS#show route 0.0.0.0/0

2. Set Prefix List named [whatever] default-route 0.0.0.0/0
3. Set as-path ALL .*
4. Set your bgp export policy to customer with the first term allow this prefix only
5. Set your bgp export policy to customer with the second term deny all.

The command :

admin@junOS#edit policy-options
admin@junOS#set prefix-list default-route 0.0.0.0/0
admin@junOS#set as-path ALL .*
admin@junOS#set policy-statement EXPORT-USER term 1 from prefix-list default-route
admin@junOS#set policy-statement EXPORT-USER term 1 then accept
admin@junOS#set policy-statement EXPORT-USER term 2 from as-path ALL
admin@junOS#set policy-statement EXPORT-USER term 1 then reject
admin@junOS#commit

admin@junOS# run show route advertising-protocol bgp 192.168.188.169

inet.0: 302188 destinations, 1452821 routes (301467 active, 0 holddown, 1146073 hidden)
Prefix                  Nexthop              MED     Lclpref    AS path
* 0.0.0.0/0               Self

a. rahman isnaini r.sutan / ervin a. taufik
also thanks to Rommy Kuntoro [CBN People] for different successful solution.

term 2
{ from
{ route-filter 0.0.0.0/0 exact; }
then accept; }

=======================
Juniper Config Manager [Here..]
=======================

Been long time googling finding out weight attribute in Juniper.
I completely forgot BGP Weight attribute is Cisco proprietary (reminded by my friend in My FaceBook, Carlos).
So this attribute will not be available in JunOS.

Honestly really hoping that  Juniper can have similar proprietary ‘like’ weight attribute in cisco, since so far it’s really useful controlling of Outgoing BGP Traffic among iBGP speakers.

What we can set are :

accept               Accept a route
+ apply-groups         Groups from which to inherit configuration data
+ apply-groups-except  Don’t inherit configuration data from these groups
> as-path-expand       Prepend AS numbers prior to adding local-as (BGP only)
as-path-prepend      Prepend AS numbers to an AS path (BGP only)
class                Set class-of-service parameters
> color                Color (preference) value
> color2               Color (preference) value 2
> community            BGP community properties associated with a route
cos-next-hop-map     Set CoS-based next-hop map in forwarding table
damping              Define BGP route flap damping parameters
default-action       Set default policy action
destination-class    Set destination class in forwarding table
> external             External route
forwarding-class     Set source or destination class in forwarding table
> install-nexthop      Choose the next hop to be used for forwarding
> load-balance         Type of load balancing in forwarding table
> local-preference     Local preference associated with a route
> metric               Metric value
> metric2              Metric value 2
> metric3              Metric value 3
> metric4              Metric value 4
next                 Skip to next policy or term
> next-hop             Set the address of the next-hop router
origin               BGP path origin
> preference           Preference value
> preference2          Preference value 2
reject               Reject a route
source-class         Set source class in forwarding table
> tag                  Tag string
> tag2                 Tag string 2
trace                Log matches to a trace file

Till this time, local-preference is always used and of course no luck with prepend among iBGP speakers since local-preference is prefered.

a. rahman isnaini r.sutan

Today I’ve tried to set both allow prefix & as-path to match in the same term of a BGP Policy for Advertisement purpose.
It doesn’t work
Checking “sh route advertising-protocol bgp 192.168.10.2″ was completely empty !

Changing & creating new different term for each prefix macth & as-path match worked fine.
Also matching more prefixes in prefixes term will work as well and similar thing to as-paths.

a. Before

policy-statement UPSTREAM-EXPORT {
term prefix-all {
from {
as-path ISP-B;
prefix-list MY-ISP;
}
term else {
from as-path ALL;
then reject;
}
}

b. after

policy-statement UPSTREAM-EXPORT {
term prefix-myisp {
from {
prefix-list MY-ISP;
}
then accept;
}
term isp-transit {
from as-path ISP-B;
then accept;
}
term else {
from as-path ALL;
then reject;
}
}

a. rahman isnaini r.sutan