Figure 13: Prefixes Originating In An As - Juniper BGP - CONFIGURATION GUIDE V 11.1.X Configuration Manual

Figure 13: Prefixes Originating in an AS

The following commands configure router NY:
The following commands configure router Boston:
Notice that a mask was not specified for the prefix originating with router Boston.
The natural mask is assumed for networks without a mask.
The following commands configure router LA:
network
host1(config)#router bgp 300
host1(config-router)#neighbor 10.2.25.1 remote-as 100
host1(config-router)#neighbor 10.4.4.1 remote-as 400
host1(config-router)#network 192.168.33.0 mask 255.255.255.0
host2(config)#router bgp 100
host2(config-router)#neighbor 10.2.25.2 remote-as 300
host2(config-router)#neighbor 10.3.3.1 remote-as 400
host2(config-router)#network 172.19.0.0
host3(config)#router bgp 400
host3(config-router)#neighbor 10.3.3.2 remote-as 100
host3(config-router)#neighbor 10.4.4.2 remote-as 300
host3(config-router)#network 172.28.8.0 mask 255.255.248.0
Use to specify the prefixes in its AS that the BGP speaker advertises.
BGP advertises the specified prefix only if a non-BGP route to the prefix exists
in the IP forwarding table. If the non-BGP route does not exist when you issue
the network command, then BGP is notified as soon as the route becomes
available in the IP routing table or IP tunnel routing table.
For IPv4 addressing, specify a network-number and an optional network-mask.
For IPv6 addressing, specify the IPv6 prefix.
You can specify a route map to filter network routes or modify their path
attributes.
The default weight for network routes is 32768; use the weight keyword to
modify the weight in the range 0–65535.
Chapter 1: Configuring BGP Routing
Advertising Routes
51